[Scons-users] Librarian tool

[Gary Oberbrunner]

On Tue, Jan 21, 2014 at 1:16 PM, Russel Winder <russel at winder.org.uk> wrote:

> On Tue, 2014-01-21 at 17:34 +0000, Kenny, Jason L wrote:

>> I personally have thought of this myself. I think this currently is

>> viewed as a tool in SCons. I personally thought of having a library

>> directory in Parts as I thought this would help separate stuff better.

>> I have not done this myself. The other point of view here might be

>> that this is a what the configure stuff should do, as this is a common

>> way it is used in a classic makefile way.

>>

>> I personally like the idea of being able to apply to the environment a

>> tool and or library and have it configured correctly.

>

> I have to admit I think the core problem is that SCons assumes you are

> using C or C++ (with Fortran tacked on) and that you will use the

> default set up – which is basically a hardwiring of a subset of the

> tools. In effect the other tools are a hack add on.

>

> I have given up on trying to have a separate D tooling and am grafting

> in D support more along the lines of C++ and Fortran. However this is

> clearly a fundamentally failing strategy as the smart_linker function

> will become so complicated it will fail under its own weight!


I've actually been working on a core enhancement, a SwitchAction which
is like a ListAction but only executes one of the listed actions based
on a predicate. I think if we replaced smart_linker with this, it
would be extensible in the ways you need, or at least it's a part of
the solution to that problem.

-- 
Gary