If you are in the market for anything gaming PC or gaming laptop
related, chances are, you have come across the industry-wide trend of
RGB illuminated hardware and peripherals. Everything is RGB, from the
graphics card to the RAM, to your headset (because you can see the
lights when you wear it 🙄), and many, many more. I am not against RGB
lighting per se, but if you follow the industry as a PC hardware
enthusiast, it is evident that in some aspects, this has gone too far.
Quick side note: after a rant about RGB software, I will show
examples of using OpenRGB on Windows and Linux. If you are interested
in only that, skip the rant and scroll to the bottom.
Quick one: Set the proper CMAKE_PREFIX_PATH value for Qt5 development on Windows 10
with MinGW and CMake.
Here is the lovely error you get from CMake.
CMake Error at CMakeLists.txt:13 (find_package):
By not providing "FindQt5.cmake" in CMAKE_MODULE_PATH this project
asked CMake to find a package configuration file provided by "Qt5",
CMake did not find one.
Could not find a package configuration file provided by "Qt5" with
the following names:
Add the installation prefix of "Qt5" to CMAKE_PREFIX_PATH or set
to a directory containing one of the above files. If "Qt5" provides a
separate development package or SDK, be sure it has been installed.
CMake asks you to tell it where to find the Qt5 *.cmake configuration
files. One option is to set the CMAKE_PREFIX_PATH variable. The
Qt5 documentation has the following to say about that:
The easiest way to use CMake is to set the CMAKE_PREFIX_PATH
environment variable to the install prefix of Qt 5.
Now, what the hell is the "install prefix"? It turns out it is the
path where you can find the compiler-specific Qt binaries, include
files and the other stuff. In my case, using MinGW, it is located at
"C:\Apps\Qt\5.14.2\mingw73_64". If you are using the MSVC binaries,
select the corresponding directory, probably something like
A few months back now I have written about how I was trying to use
Linux as my main operating system. I will not reiterate my motives
here. If you are interested feel free to read the initial story back
from March. In my one-month-later story I was
already having some doubts, but continued to stick with it.
As an avid listener of Windows Weekly I often hear discussions between Paul Thurrott, Mary Joe Foley and Leo Laporte about Microsoft’s Fluent Design. Microsoft continues to evolve the visual language of Windows and thus it’s a regular topic on one of my favorite podcasts. I’ve been noticing it here and there myself, mainly in system dialogs, but I’ve never really paid any attention because none of the applications I use on a regular basis make use of it – and currently I’m rather happy about that fact. Just recently though, I was struck by one effect in particular and that was the spark that got this blog post going. To be honest, in most cases where I notice these Fluent Design elements I think of them as rendering bugs. Like sometimes in games, when the graphics driver is not yet optimized, or a badly programmed game engine draws odd pictures sometimes, flaws in an otherwise normal picture. I have a few examples to show to you.
While I was grooming my unicorn on Crazy-Talk Island I read on the Internet about a thing called Windows 10. Curious as I am, I went out to watch the huge presentation on Jan, 21 where Microsoft officially unveiled the mobile version of Windows 10 and the cool hardware stuff. There’s also a very nice set of videos by Scott Hanselman on YouTube that show the changes from version to version.
Actually I’m very much aware of Windows 10 since the beginning, as a developer I’d be crazy not to, so I registered as a Windows Insider yesterday and downloaded the technical preview build 10041. Here’s a summary of my first impressions. Read More »