| |
Optimus
Registered: Jan 2002
Posts: 122 |
C64 crossdeveloping suggestions?
Yep. I am motivated to start coding something on the C64 again. I need to use some helpful tools that will speed up developing and make things less frustrating. I am searching for crossdeveloping tools on the C64.
I am already considering kick assembler. But I might want to hear more suggestions. Btw,. is there a C64 emulator coming with internal assembler? Something like the thing I use on CPC, the Winape32 emulator/assembler? That would be great! |
|
... 66 posts hidden. Click here to view all posts....
|
| |
Frantic
Registered: Mar 2003
Posts: 1627 |
cc65/ca65 + linker can be a little tricky to get into in the first place. You have to learn how the linker works, basically and you can't just do "* = $1000" to set the program counter from the code. In that respect KickAss, ACME or something else is a lot easier to get into.
Have you checked the docs?:
http://www.cc65.org/doc/ |
| |
HCL
Registered: Feb 2003
Posts: 716 |
@kamelito: ca65 generates obj-files, relocatable code. Then later when linking several obj-files they get absolute addresses, just like a C-compiler.
I also recon ca65 needs more setup stuff before you can get running, but i think there is a tutorial in the package.. |
| |
Cruzer
Registered: Dec 2001
Posts: 1048 |
What Shadow said, although I have on the TODO list to try some of the other tools, although I doubt assembling could get any easier - CTRL+F9, and it pops up in Vice.
Only problem I have with KickAss is that the scripting is too slow to make anything advanced. Don't know if any of the alternative assemblers are better.
|
| |
Zone
Account closed
Registered: Nov 2002
Posts: 7 |
If you want your code and data to land at certain addresses with ca65, you have to feed the linker with a link configuration file, and compile with eg. `cl65 -C [link file] mysource.s'.
But what the documentation fails to explain is that you have to append "fill=yes" to each memory segment in the link file for it to work as expected. :) It's explained in the FAQ though: http://www.cc65.org/faq.php |
| |
Radiant
Registered: Sep 2004
Posts: 639 |
Zone: Actually you don't have to add fill = yes unless you're dealing with multiple memory area definitions. I've found that practice to be a bit overused; most of the time you can deal just fine with having a single memory area, "RAM", and then using the "start = $address" attribute for your segments as needed. |
| |
JackAsser
Registered: Jun 2002
Posts: 1989 |
Quote: Zone: Actually you don't have to add fill = yes unless you're dealing with multiple memory area definitions. I've found that practice to be a bit overused; most of the time you can deal just fine with having a single memory area, "RAM", and then using the "start = $address" attribute for your segments as needed.
@radiantx: that's what I do aswell unless I have code that is loaded at one place and run at another. |
| |
Oswald
Registered: Apr 2002
Posts: 5017 |
many assemblers are only good to make your code look like a highly scientifical unreadable c sources. if you're a beginner go for 64tass, there you can just do stuff which will simply work, instead of spending a week to get a screen clr routine working. |
| |
chatGPZ
Registered: Dec 2001
Posts: 11114 |
what oswald123 said \o/ |
| |
Radiant
Registered: Sep 2004
Posts: 639 |
Quoting Oswaldmany assemblers are only good to make your code look like a highly scientifical unreadable c sources
Not all of us find "highly scientifical c sources" unreadable you know. :-) There's a point to all the metacode, though it may not be obvious at first. |
| |
Testa
Account closed
Registered: Oct 2004
Posts: 197 |
what oswald said:
i go for:
ultraedit
64tass
vice
|
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 - Next |
