Hi there.
It appears that when using the Inno Setup Action (“Build Inno Setup Script”) the resulting process is run from another working directory than the script it compiles.
This seems to be a problem when using the Inno Setup Preprocessor as its paths are relative to the Working Directory of the process and not relative to the script file they appear in.
The process working directory when building a Inno Setup Script should be the directory where the script resides.
(I’m using Inno Setup 5.2.3)
cheers,
Martin
Hi Martin
The Inno Setup action loads the Compiler DLL and uses it’s api to compile the project. I don’t see any way through this api to specify a working directory.
Posted By Vincent Parrett on 19 Jun 2009 02:04 AM
Hi Martin
The Inno Setup action loads the Compiler DLL and uses it's api to compile the project. I don't see any way through this api to specify a working directory.
Probably not. Can't you set the FB process working directory before calling the DLL?
Maybe it'd make more sense to fix the IS Dll side though ...
The workaround is simply to call ISCC.exe directly, which has the added benefit of being able to pass parameters to the compiler.
br,
Martin
Hi Martin
FinalBuilder is a multithreaded application, setting the current directory makes no sense, that’s why we tell user not to use relative paths and use variables instead. The reason we don’t call iscc.exe is we don’t get any progress feedback.