Those extra commands are exactly what I needed to know how to do. So its a good intro example imo.

Perhaps that is why VSCode colored the line white "target_link_directories(${PROJECT_NAME} PRIVATE Adder)" while all other lines were blue ....It was a mystery until I read your comment. Thanks 😀

yeaaah, thank you, I also was confused do add_subdirectory also provides knowledge about inner directories and that's true. for header files you need to specify include directories and maybe some others idk

True, I tested with that too

What undergrad teaches this?

Awesome, thank you!

Great to hear!

Glad it was helpful!

target_link_directories is indeed not needed here because the library is a subproject that cmake is building

Did you find out the difference between 2 and 3 so far?

@@vladyslavtkach2209 I think you don't need this answer but maybe someone does :D use target_link_directories(...) when you already have a static/dynamic library (*.so or *.a) to let cmake find that in the folder (and then cmake will follow target_link_libraries(...) command to add that library to project) In the video above, we don't need target_link_directories(...) because : - We do not have *.so or *.a already - That lead to the command add_library that will compile the library into .so/.a with the "name tag" : adder From this it already inside the project so we do not need to find the dir of lib anymore

Thanks. The sounds come with MX Linux, the OS I was using here. I believe it was in the sound options.

You can just compile it as a static library and you do not need a main

Yep that is next episode after this.

@@CodeTechandTutorials haha, i was about to ask the same thing. im following your series so far, it's really good for a beginner, thank you

Checkout the Beginner/Intro CMake Course at www.udemy.com/course/master_cmake/?referralCode=D08DF343ABAE2835C3B7

Noted

It is made to detect it. I'm not sure of all the limitations, but the do have extensive documentation.

Nvm I was too hasty lmao

for instance a folder containing two other libraries (adder and subtractor?)

I think there are ways around it, but if it can't seem to find the library you are linking to, give your target the directory path to search should resolve it.

Generally only if it doesn't know where to find the link library.

@@CodeTechandTutorials Thank you!

@Brown Smith In this case it is not needed, because the lib is a subproject (a "target") and cmake knows all about it, literally.

In the official Doc it says: Dont use it, if u can do it another way -> cmake.org/cmake/help/git-stage/command/target_link_directories.html I guess, u dont need it here.

PS.: Or u need it, when u did the derping before xD

That'll work. There are so many different ways cmake becomes integrated into tools. Trying to give the base explanation first and I plan on talking about some of those tools later. QMake probably inovkes CMake. I've used qmake and qt in the past but it has been a few years.

target_link_directories is not needed

It doesn't really matter, as long you don't try to use any cpp function in a c file, otherwise you have to make it compatible with extern "C" { your code in that cpp file wich must be compatible with another c file }

@@julienguay7524 Yeah. I have written it using the extern keyword. I was initially hoping to have separate C files, link them together and then use them as static library for the C++ code.

The header file is only necessary to build main.cpp, all it does is tell the compiler how to pass arguments to these functions. It will compile main with references to these functions under the assumption that you're going to link another object file with the full definitions when you put together the executable. There's an understanding between you and the compiler that those functions will be fully defined later, the header is just a stand-in. When you're compiling the library code, the compiler doesn't need to have a stand-in for those function definitions because they're right there in the file you're compiling. I don't think it would actually hurt anything to include the header, it's just not strictly necessary.

We don’t need to specify an include location in the CMaleLists.txt for Adder because adder.cpp is including a header that is located in it’s same directory. If adder.h was located in a separate directory then we would need to either specify the whole relative path to it (similar to when he did Adder/adder.h in main) or add that include directory to our system headers through Adder’s CMakeLists.txt. I think using “” makes it so the file’s directory is first searched followed by system headers, while the skips the local search and just looks into system headers.

Generally reusability and ease of exporting them, and another big thing is for testing correctness, as they could each have their own test main file.

do it often enough and this all gets trivial. It is a bit more cumbersome than .net Projects, but it's not as bad as it seems ;)

In Ubuntu

Haha good stuff. Whoops didn't even notice.

Yeah, I regret leaving that in there.

Certified Bachelor. (of the arts and tinder swipping)

It's cool that you have found some better tools and methods. Care to share?

My guess would be: either you are not using anything from the library, or are using a version of the executable that was previously built successfully.