Amiga.org
Operating System Specific Discussions => Amiga OS => Amiga OS -- Development => Topic started by: daniel_swe on March 08, 2009, 08:57:13 PM
-
Hello!
Is there any developing tools (like the great amidevcpp) that can compile c++ code for the WB 1.3? /A500
The amidevcpp seems to just work with 3.1!
-
daniel_swe wrote:
Hello!
Is there any developing tools (like the great amidevcpp) that can compile c++ code for the WB 1.3? /A500
The amidevcpp seems to just work with 3.1!
Thats just a matter of the right NDK.
If you have one for OS 1.3, you can use the includes and linker libs to create programs for 1.3
BTW There is a new Version available. (http://amidevcpp.amiga-world.de/download.php?HR_LANG=deutsch)
-
Most of the latest amiga.lib is compatible with 1.3, but check the autodocs. You just need to make sure that the images created by the linker use compatible hunk types and offsets, that you have proper startup code, and that you don't try to use library functions that don't exist in 1.3.
EDIT: You might also want to avoid the C/C++ libraries included with most m68k-amigaos-gcc distributions unless you know the functions work on 1.3. Obviously, you want to stay away from ixemul, too, and you won't have bsdsocket. When in doubt, use Amiga-specific library functions.
-
Hello!
Thank you all for your answers, but i cant seem to find a compiler set for amidevc++ that suppors os1, it only says os3 on the config?
Is there any way to get amidevc++ to work with os1.3? I really love that development environment!
Hope that you can help me with this!
Thank you.
-
I think you can use AmiDevc for ks 1.3, since Amiga (at least until 3.1) is backwards compatible. If you use functions and settings from Ks1.3 only, then your program should work from 1.3 up to and including 3.1. (I don't know the progress from 3.1 to 3.9 since I haven't received my Os3.9 from vesalia yet (after almost a month :-( ))
If you use other peoples source code, also make sure that they do not use any calls to newer functions.
The biggest changes seems to be in intuition and graphics library, whereas DOS and exec are pretty much the same for most applications.
best regards
-
The biggest changes seems to be in intuition and graphics library, whereas DOS and exec are pretty much the same for most applications.
Uhum. KS 1.3 dos.library is anemic compared to KS 2.0+ one. So as a rule of thumb unless if the application uses stdio it won't work with KS 1.3.
Even exec library has tons of new stuff, such as AllocVec/FreeVec which are used extensively in newer programs. It is quite unlikely you could take some even remotely modern amiga application and build it easily for KS 1.3.
-
Uhum. KS 1.3 dos.library is anemic compared to KS 2.0+ one. So as a rule of thumb unless if the application uses stdio it won't work with KS 1.3.
Even exec library has tons of new stuff, such as AllocVec/FreeVec which are used extensively in newer programs. It is quite unlikely you could take some even remotely modern amiga application and build it easily for KS 1.3.
I have wondered about this previously. I was investigating the possibility of creating a link library for C that implements as much of the KS2.0 exec/dos library functionality as is reasonably feasible on top of 1.3. It would obviosuly have to provide replacement headers.
In the end, I didn't have any working 1.3 machines to test the idea.