[Scons-users] Grouped dependency
William Blevins
wblevins001 at gmail.com
Tue Apr 26 09:27:44 EDT 2016
Dirk,
You could do that as long as only the first source made it to the
commandline, though its ugly.
You certainly cannot do Depends(A, B), Depends(A, C), Depends(B, A),
Depends(B, C), Depends(C, A), Depends(C, B).
V/R,
William
On Tue, Apr 26, 2016 at 8:09 AM, Dirk Bächle <tshortik at gmx.de> wrote:
> Hi,
>
> On 26.04.2016 01:51, William Blevins wrote:
>
>> Arvid,
>>
>> You cannot make them all depend on each other because that will create
>> dependency cycles.
>>
>
> hmmm, is that really true? What if Arvid would write his own Object
> builder, taking a list of sources as argument...but it would always only
> process the first list entry to actually produce (=emit) an object?
> Then one could wrap this into an ObjectGroup pseudoBuilder, such that on
>
> ObjectGroup(['a.cpp','b.cpp','c.cpp'])
>
> it would internally call
>
> ArvidsObject('a.o', ['a.cpp', 'b.cpp', 'c.cpp'])
> ArvidsObject('b.o', ['b.cpp', 'a.cpp', 'c.cpp'])
> ArvidsObject('c.o', ['c.cpp', 'b.cpp', 'a.cpp'])
>
> . As long as all source files initially exist and don't have to be
> generated by SCons itself this could actually work.
>
> Just a quick gedankenexperiment...
>
> Best regards,
>
> Dirk
>
>
> _______________________________________________
> Scons-users mailing list
> Scons-users at scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20160426/fdbac506/attachment.html>
More information about the Scons-users
mailing list