This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: My installer is not allowing the -V flag
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
May 09, 2006
04:04 PM
My installer is not allowing the -V flag
I have created an installer on linux for a product on linux. In it, I have created a custom question dialog with a file browser in it. The installer and user interface work fine except I can't seem to preload the value of the variable for my file browser from the command line. When I execute the installer as follows:
./setuplinux.bin -V DATA_DESTINATION="/tmp/mydata"
I get the following error:
The wizard cannot continue because of the following error: Invalid command line option: V is not supported (1001) (403)
The documentation all seems to indicate that the -V option is how I should set the variable from the command line, but the error indicates it is not supported. What gives? Is there something else I should do?
./setuplinux.bin -V DATA_DESTINATION="/tmp/mydata"
I get the following error:
The wizard cannot continue because of the following error: Invalid command line option: V is not supported (1001) (403)
The documentation all seems to indicate that the -V option is how I should set the variable from the command line, but the error indicates it is not supported. What gives? Is there something else I should do?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
May 10, 2006
11:23 AM
Nevermind, I figured it out. I needed to add the following line to my project.uip file in the appropriate place:
I am not sure why it didn't get put there automatically when the project was created. But it is now a FYI if someone else sees the problem.
I am not sure why it didn't get put there automatically when the project was created. But it is now a FYI if someone else sees the problem.