Re: Non Construction steps in Scons

Not sure why you'd expect there to be built in solutions for every problem..
SCons is a make replacement. Does make pre-package all logic for all
things? Nope
In fact in includes far less canned logic.

SCons expects builders to read files and write files.
The datestamp is a hack around that.
The target is needed to know when the builder should be rerun..

Your script is really unnecessary complicated, you can do all this inside a
SConstruct. (and certainly you should never call SCons from within SCons in
the same dir)
It can have regular python logic in addition to builders.

As Mats said there's a contributed doxygen builder you can use for that,
and that would handle cleaning as well.

-Bill



On Sun, May 15, 2022 at 2:16 PM Bill Deegan <[email protected]>
wrote:

> Re step 2:
> Then use env.Command().. which is what you should use when you don't want
> a full fledged builder.
> Not sure why this is a big deal...
> In the user guide.. it's even the title of the chapter about using
> env.Command()
>
> https://scons.org/doc/production/HTML/scons-user.html#chap-builders-commands
> "Not Writing a Builder: the Command Builder"
>
> On Sun, May 15, 2022 at 11:53 AM Mats Wichmann <[email protected]> wrote:
>
>> On 5/14/22 17:28, Bill Deegan wrote:
>>
>> > step 3 - not quite perfect fit, but what I would do is create a output
>> > file with a timestamp after you flash the board, env.Command() can do
>> > this, you can list 2 command, one is flash the board, second is create a
>> > timestamp file.
>>
>> Value Node of any use here?
>> _______________________________________________
>> Scons-users mailing list
>> [email protected]
>> https://pairlist4.pair.net/mailman/listinfo/scons-users
>>
>

_______________________________________________
Scons-users mailing list
[email protected]
https://pairlist4.pair.net/mailman/listinfo/scons-users