Delivering binary packages makes it much easier for the end-users to install Wireshark on their target system. This section will explain how the binary packages are made.
The Debian Package is built using dpkg-buildpackage, based on information found in the source tree under debian. See http://www.debian-administration.org/articles/336for a more in-depth discussion of the build process.
In the wireshark directory, type:
$ dpkg-buildpackage -rfakeroot -us -uc
to build the Debian Package.
The RPM is built using rpmbuild (http://www.rpm.org/), which comes as standard on many flavours of Linux, including Red Hat and Fedora. The process creates a clean build environment in packaging/rpm/BUILD every time the RPM is built. The settings controlling the build are in packaging/rpm/SPECS/wireshark.spec.in. After editing the settings in this file, ./configure must be run again in the wireshark directory to generate the actual specification script.
Careful with that configure setting | |
---|---|
The SPEC file contains settings for the configure used to set the RPM build
environment. These are mostly independent of any settings passed to the
usual Wireshark
|
In the wireshark directory, type:
$ make rpm-package
to build the RPM and source RPM. Once it is done, there will be a message stating where the built RPM can be found.
This might take a while | |
---|---|
Because this does a clean build as well as constructing the package this can
take quite a long time. Suggestion: add the following to your %_smp_mflags -j %(grep -c processor /proc/cpuinfo) |
Build requirements differ from run requirements | |
---|---|
Building the RPM requires building a source distribution which itself requires
the Qt development tools |
The OS X Package is built using OS X packaging tools, based on information found in the source tree under packaging/macosx.
In the wireshark directory, type:
$ make osx-package
to build the OS X Package.
The Nullsoft Install System is a free installer generator for Win32 based systems; instructions how to install it can be found in Section 4.17, “Windows: NSIS (optional)”. NSIS is script based, you will find the Wireshark installer generation script at: packaging/nsis/wireshark.nsi.
When building with CMake you must first build the nsis_package_prep target, followed by the nsis_package target, e.g.
> msbuild /m /p:Configuration=RelWithDebInfo nsis_package_prep.vcxproj > msbuild /m /p:Configuration=RelWithDebInfo nsis_package.vcxproj
Splitting the packaging projects in this way allows for code signing.
This might take a while | |
---|---|
Please be patient while the package is compressed. It might take some time, even on fast machines. |
If everything went well, you will now find something like: wireshark-setup-2.0.1.exe in the packaging/nsis directory in the source tree.
PortableApps.com is an environment that lets users run popular applications from portable media such as flash drives and cloud drive services.
Install the PortableApps.com Platform. Install for ``all users``, which
will place it in C:\PortableApps
. Add the following apps:
When building with CMake you must first build the nsis_package_prep target (which takes care of general packaging dependencies), followed by the portableapps_package target, e.g.
> msbuild /m /p:Configuration=RelWithDebInfo nsis_package_prep.vcxproj > msbuild /m /p:Configuration=RelWithDebInfo portableapps_package.vcxproj
This might take a while | |
---|---|
Please be patient while the package is compressed. It might take some time, even on fast machines. |
If everything went well, you will now find something like: WiresharkPortable_2.0.paf.exe in the packaging/portableapps directory.