In this video we look at the basics of implementing clean rules and phony targets! GNU make Phony Targets: www.gnu.org/software/make/man... For code samples: github.com/coffeebeforearch For live content: / coffeebeforearch
Пікірлер: 6
@a_maxed_out_handle_of_30_chars6 ай бұрын
simple and to the point, thank you :)
@tapiacarlos111 ай бұрын
Wanted to say thanks for all the amazing info! I'm an undergrad that stumbled upon your channel! I'm super interested in c++ dev and your videos are exactly what I'm looking for; I'm running through everything and learning a lot + loving the format! I'm looking through the channel and I was curious to know what are some assignments or things you've worked on while going through the graduate/PHD program (like projects or assignments)? I would love to sharpen my skills and be a better low-level engineer (as low as c++ is considered)! Thanks again for the amazing content!
@_ab_6490 Жыл бұрын
With your way of explaining you make things easy to understand I hope you talk about linker script ur YT channel 💪
@CoffeeBeforeArch Жыл бұрын
Glad you're enjoying the videos :^) Cheers, --Nick
@evgeniisharaborin8071 Жыл бұрын
Hello! What is inside a clean file? As I understand it is empty. But I have never seen a clean file in other open-source projects. It seems that adding a clean file is not a good practice, am I right?
@CoffeeBeforeArch Жыл бұрын
Having a file named "clean" is just one example of how the existence of any file with the same as the target of some rule will prevent some recipe from running. The file could be named "clean" (like this example), it could be "install", it could "help". The key point is that there are rules that we want to run the recipe for with some target name, but that rule doesn't actually generate a file named . That's where .PHONY comes in, to express that it's a phony target, and to always for the recipe to run for that role, regardless of any file with the same name as . Cheers, --Nick