CMake · 
Sorted in alphabetical order.
Time for another short guidance on how to build your own copy of the Qt framework from source.
One of the drawbacks of using such a comprehensive framework as Qt is the massively increased size of you program.
When my pet project RandFill was only using the plain Win32-API, it was a single executable file of a couple of hundred kilobytes.
Now, using dynamically linked Qt, the whole package (with DLLs, MSVC redistributables, etc.) is bigger than 20 megabytes as a 64-bit build!
The Simple DirectMedia Layer (SDL) recently released its
new major version 3
(as version 3.2.0) and that was a good oppurtunity to check it out and play a bit with it.
But before I could do that, I had to build the library first.
A short guide on how to build wxWidgets (the cross-platform GUI toolkit) from source
(the recommended way), on Windows, by using CMake and Visual Studio.
After building a 64-bit version of Qt with/for Microsoft Visual Studio,
building a simple Qt test program and doing
first steps with the CMake build system, the next hurdle appeared
on the horizon in the form of support for Qt and its Q_OBJECT features (I am currently fighting more
with the changes I made to my build environment than improving the actual program code…).
Konnichiwa, time for another status report.
Describes a few tips on how to generate a 64-bit project for Visual Studio with CMake.
This is a brief post on how to use CMake to setup a Visual Studio 2019 solution on Windows
that will use the LLVM Clang compiler instead of the orginal Visual C++ one.
Reminder for some syntax and parameter details on how to invoke the actual CMake executable/program from a command line interface (CLI).
I’ve changed the build process of the RandFill project recently
from using the Visual Studio files (*.sln, *.vcxproj, etc.) to maintaining and generating those with CMake.
Although I’ve already published an article on how to bring an external CMake project into your own CMake project,
I recently realized that I haven’t written about how one can prepare a CMake project for the use with
find_package() — despite the fact
that I’ve used it already for quite a while in RandFill for my own WPDLib(rary); so let me make up leeway for that oversight with this post.The reason for this post is that I spent a considerable amount of time1 the last two days to
convince CMake’s External Project feature to do what I wanted. And without the help of the usual
suspects (Stackoverflow, old mails, blog articles, code snippets, etc.), I might still not be done.
So I thought I could pay back the general public by posting some notes on this topic 😉
RSS