GSoC '18: CM Project Thread

[ickby]

Hello Kurt,

A silly question: are you sure freecad still uses soqt? If I remember correctly we switched the 3d view to use quarter instead of soqt a few years back. So it may not be needed anymore.

[yorik]

I think ickby is right.. only Coin and quarter are used in FreeCAD now

[Jee-Bee]

but @looo is is talking about soqt sometimes

[looo]

- I looked into and got started with the packaging for pivy and soqt. I was less familiar with these parts of FreeCAD as evidenced by the fact I forgot to include them in the first place. Since we already have a github.com/freecad/pivy we should get an official one for soqt as well. Both then will need a tagged release to help make our fork more official. We are the only thing reverse-depending on soqt and pivy in Debian that I can find.

Lorenz would it be possible for you to do the tagging and move your soqt fork into github.com/freecad?

ideally people developing coin would do this on bitbucket... As a workaround you can maybe use this sources:
https://github.com/conda-forge/staged-r ... a76d7dceR7

The soqt recipe for conda-forge never got accepted because I didn't use any official sources. But the problem is that bitbucket doesn't allow to download an archive from a commit with all submodules... I guess the workaround to add sources to the pivy release isn't that bad. I will add a new pivy release with all the needed coin sources in the next days.

A silly question: are you sure freecad still uses soqt? If I remember correctly we switched the 3d view to use quarter instead of soqt a few years back. So it may not be needed anymore.

I think ickby is right.. only Coin and quarter are used in FreeCAD now

You are absolutely right. But pivy always shipped soqt, and I don't want to remove the soqt-support in pivy. Actually quite some problems of pivy with python3 were found with the soqt interface. So dropping soqt support in pivy will also have negative impact on freecad.

[looo]

I made a new release for pivy: https://github.com/FreeCAD/pivy/releases/tag/0.6.4 . The soqt version available in this release is from todays soqt-master (1.6.0.a 08.07.18). I currently test this source for linux/win/osx 64 bit here:
https://github.com/conda-forge/staged-recipes/pull/5307

For the coin sources I use a specific commit. you can get the source with:
https://bitbucket.org/Coin3D/coin/get/{{ commit }}.tar.gz

[kkremitzki]

I made a new release for pivy: https://github.com/FreeCAD/pivy/releases/tag/0.6.4 . The soqt version available in this release is from todays soqt-master (1.6.0.a 08.07.18). I currently test this source for linux/win/osx 64 bit here:
https://github.com/conda-forge/staged-recipes/pull/5307

For the coin sources I use a specific commit. you can get the source with:
https://bitbucket.org/Coin3D/coin/get/{{ commit }}.tar.gz

Great, thanks! It now builds in a very clean way (cloning from salsa.debian.org/science-team/pivy and then pointing debian/watch at github.com/freecad/pivy, running gbp import-orig --uscan to pull in the update and adding an override in debian/rules to move to setup_old.py to setup.py) however the normal way to get both python 2 and 3 binaries from one source package, is not working atm, in that it doesn't actually produce the python 3 files for some reason.

[looo]

yes using existing coin and soqt (qt4) should work with the setup_old.py script. If you can't depent on qt4, simple removing the soqt dependency from pivy should also work. But as I said, this is the "We don't care about our dependency way". I guess there are some people using pivy with soqt, and those are then not able to use the updated pivy-package.
So if you find some time to get soqt and coin packaged (with new cmake configuration) it would be nice to have them available as debian packages. At least you should mention your ambitions regarding pivy in the coin-mailinglist. I guess they have also interest in debian packages and can help a lot. (But this mailinglist is not as responsive as the FreeCAD-forum...)

[kkremitzki]

There is a coin3 4.0.0~cmake already in Debian experimental but it looks like it's too old to work, but that means the skeleton is already there for updating it.

As for pivy, originally I had the python2 build working with very little effort. When I tried to specify only building python3, I got a bunch of errors about 'PyString_AsStringAndSize', 'PyString_FromStringAndSize', 'PyFile_AsFile', 'PyFile_Check' being undefined in this scope, i.e. PY2 was being set incorrectly for some reason. And then when I was able to get both building at the same time, the python3 package worked, but the python2 package failed on a bunch of errors like 'PyUnicode_AsUTF8' not being defined, i.e. PY2 wasn't being set! Argh! Almost there, though.

As for good news, I now have ready:

- a FreeCAD 0.17 for experimental (unfortunately qtwebkit-dev is required to build the Gui module, even turning off BUILD_WEB and BUILD_START doesn't help, so this package would require a patch to be accepted into unstable, or PySide 2's release so we can complete the Qt 5 port)
- gmsh with OCCT 7.2 support, and new Python 3 bindings package available (Python 2 already available)
- Netgen 6.2.1804 package also built against OCCT 7.2 and with new Python 3 bindings package available (I couldn't get Python 2 & 3 build simultaneously and deemed it low priority)
- My OCCT repo got moved to https://salsa.debian.org/science-team/opencascade, and OCCT 7.3 is now available there, although it still needs some symbols files porting before being available in experimental. Tobias Frost, the Debian developer who offered to co-maintain the package, beat me to having a usable import.

I am definitely missing having vejmarie's 32-core, 128GB RAM machines available for compilation, as right now my "dev environment" is beyond messy and scattered across 6 VMs on 5 physical machines. I'll probably spend a good chunk of tomorrow just cleaning everything up so I can push the aforementioned stuff.

P.S. As soon as python3-pivy is available, doesn't that mean we can have an experimental FreeCAD Python 3 package, i.e. it isn't blocked by PySide 2 not being packaged? If that's the case, we are maybe a week or 2 away from a possible `sudo apt install freecad-python3`!

[NormandC]

Hi Kurt,

These are really good news.

This may be relevant to OCCT 7.3 packaging: https://forum.freecadweb.org/viewtopic. ... 03#p238303

[kkremitzki]

Hi Kurt,

These are really good news.

This may be relevant to OCCT 7.3 packaging: https://forum.freecadweb.org/viewtopic. ... 03#p238303

Indeed it is, I can add a patch to comment out those lines.