##############
# we'll run this again only if we think it's needed.
-if [ -z "$NECHUNG" ]; then
+if [ -z "$CORE_VARIABLES_LOADED" ]; then
if [ ! -z "$SHELL_DEBUG" ]; then echo variables initialization begins...; fi
# IS_MSYS will be non-empty if this is the msys toolset. otherwise
# we assume that it's cygwin.
IS_MSYS=$(uname | grep -i ming)
+
+ # if not MSYS, then we'll assume cygwin and set the cygwin root var.
+ if [ -z "$IS_MSYS" ]; then
+ define_yeti_variable CYGROOT=$(cygpath -w -m /)
+ fi
fi
##############
# set the main root directory variable for the feisty meow codebase.
# this is only used for extreme failure modes, when the values were not
# pulled in from our auto-generated config.
- if [ -z "$FEISTY_MEOW_DIR" ]; then
+ if [ -z "$FEISTY_MEOW_APEX" ]; then
if [ -d "$HOME/feisty_meow" ]; then
- define_yeti_variable FEISTY_MEOW_DIR="$HOME/feisty_meow"
+ define_yeti_variable FEISTY_MEOW_APEX="$HOME/feisty_meow"
define_yeti_variable FEISTY_MEOW_SCRIPTS="$FEISTY_MEOW_SCRIPTS"
fi
fi
-
+
+ # main declaration of the transients area.
+ if [ -z "$TMP" ]; then
+ define_yeti_variable TMP=$HOME/.tmp
+ fi
+
+ # set up the top-level for all build creations and logs and such.
+ if [ -z "$GENERATED_STORE" ]; then
+ define_yeti_variable GENERATED_STORE="$TMP/generated-feisty_meow"
+ fi
+ if [ ! -d "$GENERATED_STORE" ]; then
+ mkdir -p "$GENERATED_STORE"
+ fi
+ # set up our effluent outsourcing valves.
+ if [ -z "$TEMPORARIES_PILE" ]; then
+ define_yeti_variable TEMPORARIES_PILE="$GENERATED_STORE/temporaries"
+ fi
+ if [ ! -d "$TEMPORARIES_PILE" ]; then
+ mkdir -p "$TEMPORARIES_PILE"
+ fi
+
# similarly, make sure we have someplace to look for our generated files, if
# we were not handed a value.
- if [ -z "$FEISTY_MEOW_GENERATED" ]; then
+ if [ -z "$FEISTY_MEOW_LOADING_DOCK" ]; then
# The generated scripts directory is where automatically generated files live.
# It is separate from the main body of the shell scripts in order to keep things from
# exploding.
- define_yeti_variable FEISTY_MEOW_GENERATED=$HOME/.zz_auto_gen
+ define_yeti_variable FEISTY_MEOW_LOADING_DOCK=$HOME/.zz_feisty_loading
fi
##############
+
+ # set up the color_add variable which is a flag that lets ls know colors work.
+
+ # test if we can use color in ls...
+ ls --help 2>&1 | grep -i -q color
+ if [ $? -eq 0 ]; then
+ export color_add='--color=auto'
+ else
+ export color_add=
+ fi
+ unset test_ls_colors
+ ##############
+
# umask sets a permission mask for all file creations.
# this mask disallows writes by "group" and "others".
umask 022
# variables for perl.
define_yeti_variable PERLLIB+="/usr/lib/perl5"
+ define_yeti_variable PERL5LIB+="/usr/lib/perl5"
if [ "$OS" == "Windows_NT" ]; then
define_yeti_variable PERLIO=:perlio
# choose perl's IO over the ms-windows version so we can handle file
# bytes properly.
fi
-
+
# iterate across our sub-directories and find the perl scripts.
# this currently only looks one level down.
for i in $FEISTY_MEOW_SCRIPTS/*; do
ls $i/*.pl &>/dev/null
if [ $? -eq 0 ]; then
PERLLIB+=":$(dos_to_unix_path $i)"
+ PERL5LIB+=":$(dos_to_unix_path $i)"
fi
fi
done
##############
# set this so nechung can find its data.
- define_yeti_variable NECHUNG=$FEISTY_MEOW_DIR/infobase/fortunes.dat
+ define_yeti_variable NECHUNG=$FEISTY_MEOW_APEX/infobase/fortunes.dat
+## # establish a pipe for less to see our beloved syntax highlighting.
+## define_yeti_variable LESSOPEN="| source-highlight -f esc -o STDOUT -i %s"
+
# ensure we use the right kind of secure shell.
# define_yeti_variable CVS_RSH=$FEISTY_MEOW_SCRIPTS/security/ssh.sh
# define_yeti_variable GIT_SSH=$FEISTY_MEOW_SCRIPTS/security/ssh.sh
{
found_build_vars=0
# we need to know the feisty meow directory, or we bail.
- if [ -z "$FEISTY_MEOW_DIR" ]; then return; fi
+ if [ -z "$FEISTY_MEOW_APEX" ]; then return; fi
# pick from our expected generator folder, but make sure it's there...
buildvars="$FEISTY_MEOW_SCRIPTS/generator/build_variables.sh"
if [ -f "$buildvars" ]; then
# now augment the environment if we found our build variables.
if [ $found_build_vars == 1 ]; then
# the binary directory contains our collection of handy programs.
- define_yeti_variable BINDIR=$TARGETS_DIR
+ define_yeti_variable FEISTY_MEOW_BINARIES=$TARGETS_STORE
# add binaries created within build to the path.
- define_yeti_variable PATH="$(dos_to_unix_path $BINDIR):$PATH"
+ define_yeti_variable PATH="$(dos_to_unix_path $FEISTY_MEOW_BINARIES):$PATH"
# Shared libraries are located via this variable.
- define_yeti_variable LD_LIBRARY_PATH="$(dos_to_unix_path $LD_LIBRARY_PATH):$(dos_to_unix_path $BINDIR)"
+ define_yeti_variable LD_LIBRARY_PATH="$(dos_to_unix_path $LD_LIBRARY_PATH):$(dos_to_unix_path $FEISTY_MEOW_BINARIES)"
fi
}
# add to the PATH variables used for locating applications. this step is taken after any
# potential overrides from the user.
- define_yeti_variable PATH="$(dos_to_unix_path $FEISTY_MEOW_GENERATED):$PATH:$(find /usr/local/games -maxdepth 1 -type d -exec echo -n {}: ';' 2>/dev/null)/sbin"
+ define_yeti_variable PATH="$(dos_to_unix_path $FEISTY_MEOW_LOADING_DOCK):$PATH:$(find /usr/local/games -maxdepth 1 -type d -exec echo -n {}: ';' 2>/dev/null)/sbin"
##############
- # set the SHUNIT_DIR so our shunit tests can find the codebase.
- define_yeti_variable SHUNIT_DIR="$FEISTY_MEOW_SCRIPTS/shunit"
+ # set the SHUNIT_PATH so our shunit tests can find the codebase.
+ define_yeti_variable SHUNIT_PATH="$FEISTY_MEOW_SCRIPTS/shunit"
##############
+
+ define_yeti_variable CORE_VARIABLES_LOADED=true
if [ ! -z "$SHELL_DEBUG" ]; then echo variables initialization ends....; fi
fi
# override individual variables and definitions. we also don't guard this
# to avoid running it again, because we don't know what mix of functions and
# aliases they want to define in there.
-for i in $FEISTY_MEOW_GENERATED/custom/*.sh; do
+for i in $FEISTY_MEOW_LOADING_DOCK/custom/*.sh; do
if [ ! -f "$i" ]; then
# skip it if it's not real.
continue;
fi
source "$i"
done
-
+
projects / feisty_meow.git / blobdiff