Release 10.1A: OpenEdge Deployment:
Managing 4GL Applications

> ## Maintaining the buildenv script

> The `buildenv` script contains settings for the following types of options:

> - Options required by OpenEdge.

> - Options required by OpenEdge tools.

> - User-defined options.

> - Environment variables.

> Figure 4–3 shows an excerpt from a sample `buildenv` script.

>     #!/bin/sh
>     MACHINE="aix"
>     export MACHINE
>     UDORA="User Defined"
>     export UDORA
>     if [ x$RDL = x -a -f `pwd`/buildenv.log ] ; then
>         rm -f `pwd`/buildenv.log
>     fi
>     ORA_MK=$DLC/oebuild/make/ORA.mk
>     if [ x$RDL != x ]; then
>         ORA_MK=$PRGSSRC/project/ORA.mk
>     fi
>     # If ORALIB is not set already, attempt to set it
>     # ORACLE_HOME must be set for the following to work.  Error if unset.
>     if [ "x$ORALIB" = x -a "x$ORACLE_HOME" != x ] ; then
>         # Execute ('source' into current environment) oralib.sh if it exists.
>         # (it is assumed to be a Bourne-shell compatible script which, when
>         # finished, has defined an appropriate value for $ORALIB.
>         if [ -x $DLC/oebuild/build/oralib.sh ] ; then
>             . $DLC/oebuild/build/oralib.sh
>         else
>     .
>     .
>     .

> Figure 4–3: Sample buildenv script on UNIX

> You can edit this script to customize environments at different sites. The `buildenv` script is located in the `$DLC/oebuild/make` directory. OpenEdge uses the `buildenv` script to maintain environment variables that define objects, libraries, and options required for building executables on UNIX. For more information about building OpenEdge executables, see Appendix A "Building OpenEdge 4GL Executables."

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095