vp-build/common/build-style
Enno Boland a02132b2ae common/buildstyle/python*: build dir can be used as python identifier
in order to make gufw installation process work, it includes itself
while installing. this raise the need that the build directory needs
to be a valid python identifier too. this commit solves this issue.
2017-01-05 20:53:47 +01:00
..
cmake.sh
configure.sh
fetch.sh
gnu-configure.sh
gnu-makefile.sh
go.sh
haskell-stack.sh environment/build-style/haskell-stack.sh: hostmakedepend automatically on ghc and stack. 2016-12-18 15:28:54 +01:00
meta.sh
perl-module.sh build-style/perl-module.sh: fake Errno.pm too. 2016-08-29 16:23:26 +02:00
perl-ModuleBuild.sh
python-module.sh common/buildstyle/python*: build dir can be used as python identifier 2017-01-05 20:53:47 +01:00
python2-module.sh common/buildstyle/python*: build dir can be used as python identifier 2017-01-05 20:53:47 +01:00
python3-module.sh common/buildstyle/python*: build dir can be used as python identifier 2017-01-05 20:53:47 +01:00
qmake.sh build-style/qmake.sh: set CC/CXX/LINK. 2016-10-05 14:03:16 +02:00
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.