The Master
29th May 2001 17:32 UTC

Was working on a new NSIS installer today, and ran into another issue.

NSIS doesn't like it if you specify a wildcard File option that returns no files. My case is a database installer for an app I'm writing. 99% of the time, there will be files in subdirectory "sop", but that 1% of the time there won't. NSIS complains about no files and dies. Instead, it should be allowed to fail gracefully, since that simply means there's nothing to install this go-around. IE:

File sop\*.sop <-- right now this fails if sop directory is empty.

File /i sop\*.sop <-- my suggestion-the /i flag will ignore the empty sop directory and keep going.

saivert
30th May 2001 11:48 UTC

Hold your horses!
Hey you! You must differenciate between compile time and run time command. Firstly: File is a runtime command and you didn't tell whether or not your error happended during installataion while running your NSIS installer program or if it happended during compile of a .nsi script.

Please provide more info on this and I can help you.

The Master
30th May 2001 13:04 UTC

File command
This was a compile-time issue. Guess I overlooked stating that :)