The GNU C-Compiler with Binutils and other useful tools for cross development
This is a Makefile based approach to build the same files as in the old amigaos-toolchain to reduce the build time.
Right now these tools are build:
- binutils
- gcc with libs for C/C++/ObjC
- fd2sfd
- fd2pragma
- ira
- sfdc
- vbcc
- vlink
- libnix
- ixemul (not really, but the headers are used)
sudo yum install wget gcc gcc-c++ python git perl-Pod-Simple gperf patch autoconf automake make makedepend bison flex ncurses-devel gmp-devel mpfr-devel libmpc-devel gettext-devel texinfo rsync readline-devel
sudo dnf install wget gcc gcc-c++ python git perl-Pod-Simple gperf patch autoconf automake make makedepend bison flex ncurses-devel gmp-devel mpfr-devel libmpc-devel gettext-devel texinfo rsync readline-devel
sudo apt install make wget git gcc g++ lhasa libgmp-dev libmpfr-dev libmpc-dev flex bison gettext texinfo ncurses-dev autoconf rsync libreadline-dev
If building with a normal user, the PREFIX directory must be writable (default is /opt/amiga). You can add the user to an appropriate group.
Install Homebrew (https://brew.sh/) or any other package manager first. The compiler will be installed together with XCode. Once XCode and Homebrew are up install the required packages:
brew install bash wget make lhasa gmp mpfr libmpc flex gettext gnu-sed texinfo gcc@11 make autoconf
By default macOS uses an outdated version of bash. Therefore, on macOS host always pass the the SHELL=/usr/local/bin/bash parameter (or any other valid path pointing to bash), e.g.:
make all SHELL=$(brew --prefix)/bin/bash
On macOS it may be also necessary to point to the brew version of gcc make and autoconf, e.g.:
CC=gcc-11 CXX=g++-11 gmake all SHELL=$(brew --prefix)/bin/bash
ALSO NOTE If you want m68k-amigaos-gdb then you have to build it with gcc
Native builds on M1 Macs are now directly supported.
Install cygwin via setup.exe and add wget. Then open cygwin shell and run:
wget https://raw.githubusercontent.com/transcode-open/apt-cyg/master/apt-cyg
install apt-cyg /bin
apt-cyg install gcc-core gcc-g++ python git perl-Pod-Simple gperf patch automake make makedepend bison flex libncurses-devel python-devel gettext-devel libgmp-devel libmpc-devel libmpfr-devel rsync
Precompiled suite with installer: http://franke.ms/download/setup-amiga-gcc.exe
pacman -S git base-devel gcc flex gmp-devel mpc-devel mpfr-devel ncurses-devel rsync
Also note that you MUST cd into an absolute path e.g. cd /c/msys64/home/test/amiga-gcc/ before running make, or builds may fail, because some files aren't found correctly (that's a msys2 bug).
same as normal ubuntu
git clone https://github.com/bebbo/amiga-gcc
cd amiga-gcc
make update
make help
yields:
make help display this help
make all build and install all
make <target> builds a target: binutils, gcc, fd2sfd, fd2pragma, ira, sfdc, vbcc, vlink, libnix, ixemul, libgcc
make clean remove the build folder
make clean-<target> remove the target's build folder
make clean-prefix remove all content from the prefix folder
make update perform git pull for all targets
make update-<target> perform git pull for the given target
display which targets can be build, you'll mostly use
*make all
*make clean
*make clean-prefix
to use NDK3.2 add NDK=3.2 to the make parameters
The default prefix is /opt/amiga. You may specify a different prefix by adding PREFIX=yourprefix to make command. E.g.
make all PREFIX=/here/or/there
The build performs the installation automatically, there is no separate make install step. Because of this, you must make sure that the target PREFIX directory is writable for the user who is doing the build.
If the PREFIX directory points to a directory where the user already has appropriate permissions the below steps can be ommited and the directory will be created by the build process.
sudo mkdir /opt/amiga
sudo chgrp users /opt/amiga
sudo chmod 775 /opt/amiga
sudo usermod -a -G users username
After adding the user to the group, you may have to logout and login again to apply the changes to your user.
Simply run make all. Also add -j to speedup the build.
make clean
make clean-prefix
time make all -j3
takes roughly 10 minutes on my laptop running ubuntu. takes forever running cygwin on windows^^.
If you plan to develop for Kickstart 1.3 you should use -mcrt=nix13 in your compiler commandline
m68k-amigaos-gcc test.cpp -mcrt=nix13
The include files for 1.3 - which are picked up by the compiler if -mcrt=nix13 is used - can be found at <PREFIX>/m68k-amigaos/ndk13-include i.E. /opt/amiga/m68k-amigaos/ndk13-include
To check the built version you may consider to run the gcc dejagnu tests. This does not cover everything but it's a start. The tests are using my improved version of VAMOS (downstream of https://github.com/cnvogelg/amitools) to emulate the Amiga, and right now not all improvements went back into the upstream.
sudo apt install dejagnu
sudo cp baseboards/* /usr/share/dejagnu/baseboards
pip install -U git+https://github.com/bebbo/amitools.git
make check
brew install dejagnu
cp baseboards/* $(brew --prefix)/opt/dejagnu/share/dejagnu/baseboards
pip install -U git+https://github.com/bebbo/amitools.git
make check
This project does not use git submodules since it's to inconvenient to work with develop and release branches in each module and the main module.
Instead the Makefile provides some targets to switch to an older state for all modules.
Use make to switch all modules to a given date. You may also add the time
make v date=2021-04-01
Run make to switch all modules back to the branch
make v
This lists all modules with the last commit. Useful if you switched to a given date to show what's where.
make l
You can switch modules to different branches. E.g.
make branch mod=binutils branch=devel1
The default branches and repositories are in the file default-repos, the local state is managed in the file .repos.