Is it possible to get additional parameters for the Inno Setup Action? I need this to pass some defines to the setup pre-processor.
Thanks,
Ulrik S.
Hi Ulrik,
At the moment we’re limited by the fact that we’re actually calling the Inno DLL, and it doesn’t seem like you can easily pass in defines.
We’ll add a “Inno Command Line” action to the to-do list. In the meantime, you can get the same functionality by using the Execute Program action.
- Angus
No hurry, I’m already using the Execute Program action. But it would be nice with a Inno Command Line action so I can reuse the Inno path from FinalBuilder settings.
I’d be interested in that as well, mainly so I could use the {param:ParamName|DefaultValue} to pass stuff like version numbers etc. to the script.
Hi Michael,
Just for the record, the way that we’re doing the same thing is by having a “template” ISS file with some FinalBuilder variable references in it (ie %VersionNo%.) Then, at build time, we use a Replace Variables action to read the “template” file, replace the variables with their current values, and then write that out to a -new- ISS file which is then built by Inno Setup.
Nevertheless, we’ll look into doing a new command-line-based Inno action in future.
Regards,
Angus
I considered using a template as well. However, right now I am using InnoSetup with the ISPP extensions, which allows me to pass defines to the script, and that works great.
Also, just to avoid confusion for anyone reading this, I noticed after my previous post that the “/param” option actually applies only to the generated setup itself, NOT the compiler, so that would not have worked anyway.