Sil0x0000
29th July 2009 11:24 UTC
Listing of files that are installed by NSIS installer
Hello Everyone,
Is it (easily) possible to create a text file with a complete list of all files that are installed during the installation. (separated by a new line, or /0) I use an NSIS installer with no optional components which means that the list can also be created at compile time. I use the file command to at files to my sections, this also includes the use of wild cards. In some case i rename the files using the /oname option.
Thanx in advance!
Afrow UK
29th July 2009 12:09 UTC
Creating at compile time is your best option. You can write an NSIS executable to do it or some other executable and run it with !system.
Stu
Sil0x0000
29th July 2009 12:21 UTC
Thanx for your reply
Originally posted by Afrow UK
Creating at compile time is your best option. You can write an NSIS executable to do it or some other executable and run it with !system.
Stu
Thats a pretty harsh way because then i have to parse the nsis file myself. I also only want to have one file containing all the entries other wise i have a double administration.
Are there hook functions that are called for every file that is added? Like the onInit
Thanx again
Afrow UK
29th July 2009 12:34 UTC
There is no callback for extracting a file I'm afraid. You could add one though and rebuild NSIS.
You haven't actually explained what you want to achieve by creating this list. If it's for use on the end users' machine then what is wrong with generating at compile time before including it in the installer?
Stu
Sil0x0000
29th July 2009 13:20 UTC
Originally posted by Afrow UK
You haven't actually explained what you want to achieve by creating this list. If it's for use on the end users' machine then what is wrong with generating at compile time before including it in the installer?
[/B]
The file is needed at runtime to run some important verification checks. Creating this list at compile time before the installer runs is quiet hard due to the fact that the files are not in the same directory structure as they will be on the end users machine. So doing recursive listing isn't the option. Keeping a list of files getting installed is a bit of redundancy. Parsing the nsis file isn't that easy.
Can the nsis installer create a log file of the installed files? I might use that to solve my problem...
Afrow UK
30th July 2009 00:32 UTC
You have the logging special build which you could parse or you could use the DumpLog function or DumpLog plugin to save the log window output to a file after installation.
Both methods will contain stuff you don't need but it's a start. Maybe you could write an executable to parse the logs and generate your file with a format of choice which you run at the end of installation.
Stu
Sil0x0000
30th July 2009 08:33 UTC
I was hoping this was not needed but i guess there is no other solution...
Thanx for thinking with meh.
Greetz Xander