On Wed, Nov 13, 2019 at 8:45 AM Graham Bloice <graham.blo...@trihedral.com> wrote: > > On Wed, 13 Nov 2019 at 16:07, Richard Sharpe <realrichardsha...@gmail.com> > wrote: >> >> Well, >> >> I seem to have gotten further, but then ran into this: >> >> CMake Error at CMakeLists.txt:91 (message): The PLATFORM environment >> variable ([undefined]) doesn't match the generator platform (win64) >> >> I notice that this page: >> >> https://osqa-ask.wireshark.org/questions/56074/cmake-build-fails >> >> discusses the problem and points to the document I was using, but that >> document does not address the PLATFORM environment variable. >> >> While it did not take long to figure the issue out, perhaps it could >> be pre-empted by adding an additional environment variable to the list >> in the documentation. >> > > The Platform env. variable is set by vcvarsall.bat which is what's actually > run to make a Command Prompt a "Visual Studio Command Prompt. Setting it > manually is NOT the correct thing to do. It appears that there's still > something wrong in your environment, as I noted on the Ask question you > linked where the OP had a similar issue for reasons that were never resolved > as they failed to respond.
This is what I see when I start the Developer Command Prompt: ********************************************************************** ** Visual Studio 2019 Developer Command Prompt v16.3.9 ** Copyright (c) 2019 Microsoft Corporation ********************************************************************** C:\Users\Richard.Sharpe.A00187\source\repos>set PLATFORM Environment variable PLATFORM not defined ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
