Timo K Suoranta wrote:
> I have been thinking about making yet another tool on top of automake
> which would generate Makefile.am files. It would make the path from
> project file to make even longer and more perverted, but at least it would
> maintain portability, and it would work.
>
> Such th
> "Timo" == Timo K Suoranta <[EMAIL PROTECTED]> writes:
Timo> I think there is no foolproof way to detect all possible
Timo> workarounds. My lucky guess is that neither wildcards nor
Timo> wildcard workarounds are considered acceptable. Automake simply
Timo> does not like the wildcard feature
On Fri, 2002-04-12 at 17:47, Philipp Thomas wrote:
> I have a package that does in configure.in
>
>GNOME_GEN_H_FILES=`cd $srcdir/src ; ls *.gen_h | xargs echo`
>AC_SUBST(GNOME_GEN_H_FILES)
>
> and then a subdir Makefile.am has
>
> gnomemmc = wrap.cc $(GNOME_GEN_H_FILES:.gen_h=.cc) gno
>GNOME_GEN_H_FILES=`cd $srcdir/src ; ls *.gen_h | xargs echo`
>AC_SUBST(GNOME_GEN_H_FILES)
This very much looks like the 'Large project support', or 'wildcard
automake' issue which I recently asked about. In general automake wants
that the source file list is not generated by any wildcar
I have a package that does in configure.in
GNOME_GEN_H_FILES=`cd $srcdir/src ; ls *.gen_h | xargs echo`
AC_SUBST(GNOME_GEN_H_FILES)
and then a subdir Makefile.am has
gnomemmc = wrap.cc $(GNOME_GEN_H_FILES:.gen_h=.cc) gnome--.cc
libgnomemm_la_SOURCES = $(gnomemmc) [.]
And automake
