Thus said Guy Harris <g...@alum.mit.edu> on Sat, 26 Jan 2019 12:06:36 -0800
On Jan 26, 2019, at 9:19 AM, Jaap Keuter <jaap.keu...@xs4all.nl> wrote:
2. What you’ve shown is a text stage of CMake to find compiler options, these
are not Wireshark build errors.
Yes. "CMakeError.log contains errors" is not a build failure; with any given
CMake-using project, you *might* happen to be lucky enough that *all* command-line flags
being tested happen to work on the compiler you're using and that *all*
symbols/functions/etc. happen to be available and that *all* of the structure being
tested have the structure member being tested for and..., but the chances of that are
rather slim on a cross-platform project.
"CMakeError.log contains errors" is the CMake equivalent of "config.log contains errors" for
autotools. The standard output and error of CMake will report the test errors that are build errors rather than
"not on this platform" test failures, just as the standard output and errors of an autotools configure script
will report the test errors that are build errors rather than "not on this platform" test failures.
Thanks Jaap and Guy! Deleting the cmake files indeed make cmake happy
and wireshark built without issues.
Have a nice weekend.
Thanks!
___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe
