Absolutely the best video on Makefiles. Barry illustrates the dependency tree, and ties it to the Makefile. Additionally, he covers the pre-processor, compiler, and assembler and ties it to the Makefile build process. Well done Sir! 5 stars.
@@profbbrown Congratulations + a Like me here! ..... Please elucidate me in 2 questions? 1) - I would like to know if I can get the value / content in my APP_1 of a variable / pointer of a switch / case from this ".so" file that my other APP_2 has invoked and is using / updating it at runtime? (summary: I want to get the value / content updated by another app in my app). 2) - And the most important thing I need to understand is: .... If this variable / pointer in a Function within ".so", which has its content / value dynamically updated by app_2 (because it gets updates by reference because it is a pointer, the value of this variable in App_2 is changed from time to time, and the file / library ".so" that my other App_1 wants to consume from it is a dependency on this application "App_2"), can this ".so" variable / pointer have its value / content (dynamically updated by App_2) consumed in my App_1 at runtime? ............. NOTE: My App_1 will only run when my other App_2 is running I think to avoid using higher level language features like BroadCastReceiver, Intents and System Calls. , etc etc .. ok. Thank you very much from my heart and Congratulations for the content once again, very didactic and easy to understand, offering a very quiet learning curve to all !! .... Strong hug, Barry !!
This is by far the best makefile tutorial on RU-vid. Only thing missing are the dependencie files (*.d) and why there are needed but explained everything about *.o files
That is the proof of your video's quality: I came back to this video after watching it for the first time two year ago. Again, congratulation for this wonderful video!
I watch a lot of videos for programming and this has by far been the most educational and biggest time saver for a complex process rather than asking my professor and waiting on him to email me back. your video layout is really helpful as well. Thank You!!!
ive been looking for videos and websites for days to understand how makefiles work. this is definitely the best explanation so far despite it being a 5 year old video. thank you so much Barry for making it simpler!!!
I am starting my career as Embedded Software Engineer and I can tell you that this is the best explanation so far!! Thank you a lot for this, it is very clear.
One of the clearest tutorial videos that I have ever found in my life about C programming and Makefile. I gonna check out the rest of your videos from this playlist. Congrats!
For me this is really the best video for learning Makefiles on RU-vid. You were really able to make a balance between diving deep into the topic and not overwhelming us with anything which is extra and could be described in a future video. Thank you!
I am in first year university and in intermediate programming. Intro to programming was fine, started intermediate... I couldn't even follow along in lectures. I just want to say, thank you for this. This video has helped me more that you may ever know. Need to secure a tutor now to keep on top of new content in my course!
Just Amazing, I would advise going straight to this video and leave the rest Makefiles introductory videos you find in RU-vid search results. You might also want to consider reading the Wikipedia page, and afterwards some advanced documentations that may include functionalities that are required for your own purposes of using makefiles. Straight to the point, detailed just enough, and very very clear. Much appreciated Barry Brown
Great explanation! It's nice to see someone use a compiler via the command line to show how it all works rather than relying on an IDE to do all of the work for you! Really appreciated.
What makes this video is unique and brilliant is the way of explaining the concepts. Even with the simple headers, instead of saying "hey guys, header is this and I'll show you how to use it.." , in this video it is explained in the way that it made us feel the reason behind why there is a need use use them instead of just a straightforward definition. Excellent explanation Sir !
You're the man Barry, your video finally made this topic come together for me! Your video feels like a more experienced co-worker taking an hour off his work to explain a topic he's intimately familiar with.
I'm not a C programmer. I came here to learn how to use Makefiles for other purposes: building a minimal static website generator. This screencast is brilliant! THX
You're welcome! Makefiles can be used to automate the build process of just about anything. If you can write out the commands needed to build a project, you can turn them into a Makefile.
Thanks a lot for this video! Was watching and thinking that if every teacher in university would explain things like you do, the world would be a little bit better.
Having only ever used an IDE for development I never really got exposed to makefiles so I came researching to plug the hole. Well explained, and now I understand that the IDE essentially provides visual abstractions of the makefile elements, and so explains how I hadn't previously bumped into their inner workings. I somehow feel less dependent on those IDEs now...
Thank you so much for this video! Everything is illustrated perfectly with your explanation and the diagrams. I was so lucky to find your video at the beginning of makefile's learning so that I didn't wasted too much time on other less comprehensible tutorials.
Hey I don't know if you're still reading comments on this video, but I just wanted to say thanks. I've been trying to wrap my head around makefiles, and it's been so confusing... targets, recipes... rules... linking? I wished I could see an explanation of how it works from the ground up, but pretty much all the videos I found were confusing... until this one, which I just watched straight through in one sitting. Now I finally get it. So thank you so much for explaining it all so carefully, clearly, and thoroughly! Also haha... when I saw the rm * .o ...I felt that.
Dear Sir, Thank you for the clear explanations. I have been hunting videos and article to learn what those make files are and how to use them. They were very complicated and had unexplained syntax in them. Today you enlightened me with this clear video. If you have time, kindly explain a bit more complicated syntax in Make files. Then, I and people like me who learn from the help of gentlemen like you who share knowledge can complete learning this stuff.
This is one very educative very, I will recommend it to my fellow software engineering students at African Leadership University and ALX. Thank you so much for the content
Absolutely phenomenal, cogent presentation. This is perhaps the clearest introduction to file organization as well as the basics of the build process I've seen. With that said, I had a quick question regarding the point you made at 25:35. We have established that header files only contain function prototypes, global variable declarations, pre-processor directives, etc. If we include, say, the math header file in a source file, then the compiler won't be able to compile the program because it isn't able to locate the actual definition of the various math functions. This is why we must use the compiler directive -lm to indicate that the compiler must search the directories for the math library. If this is true, then why isn't a similar thing done for the header file stdio.h? This too is a header file, and so it doesn't contain the actual function definition for things like printf, and scanf. Why, then, do we not use compiler directives to indicate that the compiler must search the directories for the stdio library? What is the difference between the math library and the stdio library that causes this difference in behavior?
Good question! The C standard library is linked in by default. In addition to the I/O and memory management functions, it also contains some setup code that your program needs to run. You can disable the automatic linking of the C library with the -nostdlib command line flag.
Excellent Sir. Even though I am using make for DevOps activities, the concept of dependency tree inside make was a very good concept to understand make better.
Thank you for your video. Although I know a typical Makefile for a project is more complex than this, your lecture is quite easy to understand. Thank you for your patient introduction from the very beginning of how gcc works from a .c file to an executable file then furtherly move to the introduction to Makefile.
Just what I needed. A down to basics review for Makefiles. Been trying to build up my C++ proficiency, but it's like an octopus. To write C programs on Linux you need to learn C++ (and a bunch of modifying flags), linux, editors (vi. emacs), editor systems (Visual Code), compilers (gcc, clang, etc). I have managed to compile a few simple programs without make. Breaking down the various stages of compiling was very helpful and a great intro to make. (I would also like a discussion of what the linker step actually does, nobody talks about it. My first compilations, many years ago actually talked about compiling to object files and then using a linker to link them , but now the linker step is in the shadows.) The discussion of library "header" and non header included files was helpful. The process to create a Makefile line by line was very helpful. But Makefile is just the first step of abstraction, after that it seems you need to know c make, git, docker, it just goes on and on. My goal is to download git code and be able to assemble modified working programs and this video clarified some of the basic steps. Thanks.
Thank you very muchBarry Brown, clear, easy and full explanation. Great idea with screen and you on the corner, looks really professional. Good sound, everything is clear. Other youtubers should learn from you. Just perfect!
Thank you for this outstanding lecture. This is so amazing. Thanks to your video, for the very first time, i can have a good understanding about the structure and the meaning of a makefile in detail.
Thank you very much! This is, for sure, the BEST explanation about Makefiles that I have found on the whole Internet! Thank you, thank you, thank you!!
Might be 7 years old but this should be given to every student studying C. Should also be shown to the majority of CS teachers who fail at teaching these concepts. This is how you teach - show why something is done the way it is done and why it is required and what problems it solves instead of just saying "you have to do it like this".
The mystery about the compiling process, the flags, the different temporary files and how header files actually work. I now understand why header files and implementation files that contain the code for the definitions in the headers should be separated, because this way all the code that implements the stuff defined in the header does not get compiled every time the .cpp that includes the header is being compiled. So far I always did the implementation directly in my header files and never understood why people would link some weird object files together if they could simply just compile their whole program. But they of course did that because they *had* to, because their headers only included definitions rather than implementations. Though, one thing I I still don't understand, why does one not have to explicitly link libraries like and and so on? Maybe that is a difference between C and C++? Because I do C++.
+ElizaberthUndEugen By default, C programs are linked to the Standard C Library, called libc (or glibc on Linux systems). C++ programs are linked to libstdc++. This comes automatically when you compile a program. These libc contains functions like printf, scanf, malloc, fopen, and the like. The Standard C++ Library contains the standard classes like iostream and vector. You don't need to explicitly link to these libraries.
Like I am programming during my whole Bachelors, Asking everyone what are Makefiles but unfortunately, the same Answer searched from the google, Finally, Thanks to you Sir to let us know what really Makefiles are
