void-packages

History

Alessio Sergi 8742e48972 build-style/python{2,3}-module: do not use custom build directory 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.		2017-08-25 16:17:12 +02:00
..
cmake.sh	build-style/cmake.sh: $CC and $CXX are good enough for cross-compiling.	2017-08-16 18:09:35 +02:00
configure.sh
fetch.sh
gnu-configure.sh
gnu-makefile.sh	build_style/gnu-makefile: allow good makefiles	2017-04-25 16:20:59 -04:00
go.sh
haskell-stack.sh	haskell-stack: Add support for stack.yaml in source	2017-06-26 23:21:09 -07:00
meson.sh	common/build-style: add meson build style	2017-05-23 14:18:01 +02:00
meta.sh
perl-module.sh
perl-ModuleBuild.sh
python-module.sh	Revert "common/buildstyle/python*: build dir can be used as python identifier"	2017-01-12 12:27:12 +01:00
python2-module.sh	build-style/python{2,3}-module: do not use custom build directory	2017-08-25 16:17:12 +02:00
python3-module.sh	build-style/python{2,3}-module: do not use custom build directory	2017-08-25 16:17:12 +02:00
qmake.sh	build-style qmake: detect qmake w/o qtchooser	2017-03-21 19:35:01 +01:00
R-cran.sh	Add and document R-cran build style; support CRAN in update-check.	2017-06-08 13:32:40 +02:00
README
ruby-module.sh
scons.sh
slashpackage.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.