Understanding your project's file structure.

Concept Breakdownīecause Makefile is just an amalgamation of multiple concepts, there are a few things you'll need to know in order to write a Makefile: Also, if you need a refresher on how Programming Language Processors work, we've got you covered. Well, Python is technically both an interpreted and compiled language, because in order for it to interpret a line of code, it needs to precompile it into byte code which is not hardcoded for a specific CPU, and can be run after the fact.Ī more detailed, yet concise explanation can be found on Ned Batchelder's blog. This concept is very useful and is commonly used with compiled programming languages. In this context, a child is a library or a chunk of code which is essential for its parent's code to run. It can also automatize compilation, builds and testing. Makefile essentially keeps your project up to date by rebuilding only the necessary parts of your source code whose children are out of date. However, the name Makefile is much more recognizable.

Makefile uses the make utility, and if we're to be completely accurate, Makefile is just a file that houses the code that the make utility uses. And because all good things in the software world come from some engineer being too lazy to type in a few extra commands, Makefile was born. This is a very tedious and time-consuming process. So if we make a change in opengl.source for example, we need to recompile both draw.source and main_program.source because we want our project to be up-to-date on all ends. Math.source -> uses the libraries `floating_point_calc.source` and `integer_calc.source`ĭraw.source -> uses the library `opengl.source` When you want to run a project that has multiple sources, resources, etc., you need to make sure that all of the code is recompiled before the main program is compiled or run.įor example, imagine our software looks something like this: main_program.source -> uses the libraries `math.source` and `draw.source`

Writing scripts in python