| |
ChristopherJam
Registered: Aug 2004
Posts: 1409 |
Assembler preferences.
Two questions:
- what's everyone using these days?
- on large productions, do groups tend to enforce a single assembler for the entire project, or is the code base a bit heterogenous?
I'd like to keep this discussion purely focussed on assemblers; please leave code generators, loader toolchains etc for that other thread.
(as for me, I'm still using xa65 for most projects) |
|
| |
Martin Piper
Registered: Nov 2007
Posts: 722 |
I only use one: https://github.com/martinpiper/ACME
But then I work alone and just give away my code. ;) |
| |
Mixer
Registered: Apr 2008
Posts: 452 |
64tass
Larger projects tend to end up written on multiple assemblers depending on individual preferences. |
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
64tass
hetero |
| |
Flavioweb
Registered: Nov 2011
Posts: 463 |
64tass |
| |
Karmic
Registered: Apr 2015
Posts: 66 |
64tass, all the way. :) |
| |
T.M.R
Account closed
Registered: Dec 2001
Posts: 749 |
i'm an ACME bunny. |
| |
Bitbreaker
Registered: Oct 2002
Posts: 508 |
<- Strict ACME fanboy. On projects any assembler is allowed that is able to work within a make-environment. It must accept external information liek labels and one should be able to implement a few simple macros for linking.
A project with acme, dreamass, dasm, c6510, kickass all in a mix, is no problem this way. Kickass however handles the handover of external information a bit different, so no -Dlabel=foo stuff available there, but integration is doable after finding out the differences. |
| |
Frantic
Registered: Mar 2003
Posts: 1648 |
ACME in general and specifically for a cartridge project I'm using DreamAss. |
| |
lft
Registered: Jul 2007
Posts: 369 |
xa65 here. |
| |
JackAsser
Registered: Jun 2002
Posts: 2014 |
ca65 |
... 204 posts hidden. Click here to view all posts....
|
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | ... | 22 - Next |
