aboutsummaryrefslogtreecommitdiffstats
path: root/README.macos
diff options
context:
space:
mode:
authorDavid Kreitschmann <dkreitschmann@seemoo.tu-darmstadt.de>2018-06-15 12:44:47 +0200
committerAnders Broman <a.broman58@gmail.com>2018-06-21 03:33:03 +0000
commit11ba10dd4b8865d1d4b866cd808ec8fe4defe3b2 (patch)
tree2ff94017b1d563c78bae94cb5266c94137617d9e /README.macos
parent17604f15a1a1fe4199449150675c2613874ae4a5 (diff)
Fix build paths for cmake's Xcode project generator on macOS.
Multi-configuration generators (such as Xcode or VS) append the current build configuration to most paths (eg. Debug/Release). Currently this results in inconsistent paths for the application bundle and the included command line tools. This commit sets the correct path information for multi-configuration generators for macOS application bundles. The standard Makefile behaviour is untouched. One Windows specific configuration was changed, as it was conflicting with these changes. This needs to be checked before merging. Additionally the wrapper scripts are omitted for Xcode, as the path to the binaries depends on the configuration chosen in Xcode. Therefore it is not viable to create these scripts in the cmake run. Bug: 11816 Change-Id: Ib43d82eb04600a0e2f2b020afb44b579ffc7a7c9 Reviewed-on: https://code.wireshark.org/review/28291 Petri-Dish: Guy Harris <guy@alum.mit.edu> Tested-by: Petri Dish Buildbot Reviewed-by: Anders Broman <a.broman58@gmail.com>
Diffstat (limited to 'README.macos')
-rw-r--r--README.macos16
1 files changed, 16 insertions, 0 deletions
diff --git a/README.macos b/README.macos
index f2eaeb0033..cac66f3776 100644
--- a/README.macos
+++ b/README.macos
@@ -74,6 +74,22 @@ directory;
cmake ..
make
+It is also possible to use the Xcode IDE to build and debug Wireshark
+using cmake's Xcode generator. Create a separate build directory, as
+described above and run cmake with the "-G Xcode" argument to create
+a Xcode project file in the current directory.
+
+ cmake -G Xcode ..
+
+ 1. Double click Wireshark.xcodeproj
+
+ 2. Choose to create schemes manually
+
+ 3. Create a scheme for the ALL_BUILD target
+
+ 4. Edit the scheme, go to the run configuration and select Wireshark.app
+ as executable
+
If you upgrade the major release of macOS on which you are building
Wireshark, we advise that, before you do any builds after the upgrade,
you remove the build directory and all its subdiretories, and repeat the