I have Inno setup but I'm unclear on one thing. How do you go about finding the required files to run your program.
Printable View
I have Inno setup but I'm unclear on one thing. How do you go about finding the required files to run your program.
Do the package and deployment wizard first then you'll know what files are required.
ok i got the same question too i got extra folders in it which it loads data from how do i add that to my setup?
PDW will not always find all the files that you need however ********** will expecially for Inno Setup.
And you can use depends.exe to find EVERYTHING your app calls (run it in dynamic mode). That's what I used, and then I figured all the DLLS that came installed with Windows and all the dlls that you're not allowed redistributing, and the ones that were left were the ones it needed.
EDIT: Personally If I were you I would switch to NSIS, and get HM NIS Editor, it makes everything for you, then you can customise, ask me for more help if you want to (nsis has a smaller overhead (34kb I believe)). It's a matter of personal preference though.
That's the hard way and you have to do that with each dll you have in your project to cross check.
Yeh it was pretty hard. I remember I asked the same question and you responded, and told me to use inno script. But it didn't tell me of a dll that I knew I had, and then the trial ran out so I couldn't further test it :ehh:
It would not find dll's that you do not have a reference for in your project. If you dynamically load it... it will not be found. Otherwise all dll's will be found.
I think it was that an OCX in my prog loaded a seperate DLL, and it didn't find that DLL. Anyways it did give me a good list (everything else except another dll that was called in the same way). In the end I just got rid of that dll entirely from my program because it wasn't needed, and didn't distribute it.Quote:
Originally Posted by randem
Also you may not have seen it because it was removed for possibly being unsafe to deploy.
The first dll is safe, it's xaudio.dll and it's called by mp3p.ocx. It's for playing MP3 files.
If that ocx was referenced in your project the dll would have been found or at least noted. If you did not have the correct paths in the search path for ********** to search it would not have found it, but it would have still been noted that it was needed. Two very different issues.
Moved.
Thanks everone.