Libpack 12.5.4 for Windows VS2019, Qt5.15, Python3.8, OCC7.5.3
The description in GitHub is:
FreeCAD LibPack Version 12.5.4 debug/release with
Visual Studio 2019
OpenSSL 3.0.0
LibSSL 1.1.1l
Curl
Qt 5.15.2
PySide2 build against Qt 5.15
Coin3D 4.0
Pivy
Python 3.8
OpenCascade 7.5.3 with Fillet fix from https://gitlab.com/blobfish/occt provided by Chris Hennes
Boost 1.67 (including the debug files build against python_d.exe)
I don't know what else to tell you. If you can point me to some other useful information I'll go hunt it down.
FREECAD_COPY_DEPEND_DIRS_TO_BUILD Copies depending libraries needed to execute the FreeCAD.exe to the build folder. See also section Running and installing FreeCAD.
Note: the options FREECAD_COPY_XXX only appear if the libraries were not already copied. So when you change to another LibPack version, it is important to delete all folders in your build folder, except of the LibPack folder. In CMake delete the cache and start as if you compile for the first time and you will get the FREECAD_COPY_XXX options. OFF
FREECAD_COPY_LIBPACK_BIN_TO_BUILD Copies the LibPack binaries needed to execute the FreeCAD.exe to the build folder. See also section Running and installing FreeCAD. OFF
FREECAD_COPY_PLUGINS_BIN_TO_BUILD
I always start with a completely new build folder and a completely fresh copy of everything. I have tried re-using various short-cuts and overwrites and I always take more time to fix leftover garbage than to spend the 2 minutes extra to do a clean build. In particular CMake seems to bury a number of ini-type files that can cause problems.
If someone is trying to build-debug-build-debug, etc it might be different, but for just an ordinary build intended to be used, and not further developed, go for clean.
falviani wrote: ↑Thu Jan 20, 2022 8:24 pm
I went to the given link and downloaded the file. Rebuilding with the new libpack gave the same errors and warnings.
What else could I be doing wrong?
I recommend to use the sources of the older netgen you used once to build with OCC 7.3 and rebuild it using OCC 7.4. The build failures of the netgen plugin is not because of API changes of OCC but of the newer netgen version. There e.g. the class OCCRefinementSurfaces has been removed and some global variables have become class variables.
akimfidz wrote: ↑Fri Jan 28, 2022 7:32 am
I recommend to use the sources of the older netgen you used once to build with OCC 7.3 and rebuild it using OCC 7.4.
What are you talking about? Where do you see Netgen build failures?
Note that we freeze in FreeCAD the Netgen support to the version that is distributed with the latest LibPack. You cannot use another Netgen version.
So please take the current LibPack as it is and follow strictly https://wiki.freecadweb.org/Compile_on_Windows
and you can build FreeCAD successfully.
Before the next major FreeCAD release we will upgrade to a newer Netgen version and also to OCC 7.6, for now we decided to stay with the Netgen current version
Hi all,
i am working on providing a new libpack with occ 7.6.1.
In this step i also could upgrade netgen. Any suggestion what version is compatible with the current master?
Any other suggestions or wishes can be added to my github issue list (https://github.com/apeltauer/FreeCAD/issues)
apeltauer wrote: ↑Wed Mar 16, 2022 7:16 am
i am working on providing a new libpack with occ 7.6.1.
In this step i also could upgrade netgen. Any suggestion what version is compatible with the current master?
Any other suggestions or wishes can be added to my github issue list (https://github.com/apeltauer/FreeCAD/issues)
Concerning Netgen, I fear we have to act the same as for the 0.19 release: You provide a LibPack and then we need to check how our code needs to be adapted. Then we keep the Netgen version stable for the while lifetime of FC 0.20.
There seems to be some differing standards going on here, Linux platform for FC is supported back to Python 3.6.x and throughout the 0.20 development cycle Win 7 users have been giving valuable feedback. Now at the last minute the intention is to completely disregard them, really bad karma IMHO.