Visual Studio 2017 Setup Issue

[CSmith55]

Hi,

I want to start developing for Dolphin. I am trying to get set up in Visual Studio 2017. My code builds fine, and I can actually run Dolphin. However, when I open files, errors are appearing. From the picture, you can see that VS2017 is not finding the packages that start with "Q". I looked up that these are related to the QMake package. I don't know where QMake is supposed to exist in Dolphin. I downloaded this code straight from GitHub, the most recent release, and I haven't changed anything. Is there something super simple that I am missing that will get VS2017 to recognize these includes as valid? I'm brand new to C++ and VS2017, so any tips anyone could give to resolve this problem, I would really appreciate.

Thanks!

[JosJuice]

Those includes are only used for the Qt GUI. Either ignore all the files that implement the Qt GUI, or pull the submodule that's in the Dolphin git repo if you want to be able to compile the Qt GUI.

[CSmith55]

(01-10-2018, 08:39 AM)JosJuice Wrote: Those includes are only used for the Qt GUI. Either ignore all the files that implement the Qt GUI, or pull the submodule that's in the Dolphin git repo if you want to be able to compile the Qt GUI.

Oh, I didn't know there was a submodule that had to be pulled. Could I ask, why does my solution build fine and I am able to run Dolphin if I don't have that submodule locally in my project? 

Also, is the Qt GUI the one that you see when you launch Dolphin normally? 

[Helios]

the Qt UI is not default. It's under development.

[JosJuice]

(01-11-2018, 01:11 PM)CSmith55 Wrote: Oh, I didn't know there was a submodule that had to be pulled. Could I ask, why does my solution build fine and I am able to run Dolphin if I don't have that submodule locally in my project? 

If you build the project "Dolphin", you get the wxWidgets GUI, which is the one that currently is the default. You only need Qt if you're going to build the project "DolphinQt2".

[CSmith55]

Thanks for the information guys. Is there a reason that another UI is being worked on? Is the current UI insufficient in some way? 

[Helios]

It sucks at HiDPI, obnoxious to work in.