posted by Heinz on 14-Sep-2012 16:21:41 (3887 reads)
New AROS DevPak for AmiDevCpp
What is AmiDevCpp ?
AmiDevCpp is an Integrated Cross Platform Development Environment for Windows, that helps you to comfortably develop C/C++ Applications for the AmigaOS (m68k), AmigaOS4 (PPC), MorphOS(PPC), and for AROS (i386, ppc and x86_64). In the best case, you can just select another Compiler set and compile the same program for different Platforms.
would be good to have 68k devpack extended with aros 68k features or releasing aros 68k devpack that can be used to compile plain aos if aros features are not necessary.
this of course as soon as aros v1 reaches some point of stability, where it pays compile stuff for it beyond contribs.
Well there is no aros68k crosscompiler included yet. I am not even sure if that is necessary, because there is AmigaOS3 68k crosscompiler included and aros 68k is binary compatible.
Maybe when aros68k is finished, it would be good to have a 68k crosscompiler with aros sdk to support non AmigaOS3 features in aros68k.
Status: Offline
wawa
Re: New AROS DevPak for AmiDevCpp Posted on 16-Sep-2012 22:36:48
Joined: 22-Dec-2004 Posts: 3398
From: Freedom world
I dont see point in AROS 68k (cross) compiler because it would be not different to AOS 68k backend.
I am compiling my AOS 68k stuff using MorphOS header files so I can take an advantage of MorphOS API when 68k code is executed in MorphOS machine but binary is fully AmigaOS compatible. I just check at runtime if it is MorphOS or AmigaOS environment.
You never need separate link libs or header files to compile AROS 68k or AmigaOS 68k stuff.
and what if one wants to use mesa at some point? however one should stick to minimal requirements a slong as possible, and to aos 68k compatibility of course.
Joined: 22-Dec-2004 Posts: 3398
From: Freedom world
You dont need separate compiler to support Mesa. If AROS API is used then auto-open code can check if required libraries are available and quit if some pieces are missing. This kind of things are handled in link libraries and developer can always control it using different linker options if libraries cant handle it manually.
It is not different to case where you are using AmigaOS 3.x API and user is trying to execute binary under Kickstart 1.3 -- there it would just exit due to too old or missing libraries.
Perhaps if you wish to use ELF binaries in AROS 68k you could need separate compiler. I dont know how easy it would be to switch between binary formats in GCC.
_________________ Amiga Developer Amiga 500, Efika, Mac Mini and PowerBook
Status: Offline
ChrisH
Re: New AROS DevPak for AmiDevCpp Posted on 17-Sep-2012 12:35:20
I'm only able to support AROS (and MorphOS) because of AmiDevCpp. I hope that support for AROS's new ABI will be added when it eventually gets finalised.
22 crawler(s) on-line.
95 guest(s) on-line.
0 member(s) on-line.
wawa 
