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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,474f983404143522
X-Google-Attributes: gid103376,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news2.google.com!postnews.google.com!50g2000hsm.googlegroups.com!not-for-mail
From: rotinom <rotinom@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: Compiling Ada from another directory
Date: Mon, 17 Sep 2007 19:08:32 -0000
Organization: http://groups.google.com
Message-ID: <1190056112.291445.188680@50g2000hsm.googlegroups.com>
References: <1189634389.893905.5800@50g2000hsm.googlegroups.com>
   <E6%Fi.534330$p47.124299@bgtnsc04-news.ops.worldnet.att.net>
   <1189692969.193051.231830@19g2000hsx.googlegroups.com>
   <g9d4wma9ub.fsf@hod.lan.m-e-leypold.de>
NNTP-Posting-Host: 130.210.244.193
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Trace: posting.google.com 1190056112 20811 127.0.0.1 (17 Sep 2007 19:08:32
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Mon, 17 Sep 2007 19:08:32 +0000 (UTC)
In-Reply-To: <g9d4wma9ub.fsf@hod.lan.m-e-leypold.de>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6,gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@google.com
Injection-Info: 50g2000hsm.googlegroups.com; posting-host=130.210.244.193;
   posting-account=ps2QrAMAAAA6_jCuRt2JEIpn5Otqf_w0
Xref: g2news2.google.com comp.lang.ada:1991
Date: 2007-09-17T19:08:32+00:00
List-Id: <comp.lang.ada>


RE: Simon

You're right that the Project files are rather trivial, and the
easiest way to go.  However I am using a build tool called SCons, and
adding Ada support to that.  It has support for dozens of languages,
and handles the dependency issues that gnatmake does by itself.  I'm
just figuring out what the gnattools do under the hood, and adding
that support in.


RE: Markus

A few days late, but the basic problem is that the SCons tool runs
everything out of the directory where the SConstruct file is located
(e.g.: The build root.).

A typical tree layout is:

/src/
/build_dir/
/SConstruct

so, when you build, all commands run as if you were sitting in / .
There is only ever one "current" directory, but SCons can (and
typically does) run with multiple threads at the same time (I've run
it with up to 50 simultaneous threads).  If each Action being run were
to change directory, it would cause havok, so it is really to be
avoided at all costs.

I was having problems getting the correct commands to run as I needed
them to run from this build root.