-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Bruno,
Bruno Haible wrote:
> Tom Howard wrote:
>
>>The best way I've found to do this sort of think, is to create an
>>autoconf macro that generates a Makefile fragment and use AC_SUBST_FILE
>>on that.
>
>
> Awesome! Terrific! Many many thanks f
On Tue, 7 Jun 2005, Bob Friesenhahn wrote:
Note that he said `-j', not `-j 2', or `-j 8'. Without an argument -j is
something close to infinite parallelism so it should indeed start considering
the next directory as well. If I use -j without an argument, the
GraphicsMagick build blows up. Und
On Tue, 7 Jun 2005, Ralf Wildenhues wrote:
But I have another problem with SUBDIRS. As I mentioned in the previous
thread, specifying -j starts building of l1 and src1 in parallel. l1
lasts longer, and src1 fails due to missing l1. So I think I really need
dependencies rather than sequence. What
Hi Baurzhan,
* Baurzhan Ismagulov wrote on Tue, Jun 07, 2005 at 06:23:05PM CEST:
>
> But I have another problem with SUBDIRS. As I mentioned in the previous
> thread, specifying -j starts building of l1 and src1 in parallel. l1
> lasts longer, and src1 fails due to missing l1. So I think I really
%% Ed Hartnett <[EMAIL PROTECTED]> writes:
eh> SUBDIRS = man
eh> if BUILD_F77
eh> SUBDIRS += fortran
eh> endif
eh> SUBDIRS += libsrc nc_test ncgen ncdump nctest
eh> # If we're building the f77 API, test it too.
eh> if BUILD_F77
eh> SUBDIRS += nf_test
eh> endif
There's a much
Hello Ralf,
thanks for your prompt answer!
On Tue, Jun 07, 2005 at 04:16:26PM +0200, Ralf Wildenhues wrote:
> Put
> AC_CONFIG_SUBDIRS([d1 d2 l1 l2 src1 src2])
> in toplevel configure.ac and
> SUBDIRS = d1 d2 l1 l2 src1 src2
> in toplevel Makefile.am, in the order in which you want them config
Howdy all!
The following automake file attempts to add two subdirs, "fortran" and
"nf_test", if the BUILD_F77 automake conditional is true. But this
fails:
SUBDIRS = man
if BUILD_F77
SUBDIRS += fortran
endif
SUBDIRS += libsrc nc_test ncgen ncdump nctest
# If we're building the f77 API, test i
Hi Baurzhan,
* Baurzhan Ismagulov wrote on Tue, Jun 07, 2005 at 01:12:45PM CEST:
>
> Now I want to integrate several project into the build system. The
> directory hierarchy looks like this:
>
> doc
> drv
> drv/d1
> drv/d2
> lib
> lib/l1
> lib/l2
> src1
> src2
>
> d1, d2, l1, l2, src1, src2 are
Tom Howard wrote:
> The best way I've found to do this sort of think, is to create an
> autoconf macro that generates a Makefile fragment and use AC_SUBST_FILE
> on that.
Awesome! Terrific! Many many thanks for the hint.
Harald Dunkel wrote:
> It would be pretty cool if Automake could append this
Hello,
some time ago I asked a question on how to specify directory
dependencies. At that time I solved the problem by leaving just the
top-level Makefile.am and building all targets (binaries, libraries,
test programs) from it. In this way, I could specify explicit
dependencies between the binari
Hello,
make dist-deb, dist-ebuild, ... would be nice also and I think it would
save lot of time for lot of people.
Thomas
Harald Dunkel wrote:
Tom Howard wrote:
Hi Bruno,
I used ax_add_mk_macro in ax_dist_rpm.m4 so that in my projects I can run
make dist-rpm
to create an rpm distrib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Harri,
>>I used ax_add_mk_macro in ax_dist_rpm.m4 so that in my projects I can run
>>
>>make dist-rpm
>>
>>to create an rpm distribution. Using these macros, all I have to add to
>>the Makefile.am is @INCLUDE_MK@ at the end.
>>
>
>
> It would be
Tom Howard wrote:
> Hi Bruno,
>
>
> I used ax_add_mk_macro in ax_dist_rpm.m4 so that in my projects I can run
>
> make dist-rpm
>
> to create an rpm distribution. Using these macros, all I have to add to
> the Makefile.am is @INCLUDE_MK@ at the end.
>
It would be pretty cool if Automake coul
13 matches
Mail list logo
