Never used/studied Inno before, but what about something
like this :
function InitializeSetup(): Boolean;
for param := 0 to ParamCount do
if ParamStr(param) = '/?' then begin
help := true;
if help then begin
MsgBox('Command line switches:' #13#13
'/DIR="<instdir>"'#9'- specifies install directory' #13
'/NORESTART'#9'- do not force reboot after install' #13
'/COMPONENTS="ServerComponent,Client, ..."' #13
'/SILENT - ...',
Result := false;
It would be nice, but the command line install is an artefact of
InnoSetup. You should probably put a feature request in with
The switches are documented in the installation readme,
which is available in all installs except client-only.
The intention of the command-line setup is to allow developers
to prepare an unattended install of Firebird via a control
process (batch file or executable.) Under these circumstances
the install readme ought to be adequate documentation.
What would you suggest as a resolution of this request? I've
marked it as postponed as it wont get fixed unless we switch
from InnoSetup or InnoSetup supports the feature. Some of
the other options (Invalid, Wont fix) seem a little harsh.
As previously explained, InnoSetup doesn't support this kind of feature 'out of the box'. The original solution proposed (using a message box) suffered from a major problem. The output could not be selected and copied to the clipboard. (This is a major pain with the MsgBox format in general.)
I've finally found the time to implement a solution that does work with the clipboard. It also allows us to display the full documentation for scripting installations.
Submitted by: prenosil (prenosil)
Submitted By: prenosil
It would be nice if Firebird's official setup program
has the ability to show list of its command line switches.
E.g. when specifying /? switch, list of available switches
would be printed (instead of running setup):
C:\> Firebird-22.214.171.12406-Win32.exe /?
/DIR="<instdir>" - specifies install directory
/NORESTART - do not force reboot after install
/SILENT - ...
The text was updated successfully, but these errors were encountered: