sgrogan wrote:Thanks NormandC! I'm a little intimidated by this. I was able to upgrade to OCCT 7.0 on win, but broke netgen, it's still not fixed.
I would like to start with OCCT packaging, then migrate the PPA over it first, if it doesn't bring conflicts with the existing libraries. I'll build a local package with pbuilder and validate first. As agreed previously OCCT would not be compiled against VTK, but TBB would be enabled. A visualization package not relying on VTK would be created, but FreeCAD would not depend on it.
Then move on to netgen, vtk7, med, etc.
sgrogan wrote:What can I do to help?
I still suck at Git. Here's what I have in mind, the two first points I can do on my own but not the following ones...
- git clone https://git.launchpad.net/~freecad-main ... +git/OCCT7 (easy enough that one I can do on my own)
- create a new branch, let's call it the occt710 branch (can do)
- import the OCCT7.1.0 tarball in it
- merge the occt710 branch to master - actually not sure it would be a merge, since it basically needs to overwrite the current master?
- push the occt710 branch and the new master to Launchpad
My basic idea is that our Launchpad OCCT git repo, while it would be devoid of the original git history, would have one of its own so we could go back a commit for 7.0.0, for example.
Or maybe that's unnecessary? Would it be simpler to clone the repo, delete everything in my local branch, extract the 7.1.0 tarball in it, commit then push to Launchpad? Could it be as simple?
blacey wrote:For those not on Gitter, you can apply netgen nglib patch set for OCCT 7.x as follows:
The problem is applying such a patch to a Debian package. Or maybe we stop
trying to follow the Debian rule book, patch the source before packaging it (heresy!!!) and that is that.
Please tell me: nglib is part of netgen, right?