Sorry, I didn't understand. This is used like this right:
scons CCFLAGS=-"-O3 -w" ...
No. Say, you specified CCFLAGS in one run, and do not want to use it
the next time, you do
scons load_options=-CCFLAGS
Other options will be loaded as usual.
Bo
Abdelrazak Younes wrote:
Bo Peng wrote:
All is fine now, except that the CCFLAGS of previous mingw build is
restored for the msvc build. I guess this is unavoidable and a "del
env.cache" solves the problem anyway.
I implemented load_option=-opt1,opt2 and load_option=opt1,opt2 . The
first one m
Bo Peng wrote:
All is fine now, except that the CCFLAGS of previous mingw build is
restored for the msvc build. I guess this is unavoidable and a "del
env.cache" solves the problem anyway.
I implemented load_option=-opt1,opt2 and load_option=opt1,opt2 . The
first one means do not load opt1, opt
All is fine now, except that the CCFLAGS of previous mingw build is
restored for the msvc build. I guess this is unavoidable and a "del
env.cache" solves the problem anyway.
I implemented load_option=-opt1,opt2 and load_option=opt1,opt2 . The
first one means do not load opt1, opt2,, the second o
Bo Peng wrote:
> I have problems with either mingw or msvc:
>
I cannot reproduce bug 1.
Sorry, my fault! I forgot to call scons in a MSVC2005 console.
Could you svn update and see if the fix for
bug 2 fixes bug 1?
All is fine now, except that the CCFLAGS of previous mingw build is
restor
> I have problems with either mingw or msvc:
>
I cannot reproduce bug 1. Could you svn update and see if the fix for
bug 2 fixes bug 1?
Bo
The second one is easy, please apply the following patch. Still
checking the first one.
Index: development/scons/SConstruct
===
--- development/scons/SConstruct(revision 14113)
+++ development/scons/SConstruct(working
