Welcome and thanks for your offer of help, mcgeezer. I would not like to flood this thread, so just a quick note for everyone asking
My problems are not related to programming the Amiga (yet, that will surely come later on) but about how to setup a cross-dev suite. To be honest, I just made a quick (unsuccessful) attempt.
I wanted to be able to write C code, mix with some asm (so I can start learning progressively), and find a way to build and execute in a simple step. My intended target was an Amiga 500.
So I tried setting up vbcc and vasm in my PC with no success (I can't remember why, now). Then, I stumbled upon a toolchain called winuaedemotoolchain5v3 which included everything I needed (also tools for converting graphics and such things). I compiled the included demos (asm) and they worked nicely, so I tried my first program:
Código: Seleccionar todo
int main(int argc, void *argv)
Easy as pie, isn't it? Well... no.
I learnt that the included libraries ('m68k-amigaos') were intended for WB 3.1. I had to look for a specific set of libraries for 1.3. I can't remember now how I ended up with one which did not include stdio, if I recalled correctly, although eventually I seem to have solved also that. My program (after some tweaks on the config files, which are quite difficult to master) ended up compiling and, when launched, it showed the CLI, stopped there for some time (probably loading the program) and... Guru Meditation.
If I remove the printf sentence the program loads, does nothing as expected, and the CLI ends up with the prompt: 1> Nothing else that I can do. Not even a command.
The same toolchain has a .bat file to compile and run in Aros, so I also tried. In this case the message is printed, but an Alert is shown complaining about "Sanity check on memory list failed".
And that is all my experience... I will probably have to start from scratch again, but not having a downloadable dev environment with simple C examples and instructions is quite a nightmare for us the ignorant lamers