cd<\/strong> into the extracted libexif folder. I used GitBash at the begining but was getting make errors, it turned out that some of GitBash’s tools were conflicting with MinGW’s tools.<\/p>\n4.) Make libexif by issuing the following commands:<\/p>\n
\r\n#\r\nsh .\/configure --prefix=\/tmp\/install_libexif\r\nmake\r\nmake install\r\n#\r\n<\/pre>\nNow during make, you may get an error like this:<\/p>\n
libtool: link: cannot find the library `\/home\/keith\/staged\/mingw32\/lib\/libiconv.’<\/strong><\/p>\nIf this happens, go to your MinGW lib directory (e.g. C:\\MinGW\\lib) and delete this file:<\/p>\n
libintl.la<\/strong><\/p>\nAnd try running make again, if you continue to get the above error, then the advice out there us to delete any files with ‘keith’ in them, but luckily I didn’t have to.<\/p>\n
If make & make install succeed, you should then see the install directories in \/tmp, which you can access using MS explorer in your MinGW\\msys directory:<\/p>\n
e.g. maybe in C:\\MinGW\\msys\\1.0\\tmp<\/p>\n
Thankfully that all worked for me, I was then able to link to the libexif libraries from a Visual Studio 2012 C++ project. The only gotcha I found is that when freeing the char*<\/strong> buffer allocated during a call to exif_data_save_data(), I found it important not to use free() but to use libexif’s own memory deallacator like this:<\/p>\n\r\n\/\/ \r\n unsigned char *exif_data;\r\n \r\n \/* Get a pointer to the EXIF data block we just created *\/\r\n exif_data_save_data(exif, &exif_data, &exif_data_len);\r\n\r\n \/\/ Use exif_data here, save it to file etc..\r\n\r\n \/\/ Now we want to free this memory\r\n \/\/ don't do this, we will get a heap error:\r\n \/\/ free(exif_data) \r\n\r\n \/\/ instead can do this (as long as you used\r\n \/\/ the default mem allocator earlier in your\r\n \/\/ code):\r\n ExifMem *mem = exif_mem_new_default();\r\n exif_mem_free(mem, exif_data);\r\n\/\/\r\n<\/pre>\nThis is probably due to my test application using a different malloc() to the lib.<\/p>\n
To link to libEXIF from visual studio you can directly add libexif.dll.a<\/strong> to Properties \/ Linker \/ Input \/ Additional Dependencies and then just make sure that libexif-12.dll<\/strong> is somewhere on the execution path.<\/p>\nIf you don’t fancy all of this hassle the library binaries can be downloaded from here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"This is a record of how to build \/ compile libexif (v0.6.21) binaries for windows. It is another entry in a Software Engineer’s daily ‘trial log’, however this time thanks to the excellent MinGW32 and the well written libexif things went rather well! This readme says that you have 2 options, either hack together a […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[354,350,353,91,222],"class_list":["post-2019","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-compile","tag-exif","tag-libexif","tag-visual-studio","tag-windows"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t