Assuming the installer AppnamePortable_x.xx.x.paf.exe will installed the appropriate app at X:\PortableApps\AppnamePortable. Are the following 2 statements correct?:
$INSTDIR=X:\PortableApps\AppnamePortable
$EXEDIR=X:\PortableApps\AppnamePortable
New: Run-Command (Dec 2, 2024), Platform 29.5.3 (Jun 27, 2024)
1,100+ portable packages, 1.1 billion downloads
No Ads Nov/Dec!, Please donate today
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
I think so.
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
In the documantation of NSIS the constant $EXEDIR is defined as follows:
However, if my above assumption would be correct, then must reside the file "AppnamePortable_x.xx.x.paf.exe" (this is the installer executable) in the folder AppnamePortable. Instead the folder AppnamePortable contains the launcher executable "AppnamePortable.exe".
Also I suspect, that $EXEDIR and $INSTDIR should differ.
To begin with, NSIS is a language to build installers. That is "abused" to build a launcher instead and therefore the launcher in this case is the installer from a NSIS point of view.Obviously I was wrong...
EXEDIR is the directory containing the currently running installer. So, it's wherever you run AppnamePortable_x.xx.x.paf.exe from which could be the desktop if the user downloaded and ran it themselves or somewhere in TEMP if they are using the app store/updater.
For launchers EXEDIR is wherever AppNamePortable.exe is running from and INSTDIR is NOT USED.
Sometimes, the impossible can become possible, if you're awesome!
If I use the constant $EXEDIR in conjunction with the creation of the file "custom.nsh", refers then the constant $EXEDIR to the folder AppnamePortable where AppNamePortable.exe is running from?
As already explained. If you are doing something in conjunction with the launcher (which uses custom.nsh) it would be where AppNamePortable.exe is running from.
Sometimes, the impossible can become possible, if you're awesome!