Ulf,
> Having a meta format to describe the required files seems a
> good idea.
> However, I don't think we currently have a tool to handle XML and I
> don't like the idea of adding another tool. As the number of tools a
> newbie needs to install to generate Wireshark is already very
> huge IMHO.
I have defined a very simple meta format to describe the files required for
a Wireshark distribution.
See attached (or run nmake -f makefile.nmake in the packaging directory).
It is a simple listing by destination directory of the files required.
The listing makes use of the macros defined in config.nmake.
Each file may have associated parameters:
ifdef=XXX - only include if XXX is defined
oname=xxx - rename the file to xxx
u3loc=xxx - where to locate the files on a U3 device
It is currently automatically generated (using perl) from nsis/wireshark.nsi
(which seems to be kept the most up to date) and then used by the U3 and
PortableApps packaging (through a perl script to generate a makefile).
This then ensures that the U3 and PortableApps packaging have the same
contents as the NSIS packaging.
If this approach is appropriate, we should use this meta format to generate
nsis/wireshark.nsi and then just update the manifest by hand as required.
What do you think?
Graeme
Attachment:
wireshark.manifest
Description: Binary data
