Visual Studio on Mamadou Babaei

Building Unreal Engine 5.6 From the GitHub Source Code on Microsoft Windows

Mon, 05 May 2025 23:00:00 +0200

Building Unreal Engine 5.6 from the GitHub Source Code

Alright… I’m back. Yes, I know—I vanished for a while. But just like the upcoming Unreal Engine 5.6 release, I’ve been quietly cooking in the shadows. And now… we’re both making a comeback.

Today’s tutorial is all about how to build Unreal Engine 5.6 from source—on Windows. That’s right, 5.6 isn’t officially out yet, but we’re not waiting around. If you’re impatient like me—or just curious to see what Epic’s brewing before the rest of the world—this video is for you.

Now, some of you patient folks out there might be thinking: “Why bother? Can’t I just wait for the release?” Fair question. But here’s the deal—I work for a company that publishes Unreal Engine plugins on the Fab Store. And they want their plugin ready on day zero when the new engine drops. The catch? Epic only allows you to submit plugins once the final version is officially released. So to stay ahead of the curve, we grab the source early, build it, test it, and make sure everything works before the launch day.

And hey, if you’re a Linux user—don’t worry—I’ve got a separate video coming soon. Just not today. Because building on Linux is like dating in your forties… not complicated, exactly—just different.

We’ll be diving into more Unreal Engine 5.6 goodness over the coming months, so buckle up, hit that subscribe button, and let’s get nerdy.

Post-Processing Effects in Cocos2d-x

Fri, 08 Jan 2016 22:10:30 +0330

Picture A: Gray (black and white) post-processing effect in Cocos2d-x

Update [2020/10/23]: Since I wrote this tutorial many things has changed in Cocos2d-x and I haven’t been using it in years as I switched to Unreal Engine 4. According to this GitHub issue opened by my blog readers, in order for this code to work there has to be some modifications to the code which is provided on that issue by @lazerfalcon and @madrazo. I was also having trouble with render to texture on Sprite3D which seems to have been solved in newer versions.

Despite the fact that Cocos2d-x uses the OpenGL ES Shading Language v1.0 for the shaders (in order to learn more about the language, please refer to: OpenGL ES Shading Language v1.0 Spec) the engine does not provide an out-of-the-box API to apply post-processing effects to the whole game scene output at once.

In this tutorial we will learn an easy way to apply multiple post-processing effects to the game scene output all at once.

Book Review: Application Development with Qt Creator - Second Edition

Mon, 29 Dec 2014 04:27:20 +0330

Almost three weeks ago I received a review request from one of the Packt Publishing staffs to review Application Development with Qt Creator, 2nd Edition written by Ray Rischpater which has been recently published by Packt Publishing. Since I’ve been developing cross platform Qt (cute, often mispronounced as Q-T cue-tee) applications from Qt 4 era back in 2008 – when Qt Creator was not around yet and the project was running by Trolltech at the time – and a handful of Qt Quick mobile applications over the past two years, I consider myself eligible enough to write a brief review on it. So, I was provided with a review copy and after reading it cover to cover, my thoughts on the book are as follows.

Application Development with Qt Creator, 2nd Edition

Write Your Own Cross-Platform Cryptographic Library

Fri, 15 Feb 2013 08:11:00 +0330

Previously I’ve described the process of building Crypto++ on both FreeBSD and Windows using the GCC, MinGW and VC++ compilers.

Now, we want to develop our own cross-platform cryptographic wrapper library around Crypto++. I’ve already uploaded the full source code to GitHub. You can find the link to the code on GitHub at the end of this article.

Before you proceed, you have to build the Crypto++ library as I mentioned earlier here.

How to Build C++ Cryptographic Library, Crypto++

Fri, 15 Feb 2013 03:50:00 +0330

Crypto++ is an awesome free and open source C++ class library of cryptographic algorithms and schemes which fully supports 32-bit and 64-bit architectures for many major operating systems, including FreeBSD, Linux, Solaris, Windows, Mac OS X and iOS. Currently, Crypto++ officially supports the following compilers:

MSVC 6.0 - 2010
GCC 3.3 - 4.5
C++Builder 2010
Intel C++ Compiler 9 - 11.1
Sun Studio 12u1, Express 11/08, Express 06/10

The latest version at the time of this writing is 5.6.1.

In spite of the power that Crypto++ offers, building and using it can be a little bit tricky. In the following we will describe the process of building Crypto++ on both FreeBSD and Windows using the GCC, MinGW and VC++ compilers.

Should I Check if a Pointer Is NULL Before Deleting It?

Mon, 11 Feb 2013 01:52:00 +0330

Most of the time I see some C++ programmers who check if a pointer is NULL before deleting it.

if (ptr != NULL) {
    delete ptr;
    ptr = NULL;
}

Well, according to C++03 [ISO/IEC IS 14882:2003] §5.3.5/2 which explicitly states:

…if the value of the operand of delete is the null pointer the operation has no effect.

C++ Standard Core Language Defect Reports and Accepted Issues, Revision 82 delete and user-written deallocation functions

Therefore, deleting a NULL pointer has no effect (if the deallocation function is one supplied in the standard library), so it is not necessary to check for a NULL pointer before calling delete.

delete ptr;
ptr = NULL;

Note: Keep in mind that deleting a void* pointer results in ~~undefined behavior~~ whether it’s NULL or not.