8742e48972
There is no need to use a custom build directory for python{2,3}-only
modules.
This indirectly fixes our issues with packages that use distutils-extra.
|
||
|---|---|---|
| .. | ||
| cmake.sh | ||
| configure.sh | ||
| fetch.sh | ||
| gnu-configure.sh | ||
| gnu-makefile.sh | ||
| go.sh | ||
| haskell-stack.sh | ||
| meson.sh | ||
| meta.sh | ||
| perl-module.sh | ||
| perl-ModuleBuild.sh | ||
| python-module.sh | ||
| python2-module.sh | ||
| python3-module.sh | ||
| qmake.sh | ||
| R-cran.sh | ||
| README | ||
| ruby-module.sh | ||
| scons.sh | ||
| slashpackage.sh | ||
| waf.sh | ||
| waf3.sh | ||
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.