Last night I tried for maybe about 6 hours so many combinations of efforts to compile a C++, SDL3 and Lua program on Windows, with different IDEs, build systems, compilers, package managers etc. Finally I'm just giving up and using VS with CMake and vcpkg. The main problem is that there's way too many words on all those documentation pages. It would have taken 3 or 4 days to read them all, and maybe only 2 hours worth of it would have been helpful or relevant at all.
I agree. I used chatgpt to write a makefile to compile sokol+Tracy. It's a pretty solid, generic makefile. But "build system complexity" pushed me away from sdl, magnum graphics and bgfx into the arms of sokol.
And I'm a 10+ year gamedev.
Out of all of c++'s sins, the lack of a solid integrated build system is the one that bites me the most.
My theory is that good C++ devs haven't yet made a simple yet powerful build system because they're too busy making lots and lots of money writing enterprise C++.
We all just accepted CMake. It's not perfect but it works. C++ with SDL and Lua in a mono repo should be trivial. SDL3 supports CMake and Lua is simple to compile and make a CMakeLists.txt for.
This is correct. It has the key things that most C++ devs tend to care about:
- Cross platform support well integrating into "native" tooling
- Endless ability to add weird hacks to things to get around problems
The syntax is ...passable. I've never gotten a java stacktrace during a build failure (ahem bazel ahem).
It's straightforward enough to do the horrible things that C++ devs do all of the time like having 3 dependencies from system apt, 2 vendored, actually a 3rd is vendored but only used on windows, where the other 2 come from vcpkg, and 4 of these are statically linked but the last (openssl) is dynamic and accepts any version in order to support both ubuntu LTS and arch, but shipped as a dll on windows.
I have prayed before the CMake gods and they have accepted me.
Quite a few things. For a C++ only project, the biggest ones would be reproducibility and speed. But beyond those, I find it saner overall: the language is way easier to understand (~python), and the model of packages, targets, visibility etc makes it easy to organize and manage a large codebase.
The worst part about Bazel for C++ is that it’s not yet as widespread as CMake or plain old Makefiles so it can be harder to get third party libraries into your project, but that’s changing quite fast with the bazel registry, and you have things like rules_cc that help you run other build systems inside bazel.
Something about me has always wanted to learn and master C++. I've read through Stroustrup's book almost entirely, and still never written a single line of C++. I don't know why I have this goal in life, but I do. This project still doesn't do that, since I'm just wrapping SDL3 with QuickJS and will probably almost entirely just write C functions to do it with. But a man can dream.
I wonder if there is a SDL3 wrapper that comes with a scripting language[0], hot reload and build scripts for every major platform.
Love2D seems close to that, but afaik it doesn't support SDL3 features like the new GPU API.
[0]: It's not like I'm allergic to C++, but I firmly believe when developing something that is mostly interactive, such as complex GUI or games, a language that is garbage collected and can be hot reloaded would be much more apt.
DragonRuby seems interesting, but being a paid product immediately rules it out for me. I've been working on my own similar, smaller framework, which is more work, but I believe it's valuable not to depend on a for-profit company for your work, if at all possible.
Also, the attitude much of the wiki / promotional pages are written in for that framework runs me the wrong way for some reason. "Unity and GameMaker rot your brain"... are you kidding me? No they don't. You're still writing real code and solving real problems. They just have more systems in place you have to work within. I don't like the self-righteous attitude. It's fair to not want to go open source if that's your preference, but don't act like people who don't want to use closed-source software where possible are being unreasonable. I also don't see how what is effectively a Ruby wrapper for SDL3 is such an immensely complicated piece of engineering that it needs to cost as much as they're charging for it.
Why do I want to make money from my hard work? Or why am I sad when someone offers a way to bypass paying money for hard work to get something for free?
I meant that the author of DragonRuby is generous. And depending on your use case he might be willing to give you a free copy. Additionally, whenever there is a gamejam related to DragonRuby, he usually gives away free copies to anyone who wants to participate. For you to keep. Nobody said anything about bypassing paying money. Not sure what you were thinking.
You can build a project linking SDL3 with Lua and have access to all of the features of SDL3, with the obvious caveat that you'll have to code the rest of the owl yourself, but it isn't difficult. I have a basic CMake script that I use for projects and it works fine. (also, obviously you can just run the Lua code locally and skip the build process altogether when developing.) I use LuaJIT though, and the FFI generator here[0].
Obviously you can do what you like, but I'd advise making sure box2d (or similar) is super easy. Bonus points if there is also a built in function for drawing box2d objects.
I've often taught beginning game dev in a day, and with box2d in love2d you can very quickly make a wide selection of cool games, and while it's not perfect it makes it easy to get started making platforms, doing collisions, all sorts of things.
Fair enough, maybe I'll include it after all. Unless I get hung up on the question of which physics engine to include. Endless possibilities make decisions difficult.
A good way to think about it is in my opinion, you making a choice saves all your future users having to make that choice — imagine the decision making time they will all save.
That's my idea stack as well (I tried to build something like SDL2 + V8 at some point but ended up giving up...) If you have a repo/website set up please leave a link for me to follow :)
... at least if I can get the simplest Visual Studio + CMake + vcpkg hello world working.
Which I can't.
This always happens every few years. It takes me about a week to get a C++ program compiling and running, and by the end of it, I've lost all motivation, forget how any of it works, and delete it all and move back to TypeScript/web stuff. At least that I know despite all its warts.
[edit] figured it out
Hello me from the future, googling this in a few years. It's actually really simple: just follow the same steps on that page you were on[1] except you HAVE TO run the `vcpkg new --application` and `vcpkg add port fmt` commands in the dev cmd prompt, you can't just add the file manually for some reason, even though that's all it seems like it's doing.
Mainly it just reminded me of what happened last night and seemed like good timing because of the similarity, but also I appreciate blog posts that are short and get right to the point of how to do something.
Half of the problems I got past were thanks to odd blog posts like this with code snippets that I found on google and got me unstuck immediately.
