Re: Bundles as targets

I'd use a variant dir and have different target dirs for debug/release/ and
possibly by version.
This would avoid that problem.
Also if you have specifica Alias()'s for building a package, you can check
for that in COMMAND_LINE_TARGETS and clean that directory explicitly in
your SConstruct via Execute(...)

As far as passing around a bundle of files, remember that all Builder()'s
return a nodelist.
-Bil

On Wed, Oct 7, 2020 at 12:42 AM Arvid Rosén <[email protected]> wrote:

> On 2020-10-06, 17:48, "Scons-users on behalf of Mats Wichmann" <
> [email protected] on behalf of [email protected]> wrote:
>  >   > Not sure why you have to wipe the target directory? doesn't  scons
> -c
>  >   > clean it for you?
>
>  >  If you change the name of a bundle member (or in fact any target),
> scons
>  >  only knows the new name and won't act on an old name. You'd have to
>  >  remember to clean-first-then-rename. That's been an irritant for me in
>  >  the past, although honestly, a pretty tiny one.
>
> Hi,
>
> Thanks for your replies!
> scons -c works, but this is a very dangerous to rely on in my case. For
> example, the binary name will differ when we build debug and release
> versions of our bundles. So it is very easy to build a debug version, test
> it, and then build a release version and send it to someone without
> realizing that the debug binary is still present. Also, passing bundles
> between different build steps is impractical when they are handled as a
> bunch of files.
>
> Cheers,
> Arvid
>
>
> _______________________________________________
> 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