[Bf-committers] Scons again...
Meino Christian Cramer
Thu, 26 Feb 2004 01:39:13 +0100 (CET)
From: Michel Selten <firstname.lastname@example.org>
Subject: Re: [Bf-committers] Scons again...
Date: Wed, 25 Feb 2004 20:57:13 +0100
I did the copying, cause I am not an expert of scons (hence my bunch
of questions... ;).
It is only a "security" option to not to "pollute" my cvs source
tree, where my cvs-update script will work on.
Just to be safe...nothing more.
With the copy I can do what I want ... even wrong things ;)
But I will try to do the manual "hacking" of a .c file here also
... it is a good idea.
Could you recommend one so I can see a change in the resulting
binary? (I have only a very very very very very very very little
knowledge of the sources... ;)
> On Wed, 2004-02-25 at 18:49, Meino Christian Cramer wrote:
> > Something I am doing wrong.
> > My build-Script does basicly as follows.
> > Copy the source tree to /tmp/.
> > cd /tmp/blender
> > scons
> > install the resulting binary
> as I've asked before, why are you copying the sources to /tmp/blender?
> The config.opts file enables you to specify the build location. I have
> the feeling that somehow you overwrite the .sconsign files which contain
> dependency information.
> Anyway, I tried the same you described. I used the commands:
> cp -R blender /tmp
> cd /tmp/blender
> worked like a charm.
> I updated a .c file in my source directory somewhere, and executed the 3
> above commands again. Again, worked like a charm.
> But most importantly, I want to know why you copy the source files to
> With regards,
> Bf-committers mailing list