Hi Baurzhan,
* Baurzhan Ismagulov wrote on Tue, Jun 28, 2005 at 08:46:53PM CEST:
> On Tue, Jun 28, 2005 at 06:31:57PM +0200, Ralf Wildenhues wrote:
> > Hmm. I don't know whether AC_CONFIG_SUBDIRS can give you the
> > flexibility you want here. If you unconditionally build both packages,
> > ther
Hello Bob,
On Tue, Jun 28, 2005 at 09:45:42AM -0600, Bob Proulx wrote:
> In the message headers is included this information:
Thanks!
With kind regards,
Baurzhan.
On Tue, Jun 28, 2005 at 06:31:57PM +0200, Ralf Wildenhues wrote:
> Hmm. I don't know whether AC_CONFIG_SUBDIRS can give you the
> flexibility you want here. If you unconditionally build both packages,
> there is no need to check for libl1 during src1/configure.
The problem is, I have to check th
Hi Baurzhan,
* Baurzhan Ismagulov wrote on Tue, Jun 28, 2005 at 04:59:36PM CEST:
> On Tue, Jun 07, 2005 at 04:16:26PM +0200, Ralf Wildenhues wrote:
>
> > > d1, d2, l1, l2, src1, src2 are existing projects with Makefile or
> > > configure.ac / Makefile.am. I want to leave them as they are and write
Baurzhan Ismagulov wrote:
> [This thread was started on Jun 7. I couldn't find the list archive --
> http://directory.fsf.org/GNU/automake.html doesn't mention any, and
> http://sources.redhat.com/ml/automake/2005-06/ says there were no
> messages sent this month. Which archive do you use?]
In the
Hello Ralf,
[This thread was started on Jun 7. I couldn't find the list archive --
http://directory.fsf.org/GNU/automake.html doesn't mention any, and
http://sources.redhat.com/ml/automake/2005-06/ says there were no
messages sent this month. Which archive do you use?]
On Tue, Jun 07, 2005 at 04:
* Bob Friesenhahn wrote on Wed, Jun 08, 2005 at 05:23:58PM CEST:
> On Wed, 8 Jun 2005, Ralf Wildenhues wrote:
> >
> >ECANNOTREPRODUCE. Which GNU make version?
> >Over here GNU make-3.80 does _not_ parallelize across SUBDIRs.
>
> I am using GNU make 3.80 on Solaris and FreeBSD, but the version
>
On Wed, 8 Jun 2005, Ralf Wildenhues 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.
ECANNOTREPRODUCE. Which GNU make version?
Over here GNU make-3.80 does
* Bob Friesenhahn wrote on Wed, Jun 08, 2005 at 04:14:03AM CEST:
> 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
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
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
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
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
15 matches
Mail list logo