Which files exactly are you talking about? Do you mean all the .h, .lib, .dll, .pdb, ... files?Can we therefore please put the LibPack-specific files directly to the FreeCAD GitHub?
Having trouble installing or compiling FreeCAD? Get help here.
In my opinion only:
- all *.cmake files since the are specific to the LibPack and define in what folder one has to put in what 3rd-party files
- a base textfile describing the structure of the LibPack (where to find what and what to do if a 3rd-party component should be updated)
Some of us would love to know how the FreecadLibs are build from their sources especially the various patches that are applied to these sources. But until now is like this has been hidden from us for a long time. Please let us know.
I think that even those who have created a Libpack would like to know
As far as I know only 4 people have created a Libpack from scratch in the history of the project.
I've had mixed success updating or adding dependencies.
QT is hard and long to compile so I think you need to start with the official QT binaries (release and Debug) and then build up from there.
The structure of the Libpack is to run the install project of the dependent lib.
A recent discussion is here: https://forum.freecadweb.org/viewtopic.php?f=4&t=34708
There is no cookbook. Download or build a library, add another, solve conflicts, rinse, wash, repeat.
I'd love to have a 32 bit Win Libpack, just with release libs. Maybe as a community we could try to reproduce apeltauer's 64 bit Libpack in 32 bit and learn. I've failed miserably trying myself.
"fight the good fight"
Who is online
Users browsing this forum: Google [Bot] and 4 guests