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/
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?
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 gi
Is there a reasons for using constructs like:
open(dst, 'wb').write( open(src, 'rb').read() )
in for loops in bootstrap.py rather than using shutil.copyfile ?
--
Russel.
=
Dr Russel Winder t: +44 20 7585 22
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
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 you
