Re: [Scons-dev] Where does scons determine the dependencies for object files?

2018-04-14 Thread Andrew C. Morrow
Thanks Gary - After some exploration down this path, Bill Deegan pointed out that using a generator would achieve the hoped for behavior without so much difficulty, if we paid attention to the for_signature flag. I've implemented that and it works well. You can see an example of the code here: ht

Re: [Scons-dev] Where does scons determine the dependencies for object files?

2018-03-25 Thread Gary Oberbrunner
>From a quick perusal of the source, I think the function you're looking for is SCons/Node/__init__.py, Node.add_source(). That's called from Builder._execute(). On Sun, Mar 25, 2018 at 2:05 PM, Andrew C. Morrow wrote: > > Could you point me to where in the SCons sources that connection between

Re: [Scons-dev] Where does scons determine the dependencies for object files?

2018-03-25 Thread Andrew C. Morrow
Could you point me to where in the SCons sources that connection between foo.o and foo.c is made, exactly? I'd like to understand how it happens. Regarding pseudo-builders: they don't compose, unfortunately. Once something becomes a pseudo-builder it no longer exposes the attributes that normal bu

Re: [Scons-dev] Where does scons determine the dependencies for object files?

2018-03-25 Thread Gary Oberbrunner
The builder, in this case Object(), sets up the dependency between foo.o and foo.c. The simplest way to do what you want is to create a pseudo-builder that calls Object() and also calls Depends(). -- Gary On Sun, Mar 25, 2018 at 1:07 PM, Andrew C. Morrow wrote: > > I'm fairly clear on where SCo