> -Original Message-
> From: Bruce Korb [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, April 13, 2002 10:03 AM
> To: Ian Pilcher
> Cc: [EMAIL PROTECTED]
> Subject: Re: Seeking simple example for "shallow" tree
>
>
> Ian Pilcher wrote:
> >
> > I am trying to set up a simple project for
Apparently, one can autoconf to produce a configure file with an arbitrary
name from another arbitrary name (ie, not configure.in or configure.ac)
However, I haven't found a way (in the docs) to tell automake-1.5 the name
of this new configure.XX file.
How does one do this?
H
Warning
Unable to process data:
multipart/mixed;boundary="=_NextPart_000_00B0_07A53B0C.D8172D61"
Natural Not Viagra - Half Off
Iron Man Viagra Alternative!Very safe and effective!
Iron Man is an all natural, powerful herbal supplement. No Prescription needed!
As-seen-on-TV!
click here for details
*To be removed from future promotions, please click here. Natural Not Viagra - Hal
> -Original Message-
> From: Robert Collins
> Sent: Saturday, April 13, 2002 12:01 PM
> > -Original Message-
> > From: Tom Tromey [mailto:[EMAIL PROTECTED]]
> > Sent: Saturday, April 13, 2002 7:24 AM
>
> > Also this happens a lot in libjava, where we sometimes add a
> > new .j
> -Original Message-
> From: Tom Tromey [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, April 13, 2002 6:59 AM
> To: Robert Collins
> Cc: Roger Leigh; Alexandre Duret-Lutz; Chadwick A. McHenry;
> GNU Automake List
> Subject: Re: maintainer mode
>
>
> > "Rob" == Robert Collins <[EMAI
> -Original Message-
> From: Tom Tromey [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, April 13, 2002 7:24 AM
> Also this happens a lot in libjava, where we sometimes add a
> new .java file without touching anything else. I imagine the
> same is true for many Java libraries.
And in a
Ian Pilcher wrote:
>
> I am trying to set up a simple project for automake/autoconf. I have a
> single source file, main.c, in the top-level directory; all the other
> source files are in subdirectories.
>
> Can anyone point me to a simple example/template for my Makefile.am(s)?
Here are a cou
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
Tom Tromey wrote:
>
> This sounds like a bug. Do you have a simpler example than your
> project? Or could you describe it in more detail?
>
Here is the simplest example I can come up with.
./configure.in:
AC_INIT(foo.c)
AM_INIT_AUTOMAKE(foobar, 0)
AC_PROG_CC
AC_OUTPUT(Makefi
Tom Tromey wrote:
[stuff]
Yep. It seems to be "install-recursive" related:
> $ egrep install-recursive ag/autoopts/Makefile
> install-exec-recursive installdirs-recursive install-recursive \
> uninstall-recursive check-recursive installcheck-recursive
> install: install-recursiv
Alexandre Duret-Lutz wrote:
> Bruce> install : install-man3
>
> Without this override the generated Makefile should have:
Should this override inhibit the "install: install-am" line? Why?
Besides, "install-recursive" 'cuz of the subdirectory.
> | install: install-am
> | install-am: all-am
>
> "Richard" == Richard Boulton <[EMAIL PROTECTED]> writes:
Richard> Surely one thing we could do is to implement wildcards that
Richard> are evaluated at the time that automake is run.
Just to be clear, I thought that was the only kind under
consideration. I don't think there's any way we c
> "Russ" == Russ Allbery <[EMAIL PROTECTED]> writes:
Russ> [ rebuild rules ]
Russ> It just breaks everything.
That's too extreme.
Russ> I say this largely as a user who compiles hundreds of packages
Russ> that use autoconf and automake. I have *never* been helped by
Russ> these Makefile ru
> "Bruce" == Bruce Korb <[EMAIL PROTECTED]> writes:
Bruce> I created some man3 docs and found that despite having
Bruce> added them to the man_MANS variable, they were not
Bruce> installed until I added:
Bruce> install : install-man3
What version of automake is this?
Bruce> It would seem
> "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
> "Ian" == Ian Pilcher <[EMAIL PROTECTED]> writes:
Ian> Can anyone point me to a simple example/template for my
Ian> Makefile.am(s)?
Not readily.
Ian> I've tried simply listing all the source files in a single
Ian> Makefile.am, but this doesn't work; the object files end up in
Ian> the top-
> "Rob" == Robert Collins <[EMAIL PROTECTED]> writes:
Rob> Ditto for squid. We cannot expect all our users to have automake
Rob> + autoconf on their system. After all, the entire point of
Rob> configure scripts and make dist is that the toolkit doesn't need
Rob> to be present on every system.
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
I am trying to set up a simple project for automake/autoconf. I have a
single source file, main.c, in the top-level directory; all the other
source files are in subdirectories.
Can anyone point me to a simple example/template for my Makefile.am(s)?
I've tried simply listing all the source files
>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
Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
> >>> "Roger" == Roger Leigh <[EMAIL PROTECTED]> writes:
>
> [...]
>
> Roger> In the gimp-print source tree, there are a number of
> Roger> files which we ship in the distributed tarball
> Roger> pre-built. These are PDF and HTML versions of
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
Be interested in importing motorcycles from China, you are on the right way!
China Chongqing International Econ & Tech Exchange (Group) Co., Ltd.
CHONGQING YINGANG ENERGY SAVING MOTORCYCLE CO., LTD.
Address: 18-6, Zhongxin Bank Mansion,
Jiangbei District, Chongqing,
Title: eMail
-- STOP --
Zahlen Sie nicht länger 3,65 DM/Min für
geile SexShows im Internet !
Unsere Zugangssoftware ist 100%ig KOSTENLOS
!
Wie bieten Ihnen über 20.000 private Bilder von Frauen, über 1000 Sex Videos
zum Downloaden, Live Shows mit Webcam und Chat und das Beste: Sehr viele
>>> "Roger" == Roger Leigh <[EMAIL PROTECTED]> writes:
[...]
Roger> In the gimp-print source tree, there are a number of
Roger> files which we ship in the distributed tarball
Roger> pre-built. These are PDF and HTML versions of SGML
Roger> manuals and PostScript versions of Texinfo manuals.
>>> "Eric" == Eric Siegerman <[EMAIL PROTECTED]> writes:
[...]
Eric> 4. The user imported your package into CVS (as I often do).
Eric> Because CVS checkouts are done in alphabetical order, foo.in
Eric> might well have a later timestamp than its corresponding foo,
Eric> without the files' con
>>> "Bruce" == Bruce Korb <[EMAIL PROTECTED]> writes:
Bruce> Hi,
Bruce> I created some man3 docs and found that despite having
Bruce> added them to the man_MANS variable, they were not
Bruce> installed until I added:
Bruce> install : install-man3
Without this override the generated Makefi
28 matches
Mail list logo
