[sldev] where's SCons getting the compiler string
Dana Fagerstrom
Dana.Fagerstrom at Sun.COM
Fri Jul 20 11:26:12 PDT 2007
Hmmm... Do I even dare asking if people would like to switch to make?
I recall seeing a "makefile" patch being offered a while back. Hey, I'm
only asking :)
I'm now studying the differences between the 1.16.0 and 1.18.0
SConstructs. The cause has to be a change in that file since I have not
changed the version of SCons on my system. If I have to I'll dive into
the SCons source - been there and you are right, it's UGLY.
Thanks,
D
> Dana Fagerstrom wrote:
>> This is more for Linux folks. I know most of you have never seen this
>> because you only have one compiler installed on your build systems but
>> ever since 1.17.0 I've been having trouble getting SCons to use the
>> gcc_bin defined in my SConstruct file. Instead it insists on using
>> the default compiler on Solaris, CC instead of g++.
>
> Unfortunately, the guy who switched us over to SCons left the company
> several months ago. I'm probably the person who knows most about it
> now, and I don't know the answer to your question. I'm pretty sure
> you'll need to look at the SCons internals to figure it out. Good luck
> with that - the code is horrible :-(
More information about the SLDev
mailing list