[Irene Huang]

Configuration option should be provided for the users to conveniently choose to ship FLAC++ or not.

Logged In: YES
user_id=1652242
Originator: YES

File Added: flac.diff.txt

proposed patch

• labels: 354959 -->
• assigned_to: nobody --> jcoalson

Logged In: YES
user_id=689771
Originator: NO

Note that this requirement is by Sun. Since C++ libraries can only be compiled and linked against if the user is using the same compiler, Sun doesn't want to ship these interfaces and support them. If an end user really wants to build their own code that uses the C++ interfaces, then that user would need to provide their own private flac interfaces along with their product to ensure that they are using the right compiler with their application.

So, it would be nice, if flac allowed you to configure if you want the C++ interfaces to be installed or not.

• status: open --> closed-fixed

Logged In: YES
user_id=78173
Originator: NO

ok, I checked in something similar. how will this work if I end up rewriting flac and/or metaflac to use libFLAC++? build the cpp lib always but not install if the option is given? not sure how to do that with automake.

Logged In: YES
user_id=689771
Originator: NO

Yes, building the libraries and linking should be fine. Just provide a configure option to not install the C++ header files. We can worry about this if & when you change flac or metaflac to use C++.