Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#5 add version info to public header files

closed-rejected
None
5
2005-03-11
2004-10-17
No

I just upgraded from libexif 0.5.12 to 0.6.11 and found
that my
php extension based on libexif doesn't compile anymore,
partly due to exif_entry_get_value() prototype changes.

It would be nice to be able to detect the library
verison from some define in the public header files, like

#define LIBEXIF_VERSION_ID 00611

#define LIBEXIF_VERSION_MAJOR 0
#define LIBEXIF_VERSION_MINOR 6
#define LIBEXIF_VERSION_PATCH 11

This would allow simple configure tests without
checking for actual features (like 'which prototype of
exif_entry_get_value() do i have to use') and
conditional code that supports both old and new API
versions in a flexible and convenient way

Discussion

  • Logged In: YES
    user_id=59853

    pkg-config and our libexif.pc should provide you with
    sufficient information on systems where a proper build
    environment exists.

    For now, I'd suppose that every time you have enough
    environment to run ./configure, you can install pkg-config
    and use that in configure.ac:

    PKG_CHECK_MODULES(LIBEXIF, libexif >= 0.6.11)
    AC_SUBST(LIBEXIF_LIBS)
    AC_SUBST(LIBEXIF_CFLAGS)

    like our exif CLI does.

    If I don't get negative feedback, I'm going to close this
    bug as "rejected" some time in the future.

     
    • status: open --> closed-rejected
     
    • assigned_to: nobody --> hun