Now you can specify environment variables from a config file per recipe to allow building with different toolchains or crosscompiling, etc

libretro-buildbot-recipe.sh

@@ -8,7 +8,29 @@
 # eg: FORCE=YES MAKE=mingw32-make ./libretro-fetch-and-build.sh buildbot.conf
 
 ####environment configuration:
-echo configuring build environment
+echo "Setting up Environment for $1"
+echo ============================================
+
+ORIGPATH=$PATH
+
+echo Original PATH: $PATH
+
+while read line; do
+    KEY=`echo $line | cut --fields=1 --delimiter=" "`
+    VALUE=`echo $line | cut --fields=2 --delimiter=" "`
+
+    if [ "${KEY}" == "PATH" ];
+    then
+        export PATH=${ORIGPATH}:${VALUE}
+        echo New PATH: $PATH
+
+    else
+        export ${KEY}=${VALUE}
+        echo $KEY: $VALUE   
+     
+    fi
+done  < $1.conf
+
 . ./libretro-config.sh
 
 echo
@@ -446,3 +468,4 @@ while read line; do
 
 done  < $1
 
+PATH=$ORIGPATH

recipes/recipes.win-mingw64-seh

@@ -1,4 +1,4 @@
-2048 libretro-2048  https://github.com/libretro/libretro-2048.git PROJECT NO GENERIC Makefile.libretro .
+2048 libretro-2048  https://github.com/libretro/libretro-2048.git PROJECT YES GENERIC Makefile.libretro .
 3dengine libretro-3dengine  https://github.com/libretro/libretro-3dengine.git PROJECT NO GENERIC_GL Makefile .
 4do libretro-4do https://github.com/libretro/4do-libretro.git PROJECT NO GENERIC Makefile .
 bluemsx libretro-bluemsx https://github.com/libretro/blueMSX-libretro.git PROJECT NO GENERIC Makefile.libretro .