aboutsummaryrefslogtreecommitdiffstats
path: root/INSTALL
diff options
context:
space:
mode:
authorGerald Combs <gerald@wireshark.org>2022-07-24 11:05:13 -0700
committerGerald Combs <gerald@wireshark.org>2022-07-24 11:05:44 -0700
commitd1074274d1829538f4bb1881bc6e9d81187e36e8 (patch)
treea537ae9397cd0aed5f8a8557f463fdef368b1f76 /INSTALL
parent619639483325038f4c5f070e665938396eec2742 (diff)
More Perl cleanup.
Remove perl from INSTALL and our RPM spec. [skip ci]
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL19
1 files changed, 8 insertions, 11 deletions
diff --git a/INSTALL b/INSTALL
index 55dd28d3b5..2db30c71ed 100644
--- a/INSTALL
+++ b/INSTALL
@@ -50,16 +50,13 @@ README.windows for those instructions.
Similarly, Red Hat users will need to install a "libpcap-devel"
.rpm to go along with the "libpcap" .rpm.
-4. Building Wireshark requires Perl (specifically the pod2man program)
- so that the documentation can be built.
+4. Building Wireshark requires Python, flex, and Asciidoctor.
-5. Building Wireshark requires Python.
-
-6. Create a build directory separate from the source directory. It can
+5. Create a build directory separate from the source directory. It can
be anywhere, but you might run into issues if the path contains
spaces.
-7. Run 'cmake <options> <path/to/the/wireshark/sources>' in your build
+6. Run 'cmake <options> <path/to/the/wireshark/sources>' in your build
directory. Running 'cmake -LH <path/to/the/wireshark/sources>'
displays a complete list of options. The "Tool Reference" section of
Developer's Guide contains general instructions for using CMake. Some
@@ -166,17 +163,17 @@ README.windows for those instructions.
the packet analyzers are build with support for plugins.
Use this switch to build packet analyzers without plugin support.
-8. After running 'cmake', you will see a summary of some
+7. After running 'cmake', you will see a summary of some
of the options you chose. Ensure that the summary reflects
what you want. If it doesn't, re-run 'cmake' with new options.
-9. Run 'make', or 'ninja' if you chose to create Ninja build files.
+8. Run 'make', or 'ninja' if you chose to create Ninja build files.
Hopefully, you won't run into any problems.
-10. Run './run/wireshark' or './run/tshark' or ./run/dumpcap, and make sure things are
+9. Run './run/wireshark' or './run/tshark' or ./run/dumpcap, and make sure things are
working. You must have root privileges in order to capture live data.
-11./a. Run 'make install'. If you're running a system that supports
+10./a. Run 'make install'. If you're running a system that supports
the RPM packaging systems you can run
make wireshark_rpm
@@ -189,7 +186,7 @@ README.windows for those instructions.
defaults to /usr/local, so you'll probably want to pass
-DCMAKE_INSTALL_PREFIX=/usr to CMake.
-11/b. If you 're running a system that supports APT (Debian/Ubuntu/etc.)
+10/b. If you 're running a system that supports APT (Debian/Ubuntu/etc.)
run
dpkg-buildpackage -us -uc -rfakeroot