8361c4807f
`wrksrc` is supposed to be a top-level directory. Should the build system need to be run inside a sub-directory, `build_wrksrc` should be used instead. We change to `build_wrksrc` implicitly before `do_build` and `do_install`. Let's respect `build_wrksrc` in `perl-module`. |
||
---|---|---|
.. | ||
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 | ||
python3-pep517.sh | ||
qmake.sh | ||
raku-dist.sh | ||
ruby-module.sh | ||
scons.sh | ||
sip-build.sh | ||
slashpackage.sh | ||
texmf.sh | ||
void-cross.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.