I'm trying to build QT2 for the first time (since it's the new default). I get the attached errors in visual studio. I tried running
Code:
git submodule update --init --recursive
but that didn't make a difference. I assume I need to compile QT 5 and then replace "submodule" with something? Should I also create an issue to add QT 5 to Dolphin so we don't need to separately compile QT? Ideally it should be just as easy to compile QT vs WX.
It looks like you're trying to build with CMake, which isn't really something that works well on Windows right now. Make sure that you're using the Visual Studio solution file instead.
(04-27-2018, 06:17 AM)ryanebola16 Wrote: [ -> ]I assume I need to compile QT 5 and then replace "submodule" with something?
No. You just need to run that, and it fetches everything you need for building and running Dolphin with Qt. If you haven't done that (or if you didn't do it correctly), Dolphin's build process will give you an error message that specifically mentions the submodule.
That's odd, then... dolphin-emu.sln is the one you're supposed to be using.
And expanding the error message gave me this (regardless of running git submodule update) To the issue tracker?:
Severity Code Description Project File Line Suppression State
Error CMake Error at Source/Core/DolphinQt2/CMakeLists.txt:1 (find_package):
By not providing "FindQt5.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Qt5", but
CMake did not find one.
Could not find a package configuration file provided by "Qt5" with any of
the following names:
Qt5Config.cmake
qt5-config.cmake
Add the installation prefix of "Qt5" to CMAKE_PREFIX_PATH or set "Qt5_DIR"
to a directory containing one of the above files. If "Qt5" provides a
separate development package or SDK, be sure it has been installed. Source/Core/DolphinQt2/CMakeLists.txt
No, I don't think this should be reported on the issue tracker. CMake isn't expected to be functional on Windows. I don't know why VS is trying to build with CMake, but it is possible to make it not build with CMake.
Please retry with a clean clone.
My next best guess is that your VS install is broken in some way. Thus far it doesn't look like our solution is at fault.