of Visual C++. (How did this "feature" ever see the light of day?) Make
sure we use LOCAL_CFLAGS *everywhere*. This should fix problems with
building a usable installer under Visual Studio 2008 SP1.
Add comments with links to Visual C++'s idiotic handling of assemblies
and deployment using xcopy. Move to c-ares 1.5.3. Make sure we remove
all of our manifests in epan and packaging/u3/tools.
svn path=/trunk/; revision=26219
a) Check that UPX is configured correctly and offer solutions;
b) Ignore any errors generated from UPX (e.g. from previously compressed files); and
c) Clean up the tools directory when cleaning the U3 distribtion
svn path=/trunk/; revision=23622
For the U3 package, this results in a 40% smaller package.
For the PortableApps version, the package size is not much different, but the install time is quicker.
svn path=/trunk/; revision=23484
1. wireshark.bat: Quote %U3_HOST_EXEC_PATH%\wireshark.exe so pathname
with spaces will work;
2. makefile.nmake: Use $(MAKE) /$(MAKEFLAGS) so things like
invoking nmake at the top level with /E to have environment
variables override config.namke definitions will work.
svn path=/trunk/; revision=23297
a) include smi.dll if SMI_DIR is set
b) add a batch script to run the U3 wireshark configuration by simulating the U3 environment
c) include a test step in the build process to verify that the U3 package contains all the required files (tries to run "wireshark -D")
d) include the wireshark.bat in the U3 zip file.
This final step means that the U3 package can be unzipped on any drive and run using the wireshark.bat script. (Note this currently creates an unwanted cmd window.)
svn path=/trunk/; revision=23295
references to h223 in README.plugins with agentx since it's small and
no one seems to be in a hurry to move it to epan/dissectors.
svn path=/trunk/; revision=22641
add it to the distributed files, to the Win32 NSIS and U3 packages. UNIX packages will still miss this (optional) file.
svn path=/trunk/; revision=22487
94630be0-e031-11db-974d-0002a5d5c51b
It is based upon the example code from RFC4122 and links against gcrypt.
Using this tool allows the U3 packaging UUID to be automatically changed for new versions as well as giving each buildbot version a different UUID.
svn path=/trunk/; revision=21694
Also tweak the space requirements and restore the VERSION_EXTRA information to the description, both within the manifest.u3i.
svn path=/trunk/; revision=20964
a) remove schema reference
b) assign new GUID for 0.99.6
Update makefile.nmake to:
a) include user-guide.chm - user-guide.chm is copied from the nsis packaging directory
b) include the example_snmp_users_file
c) other tidy-ups
svn path=/trunk/; revision=20555
The U3 Deployment Guide recommends a sub-directory of U3_DEVICE_DOCUMENT_PATH, so the u3util creates a "My Captures" sub-directory to use as the personal data file directory.
svn path=/trunk/; revision=20441
a) Packaging changes - including the latest GTK/GLIB/PANGO libaries
b) File associations - made when Wireshark is first run and removed when device is removed.
c) Install WinPcap - by running the installer if WinPcap is not installed. Uninstalled (if the U3 device installed it) when the device is removed. (This is an interim approach until the appropriate WinPcap U3 installation can be determined).
svn path=/trunk/; revision=19985