changing the version number via command line

Fuzzybunny · 24th January 2007, 19:51

Hi all, I've only looked at this install program for a couple days. I'd like to be able to modify the parameters VIProductVersion and VIAddVersionKey via the command line when we build an install. I've looked through the forums and help files but I haven't found anything yet. Any help would be greatly appreciated.

kichik · 24th January 2007, 19:55

You can pass VIProductVersion and VIAddVersionKey on the command line using the /X command line parameter. You could also define a constant using /D and use its value in either of those.

code:
makensis /X"VIProductVersion 1.2.3.4"

code:
makensis /DVERSION=1.2.3.4

# in script

VIProductVersion ${VERSION}

Fuzzybunny · 24th January 2007, 20:01

Hi! thanks for the really quick response.

When I try that i get an error saying:
"invalid VIProductVersion format, should be X.X.X.X"

Fuzzybunny · 24th January 2007, 20:04

sorry just to clarify, in the dos window when i try
makensis /X"VIProductVersion 1.2.3.4"

I get Invalid command: VERSION

when I try
makensis /DVERSION=1.2.3.4

I get invalid VIProductVersion format, shoudl be X.X.X.X

Fuzzybunny · 24th January 2007, 20:37

ah i got it, I can't have the script say VIProductVersion $(VERSION). If I comment or remove the line and use:
makensis /X"VIProductVersion X.X.X.X path
that works.

Thanks for the help!

Comm@nder21 · 25th January 2007, 11:33

you got a typo:

VIProductVersion $(VERSION) is wrong
VIProductVersion ${VERSION} is correct.

with the last one you can use the /D switch.

Fuzzybunny · 25th January 2007, 14:52

ahh thats why, silly typo. Thanks!

24th January 2007, 19:51	#1
Fuzzybunny Junior Member Join Date: Jan 2007 Posts: 22	changing the version number via command line Hi all, I've only looked at this install program for a couple days. I'd like to be able to modify the parameters VIProductVersion and VIAddVersionKey via the command line when we build an install. I've looked through the forums and help files but I haven't found anything yet. Any help would be greatly appreciated.

24th January 2007, 19:55	#2
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,338	You can pass VIProductVersion and VIAddVersionKey on the command line using the /X command line parameter. You could also define a constant using /D and use its value in either of those. code: makensis /X"VIProductVersion 1.2.3.4" code: makensis /DVERSION=1.2.3.4 # in script VIProductVersion ${VERSION} NSIS FAQ \| NSIS Home Page \| Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

25th January 2007, 11:33	#6
Comm@nder21 Major Dude Join Date: Jul 2003 Location: germany, b-w Posts: 734	you got a typo: VIProductVersion $(VERSION) is wrong VIProductVersion ${VERSION} is correct. with the last one you can use the /D switch. hand by comm@nder21 ---------- WiKi pages:CreateInternetShortcut\|Enhanced FindWindow\|Parse CSV-Data\|Open/Close CD-Drive\|Installer without Icon\|Vista application compatibility

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

24th January 2007, 20:01	#3
Fuzzybunny Junior Member Join Date: Jan 2007 Posts: 22	Hi! thanks for the really quick response. When I try that i get an error saying: "invalid VIProductVersion format, should be X.X.X.X"

24th January 2007, 20:04	#4
Fuzzybunny Junior Member Join Date: Jan 2007 Posts: 22	sorry just to clarify, in the dos window when i try makensis /X"VIProductVersion 1.2.3.4" I get Invalid command: VERSION when I try makensis /DVERSION=1.2.3.4 I get invalid VIProductVersion format, shoudl be X.X.X.X

24th January 2007, 20:37	#5
Fuzzybunny Junior Member Join Date: Jan 2007 Posts: 22	ah i got it, I can't have the script say VIProductVersion $(VERSION). If I comment or remove the line and use: makensis /X"VIProductVersion X.X.X.X path that works. Thanks for the help!

25th January 2007, 14:52	#7
Fuzzybunny Junior Member Join Date: Jan 2007 Posts: 22	ahh thats why, silly typo. Thanks!