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 8: | Line 8: | ||
* 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). | ||
* Use the gb_Output_* functions for notifications. | * Use the gb_Output_* functions for notifications. | ||
| − | * Keep all platform specific stuff confined in the platform subdirectory of gbuild | + | * 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)). | * Never use relative paths. Only absolute paths starting with $(OUTDIR), $(WORKDIR) and the repository roots (for example $(SRCDIR)). | ||
* Adhere to the [http://www.python.org/dev/peps/pep-0020/ Zen of Python], for it is valid in any language. | * Adhere to the [http://www.python.org/dev/peps/pep-0020/ Zen of Python], for it is valid in any language. | ||
Revision as of 14:20, 15 November 2010
Zen of gbuild
- One use make process, do not recurse.
- Always have good clean targets.
- Have exactly one target per declaration file.
- Use only tools as defined by POSIX:2008. Exception: GNU extensions are allowed for tar, cp 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)).
- Adhere to the Zen of Python, for it is valid in any language.
