Old 27th September 2010, 20:08   #1
bobbycim
Junior Member
 
Join Date: Sep 2010
Posts: 4
Should be simple, but...

I am pretty much clueless when it comes to scripting.

Here is what I am trying to do:

I have 5 different software installations of different products that I am trying to condense into a single installer package to increase user-friendliness of the installation. Most of them are just single .exe or .msi files, but a couple have more files involved. All I really need to do is wrap all of these packages up into an exe file, and when the end user runs it, have it copy these installation files into a temporary folder on their machine and run a batch file that will install all of them one after another. Not sure if NSIS is what I need to be able to do this.

Anybody have any suggestions?

Thanks so much!
bobbycim is offline   Reply With Quote
Old 27th September 2010, 20:38   #2
Animaether
Major Dude
 
Join Date: Jun 2001
Posts: 1,173
read the documentation - everything is in there.. just to give you a very basic skeleton to work with:

PHP Code:
OutFile "c:\myInstaller.exe" /* where to save the installer you build */

Section
  SetOutPath 
"$TEMP/* where to write a file on the user's machine */

  
File "c:\someInstaller.exe" /* installer you're wrapping, will be written to the path set above */
  
ExecWait "$TEMP\someInstaller.exe" /* execute that installer, wait for it to exist */

  
File "c:\someOtherInstaller.exe"
  
ExecWait "$TEMP\someOtherInstaller.exe"
SectionEnd 
Depending on your exact needs, tweak from there.
Animaether is offline   Reply With Quote
Old 27th September 2010, 21:39   #3
redxii
Senior Member
 
Join Date: Nov 2005
Posts: 115
I'd use $PLUGINSDIR instead, that way the installer doesn't leave files.
redxii is offline   Reply With Quote
Old 27th September 2010, 21:47   #4
Animaether
Major Dude
 
Join Date: Jun 2001
Posts: 1,173
can do that (call InitPluginsDir first) - the reason I stick third party installers in TEMP is that in the past, some of them allow a user to only install some features.. then the user goes to use the application, hits some feature almost immediately that needs an additional install, and the original app can't find the installer anymore (I think all of the MSI ones now copy the package to the windows installers store thing, so not an issue for those so much). Placed in $TEMP, it'll be available until the user (or some utility) clears out temporary files.

Depends on one's needs, really
Animaether is offline   Reply With Quote
Old 28th September 2010, 12:02   #5
bobbycim
Junior Member
 
Join Date: Sep 2010
Posts: 4
Thanks so much for all of the help, everyone!!
bobbycim is offline   Reply With Quote
Reply
Go Back   Winamp & Shoutcast Forums > Developer Center > NSIS Discussion

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump