Subject | Installer problems |
---|---|
Author | Jason Wharton |
Post date | 2004-11-27T20:42:40Z |
I think the installer problems people have been having is due to long file
names and how AddQuote() in my installer script puts double quotes around
things. In all the research I've done on this issue it boiled down to how
the CMD session handling the command to compile was processing the request.
Apparently only two, and only two quotes are allowed on the command line for
a CMD /C session and those quotes are only allowed around an executable file
reference.
So, I need to figure out a way to do my stuff in a CFG file rather than
having a big long command line with switches that have paths that need
double quotes around them.
Unless someone else knows more about this stuff than I do and can suggest
another alternative, I'll just keep pushing my way through this until I get
a solution that will work on everyone's machines.
Jason Wharton
www.ibobjects.com
names and how AddQuote() in my installer script puts double quotes around
things. In all the research I've done on this issue it boiled down to how
the CMD session handling the command to compile was processing the request.
Apparently only two, and only two quotes are allowed on the command line for
a CMD /C session and those quotes are only allowed around an executable file
reference.
So, I need to figure out a way to do my stuff in a CFG file rather than
having a big long command line with switches that have paths that need
double quotes around them.
Unless someone else knows more about this stuff than I do and can suggest
another alternative, I'll just keep pushing my way through this until I get
a solution that will work on everyone's machines.
Jason Wharton
www.ibobjects.com