Setting the Path for the third party software by NSIS Script

Hi,

I am using the third party software's in my application. I need to set the path for the third party software through N SIS. In which path my application is installed, that path i need to set for the third party software. If anybody knows kindly let me know.

Well this depends entirely on the installer used for that third party software, don't you agree?

thanks for your reply

I agree that, but i am new to N SIS. I didn't have much knowledge about the N SIS. It may be possible, if some one can implemented then i can use that. So only i posted here.

Well the point is that it's impossible to answer your question without knowing what kind of third party software we're talking about. It's not like there's a magic, generally applicable method to make random installer software do an automatic install to some specified directory.

It depends on how and where that third party software would be expecting the path to your application.

For example it might use the registry (see: WriteRegStr), or it might use an INI file (see: WriteIniStr), or... etc. If you know what it uses to figure out where your application is, then going forward is a lot easier 😉

Originally Posted by MSG View Post

Well the point is that it's impossible to answer your question without knowing what kind of third party software we're talking about. It's not like there's a magic, generally applicable method to make random installer software do an automatic install to some specified directory.

I want to install the Mingw through my application. User want's to click the next button, my application path wants to set for the Mingw. I need to do this mingw installation as silent installation with out user interference.

Well according to notes on AppDeploy, MingW uses NSIS. However, their installer has not been written properly and /S will not work (it appears to download files normally but they've probably done this in page callbacks - oops!) However the notes on AppDeploy are from 2008 so things may have changed since. Try running the installer with /S and see how it goes. If that works, you can use the /D switch as well (see NSIS manual for installer command line options) and you can use ExecWait.

Stu