olcPixelGameEngine VS SDL

I'm using SFML to develop my game engine (Though I might switch to olcPixelGameEngine at some point in the future).

If you want something simple (single file to drop in a project) with a nice easy C++ API for 2D graphics there is OneLoneCoder's Pixel Game Engine.

The PixelGameEngine from OneLoneCoder would probably fit here.

As always, I recommend https://github.com/OneLoneCoder/olcPixelGameEngine :) It's just one header, so you just include it in your project and you're good to go.

And if you want to try making a small game with rudamentary graphics, but not go full OpenGL/DirectX, take a look at OLC pixel game engine. It's a one header graphics library that will allow you to draw simple shapes, text, etc. perfect for prototyping or making very simple games. Eventually you'll want to try making Pong to take your training to the next level, so this will be perfect for that.

For a beginner I’d recommend the One Lone Coder Pixel Game Engine olcPixelGameEngine It is a single header library, works in Windows, Mac and Linux. The author also has some great game programming videos on his YouTube channel OLC YouTube

The source code is public and under the license of the olcPixelGameEngine found at: https://github.com/OneLoneCoder/olcPixelGameEngine

All you need is here. Just put the .h file in your project and you're done.

The linked project doesn't use any ObjC files at all. SDL2 has a bunch of Cocoa files[1] so you did use Cocoa even if unknowingly.

[1] https://github.com/libsdl-org/SDL/tree/main/src/video/cocoa

Correct. It's explained here:

https://github.com/libsdl-org/SDL/pull/9345#issuecomment-201...

XWayland has special hooks into the compositors that normal wayland clients don't get.

Found about this through the release of SDL 3: https://github.com/libsdl-org/SDL/blob/main/build-scripts/SD...

https://github.com/libsdl-org/SDL/blob/main/include/SDL3/SDL_events.h

If that app ran in a 640x480 mode, memory accesses would be just as fast as the VGA applications 25 years ago, correct?

I think there's a lot more going on than that. Here's SDL's current pixel access code:

https://github.com/libsdl-org/SDL/blob/main/src/video/SDL_su...

We use the code examples throughout the article. The ellipsis characters "...." in the code were added by the author of the article. You can find the source files on the official GitHub of libsdl. In addition, each fragment has a reference to a specific area in the code. By the time this article is published, many errors will have already been fixed thanks to the issues we opened (for example, here and there). However, the links in the examples point exactly to the code you see in this article. Not only do we enjoy teasing developers but we also like making their projects a little bit better!

FetchContent_Declare(SDL2 GIT_REPOSITORY https://github.com/libsdl-org/SDL.git GIT_TAG release-2.28.3 ) FetchContent_MakeAvailable(SDL2)

It's not that difficult, I recently started learning to use graphics APIs myself. OpenGL is for linux, etc., directx for windows and vulkan for all platforms. I read through a bunch of forums yesterday and decided to go for vulkan (here is a link to the sdk) for my next small projects because it can run on all platforms. I would recommend to watch a basic tutorial series (like this one) for the graphics api itself to get an understanding of whats going on. And on top of that I use SDL2 for eventhandling and ImGui for the graphical user interface. Here is a link to a guide for setting up vulkan on your platform in case you would go for it.

SDL (which will be bumped to SDL3), straight from the authoritative https://github.com/libsdl-org/sdl