@@ -9,6 +9,13 @@ development environment of tools and libraries.

 **mulle-brew** helps you set-up and share such playgrounds.

+## Advantages

+

+* Keep the runtime and your system clear off temporary downloads.

+* Updating brew libraries for one project, doesn't neccessarily impact parallel projects

+* An easy way to share the required build environments

+

+

 ## How does it work ?

 In the simplest form, `mulle-brew` is just a simple loop over a

@@ -32,6 +39,8 @@ and the **libpng** library in `addictions/lib` and `addictions/include`.

 `addictions` is your playground's '/usr/local' so to speak

+

+

 ## Various Playground configurations

@@ -30,7 +30,7 @@

 #   POSSIBILITY OF SUCH DAMAGE.

 MULLE_EXECUTABLE_VERSION_MAJOR=3

 MULLE_EXECUTABLE_VERSION_MINOR=2

-MULLE_EXECUTABLE_VERSION_PATCH=1

+MULLE_EXECUTABLE_VERSION_PATCH=3

 MULLE_EXECUTABLE_VERSION="${MULLE_EXECUTABLE_VERSION_MAJOR}.${MULLE_EXECUTABLE_VERSION_MINOR}.${MULLE_EXECUTABLE_VERSION_PATCH}"

@@ -30,7 +30,7 @@

 #   POSSIBILITY OF SUCH DAMAGE.

 MULLE_EXECUTABLE_VERSION_MAJOR=3

 MULLE_EXECUTABLE_VERSION_MINOR=2

-MULLE_EXECUTABLE_VERSION_PATCH=1

+MULLE_EXECUTABLE_VERSION_PATCH=3

 MULLE_EXECUTABLE_VERSION="${MULLE_EXECUTABLE_VERSION_MAJOR}.${MULLE_EXECUTABLE_VERSION_MINOR}.${MULLE_EXECUTABLE_VERSION_PATCH}"

@@ -155,10 +155,10 @@ find_compiler()

    if [ ! -z "${compiler}" ]

    then

-      compiler=`which_binary "${toolname}"`

+      compiler=`which_binary "${compiler}"`

       if [ -z "${compiler}" ]

       then

-         suggest_binary_install "${toolname}"

+         suggest_binary_install "${compiler}"

          exit 1

       fi

       echo "${compiler}"

@@ -127,7 +127,7 @@ setup_clean_environment()

    CLEAN_EMPTY_PARENTS="`read_config_setting "clean_empty_parent_folders" "YES"`"

-   OUTPUT_CLEANABLE_FILES="${REPOS_DIR}/.bootstrap_build_done"

+   OUTPUT_CLEANABLE_FILES="${REPOS_DIR}/.build_done"

    BUILD_CLEANABLE_SUBDIRS="`read_sane_config_path_setting "clean_folders" "${CLONESBUILD_DIR}

 ${DEPENDENCIES_DIR}/tmp"`"

@@ -213,6 +213,29 @@ which_binary()

 }

+# used by test scripts outside of mulle-bootstrap

+assert_binary()

+{

+   local toolname

+   local toolfamily

+

+   toolname="$1"

+   toolfamily="$2"

+

+   [ -z "${toolname}" ] && internal_fail "toolname for \"${toolfamily}\" is empty"

+

+   local path

+

+   path=`which_binary "${toolname}"`

+   if [ -z "${path}" ]

+   then

+      which_binary "${toolname}"

+      fail "${toolname} is an unknown build tool (PATH=$PATH)"

+   fi

+   # echo "$path"

+}

+

+

 #

 # toolname : ex. mulle-clang

 # toolfamily: CC

@@ -255,3 +278,16 @@ verify_binary()

    return 1

 }

+

+

+#

+# command because it's like `command -v gcc`

+#

+command_initialize()

+{

+   [ -z "${MULLE_BOOTSTRAP_LOGGING_SH}" ] && . mulle-bootstrap-logging.sh

+

+   log_debug ":command_initialize:"

+}

+

+command_initialize