Re: [Libcdio-devel] Revisit cdio_config.h do we need this?

[Rocky Bernstein]

There are various optional features like Rock-Ridge support is available,
whether libcddb was expected that are useful to know at run time.

Even without this, if you want to write a simple C program like one in the
examples program, one can use cdio_config.h to get a reasonable set of C
defines without having to write a configure script.

On Tue, May 28, 2013 at 10:16 PM, Eric Shattow <address@hidden> wrote:

> When looking at sed hacks in the libcdio git, we are distilling a copy of
> config.h as cdio_config.h but why?
>
> There's a discussion in archives about removing the need for it, and also
> some hints that it caused problems with portability.
>
> Do we really need this access to config.h beyond compile time?
>