The only progress I was able to make was making it work by adding the following directive: #define SDLMAINHANDLED This sort of overrides an SDL2 directive which replaces the main function with a custom SDLmain in order to do some optimizations. I'd like to avoid using it however and my goal is to get to the point where I can use the. CLion uses CMake as a build tool and a project model. So you need to configure CMakeLists.txt for SDL2 library using. Please try to use some examples of CmakeLists from these articles. For Windows you have to download the development package SDL2-devel-2.0.5-VC.zip and extract it to some location on your hard disk. You can create Visual Studio project files with the CMake GUI under windows but when you hit configure it will fail because it will not find the SDL2 Library.
You'll want to download the MinGW development libraries.
Open the gzip archive and there should be a tar archive. Open up the tar archive and the should be a folder called SDL2-2.something.something. Inside of that folder there should be a bunch of folders and files, most importantly i686-w64-mingw32 which contains the 32bit library and x86_64-w64-mingw32 which contains the 64bit library.
This is important: most compilers still compile 32bit binaries by default to maximize compatibility. We will be using the 32bit binaries for this tutorial set. It doesn't matter if you have a 64bit operating system, since we are compiling 32bit binaries we will be using the 32bit library.
Inside of i686-w64-mingw32 are the include, lib, and bin folders which contain everything we need compile and run SDL applications. Copy the contents of i686-w64-mingw32 to any directory you want. I recommend putting it in a folder that you dedicate to holding all your development libraries for MinGW. For these tutorials I'm putting it in a directory I created C:mingw_dev_lib
2)Next you're going to want to get up the path for mingw so you can run mingw commands in any directory. Open up the system menu either by A) right clicking My Computer and selecting Properties or B) going to the Control Panel and selecting the system menu. Once your in the system menu, click advanced system settings.
and then click environment variables
Under system variables, select the 'Path' variable and click edit.
What the path variable does is tell the OS where to look when running an executable. What we want to do is whenever we run the g++ command, the OS should look in the MinGW bin directory where g++.exe is located. If you installed MinGW by itself, the MinGW bin directory should be
C:MinGWbinAppend it to the long list of paths with a semi-colon after it and click ok. If you're using an IDE like Code::Blocks which uses MinGW, you can also set its MinGW bin directory which should be at
C:Program Files (x86)CodeBlocksMinGWbinNow when ever you run a command that uses a MinGW executable, the OS will know to look in the MinGW bin directory.
If you run your program and it complains that it can't find SDL2.dll, it means you did not set the path correctly.
3)Now go download the source for lesson 01. Extract the source somewhere. Open up a command window in the directory by holding shift and right clicking.
Now compile by entering this big old command (This command assumed you have SDL 2 extracted at C:mingw_dev_lib):
g++ 01_hello_SDL.cpp -IC:mingw_dev_libincludeSDL2 -LC:mingw_dev_liblib -w -Wl,-subsystem,windows -lmingw32 -lSDL2main -lSDL2 -o 01_hello_SDLHaving to manually punch in this compilation command gets very tedious very quickly. This is why I recommend using Make.
4) MingGW Make allows you to make build scripts that'll automate the compilation process.
After setting these two macros, we have the 'all' target which compiles the program. It's followed by the dependencies which as you can see is the OBJS macro, because obviously you need the source files to compile the program.
After specifying the name of the target and its dependencies, the command to create the target is on the next line. The command to create the target must begin with a tab or Make will reject it.
As you would expect, the command to compile the program is largely the same as the command we would compile it off the command line. A key difference is that we have macros that we insert into the command which makes things like adding new files to the project must easier since you only have to change the macro as opposed to changing the whole command.
In future tutorials, we will be using more libraries. We should probably use more macros to make the process of adding them easier.
Sdl Clion Windows
Near the top we have the macros that define the files we're compiling and the compiler we're using.
Next we have the 'INCLUDE_PATHS' macro which specifies the additional directories we're getting header files from. As you can see, we're using the include directory from the SDL2 folder we extacted earlier. The 'LIBRARY_PATHS' sets the additional library file paths. Notice how there's a -I before every include directory and a -L before every library directory.
The 'COMPILER_FLAGS' macro are the additional options we use when compiling. In this case we're disabling all warnings and disabling the console window. The 'LINKER_FLAGS' macro specifies which libraries we're linking against. Here we're compiling against 32bit mingw, SDL2, and SDL2main. Notice how there's a -l flag before every library.
Finally at the bottom we have our target compiling using all of our macros. Thanks to macros we can very easily change the macros to add more files and libraries as we need them.
Save this Makefile code to a file named 'Makefile' (case sensitive with no file extension) or you can use the one I premade here. Open a command line in the directory with the source files and run the command mingw32-make.exe. Make will search for a file named 'Makefile' in the directory Make was called in and run the Makefile that will compile your code.
Now that you have SDL 2 compiling, it time to go onto part 2 of the tutorial.
Note: to run your application you'll have to add the SDL2 i686-w64-mingw32 bin directory to your PATH just like you added MinGW bin directory so Windows can find SDL2.dll. If you updated the PATH environment variable you'll need to close your command prompt and open a new one because the command prompt only reads updated environment variables when it opens.