1 Placeholder for cmake development stuff :-)
5 The CMake build system for Wireshark is not yet ready for
6 building the whole system. You'll still need autofoo to buld it.
7 The only thing that can be build is dumpcap, and even that one
8 requires that you successfully ran autofoo prior to running cmake
9 (e.g. config.h is not yet build, lex and yacc are not run).
10 Basically this is an experiment and if we find out that it works
11 and we like cmake more than autofoo we might switch one day.
16 How to get started with cmake?
19 What needs to be done?
21 How to get started with cmake?
22 ==============================
24 You can find documentation on cmake at: http://www.cmake.org/
26 cmake is designed to support out of tree builds. So much so, that
27 in tree builds do not work properly in all cases.
29 How to do out of tree build (Unix/Linux):
31 2) Build the project with the old build system once (to generate
32 config.h and run bison and flex to generate some c-files).
33 3) Assuming, you are in the top directory of the wireshark source
37 6) cmake ../<Name_of_WS_source_dir>
42 - Can create project files for some MS and Apple IDEs.
44 - Easier to understand/learn
45 - One build infrastructure even including Windows?
51 - Everyone who wants to build from source needs cmake
52 - Current state of documentation isn't really better than
53 autofoo documentation, in some respect it's even worse
54 (you need to buy a book to get an explanation as to how
58 What needs to be done?
59 ======================
61 only dumpcap and libwiretap have been done, and even those rely on
62 autofoo having been run before:
64 - Add proper GTK1/GLIB2/GLIB1 detection (currently links against gtk2
67 - Autocreated source files in wiretap need to be build from .l, .y files.
69 All other tools and libs still need to be built.