Another milestone hit: - Win 32bit: The following executables build and run from the build directory (as well as capture if they should be able to). *: Acutally tested $ ls *exe capinfos.exe* dumpcap.exe mergecap.exe randpkt.exe reordercap.exe tshark.exe* dftest.exe editcap.exe qtshark.exe* rawshark.exe text2pcap.exe wireshark.exe*
TODO - 64bit support - GTK3 detection (i.e. getting pkg-config to work for out setting) - PORTAUDIO support (I probably only need to build it as the nmake setup process does not seem to do that). - Review the cmake and nmake log messages and (try to) fix everything that's not purely informational - Move setup completely out of the nmake Makefiles into the existing or a new setup script. - Maybe a better structured setup with a uniform layout for all packages. - Review by the people who know Windows and the nmake setup (similar to what Guy has been doing for the autotools - cmake sync). - qtshark on win *requires* that gtk includes are present to build: file_dlg_win32.c:#include <gtk/gtk.h> - abi check: Move abi check operation into a UseABICheck.cmake file and call that from CMakeLists. Then make it work on Win32 in a single place. - API check is missing for all platforms - Determine what else is missing to get rid of the old nmake infrastucture - Are there other platforms that would benefit from something similar to what I did with the setenv.bat script? - Other build platforms (there seems to be at least some interest in VS). Is someone willing to work on some of these items? I'm willing to support anyone who is interested even if that takes me more time than doing it myself. @Balint: Would you be willing to do the abi check cleanup stuff? @Graham: IIRC you already had some setup scripts to replace the old stuff when we talked about this 20 months ago? Ciao Jörg -- Joerg Mayer <jma...@loplof.de> We are stuck with technology when what we really want is just stuff that works. Some say that should read Microsoft instead of technology. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe