Compilers... What did they use before?

[uncharted]

Karlos wrote:

StormC4 (I think it's like 50 Euro now?)
SAS/C (if you can still get it)

Technically StormC 4.0 used the GCC compiler :-P

[koaftder]

lattice c

Doesnt get much simpler than that

[uncharted]

Trev wrote:
Staying 100% Amiga is great (and sometimes fun), but going through the motions on a real Amiga is a bit painful. Coding under WinUAE is a huge improvement.

I had all kinds of issues with using WinUAE to develop on, often WinUAE itself would bomb it is not helpful in the slightest.  In the end I went back to my crusty old A1200.  Perhaps it's improved now.

[Dr_Righteous]

Thanks to everyone for the info... I think I'm gonna start off with DICE, since it's free, and work my way up from there.

Looks like I'll also need a devkit... Was there ever one beyond v2.1 (OS3.5)? One for OS3.9?

[Doobrey]

Dr_Righteous wrote:
Looks like I'll also need a devkit... Was there ever one beyond v2.1 (OS3.5)? One for OS3.9?

There's an NDK for 3.9, at os.amigaworld.de, although it's nowhere as complete as the 2.1 DevCD, more like an update for 3.9 with a few examples and updated autodocs and includes.

[Karlos]

uncharted wrote:

Technically StormC 4.0 used the GCC compiler :-P

Well, technically, it shipped with both gcc and stormc3 compiler backends, you can use either. Either way, you get an easy to use IDE that in my opinion is ideal for make-loathers...

[Trev]

I had all kinds of issues with using WinUAE to develop on, often WinUAE itself would bomb it is not helpful in the slightest. In the end I went back to my crusty old A1200. Perhaps it's improved now.

The nice thing about WinUAE is the source code. If it bombs, you can find out why, fix it, and recompile it. That said, recent releases (anything released over the last three years) have been pretty stable. Most of the issues I've had with WinUAE over the years have been related to its interaction with third-party components and extensions: parallel port emulation, Catweasel timing, etc.

Trev

[Amiga1200PPC]

You will need the Amiga Dev-CD anyway.
It comes with StormC3.

[JLF65]

All my 68K programs were done in DEVPAC - 100% assembly. ADoomPPC was done with SAS/C-PPC and PASM. iFUSION was done in StormC 4.

[ltstanfo]

Dr.

You are best to stick with C.  The AMIGA, being built on the UNIX model, was almost exclusively coded in C.  I say "almost" because there were other languages available, Fortran, Pascal, Cobol, Basic, Assembler, etc... but most developers coded in the C arena as that what the folks at C= mostly used.

After the demise of C= there were several interesting attempts at AMIGA programming, most notably "E".  It never really caught on however.

Regards,
Ltstanfo

[chiark]

Another vote here for DICE C - it did the job, and mostly did it well.  Do update the thread with your experiences!

[JLF65]

DICE was great for folks who couldn't afford SAS/C. SAS/C was THE standard for the Amiga. MANX C was it's major competitor, and a rather good compiler as well. Both were commercial products.

[Dr_Righteous]

chiark wrote:
Another vote here for DICE C - it did the job, and mostly did it well.  Do update the thread with your experiences!

Well, so far no good... I can code integers just fine... Change them to floats and printf will actually print the word in place of the number. Bad stdio.h?

[Glaucus]

This isn't the answer you want to hear, but I find I'm most efficient using Visual Studio with either VBCC or a gcc cross-compiler.

Well this caught my attention!!! Are you saying that there is a VisualC++ 6.0 cross compiler that will produce Amiga 68K binaries? If so, where do I get one? If that's possible, that would be a wicked development platform as I have WinUAE setup already and have a network share of all my development stuff with my A4000 as well.

  - Mike

[Trev]

Well this caught my attention!!! Are you saying that there is a VisualC++ 6.0 cross compiler that will produce Amiga 68K binaries? If so, where do I get one? If that's possible, that would be a wicked development platform as I have WinUAE setup already and have a network share of all my development stuff with my A4000 as well.

I suppose you could integrate a compiler directly into the IDE, but I just use makefile projects, which let you call any command you want for make, make all, and make clean, and a cygwin-amigaos gcc cross and call make accordingly. Works great on Visual Studio 6.0 and higher. If you're crafty with your headers, Intellisense (type-ahead, function prototype down-downs, struct member completion, etc.) even works properly. And if you have gdb running on the Amiga side, you can even start debugging from the IDE.

Hmmm. It would be sweet to have a Visual Studio compatible remote debugger running on the Amiga side. That might not be that difficult. Don't know. Compile and continue would be cool, too. Anyhow, I don't really know anything about compilers or processing debugging information, so that's over my head.

Trev