On 03/13/2010 09:33 AM, Bruno Haible wrote: > Additionally, the user who installs a package might want to disable the C++ > part even if it is packaged as part of the tarball. I'm applying this. > > 2010-03-13 Bruno Haible <br...@clisp.org> > > Allow the user to disable C++ code and tests. > * m4/ansi-c++.m4 (gl_CXX_CHOICE): New macro. > (gl_PROG_ANSI_CXX): Require it.
This is a nice patch, but would it be possible to take it one step further, and allow the developer to populate a default state for whether C++ code should be enabled/disabled if the user did not pass a configure option? That is, I can see that for some packages (those which use C++), it is useful to test the C++ code by default unless the user says no; but for others (those that only contain C code, but which can still be compiled by a C++ compiler[1]), the default should be no C++ code, but a user requesting CC=g++ would want to turn it on. [1] Oddly enough, this describes m4 :) -- Eric Blake ebl...@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
