New unified makefile architecture

[virtualjaguar] / compile

diff --git a/compile b/compile
new file mode 100644 (file)
index 0000000..b9d9bcb
--- /dev/null
+++ b/compile
@@ -0,0 +1,60 @@
+#!/bin/sh
+
+#
+# Compile script for Virtual Jaguar GCC/SDL Portable Jaguar Emulator
+# This obviates the need for separate Makefiles for every OS architecture
+# under the sun...
+#
+# by James L. Hammons
+# 
+# If you have any parameters that you want to pass through to make, then
+# simply add them to the 'compile' command line as if 'compile' were make.
+#
+
+echo
+echo -n "*** Compiling Virtual Jaguar for "
+
+# Check the OS type...
+
+if [ "$OSTYPE" = "msys" ]; then
+
+       echo -n Win32 on MinGW
+
+       SYSTYPE=__GCCWIN32__
+       EXESUFFIX=.exe
+       GLLIB=-lopengl32
+       ICON=vj-ico.o
+       SDLLIBTYPE=--libs
+#This doesn't seem to make a difference on Win32...
+#      SDLLIBTYPE=--static-libs
+
+elif [ "$OSTYPE" = "macosx" ]; then
+
+       echo -n Mac OS X
+
+       SYSTYPE=__GCCUNIX__ -D_OSX_
+       EXESUFFIX=
+       GLLIB=
+       ICON=
+       SDLLIBTYPE=--static-libs
+
+else # *nix
+
+       echo -n generic Unix/Linux
+
+       SYSTYPE=__GCCUNIX__
+       EXESUFFIX=
+       GLLIB=-lGL
+       ICON=
+       SDLLIBTYPE=--libs
+
+fi
+
+echo ...
+echo
+
+export SYSTYPE EXESUFFIX GLLIB ICON SDLLIBTYPE
+
+# Yes, you can pass through parameters to make...
+
+make $@