Hi, I've been playing with NSIS for a few days now, and am trying to portablize an app that I would like to carry around with me on my flash drive.
I need some suggestions/leads on how to handle DLLs by the app in question. I found that putting all the DLLs in the app's directory seemed to work fine. Is that acceptable practice? Or should I have it in a separate directory and have the .NSI file tell the launcher where to find it?
Also, there is a specific file being used by the app to hold the apps' settings but it's not so simple to edit.. is there a way to export it to another directory and have the launcher call it or move it back and forth? and how can I run a call to change the settings so that it's not drive locked like C:\NARF or D:\NARF but make sure its like %DRIVE%\ wherever it is..
I'm sorry if I'm not being clear but I hope someone out there can help me.. the NSIS documentation isn't very good at helping to portablize stuff...
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
like dlls when you compile like "ProcKill"? thats compiled into the EXE! check ure temp directory (%temp%) these Dlls will be extracted there the NSIS compiler does all of this for you. so u dont have to carry it around. Hope This Helps!
Slackware 12 for system
MCP (For XP and Server 2003)
Network + Certified
aim is "nycjv321" (minus quotes)
Compiled into the .EXE?
Seems nothing gets compiled into the .EXE actually. It's just a launcher to a program that users will eventually have to download and extract into the portableapps\appdir\app\theappinquestion
----
Ryan McCue
Person 1: Oh my god. You will never believe what just happened.
Person 2: What?
Person 1: I can't remember, I've forgotten.
"If you're not part of the solution, you're part of the precipitate."