![]() |
Setup with a single command line argument
Hi again,
Probably this is how the actual ${GetOption} command works, but I wanted to be sure. Let's assume my installer parses the command line arguments passed when executed and it searches for this flag option "/argument1". code: If I execute the installer and pass the /argument1234 it detects that /argument1 was passed. Is there a way to avoid this situation? Thanks, Isa |
use GetParameters
|
I'm not sure what do you mean by ${GetParameter}.
I'm using it to get the command line arguments into my $cmdLineParams variable. |
use the /argument=1 then StrCmp $R0 1
|
That could be a solution but it's more fashion way to have a simple flag (without any value). If this is not possible then I will consider using this.
Thanks, Isa |
Quote:
Maybe I have choosed a bad name for the argument. My point is that if you want to have just a flag to be passed as the argument, when you pass as argument a string that begins with your flag the NSIS will consider the flag present it's like the argument you are passing is somehow truncated. |
If you want to match /argument1 exactly then you'll have to also check $R0 is an empty string.
Stu |
Quote:
Again thanks for your help. |
| All times are GMT. The time now is 17:40. |
Copyright © 1999 - 2010 Nullsoft. All Rights Reserved.