Compiling BasiliskII and SheepShaver for various host environments

++++ WORK IN PROGRESS, HELP IF YOU CAN ++++

Preparing your build environment

Common assumptions:

  • You have a folder called “src” inside which you are going to place all downloads mentioned below. The folder structure we are assuming looks like this:
  • src
  • src\SDL-1.2.14
  • src\BasiliskII (this folder will be created automatically if you follow the directions below)
  • src\SheepShaver (this folder will be created automatically if you follow the directions below)
Windows

You need an installation of Cygwin or MinGW which includes the GCC and G++ compilers, the cvs package, X-headers, libgnome development etc.
Inside that installation, download SDL-1.2.14 and build and install SDL. NOTE: TO BE COMPLETED, PERHAPS WITH SCREEN SHOTS

Make the “src” folder in your Cygwin or MinGW home folder.

Step by step installation of SDL-1.2.14

./autogen.sh
./configure --disable-shared --prefix=`pwd`
make
make install
PATH=`pwd`/bin:$PATH
export PATH

* You need to cd into the SDL folder every time you start cygwin and export the path (the last two command lines above) to sdl-config to build SheepShaver, so SDL libs and sdl-config file can be found.

OSX Snow Leopard

You need Xcode installed. Make the “src” folder inside your home folder.

./autogen.sh
./configure --disable-shared --prefix=`pwd`
make
make install
PATH=`pwd`/bin:$PATH
export PATH

* You need to cd into the SDL folder every time you start a new terminal window and export the path (the last two command lines above) to sdl-config to build SheepShaver, so SDL libs and sdl-config file can be found.

Linux

You need GCC and G++ installed, plus several other development packages, like SDL-1.2.14 development, the X-headers, the libgnome-development package, cvs access

  • Your SDL installation and other packages should be found automatically when you start building SheepShaver or BasiliskII

Actions for all environments

Download the sources from cygwin\MinGW (in Windows) or a terminal (In OSX and Linux):

  • cd into the “src” folder
  • run: cvs -d :pserver:anoncvs@cvs.cebix.net:/home/cvs/cebix login

(password is “anoncvs”)

  • run: cvs -d :pserver:anoncvs@cvs.cebix.net:/home/cvs/cebix checkout BasiliskII
  • run: cvs -d :pserver:anoncvs@cvs.cebix.net:/home/cvs/cebix checkout SheepShaver

These commands download the the current source code for both BasiliskII and SheepShaver into the folders “BasiliskII” and “SheepShaver”. The SheepShaver code is not needed if you only want to compile BasiliskII.

Building BasiliskII in Windows

cd to the BasiliskII folder and:

cd src/Windows
NO_CONFIGURE=1 ../Unix/autogen.sh
./configure
make
strip BasiliskII.exe

Building BasiliskII in OSX Snow Leopard

cd to the BasiliskII folder and:

cd src/Unix
NO_CONFIGURE=1 ./autogen.sh
./configure --enable-sdl-video --enable-sdl-audio --disable-vosf --enable-jit-compiler
make
make BasiliskII_app

Building BasiliskII in Linux flavours

Ubuntu:

cd BasiliskII
cd src/Unix
NO_CONFIGURE=1 ./autogen.sh
./configure --enable-sdl-video --enable-sdl-audio --disable-vosf --enable-jit-compiler
make
strip BasiliskII

Fedora:

cd BasiliskII
cd src/Unix
NO_CONFIGURE=1 ./autogen.sh
./configure --enable-sdl-video --enable-sdl-audio --disable-vosf --enable-jit-compiler
make
strip BasiliskII

Suse:

cd BasiliskII
cd src/Unix
NO_CONFIGURE=1 ./autogen.sh
./configure --enable-sdl-video --enable-sdl-audio --disable-vosf --enable-jit-compiler
make
strip BasiliskII

CentOS-64:

  • First edit the file \src\BasiliskII\src\Unix\configure.ac and comment out the lines 113 to 125, like this
dnl Check if we should really be assuming x86_64 even if we detected HAVE_I386 above. 
dnl if [[ "x$HAVE_I386" = "xyes" ]]; then
dnl  AC_TRY_RUN([
dnl    int main(void) {
dnl        #if defined(__x86_64__)
dnl                return 0;
dnl        #else
dnl                return 1;
dnl        #endif
dnl    }
dnl  ], [
dnl    HAVE_I386=no
dnl    HAVE_X86_64=yes
dnl  ])
dnl fi
cd BasiliskII
cd src/Unix
NO_CONFIGURE=1 ./autogen.sh
./configure --enable-sdl-video --enable-sdl-audio --disable-vosf --enable-jit-compiler
make
strip BasiliskII

Building SheepShaver in Windows

cd to the SheepShaver folder and:

make links
cd src/Windows
NO_CONFIGURE=1 ../Unix/autogen.sh
./configure
make
strip SheepShaver.exe

Building SheepShaver in OSX Snow Leopard

cd to the SheepShaver folder and:

make links
cd SheepShaver/src/Unix folder
NO_CONFIGURE=1 ./autogen.sh
./configure --enable-sdl-audio --enable-sdl-video --disable-vosf
make
make SheepShaver_app

Building SheepShaver in Linux flavours

  • SheepShaver currently suffers from issues regarding running in a window/full screen. For full screen support, follow the directions below. However, if you want a stable build for windowed use, delete ”–enable-sdl-video” and ”–enable-sdl-audio” from the ./configure step.

Ubuntu:

cd to the SheepShaver folder and:

make links
cd src/Unix
NO_CONFIGURE=1 ./autogen.sh
./configure --enable-sdl-video --enable-sdl-audio --disable-vosf
make
strip SheepShaver

Fedora:

cd to the SheepShaver folder and:

make links
cd src/Unix
NO_CONFIGURE=1 ./autogen.sh
./configure --enable-sdl-video --enable-sdl-audio --disable-vosf
make
strip SheepShaver

Suse:

cd to the SheepShaver folder and:

make links
cd src/Unix
NO_CONFIGURE=1 ./autogen.sh
./configure --enable-sdl-video --enable-sdl-audio --disable-vosf
make
strip SheepShaver

CentOS-64:

  • The JIT_compiler doesn't compile on CentOS-64 (see error below), so it needs to be disabled in the configure step
  • glibc detected ./dyngen: free(): invalid pointer: 0x000000007a8826c0 when compiling /dyngen -o ppc-dyngen-ops.hpp obj/ppc-dyngen-ops.o
  • Even then, SheepShaver throws an error “Xlib: unexpected async reply (sequence 0x414)!
  • giving SheepShaver more memory, and checking “ignore illegal memory access” might help a bit.

cd to the SheepShaver folder and:

make links
cd src/Unix
NO_CONFIGURE=1 ./autogen.sh
./configure --enable-sdl-video --enable-sdl-audio --disable-vosf --enable-jit=no
make
strip SheepShaver

Tidbits

  • Source code for Visual C for basiliskII and SheepShaver:

There are some unfinished attempts (jan. 2011) to update the source code for Basilisk and SheepShaver for Windows that build in Visual C. The code also builds in MinGW. It originates from here: https://github.com/tycho/basiliskii and https://github.com/tycho/sheepshaver

The code is mirrored here:
BasiliskII_source
SheepShaver_source

  • A version of Basilisk for Haiku is available:

http://sys6502.blogspot.com

The application is mirrored here:
Basilisk for Haiku
You need to set the correct rights on the application, so set it to execute for the current user.

 
compiling_sheepshaver_basilisk.txt · Last modified: 2011/04/10 16:51 by clockwise
 
Recent changes RSS feed Creative Commons License Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki