I would steer away from "Book designed for narrowly specific category X".
If you want to learn programming, you ought to learn C++, SDL, OpenGL, and game architectures in general.
The reason for this is because even though books like "Learn to make RPG games using SDL, OpenGL, and C++" actually exist, they tend to spend part of the book teaching C++ poorly (or glossing over it), part of the book teaching SDL poorly (or glossing over it), part of the book teaching OpenGL poorly (or glossing over it), part of the book teaching game architecture poorly (or glossing over it), dump a bunch of source code on your lap, and pretend that everything is obvious and "Now you know how to make games!!!!! Go make your own!!!!", leaving you with a $60 paperweight that you might've learned two or three good things from, a dozen things you could've learned online for free, and two dozen bad poisonous practices that you'll spend years not realizing have harmed you more than they helped. </opinion>
Buying a book on modern C++ is great (if written 2012 or later - almost everything before that is either outdated, or not beginner material anyway). Buying a book on game architecture is great because programming practices and general knowledge can be useful even a decade or two later. Buying a book on OpenGL or SDL or any specific API is bad, because whatever book you get is likely outdated before you even read it. For APIs like SDL and OpenGL, I suggest just using online resources.
In general, APIs change every year or so, languages change every six or seven years or so, and general programming practices change every decade or two. Leastwise, that's my experience in my tiny corner of this vast programming forest I've intentionally gotten lost wandering in.
For the things that change infrequently, a book or two can benefit greatly, coupled with online reading, googling questions, and then forum questioning.
For things that change frequently, skip the (almost always outdated, very often poorly done) books, go strait to online resources/tutorials, googling questions, and then forum questioning.
Yes, you can get some benefit from API-specific books, and some benefit from "Learn to make RPG games using SDL, OpenGL, and C++"-style books, but you can just as easily get that information online, for free, often written by the authors of those APIs, and directly ask questions tailored directly to your information-gaps when still confused.
Another general spot of advice: Don't pay for online videos or online tutorials also. While a few might be good, it seems like most are junk, and you can almost always get the same information through tutorials, articles, and googling and asking questions.
Hopefully that helps. Welcome to the community, btw! :)