Difference between revisions of "Build Environment Effort/Zen of gbuild"
From Apache OpenOffice Wiki
B michaelsen (Talk | contribs) (→Zen of gbuild) |
B michaelsen (Talk | contribs) (→Zen of gbuild) |
||
| Line 4: | Line 4: | ||
* Always have good dependencies and good clean targets. | * Always have good dependencies and good clean targets. | ||
* Have exactly one $(OUTDIR) target per declaration file. | * Have exactly one $(OUTDIR) target per declaration file. | ||
| − | * Use only tools as defined by [http://en.wikipedia.org/wiki/POSIX POSIX:2008]. Exception: GNU extensions are allowed for cp, make, tar and touch. | + | * Use only tools as defined by [http://en.wikipedia.org/wiki/POSIX POSIX:2008] and supported on all platforms. Exception: GNU extensions are allowed for cp, make, tar and touch. |
* Dont use Perl or Python for tooling, use POSIX sh, POSIX awk and GNU make instead. | * Dont use Perl or Python for tooling, use POSIX sh, POSIX awk and GNU make instead. | ||
* If those dont cut it, use C/C++ (Or ask yourself if you are doing something wrong). | * If those dont cut it, use C/C++ (Or ask yourself if you are doing something wrong). | ||
Revision as of 14:48, 15 November 2010
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.
- Dont use Perl or Python for tooling, use POSIX sh, POSIX awk and GNU make instead.
- If those dont cut it, use C/C++ (Or ask yourself if you are doing something wrong).
- 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.
