Oh - and k3b is broken right now for me. I'll see if I can't figure out the 'scope' issue - I was good at that a year ago, but I seem to have CRS syndrome. (can't remember shi...)
How do I include preprocessor checks for libcdio > 0.83?? What is the syntax?
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
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?
On Thu, 23 Jan 2014 08:46:09 -0600 "David C. Rankin" drankinatty@suddenlinkmail.com wrote:
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.
A quick poke through a random configure.in and some consultation with Google suggests you need PKG_CHECK_MODULES:
https://www.flameeyes.eu/autotools-mythbuster/pkgconfig/pkg_check_modules.ht...
Note the second sentence attached to "list-of-modules" under the syntax breakdown.
E. Liddell
On 01/23/2014 03:33 PM, E. Liddell wrote:
On Thu, 23 Jan 2014 08:46:09 -0600 "David C. Rankin" drankinatty@suddenlinkmail.com wrote:
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.
A quick poke through a random configure.in and some consultation with Google suggests you need PKG_CHECK_MODULES:
https://www.flameeyes.eu/autotools-mythbuster/pkgconfig/pkg_check_modules.ht...
Note the second sentence attached to "list-of-modules" under the syntax breakdown.
E. Liddell
It always amazes me how some people can just find the information. I never saw this link googling for every variation of "gnu preprocess check library package greater lees than required...."
Thanks. Now I'll figure out how to use it...