> "Jeremy" == Jeremy Slade <[EMAIL PROTECTED]> writes:
Jeremy> In a project, I want all objects (both C and C++) in a certain
Jeremy> subdirectory to include additional flags (defined by
Jeremy> PERL_CFLAGS) in the compile line, but I don't want those flags
Jeremy> used to build object in oth
> "edward" == edward <[EMAIL PROTECTED]> writes:
edward> + if (!defined($extension_map{$extension}))
edward> + {
edward> + &am_error ("unknown extension for `$full' in $var");
edward> + next;
edward> + }
We can't do this. We intentionally don't warn in
In a project, I want all objects (both C and C++) in a certain
subdirectory to include additional flags (defined by PERL_CFLAGS) in
the compile line, but I don't want those flags used to build object in
other directories. I'm not sure how to accomplish this.
If I do this in the Makefile.am:
CFL
Hello!
CVS Automake uses am_line_error() to inform the user that it's installing
files. As a result, --Werror causes Automake to exit after it installs the
first file:
$ automake --Werror --add-missing; echo $?
automake: Makefile.am: installing `./INSTALL'
2
$ automake --Werror --add-missing; ec
> "Lars" == Lars Hecking <[EMAIL PROTECTED]> writes:
Lars> edward writes:
>> hi akim,
>>
>> this is a plea to avoid using constructs like the "cp Makefile.am
>> Makefile.AM" below. this kills us cygwin/windows people, and i for
>> one, very much would like to keep automake, etc. working on w
edward writes:
> hi akim,
>
> this is a plea to avoid using constructs like the "cp Makefile.am
> Makefile.AM" below. this kills us cygwin/windows people, and i for one, very
> much would like to keep automake, etc. working on window based platforms!
I fully support this. There are more platfo
Right, I reset my automake dir to CVS no patches,
test log in testSubDir (running on cygwin 1.1.8-2)===
$ perl -pi.old -e 's/^\t\@/\t/g' Makefile
$ make distdir
chmod -R a+w ./am_lex_bug-0.1.1 >/dev/null 2>&1; rm -rf
./am_lex_bug-0.1.1
mkdir ./am_lex_bug-0.1.1
for file in Makefile.am Makef
hi akim,
this is a plea to avoid using constructs like the "cp Makefile.am
Makefile.AM" below. this kills us cygwin/windows people, and i for one, very
much would like to keep automake, etc. working on window based platforms!
cheers,
edward
> +cp Makefile.am Makefile.AM
- Original Message
hi peeps:
given the following Makefile.am:
noinst_PROGRAMS = foo
foo_SOURCES = foo.i
automake will die with:
+ perl ../../automake --amdir=/usr/beta/src/automake/tests/.. --foreign
-a
Use of uninitialized value in string eq at ../../automake line 5417.
unknown extensions are not tested before
- Original Message -
From: "Akim Demaille" <[EMAIL PROTECTED]>
To: "edward" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, March 13, 2001 5:39 AM
Subject: Re: pr19.test
> Thanks for the details. As I'm currently working on DIST_COMMON
> etc. (I have another bunch of patche
| From
| http://sources.redhat.com/ml/automake/2001-03/msg00183.html
|
| 2) lines 4946-4947 of automake.in version 1.977
|
| # FIXME: nodist.
| &push_dist_common ($pfx . $base . '.' . $ext);
|
| commenting out the last line removes foo.c (which is a temporary file)
| from the m
From
http://sources.redhat.com/ml/automake/2001-03/msg00183.html
2) lines 4946-4947 of automake.in version 1.977
# FIXME: nodist.
&push_dist_common ($pfx . $base . '.' . $ext);
commenting out the last line removes foo.c (which is a temporary file)
from the make distdir target,
> make[2]: Leaving directory `/usr/src/automake/tests/testSubDir'
> make[2]: Entering directory `/usr/src/automake/tests/testSubDir'
> chmod -R a+w ./am_lex_bug-0.1.1 >/dev/null 2>&1; rm -rf
> ./am_lex_bug-0.1.1
> mkdir ./am_lex_bug-0.1.1
> cp: ./foo.c: No such file or directory
I have this.
ma
13 matches
Mail list logo
