There is an advantage to having done the setup of all the elements needed a few times. I have been developing a scripted “install” of almost all the development files required on the emulated Amiga environment. Having said that things will naturally be in a state of flux. For example since prior blog posts detailing the “git clone”. A few things have changed or updated, mainly switching from revision 3 to revision 4 of the OS 3.2 NDK, so we’ll deal with that first:
cd ~/FS-UAE/Hard Drives/AmigaDev_XFER/t81t-dev git fetch git pull
If not already running launch the emulated Amiga using the usual Linux Terminal incantation:
cd ~/prg/fs-uae ./fs-uae
One minor point to note is that the self-built version of FS-UAE is code in the progress of becoming version 4, and one of the configuration options we specify (joystick configuration) doesn’t work, meaning that in a productivity (operating system) environment the default “steals” the cursor keys for a virtual joystick. To date I have not found a solution so we need to tell FS-UAE to disable this manually, and unfortunately this has to be done each time we launch the emulator.
- Press Fn-F2 for F12
- Select the option “[ J ] KEYBOARD” under “INPUT PORTS”
- Select “KEYBOARD” under “JOYSTICK PORT 1”
- Arrow up from “KEYBOARD” to “NO HOST DEVICE” and hit enter
- Backspace twice to exit
In short… Fn-F2, Down 4 times, Enter 2 times, Up, Enter, Backspace 2 times.
When booted up start up the Amiga Shell (just a double click on the icon “left out” if you’ve followed along) and most of the work is as simple as issuing these couple of commands:
CD XFER:t81t-dev Execute setupdevtools32
This will go through a large sequence of actions for many packages pulled from Aminet, mostly usually something like:
- Extract archive to temp directory
- Copy files to proper location
- Clean up temp directory
A few package will be treated differently but really “scripted” like this you don’t need to worry about the details.
At the end you will see something like this:
The VBCC compiler (actually C compiler, 680×0 assembler, linker and required ancillary files) requires you to do two “Installer” processes, once for the main “binary” files, and one for the files that tell the compiler to “target” 680×0 based Amiga systems. As described during the second install you are asked to locate the NDK. The installer ACTUALLY asks for NDK 3.9, but we can point it at the NDK 3.2 includes with no problems.
Once both installs are complete the easiest thing to do is reset the Amiga, or maybe just close the emulator and wait for the next “episode” where we’ll start going back over the “tools” used in the production of T81T productions… again…