Beginnings of win cmake support (not yet working), created by Graham Bloice,

some smaller changes by me.
- README.cmake
  Document how to (one day) run on Windows
- CMakeLists.txt
  Use MSVC compiler flags for MSVC instead of gcc flags
- FindWSWinLibs.cmake
  New: Creates HINTS for finding includes and libraries
  inside the Wireshark support library installation.
- FindXXX.cmake
  Make use of HINTS generated by FindWSWinLibs.cmake

This has not really been tested on Windows as my installation seems to have
automagically downloaded some fixes and is in an inconsistent state since.
Will probably need to reinstall.

svn path=/trunk/; revision=52194

1 files changed, 17 insertions, 2 deletions

diff --git a/README.cmake b/README.cmake
index df45e6a074..541dccf106 100644
--- a/README.cmake
+++ b/README.cmake
@@ -33,8 +33,8 @@ How to do out of tree build (Unix/Linux):
 3) mkdir build
 4) cd build
 5) cmake ../<Name_of_WS_source_dir>
-6) make
-6) (as root) umask 0022 && make install
+6) make (or cmake --build .)
+7) (as root) umask 0022 && make install
 
 Note 1:
 in step 5), you may override the defaults for features:
@@ -54,6 +54,21 @@ Note 4:
   http://public.kitware.com/Bug/view.php?id=9620
   To get predictable results please set umask explicitly.
 
+How to do out of tree build (Win32/64):
+[This is early alpha and the build will most likely die during the cmake
+ stage - don't waste your time testing unless you are willing to fix things
+ yourself]
+1) Follow http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html
+   Steps 1-9
+1a) Set WIRESHARK_BASE_DIR=c:\wireshark (the parent directory of the
+   library directory).
+2) Install cmake
+3) mkdir c:\wireshark\build
+4) cd c:\wireshark\build
+5) cmake -G "NMake Makefiles" .. (if the sources are in c:\wireshark)
+6) make (or cmake --build .)
+7) (as root) umask 0022 && make install
+
 Why cmake?
 ==========
 - Can create project files for some MS and Apple IDEs.