From 3b72a7d9767578f6be78609d0cacc34254af75b3 Mon Sep 17 00:00:00 2001 From: Guy Harris Date: Sun, 3 Aug 2014 13:13:23 -0700 Subject: Add some issues that came up when comparing autotools and CMake compile flags. Also be consistent about whether OS X is working or not, and note that we're also doing CMake builds on Solaris. Change-Id: I2da18d2fb5aec7e5806dc7ea186f729acef94272 Reviewed-on: https://code.wireshark.org/review/3389 Reviewed-by: Guy Harris --- README.cmake | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) (limited to 'README.cmake') diff --git a/README.cmake b/README.cmake index 1c416e0880..004c1fb3fc 100644 --- a/README.cmake +++ b/README.cmake @@ -108,7 +108,7 @@ All the executables now build from clean source on: * 32bit Ubuntu 9.04 * 32bit Ubuntu 10.04 * 64bit Debian Wheezy -* Mac OS X +* OS X What needs to be done? ====================== @@ -122,9 +122,8 @@ What needs to be done? (using CPack). This includes setting OS target version stuff appropriately for OS X. - Add back checkAPI target. -- Test and add support for other platforms (BSDs, OS X, - Solaris, Win32, Win64, ...) - we're currently doing CMake builds on OS - X, and Solaris. +- Test and add support for other platforms (BSDs, Solaris, Win32, Win64, + ...) - we're currently doing CMake builds on Solaris. - Add support for cmake configurations. - Automatically figure out if *shark is running from the build directory (making WIRESHARK_RUN_FROM_BUILD_DIRECTORY unnecessary like it is with @@ -147,6 +146,10 @@ What needs to be done? - Get plugins loading when running *shark from the build directory. That might involve handling ".libs" and "run" differently. - Get cross-compilation working (or ensure it does). It works with autofoo. +- Handle -DFORTIFY_SOURCE=2 appropriately. (Do a Web search for + "cmake fortify" for some information.) +- Define the GTK_DISABLE_ and GDK_DISABLE_ values as appropriate if we + care about supporting the GTK+ version. ... Links regarding cmake -- cgit v1.2.3