Build Environment Effort/Zen of gbuild

Build Environment Effort
Quick Navigation Customers Build Performance Elimination of Non-Pro Dependencies Module Problems Split Build Scalability HID List New Build System Requirements External Source Tarballs ToDo Build System Analysis Zen of gbuild Gbuild Bootstrapping Module Migration Module Migration Tips Build System Analysis:capstone2013 windows build Capstone 2013 Client Requirements Document Capstone 2013 Technology Review & Implementation Document
About this template

Zen of gbuild

• One use make process, do not recurse.
• Always have good dependencies and good clean targets.
• Have exactly one $(OUTDIR) target per declaration file.
• Use only tools as defined by POSIX:2008 and supported on all platforms. Exception: GNU extensions are allowed for cp, make, tar and touch.
• Use only POSIX sh, POSIX awk, C/C++ and GNU make in gbuild core.
• Otherwise, put the file in the extensions subdirectory and do not depend the core functionality on it.
• Use the gb_Output_* functions for notifications.
• Keep all platform specific stuff confined in the platform subdirectory of gbuild.
• Never use relative paths, only absolute paths starting with $(OUTDIR), $(WORKDIR) and the repository roots (for example $(SRCDIR)) should be used.
• Adhere to the Zen of Python, for it is valid in any language.