In fact, the only real case I can think of is a command which identifies all libs listed in LIBS, store them in a file and provide that file to the linker. Which is actually pretty much what the MSVC builder is doing, I suppose, but I didn't look into this code yet. My question was rather a theoretical one: Is this ok to rely only on the command rather than on a real dependency identification and comparison. This seems even stranger since dependencies are properly known (and was indeed mentioned in issue 2903: "it is not relinked *whereas* scons --tree=all shows the the correct dependencies).
Le 16 sept. 2013 à 01:18, Gary Oberbrunner <[email protected]> a écrit : > > On Sun, Sep 15, 2013 at 9:30 AM, <[email protected]> wrote: > 1) I hack the default SharedLib builder in SCons/Tool/__init__.py in order to > set a build command which does not change when LIBS changes: > > That part is what SCons usually counts on to handle differences in dependency > names. Do you have a real case where you have such a build command? (i.e. > one that doesn't mention the names of the sources, or has to remove them from > the signature with $(...))? There may be some other way to get those names > into the signature. > > -- > Gary > _______________________________________________ > Scons-dev mailing list > [email protected] > http://two.pairlist.net/mailman/listinfo/scons-dev
_______________________________________________ Scons-dev mailing list [email protected] http://two.pairlist.net/mailman/listinfo/scons-dev
