you have to specify three different variables for build
APP: Your application/project. 
ARCH: Selected Architecture
CORE: Core Number

example: make APP=myTestProject ARCH=psur5 CORE=0 all

ARCH examples:
	stm32f7: 	Cortex M7 on STM32F7 Disco Board
	ps7:		Cortex A9 on Zynq 7000 (ZC706 Board)
	psua53:		Cortex A53 on Zynq Ultrascale+ (ZCU102 Board)
	psur5:		Cortex R5 on Zynq Ultrascale+ (ZCU102 Board)

Naming convention and Folder Structure has to be preserved to ensure Makefile is working

The folder structure is as follows:


idaCom.git
|--- Debug/
|    |--- $(ARCH)							/* Architecture dependent debug config templates */
|--- Makefile
|--- README
|--- src/
|    |--- APP/
|    |    |--- $(APP)/
|    |         |--- $(ARCH)/
|    |              |--- core$(CORE)/
|    |                   |--- build/					/*Build configuration used by makefile (sources.mk, includes.mk, config.mk)
|    |                   |    |--- sources.mk			/* List of source files */
|    |                   |    |--- includes.mk       		/* List of include paths */
|    |                   |    |--- config.mk         		/* Compiler/Linker flags */
|    |                   |--- cfg/
|    |                   |    |--- 	/* Typically used for various header files that are project specific */
|    |                   |--- linker/
|    |                   |    |--- 	/* Various Linker files */
|    |                   |--- src/
|    |                        |--- 	/* Various source files */
|    |--- Modules/							/* This is a folder for external modules */
|    |    |--- MMU/							/* Generic MMU Helper Module for Zynq 7000 and Ultrascale */
|    |    |--- tlsf/							/* TLSF Malloc */
|    |    |--- further git submodules
|    |--- ucos_v1_42							/* ucos Sources by micrium */
|    |--- Xilinx							/* Xilinx BSP for various projects */
|--- out/ 								/* Generated compiler output, is removed during "make clean" */


The skript is managed via mkdocs and you can build and access it as follows:
    - Open a Terminal and navigate to the lab_sdes_student folder
    - Use the command [mkdocs serve] to build the skript and make it accessible 
	-> hint: you can open mkdocs as a background-process with the [&] command, however it is advisable to open it in a seperate Terminal(-Tab) 
    - once the build is done there should be an information output showing an URL (IP-Adress) mkdocs is serving it on
    	-> you can then either open the skript by clicking it in the terminal or open it in a browser manually