Basic concepts prorab is a non-recursive GNU make-based build system. Essentially it just provides convenient definitions for writing clean makefiles.

The main feature of prorab is that it allows having independent makefiles in several subdirectories of the project and at the same time there can be a main makefile in root directory of the project which builds all those subprojects. And parallel building is still supported in that case. Also, prorab provides some predefined rules for easy building of C/C++ applications and libraries. Including prorab into the makefile Including prorab in the make file is simple and obvious, just add the following directive in the beginning of the makefile include prorab.mk Basically, all makefiles in the project are supposed to use prorab and have this include directive as a first include.

Prorab 20 Tablet is used in the treatment of Gastroesophageal reflux disease (Acid reflux) and Peptic ulcer disease. View Prorab 20 Tablet (strip of 10 tablets) uses, composition, side-effects, price, substitutes, drug interactions, precautions, warnings, expert advice and buy online at best price on 1mg.com. PROBA-2 is the second satellite in the European Space Agency's series of PROBA low-cost satellites that are being used to validate new spacecraft technologies while also carrying scientific instruments. PROBA-2 is a small satellite (130 kg) developed under an ESA General Support Technology Program.

See the seller's listing for full details. Artcut6 plotter software and artcut grapic disc.

Right after inclusion of prorab.mk there will be following variables defined: • prorab_this_dir - directory where this makefile resides. • d - shorthand alias for prorab_this_dir • prorab_os - operating system where makefile is run, can be linux, macosx, windows. Note, that windows is when building under Cygwin or Msys.

• os - shorthand alias for prorab_os • prorab_lib_extension - typical extension for dynamically linked libraries in the OS (windows:.dll, linux:.so, macosx:.dylib) • soext - shorthand alias for prorab_lib_extension • exeext - typical executable extension (windows:.exe, linux: empty, macosx: empty) Prorab definitions and variables naming conventions • Prorab definitions are named using hyphen-case and start with prorab- prefix. • Output variables are named using snake case and start with prorab_ prefix. • Input variables are named using snake case and start with this_ prefix. Building subprojects with prorab As said before, prorab allows 'cascading' of makefiles.

Say, you have two subdirectories in your project: app and test. And both those directories contain some subproject which can be built independently. So, in both those directories there are project makefiles. Now, if we want to have a makefile in project root directory which builds both those subprojects, we can use prorab-build-subdirs definition and root makefile would look like this: include prorab.mk $(eval $(prorab-build-subdirs)) And that's it. This will invoke the same target on every subdirectory which has file named makefile. Note, that parallel build is still supported since it is a non-recursive technique. Prorab definitions and input variables Before invoking most of the prorab definitions one has to set some input variables for the definition.

For example: this_name:= AppName this_cflags += -I$(d)./src -DDEBUG $(eval $(prorab-build-app)) After invoking some prorab definition there might be some output variables defined like, for example, prorab_this_name which represents the resulting filename of the created binary. Including other makefiles In order to include some other makefile one can use prorab-include function. This function will check if the makefile was already included or not and only include it if necessary. # Add dependency on some other artifact, e.g. Libstuff which is built by another makefile. # All targets generated by prorab use absolute paths, so need to use $(abspath) $(prorab_this_name): $(abspath $(d)./stuff/libstuff$(soext)) # include makefile for building libstuff $(eval $(call prorab-include,$(d)./stuff/makefile)).

Echoing commands from recipes All commands in prorab recipes are prefixed with @ by default, but it is possible to make it to be verbose by setting the verbose variable to true, like this: make verbose=true Valid values for verbose are true or false or not set. The v is a shorthand alias for verbose. If v is not set or set to 0 or false then it is equivalent to verbose=false. Otherwise, if v is set to any other value it is same as verbose=true. Set verbose variable has higher priority than set v variable. Defining several builds in one makefile It is possible to define several builds in a single makefile.

Right before starting definition of a next build one has to clear all this_ prefixed varibales, so that those do not go to the next build from previous build. To do that, there is a prorab-clear-this-vars definition which can be invoked using $(eval.) as usual. Note, that this definition is automatically invoked inside of prorab.mk, so it is not necessary to invoke it for the very first build of the makefile. Include prorab.mk this_name:= app1 this_srcs += app1.cpp $(eval $(prorab-build-app)) $(eval $(prorab-clear-this-vars)) this_name:= app2 this_srcs += app2.cpp $(eval $(prorab-build-app)) Adding all source files from all subdirectories to the build It is often needed in the build to use all source files from a certain directory subtree. There is a prorab-src-dir function for that. The directory to search for source files is relative to the makefile directory.