Yep, my bad on UHD, used to doing git builds and seeing 3.10. Cool yeah gqrx would be the priority, baz is just a nice to have (and its a bit dated as its all in WX which seems to be going the route of deprecation).
So for some feedback, I installed the binaries and everything seems to work good. Hooked up the UHD and was able to receive a decent sample rate without issue. Only small issue is was a popup on first run that said:
"The xterm executable 'xterm' is missing.
You can change this setting in your gnuradio.conf, in section [grc], 'xterm_executable'.
(This message is shown only once)"
Which is understandable, as xterm is not built. Anyway, after clicking ok everything works.
On the build side, first off, I'll say while I'm quite proficient on the Linux side, on the windows side I'm pretty noobish, so the first errors I received (missing io.h header, among other errors), appeared to be due to me having old VS 2012 only half removed which confused 14.. Anywho, after figuring that out and cleaning it up everything went good till the WX python build. But first I'll throw in that I did install VS2014 into an alternate path, this caused several issues with checks, I ended up creating the windows equivalent of a symlink (or maybe multi-disk hardlink, think its called a junction) and that solved that issue, but also the scripts ask for a location to place its build files, I tried I:/gr-build but received errors where directories in C:/gr-build were missing, I just symlinked C:/gr-build to I:/gr-build and things seemed fine. I only bring it up since the build scripts asked for a location. Perhaps it was something I did as I first ran setup.ps1 before I saw the ~RUNME_FIRST.ps1. Anyway, back to the WX error:
Got the error "Validation Failed, C:/gr-build\src-stage2-python\gr-python27\lib\site-packages\wx-3.0-msw\wx\_core_.pyd was not found and is required" which seems to just be a sanity check that something we expected to build was not(i did independently verify its not there, theres no wx* in site-packages), I've uploaded the log for wx-python[1], let me know if you need any more info.
The build appears to stop there. Not sure where to go with debugging as there appears to be no error, only some warnings? I'm also not familiar with wheel, though one would assume it produces the whl installer files. I did test removing the WX block and Step4 runs to completion. So it appears to be something with WX. I did see in the comments something about debug builds not working correctly, and there's a workaround. For completeness, I went ahead and commented out the Verify line and all builds (AVX, ReleaseDLL, Debug ) appear to generate this same log (except for folder names and such), and all do not generate the appropriate pyd file.
Any ideas what could be wrong? Or maybe whats special about wx as compared to the other python modules? If it was a bunch I would suspect something in my env may just be incorrect(Which, very well may be the case), but it seems just that one library.
P.S. I did just try to bypass it for debugging purposes, but I ended up with a different error on the consolidation step(not with WX) but lets take those one at a time.
Also, if you want, I can take this to github/issues.
-Anon