On 01/23/2014 02:42 AM, Darrell Anderson wrote:
Take a gander at some of the libpng patches from a
year ago.
I'm guessing you want to test the location of cdda.h in the
configure scripts, not in the C++. Perhaps something like this:
http://www.trinitydesktop.org/patches/1380496303:5077373c0cc9e90f1bd
1d4231fb44686a3c4aa19.diff
Should the libcdio pkgconfig file reveal the location?
Darrell
I have spent hours looking at preprocessor directives and I still don't know
how we could fined a check to work that would test for a specific version of
libcdio and libcdio-paranoia. With gcc, and others with standard pre-defined
macros, then a test is relatively easy, but I can't find a preprocessor check
that says "hey, check package X and see if it is at least version Y".
There are pkgconfig files for libcdio_cdda and libcdio_paranoia:
/usr/lib/pkgconfig/libcdio_cdda.pc
/usr/lib/pkgconfig/libcdio_paranoia.pc
They include:
08:37 phoinix:/dat_e/ch14/david/usr/include/cdio> cat
../../lib/pkgconfig/libcdio_cdda.pc
prefix=/usr
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include
Name: libcdio_cdda
Description: CD paranoia CD-DA library from libcdio
Version: 10.2+0.90+1
Requires: libcdio
Libs: -L${libdir} -lcdio_cdda -lcdio -lm
Cflags: -I${includedir}
08:37 phoinix:/dat_e/ch14/david/usr/include/cdio> cat
../../lib/pkgconfig/libcdio_paranoia.pc
prefix=/usr
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include
Name: libcdio_paranoia
Description: CD paranoia library from libcdio
Version: 10.2+0.90+1
Requires: libcdio
Libs: -L${libdir} -lcdio_paranoia -lcdio_cdda -lcdio
Cflags: -I${includedir}
Now I have no idea how to hack autotool files. Since there are pkgconfig
files, doing it should not be that hard, but other than starting reading the
"Gnu Autotools Manual", I don't have any quick and dirty reference.
Any ideas?
--
David C. Rankin, J.D.,P.E.