Handling of makefiles

Handling of makefile in example codes

Let's have look at intro_function example.

After downloading and extracting, you should see the following directory/file structure:

[ghaase@math047125 new_test]$ tree -L 2

├── CLANG_default.mk
├── GCC_default.mk
├── ICC_default.mk
├── intro_function
│   ├── Doxyfile
│   ├── html
│   ├── main.cpp
│   ├── Makefile
│   ├── mylib.cpp
│   └── mylib.h
├── intro_function.zip
├── ONEAPI_default.mk
└── PGI_default.mk

with :

source files *.cpp *.h .
the Makefile for controling the actions on your code
the Doxyfile for controling your documentation via doxygen.
the *.default.mk files for various compiler environments as GCC_ and CLANG_.
html is the directory with the generated documentation of your functions.

Change into the source directory via cd intro_function. Now the following actions are available:

`make run`	Recompiles and links the whole code and runs it.
`make`	Compiles modified code parts and links them.
`make doc` `firefox html/index.html`	Generates the documentation Views the documentation in browser
`make clean`	Removes *.o files and executable (part of `make run`)
`make clean_all`	Removes *.o files, executable and documentation
`make zip`	Removes files similar to `clean_all` and generates the zip file you downloaded
`make cache`	Starts (compiles) the code with cache profiling and analysis afterwards
`make mem`	Starts (compiles) the code with memory tracing to find memory bugs
`make prof`	Starts (compiles) the code profiling and analysis afterwards
`make heap`	Starts the code with heap tracing (dynamic memory de-/allocations)
`make codecheck`	Uses a codechecker for the source files
`make info`	Provides some info in the hardware

Gundolf Haase; Oct 18, 2024