This is the mail archive of the
mailing list for the binutils project.
Re: bug#11034: Binutils, GDB, GCC and Automake's 'cygnus' option
- From: Tom Tromey <tromey at redhat dot com>
- To: Stefano Lattarini <stefano dot lattarini at gmail dot com>
- Cc: ams at gnu dot org, iant at google dot com, gcc at gcc dot gnu dot org, 11034 at debbugs dot gnu dot org, gdb at sourceware dot org, automake at gnu dot org, binutils at sourceware dot org, joseph at codesourcery dot com
- Date: Mon, 02 Apr 2012 14:19:04 -0600
- Subject: Re: bug#11034: Binutils, GDB, GCC and Automake's 'cygnus' option
- References: <4F72E239.email@example.com> <Pine.LNX.firstname.lastname@example.org> <4F7301DD.email@example.com> <firstname.lastname@example.org> <4F76C08E.email@example.com> <E1SDuIY-0004aQ-0U@fencepost.gnu.org> <4F76D8F2.firstname.lastname@example.org> <email@example.com> <4F79BFDB.firstname.lastname@example.org> <email@example.com> <4F79C5F2.firstname.lastname@example.org> <email@example.com> <4F7A0341.firstname.lastname@example.org>
>>>>> "Stefano" == Stefano Lattarini <email@example.com> writes:
Stefano> It should still be possible, with the right hack (which is
Stefano> tested in the testsuite, and required by other packages
Stefano> anyway). The baseline is: if you don't want your '.info' files
Stefano> to be distributed, then it should be easily possible to have
Stefano> them built in the builddir; but if you want them distributed,
Stefano> they will be built in the srcdir.
Now I am confused. Is it possible to continue to work the way it does
today, or not?
If so, then great.
If not, then we need some other plan.
Tom> But, I see that, according to the Automake manual, I am wrong about that.
Stefano> Weird, I didn't expect that hack to be documented in the
Stefano> manual... And in fact I cannot find it. Could you please
Stefano> point me to it? Thanks.
"Info files are always created in the build directory, and not in the
source directory. Packages that don't use the cygnus option can emulate
this effect by using the no-installinfo option and listing the generated
info files in the CLEANFILES variable. "
Re-reading the suggestion here, I can't understand how it would work.
Anyway the real use in the src tree is different, IIUC.
Info files are built in the build tree by developers, but put in the
source tree for distribution.