[Scons-users] dep defintions
bill at baddogconsulting.com
Mon Jun 15 12:09:53 EDT 2020
Generally if the target naming is predictable an emitter is used. And you'd
want to default a real builder.
(As I've previously suggested in order to add a scanner).
Is that the case? If so please let us know all the files it will generate
and perhaps we can resolve this properly.
Trying to do this the "quick" way is costing you more effort than you're
saving it seems.
On Mon, Jun 15, 2020 at 6:28 AM daggs <daggs at gmx.com> wrote:
> not sure I understand how can SideEffect improve the situation, can you
> explain please?
> > Sent: Monday, June 15, 2020 at 4:14 PM
> > From: "Mats Wichmann" <mats at wichmann.us>
> > To: scons-users at scons.org
> > Subject: Re: [Scons-users] dep defintions
> > On 6/14/20 11:27 PM, daggs wrote:
> > > Greetings Hans,
> > >
> > > Command('some/path/const.asm', './def_gen', './def_gen $TARGET'), will
> > > probably work if def_gen generates only const.asm, but it doesn't, it
> > > generates multiple const files with different entries.
> > > so unless I can do this: Command(['some/path/const.asm', 'file1',
> > > 'file2'], './def_gen', './def_gen $TARGET'), afaik, it is impossible to
> > > define multiple targets.
> > You can use SideEffect for this.
> > _______________________________________________
> > 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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Scons-users