Re: Get a list of emitted targets from the previous run

Hi Bill

I'm parsing in process using the pyang library. The reason for parsing in
the emitter phase is because other files include the generated headers. The
generated c++files are given as sources to the library builders.  That's is
why I do this in the emitter phase to declare all files that Will je
generated and get the dependency tree right

Cheers

Erik

Op di 15 jun. 2021 18:26 schreef Bill Deegan <[email protected]>:

> Erik,
>
> Why are you parsing the file in the emitter phase?
> Also, please tell me that you're not doing your generation in process, but
> rather shelling out to a python (or other script) to generate..
>
> -Bill
>
> On Mon, Jun 14, 2021 at 11:56 PM Erik Kazandjian <
> [email protected]> wrote:
>
>> Hi,
>>
>> In our project we have added some custom builder (with emitters and
>> actions) to parse yang files and generate C++ out of that. As more and more
>> yang files are added and getting complexer I would like to have the
>> possibility (with a command line option) to by pass this yang parsing in
>> the emitter pagase. Of course if I woud just return [], source in my
>> emitter all my SConscripts would see the generated targewts as empty and
>> create empty libraries (which gives linker issues). So my question is,
>> suppose I have this command line option activated, is there a way to see
>> which targets were emitted in the previous build so I can return them
>> without having to do the yang analysis.
>>
>> Regards
>>
>> Erik
>> _______________________________________________
>> 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
>

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