Would it be OK to say:
INSTALL_STRIP_FLAG=$${INSTALL_STRIP_FLAG:-s} \
in lib/am/install.am?
I'm not sure about 3 things:
- if I "quoted" that right
- if ${foo:-value} is sufficiently portable
- if it's Bad to leave INSTALL_STRIP_FLAGS set in general
In this last case, it might be a choi
install.am hardwires the INSTALL_STRIP_FLAG to -s.
I think this is a lose - there are cases (like installing kernel modules for
an embedded system) where one wants to do a stripped install but -s is "too
much".
In the existing code there is apparently no way to override this.
What's a good solu
> "Richard" == Richard Boulton <[EMAIL PROTECTED]> writes:
Richard> Executive summary: this is a KDE problem, not an automake problem.
Richard> The problem is with the am_edit script: it doesn't understand the
Richard> backslash-end-of-line line continuations.
What does am_edit do? I'm alwa
In addition to my previous message:
I'm just install automake form cvs and for simple Makefile.am got another
error:
---{Makefile.am}
bin_PROGRAMS = maketest
# qq \
maketest_SOURCES = main.cc
---
$ aclocal
$ autoconf
$ automake -a
Makefile.am:1: bin_PROGRAMS multiply defined in condition TRUE
#
Hold the presses I see some things that I have issues with. I'll attempt to
describe them usefully...
In the section of the manual:
> Unique Naming Scheme
> Automake macros (from here on referred to as variables) generally
This doesn't work. First do you realize that the term "macro" or
I just checked out my project fresh from SF CVS. Running aclocal gives me
this error:
% aclocal
aclocal: configure.in: 50: macro `AM_CHECK_PYTHON_HEADERS' not found in library
Line 50 is indeed the place where AM_CHECK_PYTHON_HEADERS is called, but it
is defined starting on line 26 as
Hi all!
I'm nitice that automake dont like comments with backspashes at the end in
Makefile.am (warning issued)... I don't know what is this bug or feature but
it is annoyed me... :)
Smbd know how to fix it? ('cept remove backspashes in comments :)
On 25 Apr 2002, Richard Boulton wrote:
> The problem is with the am_edit script: it doesn't understand the
> backslash-end-of-line line continuations.
Many thanks! That's the correct explanation!
>
> A workaround is to start each line of the definition of data_ICON with a
> newline, and ensure
christoph> Why don't you use the distutils module coming with python ?
christoph> They provide a platform-independent building/installing
christoph> mechanism of Python modules and c-extensions.
This is what my fellow Pythonistas suggest and is the workaround I'm
currently using. My
Executive summary: this is a KDE problem, not an automake problem.
The problem is with the am_edit script: it doesn't understand the
backslash-end-of-line line continuations.
Specifically, in noteedit/icons/Makefile.am, data_ICON is defined
as a set of lines joined by \-newlines. These is passe
On 24 Apr 2002 18:15:59 -0600
Tom Tromey <[EMAIL PROTECTED]> wrote:
> > "Calvin" == Calvin Arndt <[EMAIL PROTECTED]> writes:
Darn, I was trying to keep that address from getting poluted by being posted on a
freely accessible web page! please spank your mailer software for me!
>
> Calvin>
> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
Tom> I don't think autoconf and autoheader have a required ordering.
Theoretically, no. In practice, it is better to have autoconf
complain about configure.in than autoheader.
> "Paul" == Paul D Smith <[EMAIL PROTECTED]> writes:
Paul> Hi Tom et. al.: I'm working on a trivial doc to include with GNU
Paul> make that gives the exact steps to build it from a clean
Paul> checkout. I based the algorithm on what autoreconf uses, but I
Paul> can't use autoreconf (mainly d
BTW: The am_edit is not the last problem.
automake > 1.4 (i.e. automake-1.5, automake-1.6, automake-1.6.1 ,excludes some pixmaps
from
installation (perhaps they don't look good ;-)
Of course I cannot say whether this is a KDE or
automake or autoconf problem. All I know is till
automake-1.4 the
> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
adl> Automake <= 1.5: output 'generated automatically by automake' but
adl> don't grep for it Automake 1.6 and 1.6.1: output 'generated by
adl> automake' and grep for it in the *f
On Thu, 25 Apr 2002, David Faure wrote:
> >
> > Joerg> + +if ( !( $MakefileData =~ s/^(.*generated automatically by
>automake.*\n)/$1$progIdLine/ ) ) {
This does not work. The only patch that works is to
change in m4/depout.m4
if (sed 1q $mf | fgrep 'generated by automake') > /dev/null
Why don't you use the distutils module coming with python ? They provide a
platform-independent building/installing mechanism of Python modules and
c-extensions.
Regards,
Christoph
On Wednesday 24 April 2002 22:11, Alexandre Duret-Lutz wrote:
> >>> "Joerg" == Joerg Anders <[EMAIL PROTECTED]> writes:
>
> [...]
>
> Joerg> + From [EMAIL PROTECTED] Wed Apr 24 07:58:00 2002
> [...]
> Joerg> + > + Unfortunately this fools Automake, as it recognizes its
> Joerg> + > + Makefile
18 matches
Mail list logo
