[SANTUARIO-435] Automake misses the subdir-objects option

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: C++ 1.7.3
• Fix Version/s: C++ 2.0.0
• Component/s: C++
• Environment: Debian Linux x86_64; autoconf 2.69; automake 1.14.1
• Flags: Patch
• Assignee: Scott Cantor
• Reporter: Ferenc Wágner
• Created: 26/Nov/15 16:47
• Updated: 27/Jun/18 15:28
• Resolved: 01/Sep/17 23:01

Description

The autoreconf procedure complains like this:

[...]
libtoolize: copying file `m4/lt~obsolete.m4'
configure.ac:25: installing 'build-aux/compile'
xsec/Makefile.am:370: warning: source file 'canon/XSECC14n20010315.cpp' is in a subdirectory,
xsec/Makefile.am:370: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'
automake: automake option hasn't been enabled.  For now, the corresponding output
automake: object file(s) will be placed in the top-level directory.  However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.
xsec/Makefile.am:370: warning: source file 'canon/XSECXMLNSStack.cpp' is in a subdirectory,
xsec/Makefile.am:370: but option 'subdir-objects' is disabled
xsec/Makefile.am:370: warning: source file 'canon/XSECCanon.cpp' is in a subdirectory,
xsec/Makefile.am:370: but option 'subdir-objects' is disabled
[...]

A possible fix is adding the option to AM_INIT_AUTOMAKE in configure.ac, like

AM_INIT_AUTOMAKE([subdir-objects])