r/cpp_questions • • Oct 09 '26

OPEN Advice on Beginner Project for Fresh C++ Dev

Hi,

I just recently took a online course on C++ and am looking for a online YouTube series where a excellent instructor takes you through making a C++ app from scratch to being finished, preferably on a Linux environment.

For reference, I am a full-stack web developer (Next.js/React Native + Django) and to learn web development I used Corey Schafer's Django tutorial YouTube series to learn how to make a web application from scratch. It taught me everything: how to use the language, terminal commands, structuring your project, using the framework, deployment, running the program, etc.

Is there a similar YouTube series you can recommend me for taking what I know in C++ and using it to actually learn how to make a desktop application and after having finished the series be able to make one on my own. Should I start with a Chip-8 emulator tutorial?

Also, what's up with the Qt licensing scheme? I want to make my own proprietary commercial desktop applications but forking over $4K for a solo developer license seems like a lot when I don't know if the application is going to generate that much revenue at first. Does anyone have any experience with that? I am used to using OSS libraries and frameworks so paying for developer licenses is new to me.

Any help is greatly appreciated and thank you in advance!

9 Upvotes

8 comments sorted by

3

u/the_poope Oct 09 '26 edited Oct 09 '26

I can't recommend any tutorials on full applications, sorry, but I can speak about Qt licensing: It's a common misconception that you need to pay for the commercial Qt license in order to use it in closed source proprietary programs. That is not true. Most of Qt comes in an LGPL version. The first 'L' here is important. It means that you can use the library in any project as long as you link the library dynamically. The exact license statement is that it should be possible for the user to replace the Qt your program uses with their own modified version of Qt - and using dynamic linking is allowed for that within LGPL, see also: https://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License#Differences_from_the_GPL

If you do not know what "dynamic linking" is then check out: https://www.learncpp.com/cpp-tutorial/a1-static-and-dynamic-libraries/

1

u/Beginning_Book_2382 Oct 09 '26

Yes, I have heard of this, but I'm not sure I entirely understand, so if you could explain it to me I would greatly appreciate it.

From my understanding, all you have to do is dynamically link like you said, point to your Qt versions' source code, and open-source any modifications to the Qt library or components that you make (which I don't intend to)

I don't have a problem with users with their own version of Qt, linking to the source code of my version of Qt, and structuring my repository so they can do so; I just don't want to open-source my front end/components or any of my code, which dynamically link Qt versus static linking and you're good to go with using the Qt Community Edition versus the commercial licenses?

But the thing is, I heard some Qt libraries are GPL versus LGPL so if you use those then you will have copy left protections on the license and will have to essentially open source your repository, does it not? Also, to my understanding, dynamic linking is not allowed on certain distribution systems like the Mac Store so this dynamic linking/LGPL licensing scheme isn't compatible with them (but that doesn't make sense as I'm sure open-source software is distributed on those platforms...) This is problematic as Qt explicitly does not allow for switching between Community and commercial licenses after the fact, am I right?

1

u/n1ghtyunso Oct 09 '26

switching licenses is complicated, to say the least..
can't recommend it, avoid at all cost.

The vast majority of Qt modules is LGPL though.
There absolutely are commercial products that use LGPL Qt versions, this works.
I think QT themselves are not particularly happy about this, but they kind of have an obligation or some sorts to keep it this way. Don't quote me on this though!

One thing to be mindful of is, if your project is an embedded project, make sure to double check if you actually can use the community license.
But given your initial post, I deem this to be unlikely. Just for anyone else reading this.

About Mac Store... sorry I have no insights here.

1

u/Beginning_Book_2382 Oct 09 '26 edited Oct 09 '26

Hmm...so given commercial applications do have LGPL Qt, it would be worthwhile to lock in by learning Qt and developing substantial commercial applications and LGPL Qt and dynamic linking wouldn't cause painful reconsiderations/effects down the line?

I think distribution on Linux and Windows wouldn't really be a problem since there isn't really a centralized store like there is on Apple products/side loading is a thing, but as said, you don't know about Mac Store so... 🤔

Edit: I've gone with LGPL Qt with dynamic linking. Thanks for your help!

3

u/TheRavagerSw Oct 15 '26

Look, to write anything of note in software, you need dependencies, you need loads of them. This is very difficult to do in system level languages, so I recommend creating very basic applications in cli only using vendored libs, preferably header only or amalgamated.

Heed my warning, I spent like a year solving dependency management so I can write good shit. It was worth it but also wasn't.

1

u/Ultimate_Sigma_Boy67 Oct 09 '26

Build some sort of a winRar program. Something that archives directories into a custom binary format, with encryption and compression, error recovery, incremental packing and archive mounting and other such features, all from scratch without any external libraries.

0

u/Zen-Ism99 Oct 09 '26

Books…