Configuring Crosser.sh & libstack.sh
=====================================

Both libtool.sh and crosser.sh (which is not included in this release)
can be configured with file names local_setup.conf in main crosser
directory. This is same directory where libstack.sh and crosser.sh
scripts are.

This file lists some of the variables one can place to local_setup.conf

Entries are of form:
VARIABLE=VALUE

=======================================================================

AUTOWINE
 ; If this has value "yes", libstack.sh uses wine to run some
 ; gtk+ configuration programs. Do not define this if wine is not available
 ; and automatically usable.
 ; These configuration programs must be run when doing actual install to
 ; Windows machine.

PREFIX
 ; Directory hierarchy where generated environment will be installed.
 ; This directory will be completely removed.
 ; This path is parsed:
 ;   - <TARGET> -> Target architecture
 ;   - <DATE>   -> Build start date. Note that build may take long time and
 ;                 often start date is not same as current date of some build
 ;                 action.
 ;   - <CLIB>   -> libc to use
 ; Either enclose value inside quotes or escape tags like \<TARGET\>

NATIVE_PREFIX
 ; Directory hierarchy where native environment generated in native-step
 ; will be installed. This affects only crosser.sh, not libtstack.sh at all.
 ; Path parsing is similar to that of PREFIX.

LOGLEVEL_STDOUT
LOGLEVEL_STDERR
 ; Level of logging to screen and to file. Values can be from
 ; 1 (Fatal errors only) to 5 (debug logging).
 ; Defaults are 2 for screen and 4 for file.

FORCERM
 ; If this is set to 'yes', scripts will not provide confirmation prompts
 ; when deleting old directories. It's recommended that this is never
 ; used in local_setup.conf and set as environment variable before running 
 ; script only when setup has been already tested and one really knows
 ; that nothing important will be destroyed.

MAINSRCDIR
 ; Directory hierarchy where sources will be unpacked.
 ; Default is tmp/src under crosser main dir.

MAINBUILDDIR
 ; Directory hierarchy where binaries will be built
 ; Default is tmp/build under crosser main dir.

MAINLOGDIR
 ; Directory where logfiles will be written.
 ; Default is log under crosser main dir.
 ; Some log files are created anew for each build, some contain
 ; information about all builds done with crosser.

CROSSER_DOWNLOAD
 ; This defines packet download model. Packets are ever downloaded only
 ; if they are missing, but time their existence is checked depends on
 ; this setting. Actual implementation is not yet too sophisticated.
 ; Even with "on demand" setting quite a lot of stuff is downloaded
 ; in the beginning. Default is "demand".
 ;   "yes"           - crosser.sh / libstack.sh download all required
 ;                     packets in the beginning.
 ;   "demand"        - On demand; download just when packet is really
 ;                     needed. This setting has advantage that not time
 ;                     and resources are wasted to downloading if
 ;                     compilation of some earlier component fails.
 ;   any other value - Assume that packets are already downloaded.
 ;                     Fail if not.
 ; Options other than "demand" have advantage that time is not wasted
 ; on compiling earlier packets in case some packet cannot be downloaded.

=======================================================================

local_setup.conf is actually shell script fragment. Here are some things
one may want to do in it in addition to setting variables.

renice 15 $$
 ; Crosser build takes very long time. If you want to do something
 ; else with the computer meanwhile, you may want to make crosser low
 ; priority. That makes other tasks to run faster and crosser to use just
 ; those CPU cycles left over. Above command makes current script
 ; (crosser.sh itself) to run at nice level 15.
