them nodes. Add a Glob(‘*’) call and you will see all items in
the current directory
Jason
From: Scons-dev [mailto:scons-dev-boun...@scons.org] On Behalf Of Gary
Oberbrunner
Sent: Wednesday, June 3, 2015 6:31 AM
To: SCons developer list
Subject: Re: [Scons-dev] How to traverse the graph after files
On Wed, Jun 3, 2015 at 2:30 PM, Gary Oberbrunner wrote:
> On Wed, Jun 3, 2015 at 6:54 AM, anatoly techtonik
> wrote:
>>
>> But I have plenty of other files in current directory. Why those are
>> not included?
>>
> At the end of reading the SConstruct, i.e. before the build phase begins,
> SCons o
On Wed, Jun 3, 2015 at 6:54 AM, anatoly techtonik
wrote:
> But I have plenty of other files in current directory. Why those are
> not included?
>
> At the end of reading the SConstruct, i.e. before the build phase begins,
SCons only creates Nodes for files it has been told about. I think if you
But I have plenty of other files in current directory. Why those are
not included?
On Wed, Jun 3, 2015 at 1:44 PM, Gary Oberbrunner wrote:
> Because it is a child of "." (the top dir) -- Dir nodes have all their
> existing and to-be-generated files as children.
>
> On Wed, Jun 3, 2015 at 2:10 AM,
Because it is a child of "." (the top dir) -- Dir nodes have all their
existing and to-be-generated files as children.
On Wed, Jun 3, 2015 at 2:10 AM, anatoly techtonik
wrote:
> Interesting stuff. If I create an empty SConstruct:
>
> Entry("xxx")
>
> Then `scons --tree=all` gives a tree with
Interesting stuff. If I create an empty SConstruct:
Entry("xxx")
Then `scons --tree=all` gives a tree with SConstruct
name included into the build graph:
scons: `.' is up to date.
+-.
+-SConstruct
+-xxx
I can understand that xxx is at the root, but why
SConstruct is also
15 1:31 PM
To: SCons developer list
Subject: Re: [Scons-dev] How to traverse the graph after files are read
On Wed, May 20, 2015 at 6:51 PM, Kenny, Jason L wrote:
> [...]
Thanks for the explanation. I wrote it down to ask questions later when I get
some output with the tree.
> To get t
On Wed, May 20, 2015 at 6:51 PM, Kenny, Jason L wrote:
> [...]
Thanks for the explanation. I wrote it down to ask questions later
when I get some output with the tree.
> To get the tree you want all you have to do is grab the target list ie...
> SCons.Script.BUILD_TARGETS and for each item in
nce of a few builder objects vs ideally
1000s... 100,000 of node objects.
-Original Message-
From: Scons-dev [mailto:scons-dev-boun...@scons.org] On Behalf Of anatoly
techtonik
Sent: Wednesday, May 20, 2015 9:25 AM
To: SCons developer list
Subject: Re: [Scons-dev] How to traverse the g
On Wed, May 20, 2015 at 11:50 AM, Alexandre Feblot
wrote:
> I did such kind of traversal once: http://pastebin.com/KyEg5ngS
> Maybe that was even based on something found in the wiki.
I'm not 100% certain, but I believe calling node.children() can invoke
scanners and other things that should n
I did such kind of traversal once: http://pastebin.com/KyEg5ngS
Maybe that was even based on something found in the wiki.
2015-05-20 17:43 GMT+02:00 Gary Oberbrunner :
>
> On Wed, May 20, 2015 at 11:25 AM, anatoly techtonik
> wrote:
>
>> I want to get target Node based on name passed from comman
On Wed, May 20, 2015 at 11:25 AM, anatoly techtonik
wrote:
> I want to get target Node based on name passed from command line.
> How to do that?
>
node = File(name)
How to get list of all targets to be built? User guide:
http://www.scons.org/doc/HTML/scons-user/ch10s03.html#idp3074280
the BUI
On Wed, May 20, 2015 at 5:46 PM, Gary Oberbrunner wrote:
> On Wed, May 20, 2015 at 9:47 AM, anatoly techtonik
> wrote:
>>
>> If so, then that means that every target should
>> be a filesystem object?
>>
>> What is target then? If it is a name, how a lookup if made to locate it in
>> FS tree?
>
>
On Wed, May 20, 2015 at 9:47 AM, anatoly techtonik
wrote:
> If so, then that means that every target should
> be a filesystem object?
>
> What is target then? If it is a name, how a lookup if made to locate it in
> FS tree?
>
Every target (and source, and intermediate) is a Node. The Node objec
On Wed, May 20, 2015 at 4:59 PM, Kenny, Jason L wrote:
>>>Are there two separate FS objects for that?
>
> No there is one global fs that is shared with all environment objects.
>
> After the Sconstruct are read in this will hold all nodes that are known to
> the SCons and their relationships. The
natoly
techtonik
Sent: Wednesday, May 20, 2015 8:47 AM
To: SCons developer list
Subject: Re: [Scons-dev] How to traverse the graph after files are read
On Wed, May 20, 2015 at 3:36 PM, Gary Oberbrunner wrote:
> On Wed, May 20, 2015 at 6:43 AM, anatoly techtonik
>
> wrote:
>>
>>
On Wed, May 20, 2015 at 3:36 PM, Gary Oberbrunner wrote:
> On Wed, May 20, 2015 at 6:43 AM, anatoly techtonik
> wrote:
>>
>> The confusing part is that
>> node graph is derived from filesystem.
>
>
> FS represents the filesystem, both on disk and what will exist once all
> targets are built.
Are
On Wed, May 20, 2015 at 6:43 AM, anatoly techtonik
wrote:
> The confusing part is that
> node graph is derived from filesystem.
>
FS represents the filesystem, both on disk and what will exist once all
targets are built.
I didn't say start from the filesystem, I said start from your target(s).
On Wed, May 20, 2015 at 10:26 AM, Dirk Bächle wrote:
> On 20.05.2015 09:01, anatoly techtonik wrote:
>> On Tue, May 19, 2015 at 3:19 PM, Gary Oberbrunner
>> wrote:
>>>
>>> At the end of your SConstruct, start with the target nodes and recurse
>>> into
>>> each node.sources .
>
>
> the "recurse in
Hi all,
On 20.05.2015 09:01, anatoly techtonik wrote:
On Tue, May 19, 2015 at 3:19 PM, Gary Oberbrunner wrote:
At the end of your SConstruct, start with the target nodes and recurse into
each node.sources .
the "recurse into" is what's important here, Anatoly.
[...]
But the logic what ha
On Tue, May 19, 2015 at 3:19 PM, Gary Oberbrunner wrote:
> At the end of your SConstruct, start with the target nodes and recurse into
> each node.sources . This is incomplete of course if you have any source
> generation or emitters etc. But it may be useful depending on what you're
> doing.
I a
At the end of your SConstruct, start with the target nodes and recurse into
each node.sources . This is incomplete of course if you have any source
generation or emitters etc. But it may be useful depending on what you're
doing.
--
Gary (sent from my Android)
On May 19, 2015 3:58 AM, "anatoly tec
So far I discovered Taskmaster.
Taskmaster
This is the main engine for walking the dependency graph and
calling things to decide what does or doesn't need to be built.
But it looks like it already needs a graph of nodes to process and
I don't see where to get them.
On Tue, M
No. I need a programmatic way to do this from Main.py
There is a fs object after SCons read all files, but I don't
understand how filesystem becomes a build graph.
On Tue, May 19, 2015 at 1:03 AM, William Blevins wrote:
> --tree=all plus --dry-run should work?
>
> On May 18, 2015 2:11 PM, "anato
--tree=all plus --dry-run should work?
On May 18, 2015 2:11 PM, "anatoly techtonik" wrote:
> Hi,
>
> I am trying to get SCons build graph after files
> are read, but before the processing is started.
>
> I want it to be an alternative to build process
> and interactive mode:
>
> https://bitbucket
Hi,
I am trying to get SCons build graph after files
are read, but before the processing is started.
I want it to be an alternative to build process
and interactive mode:
https://bitbucket.org/scons/scons/src/95b566e4baf0253e1b36b8a9e00a97cd84d22566/src/engine/SCons/Script/Main.py?at=default#cl-1
26 matches
Mail list logo
