David Lindecrantz

`rcc` is part of the qt toolchain, so it seems you haven’t added qt to $PATH before building. As a side note I began porting over a minimum of my...

@azoreseuropa Depending on if you installed qt via `brew` or the installer from qt.io the path to add will be different. I use the installer since I find it easier...

If you are able to build from source (and identify possible build issues since building on windows can be rather finicky), you can try my branch which is already on...

Hmm, looks like the linker can't find the Qt frameworks... No idea why. I've migrated my branch to Qt5 and have done some more macOS UI improvements, I wonder if...

What errors do you get when building my fork?

You need to export $qtpath, try changing the definition in .bash_profile to `export qtpath=$HOME/Qt/5.8/clang_64`

Hmm. When you run `make`, how do the compiler invokations look? [Here's how they look over here](https://pastebin.com/N7R1y5HV), for reference.

@BooBerry Odd, but it certainly sounds like `$qtpath` isn't exported. What is output when you issue the following commands in a new terminal window: `echo $qtpath` `$qtpath/bin/moc --version` `cat $qtpath/lib/QtWidgets.framework/Versions/Current/Headers/QApplication`

@BooBerry Since it sounds that you're after the macOS gamepad support specifically, I'm certainly interested in getting some feedback from testers regarding that feature. My current commit will only capture...

Supporting any number of memory monitor views is unrelated to the symbol/label lookup feature, and should be a relative breeze to implement. It would be quite useful, too!