Merge pull request #46 from kubilus1/upgrade-141
Upgrade to SGDK 1.41
|2 months ago|
|.circleci||7 months ago|
|doc||2 years ago|
|examples||7 months ago|
|extras||5 years ago|
|gen_gcc||1 year ago|
|pkg/DEBIAN||7 months ago|
|sgdk||2 months ago|
|toolchain||2 years ago|
|tools||2 years ago|
|.gitignore||4 years ago|
|.travis.yml||6 months ago|
|Dockerfile||6 months ago|
|LICENSE||1 year ago|
|Makefile||6 months ago|
|README.md||6 months ago|
|_config.yml||2 years ago|
|logdoer.sh||2 years ago|
GENDEV - Genesis development environment for Linux.
Gendev exists to setup a Linux (or presumably other Unix) system for Sega Genesis development. Gendev is not intended to replace, but to be a companion project to the SGDK (Sega Genesis Development Kit).
The quickest way to get going would be to simply install one of the release packages for this project. Both a ‘txz’ and ‘deb’ package are provided.
To run SGDK or in our case, Gendev, you need following packages:
Set the GENDEV environment variable to the install location of the project. Typcially this should be ‘/opt/gendev’
$ export GENDEV=/opt/gendev
You may, perhaps, add this into your bash profile for ease of use.
You may enter your project directory, or perhaps SGDK sample directory and build the projects by specifying the provided makefile.gen.
$ cd myaweseomeproject $ make -f $GENDEV/sgdk/mkfiles/makefile.gen clean all
You may wish, alternatively, to copy the makefile directly to your project.
The toolchain is now setup with CircleCI for continuous integration. This should ease porting and allow better validation of incoming patches.
You may decide to build the full toolchain by making sure you have the following package installed:
$ cd gendev $ make
… and wait about 45 minutes or so.
The .circleci/config.yml script is a good place to look to see how the individual build stages are executed.
Initally this project was a quick hack pulling together GCC build chain scripts from ChillyWilly, and slapping together some hacks to get SGDK to compile under linux.
In effect this was at least 2 projects in one:
The original approaches led to encouraging users to rebuild toolchains, long build times, and large file footprint. Plus it was very difficult to maintain.
I am attempting to: