....
In addition to running a shell for interactive use, bldenv can optionally run a single command in the given environment, in the vein of sh -c or su -c. This is useful for scripting, when an interactive shell would not be. If the command is composed of multiple shell words or contains other shell metacharacters, it must be quoted appropriately.
bldenv is particularly useful for testing Makefile targets like clobber, install and _msg, which otherwise require digging through large build logs to figure out what is being done.
By default, bldenv will invoke the shell specified in $SHELL. If $SHELL is not set or is invalid, csh will be used.
Example 1: Interactive use
Use bldenv to spawn a shell to perform a DEBUG build and testing of the Makefile targets clobber and install for usr/src/cmd/true.
\f5% rlogin wopr-2 -l gk
{root:wopr-2:49} bldenv -d /export0/jg/on10-se.env
Build type is DEBUG
RELEASE is 5.10
VERSION is wopr-2:on10-se:11/01/2001
RELEASE_DATE is May 2004
The top-level `setup' target is available to build headers
and tools.
Using /usr/bin/tcsh as shell.
{root:wopr-2:49}
{root:wopr-2:49} cd $SRC/cmd/true
{root:wopr-2:50} make
{root:wopr-2:51} make clobber
/usr/bin/rm -f true true.po
{root:wopr-2:52} make
/usr/bin/rm -f true
cat true.sh > true
chmod +x true
{root:wopr-2:53} make install
install -s -m 0555 -u root -g bin -f\
/export0/jg/on10-se/proto/root_sparc/usr/bin true
`install' is up to date.
Example 2: Non-interactive use
Invoke bldenv to create SUNWonbld with a single command:
\f5example% bldenv onnv_06 'cd $SRC/tools && make pkg'