| |
JAC
Registered: Aug 2002
Posts: 56 |
WUDSN IDE: Integrate ACME or Kickassembler or ...
Hi there,
I'm the creator of the WUDSN IDE development environment. It can be used for different platforms and compilers.
For C64, currently ACME is included (not 100% yet). The next version will support MADS in all platforms.
Besides this, I'd like to include a special C64 compiler, because I know codes always have a lot a sources in their favourite syntax and they like to keep them. Therefore I'd like to get some feedback on the following question.
Which cross-compiler it used most often for C64 coding nowadays?
Is it ACME (seems a bit outdated for me), or Kickassembler (seems very vidid), or...
|
|
... 22 posts hidden. Click here to view all posts....
|
| |
MagerValp
Registered: Dec 2001
Posts: 1055 |
Quoting JACInteresting to see DASM mentioned here and also very heterogenous feedback so far. Please keep on voting :-)
Yep, there just isn't a standard assembler in the C64 community. Fortunately most of the assemblers here are relatively bug free and quite capable. Everyone can pick the syntax they prefer and the advanced features they want the most. |
| |
Perplex
Registered: Feb 2009
Posts: 254 |
Here's yet another vote for ca65 (part of cc65, see http://www.cc65.org/).
|
| |
Mr. SID
Registered: Jan 2003
Posts: 421 |
I don't care much for this IDE (looks like Java ;), but since there's quite a large number of assemblers to support, you should have some kind of data-driven approach, i.e. a definition language for the assembler syntax.
Then everyone can add support for their own favorite assembler (and the ones that will come out in the future).
|
| |
JAC
Registered: Aug 2002
Posts: 56 |
@Mr. Sid: Compilers and Emulators are added via extension points. For a new compiler, you provide a simple XML file which describes the syntax elements. With this you'll get about 90% of all features inkl. navigation and hyperlinks already. For the rest and more sophisticated things, for example parsing of console output and output files to extract messages and label values, mapping message severities, own preferences, icons and texts all you need are 10-80 lines of code typically.
The support for Apple2 for example is currently under development by Nick Westgate using this mechanism. Here's the example file. The point is that once it works I like to provide the support for all the users. That's why I merge extensions with the standard delivery and provide it as a service. And of course compilers I have not used yet might require extensions to the parser, in case the compiler has some new unknown features. But now that MADS support is complete, I think this hardly will be significant :-) |
| |
PopMilo
Registered: Mar 2004
Posts: 145 |
@JAC: I use WUDSN for A8 development and must say it is an awesome tool, and I love where you are heading with its development.
As you make it useful for C64 also and mention MADS as possible assembler for it (if I understood you correctly) I wonder if you know if there will be better documentation for MADS in English ?
|
| |
Martin Piper
Registered: Nov 2007
Posts: 634 |
I always use a slightly modified ACME. |
| |
Oswald
Registered: Apr 2002
Posts: 5017 |
Do you have a tutorial on this XML ? Some people would surely start on adapting it for their fave assemble, and the rest would benefit greatly :) |
| |
AüMTRöN
Registered: Sep 2003
Posts: 42 |
+1 for DASM. I use this one: http://iancoog.altervista.org/C/dasm2.20.07-iAN_Rev_L.rar |
| |
JAC
Registered: Aug 2002
Posts: 56 |
@PopMilo: I still hope a fairy grants me 3 wishes one day, one of them would be the English MADS tutorial for sure. Or enougth time to translate it myself...
@Oswald: No documentation yet, but I'll create one. I found that best thing is direct contact to the owner/maintainer of the compiler, because I also need a "test suite" and they usually have one for themselves already and this way I'm always informed about new features. In fact I have ACME and DASM definition almost complete already and regarding KickAss I'm in contact with Mads now. For ACME & KickAss the parser will have to learn "{ }" - what will change the XML and take some time, I assume. Also I want to separate the compiler from the hardware (currently they are linked, e.g. in the preferences).
So this thread was intended to get a "stament of direction", but of course I would really appreciate to have volunteers for testing.
|
| |
Oswald
Registered: Apr 2002
Posts: 5017 |
looking forward for the docs, 64tass is a very simple compiler compared to the rest, I guess it will be easy to xmlize it :) |
| Previous - 1 | 2 | 3 | 4 - Next |
