Charlie_Gibbs@mindlink.UUCP (Charlie Gibbs) (02/27/91)
In article <39635@cup.portal.com> Peter_Warren_Lee@cup.portal.com writes: >I'm trying to get started programming is assembly language on the Amiga >and need some advice on what assembler to buy. I tried A68K but can't >seem to get anything useful out of it. It will create the .o file but >how do you turn it into an executable file? Is there anyone out there >that uses A68K regularly that can point me in the right direction? >Thanks, > Pete I guess you could call me a regular A68k user - I wrote it. :-) Anyway, you need a linker, not just for A68k but for any other assembler or native code compiler (except, I hear, for AssemPro). Look for an older version of Blink - the latest versions are commercial products and belong to SAS, but version 6.7 was freely distributable and works quite well. It's included, among other places, with Matt Dillon's DICE package if I remember correctly. BTW I've finally taken the time to work on another version of A68k. (Still no time for 68020/030/881/xxx support, sorry.) Version 2.70 is undergoing beta testing as I speak; it incorporates most of the bug fixes and enhancement requests that I've received over the past year. When I get the new version working to my satisfaction I'll send it to Fred Fish as well as making it available to anyone who wants to send me a disk. Charlie_Gibbs@mindlink.UUCP Elevator music brings me down.
Peter_Warren_Lee@cup.portal.com (02/28/91)
I'm trying to get started programming is assembly language on the Amiga and need some advice on what assembler to buy. I tried A68K but can't seem to get anything useful out of it. It will create the .o file but how do you turn it into an executable file? Is there anyone out there that uses A68K regularly that can point me in the right direction? Thanks, Pete Peter_Warren_Lee@cup.portal.com
mpierce@ewu.UUCP (Mathew Pierce) (03/01/91)
In article <39635@cup.portal.com>, Peter_Warren_Lee@cup.portal.com writes: > I'm trying to get started programming is assembly language on the Amiga > and need some advice on what assembler to buy. I tried A68K but can't > seem to get anything useful out of it. It will create the .o file but > how do you turn it into an executable file? Is there anyone out there > that uses A68K regularly that can point me in the right direction? > Thanks, > Pete > > Peter_Warren_Lee@cup.portal.com To make use of the #?.o files (object files) you need to employ a linker and the approriate libraries. A68k will work fine, you need to get a linker, I suggest the public domain Blink linker from the Software Distillery, it's available on may fred fish disks. You will also need the appropriate library, normally amiga.lib is used, but if you want to stay PD, try the PD version of this called small.lib, I think that Matt Dillion put this together. All in all, I would suggest that you get the Blink linker, and get the Native Compiler Update from CATS, I don't have the address right off, but I'm sure that someone can post it. That should get you going. Matt Pierce
dillon@overload.Berkeley.CA.US (Matthew Dillon) (03/04/91)
In article <1475@ewu.UUCP> mpierce@ewu.UUCP (Mathew Pierce) writes: >In article <39635@cup.portal.com>, Peter_Warren_Lee@cup.portal.com writes: >> that uses A68K regularly that can point me in the right direction? >> Thanks, >stay PD, try the PD version of this called small.lib, I think that >Matt Dillion put this together. All in all, I would suggest that you get >the Blink linker, and get the Native Compiler Update from CATS, I don't have >the address right off, but I'm sure that someone can post it. That should >get you going. > >Matt Pierce no, I didn't. The freeware version of DICE includes DLINK and a generated (freeware) version of amiga.lib called AMIGAS13.LIB (since DICE handles both 1.3 and 2.0 includes this differentiates between the 1.3 and 2.0 amiga.lib). -Matt -- Matthew Dillon dillon@Overload.Berkeley.CA.US 891 Regal Rd. uunet.uu.net!overload!dillon Berkeley, Ca. 94708 USA
sschaem@starnet.uucp (Stephan Schaem) (03/04/91)
Just to say anything.I tryed C.A.P.E , MACRO 68, A68k, quelo, all PD 6800x0 assembler and find Devpac 2.0 the most reliable. Havent checked adapt or the one from argonaut.... The only thing about devpac is, no precompile file, 2 pass include only, no fancy instruction support like math coprocessor or amiga copper.(also for some, no arexx support). Devpac like K-Seka like assempro do not need a linker to creat executable file... (I do not recomend old K-Seka version or any of assempro). I do not use macro 68 because it doesn't seem to work perfectly, I hang on some supposed macro error! (That only happen with macro 68, and is not cause by the macro layout or content.... ) Devpac is pretty fast but it will still take 10-15minuts to compiles 2-3megs of source code (with anything but command/instruction striped). For linker, blink is good enaught but not 100% reliable.C.A.P.E linker seem to be faster and more reliable since it will link what blink BUG on. If you are doing commercial product or want your program to run on all machine I strongly sugest Devpac... (You can trash the editor that come with devpac and use CED-pro instead).