[Dev] Streamlining development outside of chandler dir, includingdebugging native code

[Mike Taylor]

Andi +1

-----Original Message-----
From: dev-bounces at osafoundation.org
[mailto:dev-bounces at osafoundation.org]On Behalf Of Andi Vajda
Sent: Wednesday, July 28, 2004 7:51 AM
To: Heikki Toivonen
Cc: dev at osafoundation.org
Subject: Re: [Dev] Streamlining development outside of chandler dir,
includingdebugging native code

Another approach to sparing the extra install step would be to tell Chandler
where the binaries are. You and Markie just went through the exercise of
moving release|debug one level down, into the chandler directory. If this
location for release|debug were not hardcoded but configurable, say with a
command line flag, or an environment variable, then you could tell Chandler
that release|debug were inside external, for example, or wherever else you
choose. This has the added benefit that, when tracking down build problems,
you can keep multiple binary trees ready and run the same Chandler against
each of them to see what changes and how.

Andi..