NSIS uses "File" to extract file.
When I have so meny files to be extracted, I have to write "File file_name" for each file.
Is there another way to handle such installation with a mass of files?
Add a mass of files and directories into my script.
5 posts
If this file don't change often
you can simple put this into a zip file
install this zip file in the temp folder
and after this unzip the files in the required destination...
But why not putting the "File" operation into a include file?
so you have a main script which only controls the installation process and the huge list is in a extra file.
To create the list of files
probably this is usefull for you
(Eclipse NSIS also have this feature included)
you can simple put this into a zip file
install this zip file in the temp folder
and after this unzip the files in the required destination...
But why not putting the "File" operation into a include file?
so you have a main script which only controls the installation process and the huge list is in a extra file.
To create the list of files
probably this is usefull for you
(Eclipse NSIS also have this feature included)
It's very kind of you for telling me that.I have handled this problem with wildcard in use of File.But the deletion of files and directories while uninstallion is still a little troublesom.
You can use wildcards also in the remove file
and if you like to delete a whole directory with files use
RMDIR /r "directoryname"
this recursivly deletes the whole directory (also all files inside)
Also for the normal delete wildcards are working.
and if you like to delete a whole directory with files use
RMDIR /r "directoryname"
this recursivly deletes the whole directory (also all files inside)
Also for the normal delete wildcards are working.
It is not recommended that you use RMDir /r to remove your program. What happens if the user installs your program to My Documents?
I recommend that you create a seperate NSIS installer:
Which recursively loops through your files using:
And generates NSIS code which implements the following:
This seperate NSIS installer can be executed at compile time with !execute and you can include the generated script in your main script with !include.
-Stu
I recommend that you create a seperate NSIS installer:
Which recursively loops through your files using:
And generates NSIS code which implements the following:
This seperate NSIS installer can be executed at compile time with !execute and you can include the generated script in your main script with !include.
-Stu