I have been attempting to setup a AmigaOS development environment on X86 Linux.
I can get it to compile C progs for Amiga, but none that require Amiga specific stuff like ReAction windows. Yes, I have the SDK installed, links made, export path, etc..
Does anybody have a working cross-compile setup on Linux?
Normally you can compile whit -lauto -lraauto flas, but don't know if that works whit a cross compiler, if not you will need to OpenLibrarie's and OpenClass's manually.
Don't forget -D__USE_INLINE__ saves you alot of truble in the long run, the -lauto stuff should not be used anyway.
Do you get any errors?
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
@ssolie What about removing -lauto totally from next SDK ? If it obsolete and should be not used, then there should be no place in SDK for it at all to avoid any confusion.
@mechanic Quote:
Does anybody have a working cross-compile setup on Linux?
I use crosscompiler on my winxp/cygwin all the time. All you need its follow zerohero's install instructions. If you will have after that any questions, just ask.
Normally you can compile whit -lauto -lraauto flas, but don't know if that works whit a cross compiler, if not you will need to OpenLibrarie's and OpenClass's manually.
Do you get any errors?
Yes. No header files.
The problem is the compile process is not finding the /SDK. It will build Amiga compatible C routines.
I have followed zerohero's instructions (several times). It will build 'Hello world', but no ReAction stuff. It reports something like 'reaction.h no such file or directory'.
I do not have any windows computers, so no cygwin.
I wonder if I could add some kind of #include statement to the programs to find the /SDK directory? Any hints?
Read more carefully He (ssolie) said "raauto" not "auto" the code from libraauto.a has been merged with libauto.a for sometime now. (since OS4 itself?)
it exists only as a stub in newlib and clib for backwards compatabilty, similar to libm.a and libsocket.a in the newlib libs which are also stubs for code that is elsewhere.
Read more carefully He (ssolie) said "raauto" not "auto" the code from libraauto.a has been merged with libauto.a for sometime now. (since OS4 itself?)
The path to the OS includes should be "/SDK/include/include_h" (lower case "i" in "include" directory name) as stated in the instructions here and not "/SDK/Include/include_h". As I said before case matters because linux filesystems are case sensitive.
I was suspecting you weren't using the right command-line (which would have explained why it would not find the includes unless you were explicitly state absolute path to them)...
Obviously I wasn't clear enough. You need to **rename** the **directory** "/SDK/Include" to "/SDK/include" otherwise the cross-compiler won't find the files unless you specify the path manually when compiling using "-I/SDK/Include/include_h".
I usually leave that up to the wife, but this was another of those instances where you do something silly and look around wondering if somebody seen you do it. Like the time I stepped off my bike without putting the side stand down. DOH!