Afternoon users of FreeCAD for WINDOWS!
I have had some frustration (lack of knowledge with too many try and fail attempts) with regard to building FreeCAD from source using the available libpacks. To provide more detail, I can say the actual compiling succeeds without issue. It has been the provision of dependencies for the new build that has been the source of mild agitation (rage... lol
Anyhow, after a number of searches on the forum for 'Access Violation' errors and other issues, I think the most recent finding, FreeCAD debug build with apeltauer's libpack builds release instead
, mentioned by @wmayer has been the "bread of life" to my FreeCAD builds. So far, I have had success with building and running FreeCAD from source on Windows with MSVS Community 2017 and the libpacks by @Apeltaeur.
So, instead of adding a .bat file to the source distribution or the libpack, I thought how about mods to the CMakeLists.txt file. After all, that is the best place, yes? I added code to copy the required dependency folders from the libpack to the build folder, with checks and user options included.
Please check out my GH branch, CMake
, for the one file changed - CMakeLists.txt. These changes are unique to the existing PR #2080 - Some minor CMake improvements
. Some of the formatting issues addressed in that PR I have included in my changes.
Please review: . . . PR #2160 - Windows: Add libpack dependency install support
UPDATE: 2019-05-08 1828 CST
This PR closed so I can clean up the commit list that was included. @Mlampert is assisting me with the task. I'll re-submit a new PR when I finish the process.
UPDATE: 2019-05-11 1350 CST
The PR has been resubmitted and improved. Please review. Local testing on Windows 10 x64 machine yields intended results. Some new options are carried out during CMake configure and generation. The install changes affect the INSTALL
project output when you run it after a successful ALL_BUILD