Wireshark-users: Re: [Wireshark-users] unrecognized command line option '-fmacro-prefix-map=old=n
Date Prev · Date Next · Thread Prev · Thread Next
From: jungle boogie <jungleboogie0@xxxxxxxxx>
Date: Sat, 26 Jan 2019 19:22:38 -0800
Thus said Guy Harris <guy@xxxxxxxxxxxx> on Sat, 26 Jan 2019 12:06:36 -0800
On Jan 26, 2019, at 9:19 AM, Jaap Keuter <jaap.keuter@xxxxxxxxx> 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!