Comments from the developer trying to help with the compile:
Quote:
Well to answer the first question, although caliber only ships with those, the source for those libraries references and pulls in other lib files like libxml2.lib.
Which is actually referred to in the directions to setup as a dependencies when setting up new projects.
• Properties -> Linker -> Input -> Additional Dependencies: libxml2.lib
It also talks about this file existing in:
• Properties -> Linker -> General -> Additional Library directories: ~/sw/lib (for libxml2.lib)
That folder doesn’t exists in my world but I found it in a debug folder.
The setup also calls for setting up dependencies to the following libraries:
• Properties|Linker|Input|Additional Dependencies:
libeay32.lib ssleay32.lib libplist.lib libgen.lib libusbmuxd.lib ws2_32.lib
the first two lib files are openSSL libraries that I went and found on the web and downloaded, these were not part of the downloaded code…whether the ones I downloaded are the versions needed or if version matters I have no idea.
These came into play because of another change adding the following preprocessor definitions:
Preprocessor Definitions:
ASN1_STATIC HAVE_OPENSSL __LITTLE_ENDIAN__ _LIB
Adding the highlighted preprocessor definition included code to be compiled which referenced OpenSSL.
And Part of the issue is the solution as downloaded, where everything compiles, is compiling everything as static .LIB library’s. The directions for two of the libraries being compiled have them output to a .DLL. Which makes a difference in the way linking to dependences are done.
|