CMake Tutorial EP 8 | find_library(...) (part 1/2 of find lib)

[@prashantchavan2673]

Most organic tutorial with real failures! This way will get to know where things can go wrong in real scenarios. Superb and keep it Organic as much possible!

[@fededevi1985]

The intro background music is so mystical and depressing, perfect for c++ build systems.

[@henryliu2644]

The background music made me pee a little bit in the beginning

[@behshadmohebali6234]

One thing I like about your tutorials is that you run into problems, go back and show how to fix them instead of going back and do it right from on the first try without showing what would happen if we miss something. That helps a lot!

[@namedtoaster]

Should be more likes. Couldn’t find many other places where Cmake is explained this well and in this format. Good work 👍🏼

[@amarboldbatzorig7313]

This tutorial is the best that I have found because it keeps things simple and you explain it well.

[@aleksanderklepov8881]

Thank you very much for your videos! I really appreciate your work. This is the most helpful CMake tutorial on the whole youtube!

[@CodeTechandTutorials]

Glad it was helpful!

[@MrDemultiplexer]

I thought you were going to throw some of them jokes during that dramatic introo

[@mariapanneerrajan]

Great videos on Cmake, just now completed watching all the 8 videos. Your explanation is very clear, by watching these videos I have a better understanding on how to make use of CMake. Thanks for making these videos. Looking forward to the next episode on CMake, :)

[@CodeTechandTutorials]

Glad it helped!

[@sahilgupta221]

This is really helpful. Small video series that people can watch in small quantum. Thanks a lot. Keep up the good work.

[@dex8487]

you are the fricken man, CTT!! these tutorials are so well explained - an excellent resource

[@tenprinthello8127]

The most important takeaway from this video series is that Cmake has some very strange practices that do not make any sense at all. The whole -DNOSPACEBETWEENDANDTHEREST thing for instance, I had to stop the video for a moment so I could scream WHYYYYYYYYYY

[@mouduge]

Nice video. However, at 6:04, the problem comes from the fact that you should use `if (myglewlib)` instead of `if (${myglewlib})`. Your code is equivalent to writing `if (/the/library/path)` when the lib is found, or `if (myglewlib-NOTFOUND)` when the lib is not found. Neither of these match any variable name, so they are both considered FALSE. Conversely `if (NOT ${myglewlib})` always evaluates to TRUE, so the `if` block will always be executed, even if the library is not found. That's not what you want! The proper solution is writing `if (myglewlib)`.

[@Jack-4242]

Thank you, this tutorial helped me very much :)

[@marcin8680]

One of the true crime podcasts I listen to uses that tune too, feels weird watching a cmake tutorial with it 😂

[@SteigerMiller]

YOU SIR are my lord and savior

[@ridwannana-yawamoako2939]

Great tutorials. We need a complete playlist on Cmake for windows

[@xiaoxucao470]

When u include the header in main.cpp how to get the path ?

[@yy84869]

You are a life saver , thank you so much .

[@j.c.s5630]

order of operations bro. you need to use the NOT with parenthesis

[@karmavil4034]

LOL :D hilarious the way STREQUAL works is ridiculous I am verifying that something like A = A evaluates to false how is that possible (cmake -v 3.22.1) Is this a bug introduced as feature for backward compatibility? ;D And according to the documentation it should work as it is expected.. but it doesn't if( STREQUAL ) True if the given string or variable's value is lexicographically equal to the string or variable on the right.

[@karmavil4034]

My bad (clearly) trailing } symbol :( although I couldn't make this command to do its job it was a great video as always. Good content

[@CodeTechandTutorials]

Thanks for clarifying. I have learned to put quotations around string equal comparisons

[@karmavil4034]

@@CodeTechandTutorials I loved it! It's my new friend:)

[@ahmadalghooneh2105]

Thanks !

[@mohamedhussien4013]

Good tutorial but it can be compressed to be shorter.

[@fanpeter-z3c]

thank u

[@GalaxyExpress-hq9qb]

Good song 👍

[@gregorycarlson6445]

I appreciate the progression of libraries in your example: glew -> glu -> gl It's like its slowly breaking down more with each step.