I obviously don't understand how this works. It seems mostly straightforward in the documentation, but I'm having absolutely no luck with Create Zip with wildcards.
My root directory is correct. The files are there.
My included files are: Release\??.mnu
There are at least a dozen files that match this description in this directory (C:\TheRootDir\Release\??.mnu).
I keep getting this response: "No Such File : Report\??.mnu".
I have tried every combination of checked boxes for Relative paths, Store Paths, and Recurse Directories that the Action dialog allows.
But there is no joy in Zip Town. Similarly, changing the wildcard to "Report\*.mnu" also fails. What am I doing wrong?
Note: I have other files that need to be included. I've narrowed this down to the simplest case.
In addition, I want wildcards for this directory but not any subdirectories. However, if I choose Relative Paths, it forces Recurse Directories to be checked. But I don't want to recurse.
Try using absolute paths in the include files field, for instance, C:\TheRootDir\Release\??.mnu.
> In addition, I want wildcards for this directory but not any subdirectories.
Using the above file spec won't match files in a subdirectory.
Regards,
Paul.
OK, so that works. I get a zip file, yes, and the files are in it.
But I have a dozen filespec wildcards similar to this one, in different subdirectories, that have to go into this zip archive, and the paths are going to be a total mess to read for anyone looking at the defined action. The root path is 70-something characters long.
So thanks, yes, you've provided a solution.
I think it would be really cool if there were a slightly more elegant (and obvious) way to handle it.
You could define a variable called %ArchiveRoot%, set it to the 70 character long root path, and then use this in the file path? That would keep the list a lot more readable.
Regards,
Paul.
Your suggestion of a variable (which became an action list parameter) was helpful.
We need the process to completely replace the existing zip file when it is created. Putting these two actions into an action list and using a parameter for the archive source root directory helped. The action list pre-deletes the zip file and then properly creates the zip, and readability is improved for the builder.
Thanks for the advice.
One last suggestion: it would be really convenient if there was an option in Create Zip that caused the entire zip file to be replaced if it existed. Like I said, we added a step to delete it first, but it would be a nice convenience feature.