[Scons-users] Order of execution of a one-file builder

[Javier Llopis]

Thank you so much!

I don't think adding the signing functionality to the NSIS builder works for me because, in addition to the code I have shown, the build system creates a DLL and several different executables that should also be signed, not only the installer. I would like a more general purpose tool that can sign any eligible file I create and that is available for future projects.

J

----------------------------------------
From: Mats Wichmann <mats at wichmann.us>
Sent: 11/23/22 4:38 PM
To: SCons users mailing list <scons-users at scons.org>, javier at llopis.me
Subject: Re: [Scons-users] Order of execution of a one-file builder
On 11/23/22 09:18, Bill Deegan wrote:
> env.Sign = Action(....)
>
> But as I said earlier a better solution would be to change your
> Installer builder to optionally do the signing Action.

Or perhaps a bit more formally, use AddMethod() to add it - but I'll
agree with Bill, don't add it if there's another, more direct, way.

>
> On Wed, Nov 23, 2022 at 4:25 AM Javier Llopis
> > wrote:
>
> I'm exploring creating an Action instead of a builder. Is there any
> way I can give a name to my Action, just like the built-in actions
> "env.Chmod" or "env.Copy" have? If possible, I'd like my action to
> be called "Sign", so the code would like AddPostAction(installer,
> env.Sign)
>
> TIA
> J


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20221123/9f365b12/attachment.htm>