5af961ece2
This allows the build system to detect itself whether it should use certain features, instead of defaulting to (potentially bad) enabled status. Features that aren't detected properly, be it because false positives or negatives, should be explicitly called out in the templates. |
||
|---|---|---|
| .. | ||
| R-cran.sh | ||
| README | ||
| cargo.sh | ||
| cmake.sh | ||
| configure.sh | ||
| fetch.sh | ||
| gem.sh | ||
| gemspec.sh | ||
| gnu-configure.sh | ||
| gnu-makefile.sh | ||
| go.sh | ||
| haskell-stack.sh | ||
| meson.sh | ||
| meta.sh | ||
| perl-ModuleBuild.sh | ||
| perl-module.sh | ||
| python-module.sh | ||
| python2-module.sh | ||
| python3-module.sh | ||
| qmake.sh | ||
| raku-dist.sh | ||
| ruby-module.sh | ||
| scons.sh | ||
| slashpackage.sh | ||
| texmf.sh | ||
| waf.sh | ||
| waf3.sh | ||
README
BUILD STYLES ============ These shell snippets provide support for multiple build systems, i.e GNU configure, CMake, etc. A build style file must provide at least the following functions: - do_configure - do_build - do_install If a source package defines its own do_xxx() function, the function defined in the build style file is simply ignored.