[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libname with versio number
From: |
Ralf Wildenhues |
Subject: |
Re: libname with versio number |
Date: |
Mon, 11 Jan 2010 21:31:39 +0100 |
User-agent: |
Mutt/1.5.20 (2009-10-28) |
Hello Martin,
* Martin Kalbfuß wrote on Mon, Jan 11, 2010 at 03:13:22AM CET:
> I have a libname with version number.
>
> liballegro-4.9.14
>
> I added this name to AC_CHECK_LIB. And it is found.
>
> # Checks for libraries.
>
> AC_CHECK_LIB([allegro-4.9.14], [al_create_display], [],
> [AC_MSG_ERROR("allegro-4.9.14 not found")])
>
> AC_CHECK_LIB([allegro_image-4.9.14], [al_load_bitmap], [],
> [AC_MSG_ERROR("allegro_image-4.9.14 not found")])
>
> # Checks for header files.
>
> AC_CHECK_HEADERS([allegro5/allegro.h], [],
> [AC_MSG_ERROR("allegro5/allegro.h not found)])
>
> AC_CHECK_HEADERS([allegro5/allegro_image.h], [],
> [AC_MSG_ERROR("allegro5/allegro_image.h not found")], [#include
> <allegro5/allegro.h>])
>
>
> But I want to have a configure.ac recognizing later versions up to
> 4.9.17, too.
You have to write more checks with those different version numbers.
Just shows again what a bad idea it is to embed the version number into
the library name, rather than just bumping the version info, as it is
needed. Tell your upstream about it.
Cheers,
Ralf