Re: [Scons-dev] Using SCons via bootstrap.py

[Gary Oberbrunner]

Are you at the tip of the default branch?


On Fri, May 17, 2013 at 1:13 PM, Russel Winder  wrote:

> Is anyone else finding that the bootstrap.py script no longer works? It
> worked for me before I went away for a short break and now after
> updating Debian Unstable, it is failing. I get the same behaviour with
> Python 2.6, 2.7 and PyPy 2.0.
>
> Traceback (most recent call last):
>   File
> "/home/users/russel/Repositories/Mercurial/Masters/SCons_D_Tooling/bootstrap.py",
> line 233, in 
> main()
>   File
> "/home/users/russel/Repositories/Mercurial/Masters/SCons_D_Tooling/bootstrap.py",
> line 204, in main
> for x in parseManifestLines(src_engine, open(MANIFEST_in).readlines())]
>   File
> "/home/users/russel/Repositories/Mercurial/Masters/SCons_D_Tooling/bootstrap.py",
> line 85, in parseManifestLines
> os.chdir(basedir)
> OSError: [Errno 2] No such file or directory: 'src/engine'
>
>
> --
> Russel.
>
> =
> Dr Russel Winder  t: +44 20 7585 2200   voip:
> sip:russel.win...@ekiga.net
> 41 Buckmaster Roadm: +44 7770 465 077   xmpp: rus...@winder.org.uk
> London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> http://two.pairlist.net/mailman/listinfo/scons-dev
>
>


-- 
Gary
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Using SCons via bootstrap.py

[Russel Winder]

On Fri, 2013-05-17 at 14:43 -0400, Gary Oberbrunner wrote:
> Are you at the tip of the default branch?

Of course.  How else can you be at the bleeding edge ;-)

-- 
Russel.
=
Dr Russel Winder  t: +44 20 7585 2200   voip: sip:russel.win...@ekiga.net
41 Buckmaster Roadm: +44 7770 465 077   xmpp: rus...@winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder


signature.asc
Description: This is a digitally signed message part
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Using SCons via bootstrap.py

[Dirk Bächle]

Hi Russel,

On 17.05.2013 19:13, Russel Winder wrote:

Is anyone else finding that the bootstrap.py script no longer works? It
worked for me before I went away for a short break and now after
updating Debian Unstable, it is failing. I get the same behaviour with
Python 2.6, 2.7 and PyPy 2.0.

Traceback (most recent call last):
   File 
"/home/users/russel/Repositories/Mercurial/Masters/SCons_D_Tooling/bootstrap.py", 
line 233, in 
 main()
   File 
"/home/users/russel/Repositories/Mercurial/Masters/SCons_D_Tooling/bootstrap.py",
 line 204, in main
 for x in parseManifestLines(src_engine, open(MANIFEST_in).readlines())]
   File 
"/home/users/russel/Repositories/Mercurial/Masters/SCons_D_Tooling/bootstrap.py",
 line 85, in parseManifestLines
 os.chdir(basedir)
OSError: [Errno 2] No such file or directory: 'src/engine'


the bootstrap.py works fine for me, I guess because I have a 
"src/engine" folder. Where did yours go? ;)


Best regards,

Dirk

___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Using SCons via bootstrap.py

[Russel Winder]

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):
  File 
"/home/users/russel/Repositories/Mercurial/Masters/SCons_D_Tooling/bootstrap.py",
 line 233, in 
main()
  File 
"/home/users/russel/Repositories/Mercurial/Masters/SCons_D_Tooling/bootstrap.py",
 line 204, in main
for x in parseManifestLines(src_engine, open(MANIFEST_in).readlines())]
  File 
"/home/users/russel/Repositories/Mercurial/Masters/SCons_D_Tooling/bootstrap.py",
 line 85, in parseManifestLines
os.chdir(basedir)
OSError: [Errno 2] No such file or directory: 'src/engine'

|> ls 
/home/users/russel/Repositories/Mercurial/Masters/SCons_D_Tooling/src/engine
./  ../  .aeignore  MANIFEST.in  MANIFEST-xml.in  SCons/



-- 
Russel.
=
Dr Russel Winder  t: +44 20 7585 2200   voip: sip:russel.win...@ekiga.net
41 Buckmaster Roadm: +44 7770 465 077   xmpp: rus...@winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder


signature.asc
Description: This is a digitally signed message part
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Using SCons via bootstrap.py

[Russel Winder]

I updated to 2870:1bdda9a31f35 which is just prior to the new
documentation tool set change of 2013-05-03 and everything works as it
should.

Looking up the changes I see that 2888:102c1bf4e8cd makes changes to
bootstrap.py and I can confirm that this changeset breaks things for me:
2887:2126e0af534e works fine, 2888:102c1bf4e8cd is broken.

I am guessing the revision numbers are different for everyone?

-- 
Russel.
=
Dr Russel Winder  t: +44 20 7585 2200   voip: sip:russel.win...@ekiga.net
41 Buckmaster Roadm: +44 7770 465 077   xmpp: rus...@winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder


signature.asc
Description: This is a digitally signed message part
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Using SCons via bootstrap.py

[Dirk Bächle]

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.


Regards,

Dirk

___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Using SCons via bootstrap.py

[Gary Oberbrunner]

On Sat, May 18, 2013 at 3:48 AM, Dirk Bächle  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.
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Using SCons via bootstrap.py

[Russel Winder]

On Sat, 2013-05-18 at 09:48 +0200, Dirk Bächle wrote:
[…]
> But it still works if you start the "bootstrap.py" from the top-level 
> folder ("SCons_D_Tooling" in your case), right?

I have never tried that, I am not sure what the use case would be for
non-SCons-itself builds as you would have to give the absolute path to
the SConstruct you wanted run.

> 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 guess the problem is that with this change the bootstrap.py file has
now become the SCons distribution build tool. :-( 

> 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.

No I think we must move forward, not back.

The question in my mind is why is the os.chdir executed when the script
is being used for launching SCons on a user SConstruct. The os.chdir is
only needed to process documentation files in the SCons tree, cannot it
then be in a select statement of some sort? Can the new processing be
separated out and only executed if needed?

Another question in my mind is why use os.chdir at all couldn't all the
"alternate directory" stuff be done using subprocesses and adding data
to a multiprocessing.Queue?

-- 
Russel.
=
Dr Russel Winder  t: +44 20 7585 2200   voip: sip:russel.win...@ekiga.net
41 Buckmaster Roadm: +44 7770 465 077   xmpp: rus...@winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder


signature.asc
Description: This is a digitally signed message part
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Using SCons via bootstrap.py

[Gary Oberbrunner]

On Sat, May 18, 2013 at 11:58 AM, Russel Winder wrote:

> On Sat, 2013-05-18 at 09:48 +0200, Dirk Bächle wrote:
> […]
> > But it still works if you start the "bootstrap.py" from the top-level
> > folder ("SCons_D_Tooling" in your case), right?
>
> I have never tried that, I am not sure what the use case would be for
> non-SCons-itself builds as you would have to give the absolute path to
> the SConstruct you wanted run.
>

The main use case for that is building SCons with itself: 'python
bootstrap.py'.

-- 
Gary
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Using SCons via bootstrap.py

[Russel Winder]

On Sat, 2013-05-18 at 13:29 -0400, Gary Oberbrunner wrote:
> On Sat, May 18, 2013 at 11:58 AM, Russel Winder wrote:
> 
> > On Sat, 2013-05-18 at 09:48 +0200, Dirk Bächle wrote:
> > […]
> > > But it still works if you start the "bootstrap.py" from the top-level
> > > folder ("SCons_D_Tooling" in your case), right?
> >
> > I have never tried that, I am not sure what the use case would be for
> > non-SCons-itself builds as you would have to give the absolute path to
> > the SConstruct you wanted run.
> >
> 
> The main use case for that is building SCons with itself: 'python
> bootstrap.py'.

Not for developers using tip, the main use case of the command line:

pypy /path/to/scons/bootstrap.py

is to build whatever it is they want to build. Building SCons is a
side-effect!

:-)

-- 
Russel.
=
Dr Russel Winder  t: +44 20 7585 2200   voip: sip:russel.win...@ekiga.net
41 Buckmaster Roadm: +44 7770 465 077   xmpp: rus...@winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder


signature.asc
Description: This is a digitally signed message part
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Using SCons via bootstrap.py

[Dirk Bächle]

Hi,

I started to fix bootstrap.py, such that the parseManifestLines() 
doesn't need os.chdir() anymore. After the rewrite, the local call 
"python bootstrap.py" works fine again...so far, so good.

But I'm not able to figure out how to call it from a different folder.

I even switched back to revision "018709cfd9f4" (merge of pull request 
#66, +1), but when I call


  python /home/dirk/workspace/scons_dirkbaechle/bootstrap.py

from "/home/dirk/tmp/boottest", all I get is:

=

dirk@ubuntu:~/tmp/boottest$ python 
/home/dirk/workspace/scons_dirkbaechle/bootstrap.py
/usr/bin/python 
/home/dirk/workspace/scons_dirkbaechle/bootstrap/src/script/scons.py


scons: *** No SConstruct file found.
File 
"/home/dirk/workspace/scons_dirkbaechle/bootstrap/src/engine/SCons/Script/Main.py", 
line 905, in _main

dirk@ubuntu:~/tmp/boottest$

=

Any pointers about what I'm doing wrong are welcome. I checked the 
README.rst, but couldn't find any advice about what paths or env vars to 
set additionally. Or do I need special arguments on the command line?


Thanks a lot in advance,

Dirk

___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Using SCons via bootstrap.py

[Gary Oberbrunner]

I assume you do have a SConstruct in /home/dirk/tmp/boottest?

Basically, "python .../bootstrap.py" should work just like saying "scons"
except you don't have to have SCons installed.


On Wed, May 22, 2013 at 3:10 PM, Dirk Bächle  wrote:

> Hi,
>
> I started to fix bootstrap.py, such that the parseManifestLines() doesn't
> need os.chdir() anymore. After the rewrite, the local call "python
> bootstrap.py" works fine again...so far, so good.
> But I'm not able to figure out how to call it from a different folder.
>
> I even switched back to revision "018709cfd9f4" (merge of pull request
> #66, +1), but when I call
>
>   python /home/dirk/workspace/scons_**dirkbaechle/bootstrap.py
>
> from "/home/dirk/tmp/boottest", all I get is:
>
> ==**===
>
> dirk@ubuntu:~/tmp/boottest$ python /home/dirk/workspace/scons_**
> dirkbaechle/bootstrap.py
> /usr/bin/python /home/dirk/workspace/scons_**dirkbaechle/bootstrap/src/**
> script/scons.py
>
> scons: *** No SConstruct file found.
> File 
> "/home/dirk/workspace/scons_**dirkbaechle/bootstrap/src/**engine/SCons/Script/Main.py",
> line 905, in _main
> dirk@ubuntu:~/tmp/boottest$
>
> ==**===
>
> Any pointers about what I'm doing wrong are welcome. I checked the
> README.rst, but couldn't find any advice about what paths or env vars to
> set additionally. Or do I need special arguments on the command line?
>
> Thanks a lot in advance,
>
>
> Dirk
>
> __**_
> Scons-dev mailing list
> Scons-dev@scons.org
> http://two.pairlist.net/**mailman/listinfo/scons-dev
>



-- 
Gary
___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

Re: [Scons-dev] Using SCons via bootstrap.py

[Dirk Bächle]

On 22.05.2013 22:15, Gary Oberbrunner wrote:

I assume you do have a SConstruct in /home/dirk/tmp/boottest?

Basically, "python .../bootstrap.py" should work just like saying 
"scons" except you don't have to have SCons installed.



I really didn't know that, thanks for helping me out Gary. :)

I'm preparing the pull request right now...

Dirk


___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev