This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Re: How build C++ header with m4 and install them - no program
- From: Tom Tromey <tromey at redhat dot com>
- To: Marc Waeckerlin <Marc dot Waeckerlin at siemens dot com>
- Cc: automake at gnu dot org
- Date: 21 Sep 2002 17:46:23 -0600
- Subject: Re: How build C++ header with m4 and install them - no program
- References: <200209191339.42258.Marc.Waeckerlin@siemens.com>
- Reply-to: tromey at redhat dot com
>>>>> "Marc" == Marc Waeckerlin <Marc.Waeckerlin@siemens.com> writes:
Marc> I have a little C++ signal-slot library, that consists of only
Marc> two C++ header files. The automake script should do the
Marc> following:
Marc> [ ... ]
Marc> How do I write the makefile.am?
nobase_include_HEADERS = sig/functor.hxx sig/sigslot.hxx
SUFFIXES = .m4
sig/functor.hxx: sig/functor.hxx.m4
m4 $(srcdir)/sig/functor.hxx.m4 > sig/functor.m4
[ also for sigslot.hxx ]
This isn't perfect since you must arrange for mkdir sig somehow.
Automake doesn't do this automatically in this situation.
Marc> - How to tell that the *.hxx are targets that must be cleared?
CLEANFILES = $(nobase_include_HEADERS)
Marc> - How to tell that the *.hxx are derieved from the *.m4?
As above.
Suffix rules don't work if the files are in subdirs.
Suffix rule support in automake could use some enhancements.
Marc> Is there a check or macros for invoking m4 in autoconf, automake?
Not that I know of.
Tom