Note that my development environment is Windows 2000 using the Cygwin development kit. It may work with MingW or probably even on Linux running a cross-compiled version of gcc that produces PE files, however, I have not tested either of these cases. [Note - I am interested in hearing from you if you have tried either of these scenarios].
There is very little that is actually required as a pre-req for installing and running OpenXDK. Once this process has been completed, you will have OpenXDK installed into the /usr/local/openxdk
directory.
src
directory of your OpenXDK directory and type:
./install.shTo check that the installation worked correctly, run
ls -las /usr/local/openxdk/lib
, and you should see something like:
bash-2.05b$ ls -las /usr/local/openxdk/lib total 720 4 drwxrwxrwx+ 2 edwardsc None 4096 Sep 8 08:16 . 0 drwxrwxrwx+ 6 edwardsc None 0 Sep 8 08:15 .. 255 -rw-rw-rw- 1 edwardsc None 261086 Sep 8 08:16 libSDL.a 63 -rw-rw-rw- 1 edwardsc None 64490 Sep 8 08:15 libhal.a 32 -rw-rw-rw- 1 edwardsc None 32200 Sep 8 08:15 libopenxdk.a 100 -rw-rw-rw- 1 edwardsc None 102348 Sep 8 08:16 libusb.a 266 -rw-rw-rw- 1 edwardsc None 271764 Sep 8 08:02 libxboxkrnl.aBy default, everything is configured to install into
/usr/local/openxdk
. If you want it somewhere else, you will have to edit the individual make files and change them. I tried to understand the automake/autoconf, but am obviously just not smart enough! Oh well...
bin
directory of wherever you installed OpenXDK, there is a program called cxbe.exe.renameme
. You need to copy this into your path, and rename it to cxbe.exe
(the reason that it is not stored in as cxbe.exe is because my CVS is setup to ignore .EXE files).