found this, https://projects.archlinux.org/svntogit/community.git/tree/trunk/cdio.patch?h=packages/xbmc and headers cdda.h and paranoia.h now lives under cdio/paranoia/ instead of directly in cdio/ please test and if paranoia.h or cdda.h is being used, the dep goes like: || ( dev-libs/libcdio-paranoia <dev-libs/libcdio-0.90[-minimal] ) but I really don't know. xbmc requires such dependencies it won't emerge on my devbox, but that's another story thanks!
xbmc-12.0_rc3 builds fine for me even with no paranoia.h / cdda.h present at all. # emerge -C libcdio-paranoia <.. successful unmerge> # qlist -ICv libcdio dev-libs/libcdio-0.90 # updatedb # locate cdda.h # locate paranoia.h # emerge =xbmc-12.0_rc3 <successful emerge> #
The bundled FFmpeg in the _rc3 source code is at least broken: $ grep -r cdda.h * lib/ffmpeg/libavdevice/libcdio.c:#include <cdio/cdda.h> lib/ffmpeg/configure: check_lib2 "cdio/cdda.h cdio/paranoia.h" cdio_cddap_open "-lcdio_paranoia -lcdio_cdda -lcdio" $ grep -r paranoia.h * lib/ffmpeg/libavdevice/libcdio.c:#include <cdio/paranoia.h> lib/ffmpeg/configure: check_lib2 "cdio/cdda.h cdio/paranoia.h" cdio_cddap_open "-lcdio_paranoia -lcdio_cdda -lcdio" But it's propably not used by the ebuild. So having plain 'dev-libs/libcdio' dependency is fine if the bundled FFmpeg is not used.
Current xbmc does not even have the option to use internal ffmpeg, so this can be closed, right?
(In reply to comment #3) > Current xbmc does not even have the option to use internal ffmpeg, so this > can be closed, right? Still not convinced it works without seeing a build log (or a word from the maintainer) which implies libcdio is actually picked up and used. But oh well
You are right after all, xbmc-11 does use cdda.h and requires the patch from archlinux to build against libcdio-0.90. xbmc-12 is fine, though.
xbmc-12 works fine
