[Scons-dev] Tool order

[Kenny, Jason L]

Order is very important in Scons with the way some tools are defined, or when tools tend to rely on common tools. For example Fortran and c compiler tend to depend on the same linker. If the linker is defined with a C bias it makes it hard to set up fortran builds. More so when you have a mix of c and fortran in the same environment.

For example intelc and gcc have to defined in the correct order else the gcc will be used as CC not icc.

I also have found the gnulink is order dependent to help it make sure it does certain things correctly. 

As a general note with tool. I have found as I have been reworking some tools in Parts, I found that it work better for me to make sure a tool sets stuff up, and any logic that might be needed, is pushed off to later. I also found it best to not chain tools whenever possible. This greatly helps the ability to configure toolchains with different tools independently. 

I tend to find if the tools are independent of each other for example a zip builder can be setup independently of a C compiler, in cases like these order does not mater.

Jason

-----Original Message-----
From: scons-dev-bounces at scons.org [mailto:scons-dev-bounces at scons.org] On Behalf Of Russel Winder
Sent: Sunday, November 11, 2012 3:44 AM
To: SCons_Developers
Subject: [Scons-dev] Tool order

When specifying a tool chain is the order important? For example,
should:

        Environment(tools=['gdc', 'gnulink'])

be the same or different from:

        Environment(tools=['gnulink', 'gdc'])

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