| |
Trap
Registered: Jul 2010
Posts: 223 |
Loading, packing and linking on crossdev
Hi all,
I've spent some time coding some stuff and now I'm at a point where I need to look at putting the whole thing together. Packing, linking, adding a loader for the parts etc.
I'm using KickAss.
How do you manage files in a crossdev environment? Do I need a D64-editor of some sort to put it all together?
What (IRQ-)loaders and packers are you using these days? .... a lot has happened since SledgeHammer, so please bear with me :)
Trap
|
|
| |
JackAsser
Registered: Jun 2002
Posts: 2014 |
Nowadays I'm using the Booze Design tool-chain, but previously I used pucrunch as packer, cc1541 as d64-creator and krill-load as loader. Worked like a charm and all ofcourse command-line driver and Makefilable. |
| |
Digger
Registered: Mar 2005
Posts: 437 |
Booze Design tool-chain? What's that? |
| |
JackAsser
Registered: Jun 2002
Posts: 2014 |
Quote: Booze Design tool-chain? What's that?
Some internal Booze Design stuff: HCL's d64-utility, ByteBoozer and HCL's loader. Totally similar to the other tool-chain I mentioned (cc1541, pucrunch and krill-load). |
| |
Mr. SID
Registered: Jan 2003
Posts: 424 |
Many people prefer exomizer to crunch their stuff.
And you can also use c1541 (part of VICE) instead of cc1541 to automate the creation of a .d64 file.
And you probably want to use Krill's loader, cause it works. |
| |
WVL
Registered: Mar 2002
Posts: 902 |
I can also recommend :
For packing Pucrunch or Exomizer (though I mostly use pucrunch since depacking is quite a bit faster than exomizer). If you really need a fast depack, you can use a bit simpler packers or even RLE.
For making your disks : C1541 or CC1541. I'd recommend to use C1541, because you can add files one at a time. When using CC1541 you have to add all the files in one go, which can make a really long and unreadable statement. However, CC1541 has some nifty tricks that C1541 doesnt have. So I'd suggest C1541 until it doesnt do the trick for you anymore.
For loading : Krill's loader. You can add and remove options to it, so it fits your purpose like a glove. |
| |
algorithm
Registered: May 2002
Posts: 705 |
I use 64Copy to add files to the D64. Notepad, ACME and WinVice for the development.
By the way, is there a raw incbin image for the Krill loader (something i can just incbin at the end of the c64's ram) |
| |
Mr. SID
Registered: Jan 2003
Posts: 424 |
Yes, you'd still need the cc65 toolchain to build it though.
Edit config.inc to turn the right features on/off.
Then build it like this for example:
make prg INSTALL=0800 RESIDENT=2000 ZP=f0
The build process will spit out a loader.zip containing install.prg at $0800 and loader.prg at $2000, and a loadersymbols.inc containing the entry points into the code and the ZP variables. |
| |
algorithm
Registered: May 2002
Posts: 705 |
I will need to see whether i have all the prerequisites required. Including the make utility etc. |
| |
Frantic
Registered: Mar 2003
Posts: 1648 |
I would also recommend learning how to use makefiles to do stuff like this. Then you can just configure your text editor to call the makefile in your working directory and it will work no matter if you code c64 stuff or c coding for PC/Mac or whatever...
In case you start writing your own conversion scripts and stuff like that for special purposes it is also easy just to put it into the makefile just as well, i.e. you can also customize the build process for each particular project in just the right way. |
| |
algorithm
Registered: May 2002
Posts: 705 |
Aaargh Makefiles. Used to just using notepad for C64 or PC asm. Will have a look at it later, although would prefer if there was a stand alone raw file instead of having to install all this stuff etc. |
... 19 posts hidden. Click here to view all posts....
|
| Previous - 1 | 2 | 3 - Next |
