-fi
-
-# augment the configuration if we found our build variables.
-if [ $found_build_vars == 1 ]; then
-
- # the binary directory contains handy programs we use a lot in yeti. we set up the path to it
- # here based on the operating system.
- # note that yeti has recently become more dependent on hoople. hoople was always the source of
- # the binaries, but now we don't ship them with yeti any more as pre-built items. this reduces
- # the size of the code package a lot and shortens up our possible exposure to compromised
- # binaries. people can bootstrap up their own set from hoople now instead.
- export BINDIR=$FEISTY_MEOW_DIR/production/binaries
-
- # add binaries created within build to the path.
- export PATH="$(dos_to_msys_path $BUILD_TOP/build/bin):$PATH"
-
- # Shared libraries are located via this variable.
- export LD_LIBRARY_PATH="$(dos_to_msys_path $LD_LIBRARY_PATH):$(dos_to_msys_path $BINDIR)"
-fi
-
-##############
-
-# windoze specific patching up missing things.
-
-if [ "$OS" == "Windows_NT" ]; then
- export HOSTNAME=$(echo $HOSTNAME | tr A-Z a-z)
+ # add in any site avenger applications that are in the applications folder.
+ if [ -d "$HOME/apps" ]; then
+ # general search for normal project folders in apps.
+ REPOSITORY_LIST+="$(find "$HOME/apps" -maxdepth 2 -mindepth 2 -iname ".git" -type d -exec dirname {} ';') "
+ REPOSITORY_LIST+="$(find "$HOME/apps" -maxdepth 2 -mindepth 2 -iname ".svn" -type d -exec dirname {} ';') "
+
+ # special search for site avenger directories; they have avenger5 as second level.
+ REPOSITORY_LIST+="$(find "$HOME/apps" -maxdepth 2 -mindepth 2 -iname "avenger5" -type d) "
+ fi
+
+ # the archive list is a set of directories that are major repositories of
+ # data which can be synched to backup drives.
+ define_yeti_variable MAJOR_ARCHIVE_SOURCES=
+ # the source collections list is a set of directories that indicate they
+ # harbor a lot of source code underneath.
+ define_yeti_variable SOURCECODE_HIERARCHY_LIST=
+
+ # initializes the feisty meow build variables, if possible.
+ function initialize_build_variables()
+ {
+ local found_build_vars=nope
+ # we need to know the feisty meow directory, or we bail.
+ 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
+ # yep, that one looks good, so pull in the build defs.
+ source "$buildvars" "$buildvars"
+ found_build_vars=true
+ fi
+ # now augment the environment if we found our build variables.
+ if [ $found_build_vars == true ]; then
+ # the binary directory contains our collection of handy programs.
+ define_yeti_variable FEISTY_MEOW_BINARIES=$TARGETS_STORE
+ # add binaries created within build to the 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 $FEISTY_MEOW_BINARIES)"
+ fi
+ }
+
+ ##############
+
+ # windoze specific patching up missing things.
+
+ if [ "$OS" == "Windows_NT" ]; then
+ define_yeti_variable HOSTNAME=$(echo $HOSTNAME | tr A-Z a-z)
+ fi
+
+ ##############
+
+ # load in the build environment.
+ initialize_build_variables
+
+ ##############
+
+ # add to the PATH variables used for locating applications. this step is taken after any
+ # potential overrides from the user.
+#old: 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"
+ define_yeti_variable PATH="$PATH:$(find /usr/local/games -maxdepth 1 -type d -exec echo -n {}: ';' 2>/dev/null)/sbin"
+
+ ##############
+
+ # set the SHUNIT_PATH so our shunit tests can find the codebase.
+ define_yeti_variable SHUNIT_PATH="$FEISTY_MEOW_SCRIPTS/testkit/shunit"
+
+ ##############
+
+ define_yeti_variable CORE_VARIABLES_LOADED=true
+
+ if [ ! -z "$DEBUG_FEISTY_MEOW" ]; then echo variables initialization ends....; fi