Error building Audacity (can't find wxWidgets)

[adi_ganti]

	Close Visuual Studio.

This should be changed to Visual Studio

 b) Open the CMake GUI
     ==> Open VS 2019 > "continue without code" > File > Open > CMake
     ==> Open CMakeLists.txt in root of audacity source folder you cloned
	 ==> Wait for the CMake Overview Pages tab to appear (be patient)
	 ==> Click "Open the CMake Settings Editor" in this new tab
	 ==> Scroll up to the top of the window and settings
	 ==> In the Configurations window, click the green "+", then select x86-Release
	 ==> Set Configuration type: Release
	 ==> Verify Toolset: msvc_86
	 ==> Keep Build Root: ${projectDir}\out\build\${name} (default, you can change it)
	     (this corresponds to CMAKE_BINARY_DIR)

In this part, is it necessary to open CMake-GUI? Following the rest of the instructions, it’s clear that there is no need for CMake-GUI to be opened. It certainly confused me for 2 minutes, when I opened CMake-GUI → tried to search for an ‘Open VS2019’ option

==> Click on “Show advanced settings” (scroll down).
==> Change CMake generator: VS 16 2019 (was Ninja)
==> Click “Save and Generate CMake cache to load variables” once, then
==> Click “Save and Generate CMake cache to load variables” a second time
or select Project > Generate CMake Cache

c) Switch to the Ouput tab
==> Wait for “CMake generation finished”.
==> Check the Error List window:
you should have 0 Errors and 0 Warnings.

>

Maybe it can be elaborated a little more? Click "Save and Generate CMake cache to load variables" once, after this wait for some time for the output. It will either be 0 Errors and 0 Warnings, or 0 Errors and 1 Warning (Jack). After this output,  Click "Save and Generate CMake cache to load variables" one more time. This time, the output should be the same (in my case, it went from 1 warning to 0 warnings).

I'm suggesting a little more clarity on this because I clicked on it the first time, and the cursor switched to the loading cursor (the busy circle) and then back to normal. I thought the process was done, so I clicked on it a second time. The same happened. I was starting the next step, when the  output tab screen started showing some activity. It takes a couple of seconds to initiate. It's possible the next step will be started before the previous one completes execution. That's why.
\
\
The rest is all good, easy to follow! The 68 errors solution also can be appended to this build instruction.

Thanks a lot jademan 🙌