Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. 3rd Party Software
  4. Compiling libexif in windows 7
Forum Update on Tuesday, May 27th 2025

Compiling libexif in windows 7

Scheduled Pinned Locked Moved Solved 3rd Party Software
3 Posts 2 Posters 1.4k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    samdol
    wrote on 19 Jan 2017, 10:40 last edited by
    #1

    Hi,

    Since Qt does not supply class to extract exif info in jpg file, I decided to
    use third party library-- libexif.
    I have downloaded libexif-0.6.21.zip.
    When I compiled on linux, I successfully could get libexif.a static library
    file which is the only file needed for static linking to my application.
    On windows 7, I followed the instruction at
    http://www.ridgesolutions.ie/index.php/2015/03/13/build-libexif-for-windows-and-visual-studio/
    I use mingw492_32 which comes with Qt5.6.2 and installed MSYS. After
    configure, I excuted make to compile it. What I got is the following Error.

    libtool: link: object name comflicts in archive:
    .libs/libexif.lax/libmnote-canon.a//d/libexif-0.6.21/libexif/
    ./.libs/libmnote-canon.a
    make[2]: *** [libexif.la] Error 1
    make[2]: Leaving directory '/d/libexif-0.6.21/libexif'
    make[1]: *** [all-recursive] Error 1
    make[1]: Leaving directory '/d/qqes/libexif-0.6.21'
    make: *** [all] Error 2

    And I could not find libexif.a which is all I need. Does anyone have the
    similar problem?

    1 Reply Last reply
    0
    • M Offline
      M Offline
      mrjj
      Lifetime Qt Champion
      wrote on 19 Jan 2017, 10:46 last edited by
      #2

      Hi
      The tut didn't load so could not check.
      Alarm just went off with VISUAL studio and mingw492_32 in same sentence.
      You are not mixing anything compiled with studio with mingw?

      also MSYS adds a whole new layer of stuff that can go wrong.

      Anyway, it might be a PATH thing

      http://stackoverflow.com/questions/12060186/libtool-object-name-conflicts-in-archive-netcdf-mingw

      S 1 Reply Last reply 19 Jan 2017, 12:19
      1
      • M mrjj
        19 Jan 2017, 10:46

        Hi
        The tut didn't load so could not check.
        Alarm just went off with VISUAL studio and mingw492_32 in same sentence.
        You are not mixing anything compiled with studio with mingw?

        also MSYS adds a whole new layer of stuff that can go wrong.

        Anyway, it might be a PATH thing

        http://stackoverflow.com/questions/12060186/libtool-object-name-conflicts-in-archive-netcdf-mingw

        S Offline
        S Offline
        samdol
        wrote on 19 Jan 2017, 12:19 last edited by
        #3

        @mrjj
        Thank you for your quick reply. Yes, it was the setting path environment problem. The link you provided gave me the answer. I had to put the path of MSYS and mingw32 at the begining of system path evironment.

        1 Reply Last reply
        1

        1/3

        19 Jan 2017, 10:40

        • Login

        • Login or register to search.
        1 out of 3
        • First post
          1/3
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved