Statically Link Libraries

[pjrinaldi]

For simpler portability, compilation, and to prevent breaking when newer libraries are used than what I compiled against, I will attempt to statically link all the forensic libraries I am using, for instance: libewf, afflib, liblnk, libregf, libfwnt. Currently gonna assume I can do the above for a v0.4 release.

If I get really good at this, I can attempt to statically link qtav, qt, libudev, libzip, libcrypto, and other utility libraries to make an installable runnable binary. (but this might be a later release and will invariably be a new ticket)

[pjrinaldi]

Might not statically link, since it would hurt vulnerability management from the OS to my code, but I’ll play with it and see when I get nearer to an actual 0.4 release

[pjrinaldi]

I don't think i'll statically link for this version, I might play around for another version.

[pjrinaldi]

I have written commented out entries to the project file to test static linking the various forensic libraries i'm using, since changes to what gets pulled down will potentially screw up my program. Will test and see how big the executable is and decide from there, but now I'm leaning towards statically linking some/most of the non standard libraries used.

[pjrinaldi]

tested static link pro file and a slew of other libraries are missing, probably dependencies which were linked with dynamic libraries which are now static, so i need to figure out how to list the libraries they need and then link them in dynamically or statically and try again.

[pjrinaldi]

I statically linked the blake3 library so there is no installation or fudging around with it, it's small and works well with wombathasher testing so it should work here as well.