Skip to content
⌘ NSIS Forum Archive

$exedir

9 posts

kulakshay#

$exedir

Why path created using $EXEDIR is not working...

e.g. "$EXEDIR\dir1\dir2\fil1.dll"

is not working...

what could be the problem...?
Red Wine#
$EXEDIR is the directory from where the installer is running.
So if you're referring files in $EXEDIR they have to be always in the same dir where installer resides.
kulakshay#
yes I'm doing my .nsi file is one folder...
and I've kept other files and folders in the same folder..
I want to copy them @ $INSTDIR ....
so I'm uing FILE /r "$EXEDIR\dir1\*.*" etc.

but the error is file not found ...!
Red Wine#
You can't use $EXEDIR in compile time, as you probably realize when you compile your script the installer does not executed, you can't expect from the compiler to know what is the $EXEDIR.
Red Wine#
Already discussed, you may use !define or just add the absolute path.
Are you a developer who uses NSIS to distribute your application? Are you a Winamp plug-in developer who wants to use NSIS to distribute your plug-in? Have suggestions for other people like you? This is the place.
Red Wine#
The messagebox is a runtime action.
It's not the compiler who displays the message, it's the installer.