Makefiles Make Your Life Easier 

Br

Yo

Ar

So goo

Top

thats because makefile has nothing to do with C. its just a software thar allows you to use logic while executing CLI commands. of course, you can use it to compile C projects too

Long prompts are not bad if you're using a 2 line prompt, which for bash can easily be fixed with oh my bash

Downside / Consequence of using WSL?

It is an extra step. The reason is because if you're working on a large project with thousands of files, recompiling every single file will take hours. By splitting the build into separate compiling and linking stages, you can skip the compiling stage for files that don't need to be recompiled.

One reason is to rebuild the entire project from scratch, in case something got corrupted along the way or just to be safe when building the final executables. Or maybe just to free some space of build artifacts, once everything is finished.

@@tiagobecerrapaolini3812 But it’s not something you would want to do every time.

@@lawrencedoliveiro9104no the point is to simplify the process and write less commands

@@CorneliusCorndogJr The point of “make” is to follow the dependency chain and only rebuild what needs to be rebuilt.

@@lawrencedoliveiro9104 what the first reply says

Including hello.c in main.c would create one huge .c file when compiling. That prevents you from splitting builds into separate compile and link stages, which greatly slows down builds when you're working on projects with thousands of files. The strength of makefiles is more than just running the gcc or compiler commands for you; makefiles also determine which files need to be compiled and which ones can be skipped.

Ninja is an alternative to makefiles. Make originated at a time when it was expected you would write makefiles by hand. So Make (particularly GNU Make) includes a lot of features for expressing complex rules and expressions and things, to minimize the size of the makefiles you have to write. But nowadays, many if not most makefiles are generated by front-end processors like CMake or Meson or even GNU Autotools. So a lot of the advanced stuff in Make is not really necessary and just duplicates the functionality of those front-end processors. So we have Ninja, which is like a stripped-down reimagining of Make, which assumes that you will use such a front-end processor, rather than writing your Ninja files by hand.

use touch

maybe alias dude

Neovim?

Its neovim

@@zjardynliera-hood5609 thanks. sounds like a pokemon or something

Neovim

They have more power than that for incremental builds. Makefiles are s**t, but at least they're simple