Back port commits to 0.18 branch

[sgrogan]

Thanks, I updated the 0.18 package which is available from conda-forge. Now the question is if we should go with the old (qt5.6) deps or if we should switch to new (qt5.9) deps. On osx qt5.9 is working better.

For win I still have problems with self compiled QT5.9 (because of the boost 1.7) so I used QT5.6
I would suggest using QT5.9. I'll update it when I get it working (I did see your pull request test)

I could also package directly from your win QT5.9 Conda Win build in a new conda env. This might be a good exercise, after this it should be easy to add it to the Travis weekly Conda builds.

[uwestoehr]

To me issue #4017 seems worth to be backported.

I have again a proposal :
I notice that bugs are immediately closed when the fix is in master. I think it would be good to keep them open until the fix was released or at least until it is also backported.
Users affected by a bug might search if it is a known one. If the bug report is closed you won't find it since you search if course for open bugs. So the status "closed" implies it is fixed while for the majority of users (using 0.18.x) it is not - yet.

-

[wandererfan]

To me issue #4017 seems worth to be backported.

Sounds reasonable to me. I'll see if I can figure out how to do it.

[looo]

Thanks, I updated the 0.18 package which is available from conda-forge. Now the question is if we should go with the old (qt5.6) deps or if we should switch to new (qt5.9) deps. On osx qt5.9 is working better.

For win I still have problems with self compiled QT5.9 (because of the boost 1.7) so I used QT5.6
I would suggest using QT5.9. I'll update it when I get it working (I did see your pull request test)

Yes, moving 0.18.3 to qt5.9 looks quite obvious to me. But as said I need come help from @triplus as I have no idea about the upload-scripts.

I could also package directly from your win QT5.9 Conda Win build in a new conda env. This might be a good exercise, after this it should be easy to add it to the Travis weekly Conda builds.

Yes, this would be nice addition.

[sgrogan]

Yes, this would be nice addition.

From which channel do I get the 0.18.3 build?

Yes, moving 0.18.3 to qt5.9 looks quite obvious to me. But as said I need come help from @triplus as I have no idea about the upload-scripts.

When I am successful with Win I will look at this, I need to understand for Win as above.

[sgrogan]

Sounds reasonable to me. I'll see if I can figure out how to do it.

Unfortunately we have published the 0.18.3 tag, so this will be part of 0.18.4.

[kkremitzki]

The stable PPA is updated btw.

[looo]

Yes, this would be nice addition.

From which channel do I get the 0.18.3 build?

Everything should be in conda-forge:

Code: Select all

conda create -n freecad-0.18.3 freecad=0.18.3 -c conda-forge

[sgrogan]

Everything should be in conda-forge:

Thanks, should the WebGui work?

[looo]

Thanks, should the WebGui work?

You are right. Seems like qtwebengine is not supported in 0.18.3. In 0.19 it's automatically detected.

edit: this one is needed: https://github.com/FreeCAD/FreeCAD/comm ... 92a53c7291