Best C compiler for Amiga?

[neofree]

Note sure if this is the right site/forum, but thought I'd get some opinion...

What is the best C compiler for Amiga?

I'm not sure if any of them make it easier to design GUI interfaces, but that would be a plus.  My app would only need simple GUI but still would need it.

Free is preferable, but I'm also not going to settle for free when the pay version is so much better..

Serial I/O is a key thing, so if one has notably better serial functions that would be helpful to know.

Thanks!

Neofree

[neofree]

Oh I forgot to mention that the target platform is preferably ALL Amiga's, but if it makes a difference I'd rather it work on classics.  (1.3-3.1)  If the program will run in a WB compatibility mode on 4.x then that's fine with me.  I will probably never have anything other then classic hardware...

[mongo]

If you have a PC running Windows, I'd recommend AmiDevCpp.

http://amidevcpp.amiga-world.de/aboutamidevcpp.php?HR_LANG=english

[ChaosLord]

If you are planning to debug your software then you want to use the SASC fully Amigatized C compiler.  You can debug your code on a single Amiga using the GUI Source Level debugger or you can debug it from another Amiga across the serial port using the GUI source level debugger.


If you do not care about debugging then use VBCC.


Matt can give you more detailed infos

/me casts Summon Matt Hey

Matt Hey suddenly appears in a puff of mystical smoke

[NovaCoder]

If you have a PC running Windows, I'd recommend AmiDevCpp.

http://amidevcpp.amiga-world.de/aboutamidevcpp.php?HR_LANG=english

I couldn't really get on with AmiDev (too buggy), I'm currently trying to setup Eclipse CDT with gcc (cross-compiler), looking good (so far).

If you want to code on a real Amiga instead then I'd recommend either CubicIDE or StormC V4 (which also has a GUI editor called StormWizard, which is now open source).

Anyway....have fun!

[neofree]

Don't care too much about the debugging...

The compiler needs to support Stock/Original Amiga 500 targets (68000/1.x/512k+ RAM)...   Since all I have is the above mentioned target right now, it will either need to be a Windows (such as the first one mentioned here) compiler, or something else...

edit: NovaCoder - missed your reply when I wrote this -..  Will CubicIDE or StormC (sounds familiar) run on A500?  I'm building a 2meg/IDE upgrade to help there..

Thanks,

Neofree

[NovaCoder]

Don't care too much about the debugging...

The compiler needs to support Stock/Original Amiga 500 targets (68000/1.x/512k+ RAM)...   Since all I have is the above mentioned target right now, it will either need to be a Windows (such as the first one mentioned here) compiler, or something else...

edit: NovaCoder - missed your reply when I wrote this -..  Will CubicIDE or StormC (sounds familiar) run on A500?  I'm building a 2meg/IDE upgrade to help there..

Thanks,

Neofree

Hiya,

Unless you have a RTG Amiga, you're better coding on a PC if you're after a decent IDE.

Basically for win32 native coding you either have AmiDevCPP or some other IDE using gcc (eg Eclipse).   If you want to code using WinUAE or have an RTG Amiga then you're looking at CubicIDE or StormV4.

[neofree]

What about a simple editor and a command line compiler?

Will anything like that run on an A500?

Thanks

[neofree]

What was the standard compiler for A2000 back in the day?  Certainly it had a compiler available for purchase?

I don't care about MUI, RTG, etc.  I prefer original A500/A2000 (and A3000) computers ... If I want to keep upgrading an Amiga to be modern I might as well use a PC (which I have several).

[ferrellsl]

SAS/Lattice was the best compiler if you don't need an IDE.  I used an ASCII text editor and the command line to develop my programs and it wasn't bad at all.

I was able to cram the compiler and all my tools onto one floppy disk.  Booted Workbench on DF0: and ran the compiler from DF1:

I compiled my programs to RAM: which greatly speeded up the compile and link process.

[rkauer]

Nobody into Cubic IDE? It is commercial and still available, have powerful cross-compiler but I think it is not 1.3~2.x friendly, nor have an enhanced debug tool. But it is the latest available commercial compiler.

[ferrellsl]

Sounds to me like neofree is looking for a retro environment to develop his software and wants to target Amigas running WB 1.2 thru 3.1.  He isn't looking for the latest commercial compiler.  Just a good, solid compiler that works from a command prompt and produces small, fast programs.  SAS/Lattice is it unless he wants to try Aztec C.

[mousehouse]

SAS/Lattice was the best compiler if you don't need an IDE.  I used an ASCII text editor and the command line to develop my programs and it wasn't bad at all.

I was able to cram the compiler and all my tools onto one floppy disk.  Booted Workbench on DF0: and ran the compiler from DF1:

I compiled my programs to RAM: which greatly speeded up the compile and link process.

I had a two-floppy boot set that would create a RAD: disk with a full workbench install and compiler set. Ran completely from the 4MB RAM on my A2000 ;-)

Back on topic,

I did most of my stuff on Lattice C, later SAS/C which has kept on working great from a stock A2000 (ks1.3) to my recently acquired A4000 (ks3.1/3.9). The latest patches even provide for PowerPC builds for the Cyberstorm cards, I tried it and works great. The last versions (6.5.something) even include a basic editor / shot at an IDE. Never used that though, always worked with MicroEmacs or CygnusEd for programming, and doing compiles / makes from AmigaDOS.

I also have several other native-Amiga compilers... think Aztec C and Maxon C++. If you need documentation for any of them, I have the official retail versions and can have a look if I can digitize them somehow...

[davideo]

@mousehouse

If the Maxon C++ documentation contains more information than the help file does then I would be interested in a copy of it please.

Dave G :cool:

[Heinz]

I couldn't really get on with AmiDev (too buggy),

I often see people posting that AmiDevCpp is buggy, but I dont get much bug reports from the people that are actually using it (DaveAE / AudioEvolution, Jahc / WookieChat etc.)

So would you please post proper bug reports or stop calling it buggy ?