On Tue, Mar 10, 2015 at 11:54 AM, Vincent Torri vincent.to...@gmail.com wrote:
On Tue, Mar 10, 2015 at 10:47 AM, Marc Wäckerlin m...@waeckerlin.org wrote:
Any comments on what is a proper solution?
Requirements fo a solution:
- Add makefile rules from within configure.ac
- No maual changes
Am 10.03.2015 12:56, schrieb Bert Wesarg:
On Tue, Mar 10, 2015 at 11:54 AM, Vincent Torri
vincent.to...@gmail.com wrote:
imho, configure.ac is for configuring the project, not defining 'make'
rules. These 'make' rules should go into Makefile.am :
I can only second this. Nobody is forced to
Thank you for the answers.
The question remains:
Isn't there a proper way to add makefile rules from within a
configure.ac script?
Am 10.03.2015 00:46, schrieb Peter Johansson:
On 03/09/2015 06:34 PM, Marc Wäckerlin wrote:
Just to state my intention: I want to ad a couple of M4-Macros to
On Tue, Mar 10, 2015 at 10:47 AM, Marc Wäckerlin m...@waeckerlin.org wrote:
Thank you for the answers.
The question remains:
Isn't there a proper way to add makefile rules from within a configure.ac
script?
Am 10.03.2015 00:46, schrieb Peter Johansson:
On 03/09/2015 06:34 PM, Marc
() Marc Wäckerlin m...@waeckerlin.org
() Tue, 10 Mar 2015 10:47:37 +0100
Any comments on what is a proper solution?
I think this kind of scan + conditionalized-inclusion mucking
is best done in autogen.sh by way of creating m4 fragments for
configure.ac and makefile fragments for the
On 03/09/2015 06:34 PM, Marc Wäckerlin wrote:
Just to state my intention: I want to ad a couple of M4-Macros to
support users of now unsupported build tools, namely doxygen, Qt,
dpkg-buildpackage, rpmbuild, ...; then I will deliver those as M4
macro library that can be included in configure.ac
Just to state my intention: I want to ad a couple of M4-Macros to
support users of now unsupported build tools, namely doxygen, Qt,
dpkg-buildpackage, rpmbuild, ...; then I will deliver those as M4 macro
library that can be included in configure.ac and that should do as much
as possible