Thanks John, I'll take a look (actually I had already seen your online
book, but not the part on doxygen).
However, I think that some macro/base functionality should be provided
in autotools, and I read in this very list that the autoconf macro does
not work well...
cheers
Lorenzo
J
On Tuesday 2009-04-14 08:09, Ralf Wildenhues wrote:
>Here's why:
>[...]
>Yet another way out: remove per-Makefile.am `AUTOMAKE_OPTIONS =
>silent-rules' as well as `automake --silent-rules' so that the only way
>to specify them is as option listed in AM_INIT_AUTOMAKE. This may be
>inconvenient for
Hi
I was trying to have 'make install' install a whole directory (together
with all its contents) by specifying in the Makefile.am
doc_DATA = html
where html is a directory
I get no error from automake, but during in the installation (make
install) I get:
/usr/bin/install -c -m 644 './ht
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ralf Wildenhues on 4/14/2009 12:09 AM:
> Hello Bob, Eric, all,
Hello Ralf,
>> This is an approach that I am happy with. I would not want to deny
>> anyone access to silent rules if they want it (and I will am likely use
>> it for my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[really adding autoconf and automake lists this time]
According to Alfred M. Szmidt on 4/14/2009 6:22 AM:
>Hmmm. Would it be worth changing autoconf to make './configure
>--help' state something like the following:
>
>| Some influential
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Alfred M. Szmidt on 4/14/2009 6:49 AM:
>`To install FOO in a staging directory, use `make install DESTDIR=...''
>
> I like that.
>
>packages where DESTDIR doesn't work properly. But automake already
>does such a good job at
Hi,
I have a cross-compile situation where I want to compile sources of a
subdirectory for the host system as well as for the build system. I pass
--host, --build and CC_FOR_BUILD to configure. Then I have two
Makefile.am in distinct subdirectories, one has the statement
CC=$(CC_FOR_BUILD), the ot
>Hmmm. Would it be worth changing autoconf to make './configure
>--help' state something like the following:
>
>| Some influential environment variables:
>| ...
>| DESTDIRleave unset during configure; allows installation to
>| spec
>packages where DESTDIR doesn't work properly. But automake
>already does such a good job at providing DESTDIR support
>(especially if the user remembered to run 'make distcheck'),
>that I think it would be nice if using AM_INIT_AUTOMAKE did
>make the ./configure
On Tue, 14 Apr 2009, Eric Blake wrote:
If so, is it worth trying to trim the AC_ARG_ENABLE output to only mention
the non-default case? That is:
AM_SILENT_RULES=> outputs 2 lines for --{en,dis}able-silent-rules
AM_SILENT_RULES([yes]) => outputs 1 line for --disable-silent-rules
AM_SILE
Lorenzo,
There may be a better way to do it so I'm looking forward to hearing how
others did this, but I did this by creating an install hook like this:
Makefile.am:
~snip other stuff ~
EXTRA_INSTALL =
install_dir =
help_dir =
include ../../install-hook.in
../../install-hook.in:
# This hook
Hello Christian,
* Christian Rössel wrote on Tue, Apr 14, 2009 at 03:20:35PM CEST:
> I have a cross-compile situation where I want to compile sources of a
> subdirectory for the host system as well as for the build system. I pass
> --host, --build and CC_FOR_BUILD to configure. Then I have two
> M
* Ralf Wildenhues wrote on Tue, Apr 14, 2009 at 08:09:12AM CEST:
> silent-rules reorganization, --enable-silent-rules switch.
[...]
> * automake.in (define_verbose_var): Define the default verbose
> variable in terms of `$(AM_DEFAULT_VERBOSITY)'.
> (handle_configure): Do not pass `-
Hi Eric, Bob,
* Eric Blake wrote on Tue, Apr 14, 2009 at 02:12:55PM CEST:
> According to Ralf Wildenhues on 4/14/2009 12:09 AM:
> >
> > This patch introduces such an --enable-silent-rules switch.
[...]
> Looks like you got what we wanted! Thanks for doing this. The patch
> seemed fine by my rev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ralf Wildenhues on 4/14/2009 2:32 PM:
> Hi Eric, Bob,
Hello to you as well,
>>> +Enable the machinery for less verbose build output (@pxref{Options}).
>> Are you going to document the (optional) argument that specifies the default?
>
>
Hello Alfred, Eric,
* Alfred M. Szmidt wrote on Tue, Apr 14, 2009 at 02:49:30PM CEST:
>>Hmmm. Would it be worth changing autoconf to make './configure
>>--help' state something like the following:
>>
>>| Some influential environment variables:
>>| ...
>>
Hello Laura, Lorenzo,
* Laura Hughes (lahughes) wrote on Tue, Apr 14, 2009 at 06:08:58PM CEST:
>
> There may be a better way to do it so I'm looking forward to hearing how
> others did this, but I did this by creating an install hook like this:
If you are installing a list of files only, then I
17 matches
Mail list logo
