[cmake-developers] FindJasper version v. mageia multiarch-utils
Brad King
brad.king at kitware.com
Tue Jul 17 11:43:45 EDT 2012
On 07/17/2012 11:11 AM, Shlomi Fish wrote:
>> On 07/17/2012 05:41 AM, Shlomi Fish wrote:
>>> With cmake-2.8.9-rc2 on Mageia Linux Cauldron (see
>>> https://wiki.mageia.org/en/Cauldron ) I am getting:
> shlomif at telaviv1:~$ rpm -qa '*jasper*'
> lib64jasper-devel-1.900.1-13.mga2
> lib64jasper1-1.900.1-13.mga2
>
> shlomif at telaviv1:~$ rpm -ql lib64jasper-devel | xargs grep JAS_VERSION
> grep: /usr/include/jasper: Is a directory
> /usr/include/jasper/jas_version.h:#ifndef JAS_VERSION_H
> /usr/include/jasper/jas_version.h:#define JAS_VERSION_H
> /usr/include/jasper/jas_version.h:#if !defined(JAS_VERSION)
> /usr/include/jasper/jas_version.h:#define JAS_VERSION "unknown"
> /usr/include/jasper/jas_version.h: returned by this function may not necessarily correspond to JAS_VERSION. */
> grep: /usr/include/multiarch-x86_64-linux/jasper: Is a directory
> /usr/include/multiarch-x86_64-linux/jasper/jas_config.h:#define JAS_VERSION "1.900.1"
> /usr/include/multiarch-x86_64-linux/jasper/jas_config.h:#define JAS_VERSION "1.900.1"
> grep: /usr/share/doc/lib64jasper-devel: Is a directory
>
> hope it helps.
>
> /usr/include/jasper/jas_config.h just contains this:
>
> #define _MULTIARCH_HEADER jasper/jas_config.h
> #include <multiarch-dispatch.h>
Well, it looks like we can't even detect the version of a
library from a header file without running the preprocessor
with a specific architecture.
http://www.mageia.org/en/about/
http://svnweb.mageia.org/soft/multiarch-utils/trunk/
At a quick glance what multiarch-utils is doing works around
projects that violate the Filesystem Hierarchy Standard
http://www.pathname.com/fhs/
by installing architecture-specific files into <prefix>/include.
-Brad
More information about the cmake-developers
mailing list