|
bozoconf − triggers some regular "./configure.sh" if available, if not it will try to build one via autoall(1) before launching it |
|
bozoconf [ --track-changes ] |
|
bozoconf tries to find a ./configure.sh script ; if it is missing, bozoconf attempts to build one via the autoall(1) utility. bozoconf may inherits several environment variables in order to efficiently build into alternates trees, cross-compile, or use alternative build environments. |
|
--track-changes |
|
Tries to log all changes between every steps, in order to find which process performed them. Changes are output to defaults to /tmp/configure-track-PID. |
|
--version |
|
reports bozoconf version, and also versions from all sub-called utilities. |
|
$OURBUILDDIR and $OURSOURCDIR |
|
sets separate build-dir and source-dir, typically : OURBUILDDIR=targetdir OURSOURCDIR=‘pwd‘ bozoconf in the source dir does the trick ... |
|
$BOZOCONFCACHE |
|
sets ./configure.sh --cache-file= option in order to speed configurations. |
|
$BOZOCONFMAKE |
|
uses an altername make build utility, mainly relevant for cross compiling and such. |
|
$BOZOCONFTARGET |
|
sets a default make target, usefull when called from a GUI. |
|
$BOZOMAKEEXT |
|
obscure ... probably in order to get compile logs separated ? |
|
bozoconf builds a .vim.prepend file in order to map the F12 key to the proper build operation. |
|
(1)autoall, (1)repozclean |
|
There are probably plenty. Please report them to bozomake@disjunkt.com |
|
Jean-Daniel Pauget (bozomake@disjunkt.com) |
|
$Id: bozoconf.1.in 581 2010-04-08 21:42:14Z jd $ |