[Scons-dev] Using SCons via bootstrap.py

Gary Oberbrunner garyo at oberbrunner.com
Sat May 18 10:58:17 EDT 2013


On Sat, May 18, 2013 at 3:48 AM, Dirk Bächle <tshortik at gmx.de> wrote:


> On 18.05.2013 08:09, Russel Winder wrote:

>

>> On Sat, 2013-05-18 at 00:57 +0200, Dirk Bächle wrote:

>>

>>> Hi Russel,

>>>

>> […]

>>

>>> the bootstrap.py works fine for me, I guess because I have a

>>> "src/engine" folder. Where did yours go? ;)

>>>

>> Still exactly where it has always been, in the repository:

>>

>> |> python /home/users/russel/**Repositories/Mercurial/**

>> Masters/SCons_D_Tooling/**bootstrap.py

>> Traceback (most recent call last):

>>

>>

>>

> But it still works if you start the "bootstrap.py" from the top-level

> folder ("SCons_D_Tooling" in your case), right?

>

> For the doc toolchain changes I also added some basic support for

> wildcards in the Manifest files, and I use os.chdir inside...this obviously

> breaks "bootstrap.py" when calling it from another path. I wasn't aware

> that this functionality was ever supported and had assumed that the whole

> bootstrapping process would have several hardcoded paths and stuff anyway.

> Sorry about that...

>

> I'll have a look and see if I can improve things, or if we have to switch

> back to the old handling of Manifest files.



I sometimes use bootstrap.py from a different dir too. I think it's
moderately important to preserve that.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://two.pairlist.net/pipermail/scons-dev/attachments/20130518/45a0b86f/attachment.html>


More information about the Scons-dev mailing list