I use "external" nsis installer: setup.exe and Instdata dir is packed into one with WinRar sfx. During install they're both unpacked to tempdir, and setup.exe copies files from Instdata using CopyFiles. So far so good.
Uninstaller reads filenames from $INSTDIR\files.lst, where files.lst is a text list of all the files that must be removed:
And so on (~300 entries).
file1.exe
file2.dll
Data\file3.dat
Data\Sound\file4.wav
Now the problem is that I make files.lst myself and supply it in Instdata\files.lst. So being lazy (and it's not very comfortable, because the only thing that changes in the package are files in Instdata, and sometimes i'm not the last one who adds files to package) I thought:
"Wouldn't it be cool, if setup.exe on the run scans $EXEDIR\Instdata and automatically generates Instdata\files.lst" or something similar. But I'm not programmer, in truth I have 0 experience in this field. I've tried to write using Findfirst & Findnext, but it didn't work (as if I'm surprised) - wasn't working on subdirs and in the end crashed anyways, so I have no idea whatsoever. 🧟
TIA,
galil