[Scons-users] What is the difference between Variables and Options

[William Blevins]

On Sun, Jan 3, 2016 at 11:34 PM, William Blevins <wblevins001 at gmail.com>
wrote:

> Bill,
>
> As you already said, I think it would be a good idea to have some "big
> picture" explanation in the introduction that covers core SCons artifacts
> and maybe contains some diagrams about how SCons artifacts interact.
>
> Those artifacts would include builders (actions), scanners, emitters,
> nodes, etc. I think this would be extremely helpful even for more
> intermediate user's like myself. I think Dirke started a wiki page for this
> at one point, but I don't know if it ever got traction. Let me look for it.
>

Victory!! https://bitbucket.org/scons/scons/wiki/BasicConcepts


>
> V/R,
> William
>
> On Sun, Jan 3, 2016 at 10:39 PM, Bill Deegan <bill at baddogconsulting.com>
> wrote:
>
>> Stefan,
>>
>> It really depends if you're a depth first or breadth first learner how
>> much it would help/hurt learning SCons to dig into the architecture first.
>>
>> I started using Cons (the perl forerunner to SCons) and learned via an
>> existing build system and it's documentation.
>> The SCons came along and the docs were much better..
>> Of course there's always room for improvements (and pull requests.. ;)
>>
>> -Bill
>>
>> On Sun, Jan 3, 2016 at 2:27 PM, Stefan Seefeld <stefan at seefeld.name>
>> wrote:
>>
>>> On 03.01.2016 17:20, William Blevins wrote:
>>> >
>>> >
>>> > On Sun, Jan 3, 2016 at 10:13 PM, Bill Deegan
>>> > <bill at baddogconsulting.com <mailto:bill at baddogconsulting.com>> wrote:
>>> >
>>> >     Stefan,
>>> >
>>> >     I think of a user guide as a low depth document and a reference
>>> >     guide and/or manpage as the depth document.
>>> >     So when I'm not sure about the details in the user guide I look to
>>> >     a reference guide or manpage.
>>> >     This is a pretty typical pattern.
>>> >
>>> >     We've not heard much (if any) other requests for such cross
>>> >     referencing.
>>> >     If you'd like to create a pull request to demonstrate more fully
>>> >     what you're suggesting, please feel free.
>>> >
>>> >     It does sound like perhaps there should be a section in the user
>>> >     guide with more foundational information, what's a builder, what's
>>> >     an action, whats a scanner,etc.
>>> >     Or perhaps you can file a doc bug for the specific example above
>>> >     and we'll see what we can do.
>>> >
>>> >
>>> > Yes, I think this would be useful. I have also thought about need a
>>> > section in the introduction that describes key SCons constructs and/or
>>> > paradigms. I find that the SCons mailing list gets a lot of questions
>>> > that I would consider to be about basic architecture. This might help
>>> > with that,
>>>
>>> I just noticed the "Design" document (e.g.
>>> http://www.scons.org/doc/2.4.1/HTML/scons-design/), which isn't linked
>>> to from the website. I think that contains useful bits that might be
>>> used for that, at least as a starting point.
>>>
>>>         Stefan
>>>
>>> --
>>>
>>>       ...ich hab' noch einen Koffer in Berlin...
>>>
>>> _______________________________________________
>>> Scons-users mailing list
>>> Scons-users at scons.org
>>> https://pairlist4.pair.net/mailman/listinfo/scons-users
>>>
>>
>>
>> _______________________________________________
>> 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/20160103/af99e291/attachment-0001.html>