![]() Placing the following files in Uploadr's components/ directory has allowed life to go on for the moment. The solution, as it stands, is simply to include the C Runtime and its manifest in the distribution. It seems that the static linker can't resolve the duplicate definitions caused by overzealous static linking. When they themselves are statically linked into the XPCOM component later, all hell breaks loose. Both of these libraries will build fine given the /MT flag, which instructs them to statically link the C Runtime. Problem is, they both link the C Runtime themselves by using std::string and such. The image processing component of the Flickr Uploadr links against GraphicsMagick and Exiv2, libraries that do image processing and EXIF/IPTC metadata processing, respectively. ![]() However I've run into a case where I cannot do this (deciding whether this is due to technical limitations or lack of competence is for readers to help me decide). The wisdom of the collective T-Rex ( #xulrunner on ) says that statically linking against the Microsoft C Runtime ( msvcr80.dll and friends) is the way to go. ![]() Manifest (verb): To embed XML describing libraries which are expected to be available at runtime, done in the course of developing software using Microsoft Visual Studio. When you can't statically link, manifest 4 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |