Hi guys, I will be finishing some improvement packaging logic for Parts soon. I hope that most of this should be easy to more to SCons once this is done, after I finish validating it being use in some large products here.
I have a question on something I am not sure what is the best way to do in SCons. The issues is that with the packaging logic we need to call some build logic after we define all the code we are going to build. The reason for this delay it prevent ordering issues with files we want to add to a package after we defined the package itself. The way I have hacked this is the way I have hacked improvement in Parts to deal with stuff like RPATH handling, etc, which is via a post process queue that I call before the SCons.Script.Main._build_targets() API is called via I hook I monkey patch in. This is nice as I can still call builders on the environment and the emitter and build logic works as expected. The major negative at the moment is that these actions go off even if we are not building the primary node returned by the package API. ( I could hack this to only run the logic if the parent(s) are in the target list being built.) Ideally I would like to call this logic when we scan for the or something to add the rest of the build tree at that time, However I am not sure if this is a safe usage of the scanner to add node dynamically, or if there might be some other issue with that. So the question for someone that understand the task processing of the node tree better is.. What is the best known way to add build logic to the tree after the Sconstruct has been read? Is there a way to have Scons call delayed build definition logic to a given node to add stuff the node tree when and only when it will be built? Thanks Jason
_______________________________________________ Scons-dev mailing list [email protected] http://two.pairlist.net/mailman/listinfo/scons-dev
