honold
4th November 2002 23:23 UTC

makensis fails w/nsis2 from cli
my installer distfiles are located on a network share, which could be mounted with \\server\sharename or mounted as a drive. in either case, all one has to do to generate an installer is double-click the binary i made that calls makensis-bz2.exe - which is located in that directory.

this enables the developers to be able to generate installers with a script (or do it as needed) without having to have nsis installed on their own machines.

i just tried out nsis2, and makensis.exe fails when run from a network share when it looks for plugins. copying the plugins directory to the network share did not help, not did specifying /noconfig / etc. any ideas? could this be a bug?

Dick4
5th November 2002 04:04 UTC

I do something very similiar using vbscript to copy files into a certain directory (again, on a network share) and making an NSIS to distribute these files. I believe I had a problem where if my paths were not absolute in the .NSI script, I had to either make them absolute or set my working directory for the script. I dont' remember exactly but I'll check at work tomorrow, but look at that.

kichik
5th November 2002 15:29 UTC

What version of NSIS 2 are you using?
Pleaes attach the compiler output.

honold
7th January 2003 17:34 UTC

i don't know at what point it changed, but things now work as they did in 1.98 with 2.0b0 :)