Google "(language) koans"
If a project itself has no purpose (i.e. is just providing a justification to code something), you will 1) experience that the project scope will expand into many directions, leading to an overhelming amount of ideas and work, and/or 2) you will abandon the project early on, after you have written a lot, but before you have learned much. This is usually a demotivating experience, followed by a guilty feeling of not having "finished" it.
You need at least one real user for that project, be it yourself, some friend, or a charity organization. That way, you will find it more easy to limit the project scope and to stick to realistic goals. This will be more motivating and satisfying, even if it ends up not being used in the real world. Along that route, you will probably learn more, and the things you learn will be more useful to you.
I've done useless projects at school and at work but the point of those projects was to get credentials or money.
If you're doing this for fun, you should start with something you want to make. A game idea, an app idea, a robot that does something. Break the problem into the smallest parts and start with that.
I also hate complicated compiling processes, bloated tools, or anything to do with configuration. But that's just part of software development. You'll have the motivation to plow through that if you really want to build something.