From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,163994d4f34e92d0
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.66.74.225 with SMTP id x1mr1856770pav.45.1344324784329;
        Tue, 07 Aug 2012 00:33:04 -0700 (PDT)
Path: 
 p10ni3174905pbh.1!nntp.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!ctu-peer!news.nctu.edu.tw!csnews.cs.nctu.edu.tw!news.cs.nctu.edu.tw!feeder.erje.net!news2.arglkargh.de!news.albasani.net!news.szaf.org!news.gnuher.de!rz.uni-karlsruhe.de!feed.news.schlund.de!schlund.de!news.online.de!not-for-mail
From: Dirk Heinrichs <dirk.heinrichs@altum.de>
Newsgroups: comp.lang.ada
Subject: Re: how to tell gnatmake to send executables to a different directory
 when compiling multi source?
Date: Mon, 30 Jul 2012 08:06:12 +0200
Organization: Privat
Message-ID: <jv588k$88t$1@online.de>
References: <jv2vu5$9tm$1@speranza.aioe.org>
 <p646bl8ekmhm.qkoxmbj6j4fq$.dlg@40tude.net> <jv376e$sla$1@speranza.aioe.org>
 <214bbd15-f7cb-4710-a6a7-64f37923bf4e@googlegroups.com>
 <jv3c8f$8oq$1@speranza.aioe.org> <87wr1moexq.fsf@ludovic-brenta.org>
 <jv3g7h$ib4$1@speranza.aioe.org> <87sjcaoa08.fsf@ludovic-brenta.org>
 <op.wh7xsqqmka8ora@aspire.local>
NNTP-Posting-Host: pd9ff8905.dip0.t-ipconnect.de
Mime-Version: 1.0
X-Trace: online.de 1343628372 8477 217.255.137.5 (30 Jul 2012 06:06:12 GMT)
X-Complaints-To: abuse@einsundeins.com
NNTP-Posting-Date: Mon, 30 Jul 2012 06:06:12 +0000 (UTC)
User-Agent: KNode/4.9 beta2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7Bit
Date: 2012-07-30T08:06:12+02:00
List-Id: <comp.lang.ada>

Vasiliy Molostov wrote:

> More productive is recursive and parallel make.

Nope. That makes the problem even worse. In a recursive, parallel build, the 
build can kind of overtake itself, which means that for example one library 
that needs relinking is itself linked into some executables before said 
relinking has been done, while other executables are linked to this library 
ofter its relinking has been done. Debugging this is real fun.

Bye...

	Dirk
-- 
Dirk Heinrichs <dirk.heinrichs@altum.de>
Tel: +49 (0)2471 209385 | Mobil: +49 (0)176 34473913
GPG Public Key C2E467BB | Jabber: dirk.heinrichs@altum.de