1.Try SFML,then opengl or 2.SDL/SFML,then directx

I don't feel there is any reason to move on to openGL or directX after using SDL or SFML. There are quite a few successful projects made in SFML, such as Kill Fun Yeah. A move from one library to another shouldn't be done unless you feel that SDL or SFML arent serving you right.

If you want just to create a game,after C++ try Unity3D,it's a nice tool for creating games ;] ,HOWEVER,you will not be allowed to sell that game(if you are thinking about a serious game ),it's just for fun.Gl

This is not true. You can sell the games you make with the free version of Unity, as long your profits do not exceed about $100,000, in which case your will need to purchase Unity pro, which should be affordable for anyone making over 100,000.

But the thing is I've checked out C++ languages. And I'm wondering. How do I use this to create a game? I know that I can use these commands to imput text and algorithms but the tutorial doesn't even tell me how to use this in an application. And how are game engines used in game making? And is C++ totally different from things like Python in types?

You're trying to run before you can even crawl! Those are all great questions, but they require more than a few lines to adequately answer. What's more, you're going to need a basic set of knowledge to be able to properly understand them. I highly recommend you store these questions away somewhere (don't forget them!) and dive in to learning how to actually use a programming language, be it C++, Python or whatever. As you learn to write simple programs, you'll eventually start to understand how everything comes together to make an application. As you become more and more comfortable with the language, you'll be able to make more advanced programs. Eventually, you'll be ready for some simple games and that will lead you to understand how game engines are used to make games. At some point, you'll also find that you're able to learn other languages more easily than the first one you learned, then you can start to make comparisons between them (like C++ and Python).

In short, take it one step at a time. Start with the basics and one day you'll be able to answer many of your questions yourself. For those you can't, you'll be more equipped to understand the answers others give you.

I agree with a lot of mentioned here. But I think as mentioned the learning the language you want to program your game in is key. Some say get to work on rendering and animating etc... but what about looking at the basics;

Variables and data types

Classes and Objects

Conditional Code, If, Case, While, For

and so on.

C++ is a good language but it is far from the easiest language to learn. C, Java, C# are a little more forgiving than C++ (as in if you make mistakes, accessing memory not yours can get you into big trouble) and lead you nicely into C++ when the time comes to push things further.

But also one can learn about the way a game works, using GameMaker can simply enable you to see the game come together, wonderful tool for prototyping but even releasing the game itself. Most of what I have read here should get you inspired to go further into games and I wish you all the luck.

Troubles, just ask there are many people here who are willing to help for nothing and

But the thing I'm wondering about is what do I need to make a game... APIs, game engines, libraries etc to make a very basic game. (And whether I even need them... it's 2D btw.)

What you need is what's already been said: a language that you know and a compiler/IDE in which to use it. And then, you'll need experience coding. You need nothing else. You can and in many cases should use various APIs, engines, libraries, etc., but you don't need any particular one. Which ones are even options depends on what specifically it is you'd like to make.

From the information you've provided so far, I'd say SFML is a great library to use. C++ is fine, though I think you'll get off the ground more quickly with C#.

Beyond this your question is pretty vague, which may be why the answers you are getting don't appear to be quite what you're looking for. If you want to code your own game (as opposed to using game-making software) you're going to be building just about everything I think you mean by "game" by yourself and out of nothing. Have you designed any specifics of what you want your game to be yet? If not, doing so will really help you break down the tasks that you still need to do.

A good first step might be to open a window. Does your game use a GUI-style menu? Sketch out some ideas on how you would do that using your language of choice and any libraries you plan to use. How you start a game is the same as how you make any other part of it: you identify a task that needs to be done, and you figure out a way to code it up. It's always overwhelming at the start, and getting to work is the only way through.

but the tutorial doesn't even tell me

This strongly suggests to me that a 2D game might be a bit advanced of a project for you right now. It's not that you can't do it, it's more that people tend to radically underestimate how much stuff there is to do to make the game they're imagining. You'll know your experience level better than any of us. Have you done much coding yet? If not, a simpler game might help you get a handle on the game-making process without seeming so daunting.