วีดีโอ

That's fantastic thank you very much, I hope you create more content (;

this is a really cool and useful video, help me a lot, thank you for doing it!, may i ask you which theme were you using for this video if you recall it?

Yes, just what I need. Thank you

Amazing! You deserve another comment!

This is THE BEST tutorial on make out there. I've looked at so many other resources but I couldn't understand a thing reading/watching them. Thanks a lot for your effort :)

great class! Is there a way I can ask you some questions directly?

I LOVE YOUR VIDEOS! IM LEARNING A LOT!

Thank you for this video! This is exactly what I need.

Very interesting stuff your videos are really unique and your explanation is crystal clear thank you for putting the effort in those videos

Very good video! A couple of things though; how properly to place all build files (*.o, *.d) in its own "build" directory and the use of .PHONY. Keep up the good work!

void* are great in C. we can do almost everything we want. combined with tagged (with enum type) union type inside struct type ...allow to make versatile objects.

Which Linux Distro are you using in this video?

Thanks for the video and all the great information! A higher resolution than 480p would be lovely for fluent readability.

Great video!

What an absolute goldmine of knowledge, thank you!

Your video's are a very usefull resource to me. Thanks a million times :D

Great video of the basics <3

Having inherited a project that uses make on Linux, and coming from a Visual Studio on Windows background, this has been so useful in helping me understand what is going on. Thanks.

With compiling C programs into one binary I discovered a more slick and actually more efficient approach. When compiling from source code into executable directly (without intermidiate object files) with addition of `-flto` and `-fwhole-program` arguments, compiler implies much more efficient optimizations, kinda like putting everything into one big `.c` file, but still presuming file scopes and other stuff from C language, but whatever. What I did is created a make macro `define prog-compile` (read about define thingy) to compile a target `$@` with all requirements of target put into `$(filter)` make command. Like that: $(CC) $(filter %.c %.s,$^) -o $@ $(CFLAGS) ... and then wrote a target: myprog: main.c config.h assembly-inlines.s assembly-inlines.h <TAB> $(prog-compile) Essentially `filter` filters out arguments from `$^` (which is all target requirements) and leaves to compile only `.c` and `.s` files as compiler arguments, but still detects them been updated to rebuild `myprog`. This is HUGE improvement over programs compiled from object files because compiler can even elliminate all your internal function calls, inline them and replace everything with jumps or whatever. Try it, you will fall in love with it.

its much simpler to use addprefix instead of foreach cycle for CFLAGS, isnt it?

Amazing video! Thank you!

Great video. Other tutorials only ended up in confusion for beginners. This is THE makefile tutorial. Thanks for doing this.

Nice video, thx for sharing

Great video. came with no information and left with all. thank you

Absolutely flawless video, and flawless teaching style. Never stop teaching, you have what it takes!

Is Make able to detect changes in .h files from system or compiler libraries?

This is very useful for me.

You are a genius educator!

Ngl you kinda sound like Joe from family guy 😂.

Thank you for that!

Hi there, Why is there a difference in declaring the directories? I mean, why are both directories not addressed in the same way? Like either: CODEDIRS=. lib INCDIRS=. include or else: CODEDIRS=. ./lib/ INCDIRS=. ./include/

Dude … this is so good. The stuff you can find FOR FREE on the internet.

I rarely comment on videos, but this one slaps

the remaining 5% would take you the next 10 years to learn

Are you using emacs?

Thanks man!

Why did it take me a month to hear about .d files. I swear nobody mentions those but it’s so confusing trying to understand something when people omit information like that. Thanks boss :)

This is an unusual use of header files. Usually you have a corresponding .h file for every .c file except main.

this is a great video. Thank you very much!

i have a question abut the declaration of CODEDIRS and INCDIRS. What is the meaning of the one dot "." or 2 dot ? CODEDIRS=. lib #Source code directory INCDIRS=. ./include/ # Include directory Is it important to include since i saw other people do not use it

What a great tutorial. I’m only jumping back into Linux recently and not only did you teach me about make, but you also provided a great refresher regarding C, lib, includes etc. thanks a lot

Great, fantastic, love it. The only part missing for my prog was a way to include a pre-compiled library; in my case the "mosquitto" library. I just added a 4th line to your first three. OTHERLIBS=mosquitto Then LLIBS=$(foreach D,$(OTHERLIBS), -l$(D)) and lastly chg'd the rule for $(BINARY): $(OBJECTS) to [tab]$(CC) -o $@ $^ $(LLIBS)

thank you for explaining in a way that is so easy to understand

This video is very very good starting point for those beginners who are learning build systems. Thanks for such amazing content

I've looked for a long time, finally I've found the ultimate Makfile tutorial. This was so great, thanks so much

Thank you for a very informative and complete tutorial. Much appreciated.

Thanks for an amazing video! I've recently started watching your vides/lessons after a suggestion from a friend of mine. And so far everything is going great! Your explanations are clear and pretty straightforward [for beginners like me]. I have one question though. Does it really makes sense to compare VMs to monolithic kernels? Sure, they are very similar in terms of their structures, but they are two different categories IMO. So, questions like: Why VMs are better? is super weird to me.

Great video. Thank you!

Lovely explanation , Brilliant and I mean brilliant !! I wish there more of you about who can explain this with the well defined , well thought out descriptions that you have used in your presentation I understood everything you were doing Thank you PS for other people as we now in 2023 who feel AI will give you these answers then Im going to say , "No AI no matter how good you think this is will and no AI will help you and guide you to this depth and understanding This is why we need people like Gabriel Parmer especially in poorer and less educated sectors where this is no help and all controlled by finances " You need to understand the essentials of this Im pleased we still have some who have recognised this and know what is required Its not a case of how quick , how fast or , how many cuts to education our officials can make or where others see AI as a method of doing away with people especially in education Its very much a case of how the use of AI where people in positions of power need to be very clearly show just how much they dont understand and why persons such as Gabriel Parmer are very much in demand I hope this justifies all comments I make whilst I highly recommend tutors such as this which we are lucky to have If only many other people in many an industry would actually wake up to the damage they do by making the cuts they have in conjunction with the loss of real professionals in all industry even more so in teaching and training

why is your /home file called ycombinator ?