| |
Slammer
Registered: Feb 2004
Posts: 416 |
Kick Assembler Thread 2
The previous thread took a little long to load, so this is a new fresh one.. |
|
... 592 posts hidden. Click here to view all posts....
|
| |
TWW
Registered: Jul 2009
Posts: 543 |
I followed yuor receipy to the letter (Which is the same as I initially did). When I selected KackAss as a compiler the parameters are generated automatically (here is a ctrl+c+v of my parameters):
-log c64error.txt INPUT -o OUTPUT
and yes KickAss is selected in the drop down thingy aswell.
The Relaunch64 I use is a Beta version can this matter?
Can the location of the different files matter (Here is my setup):
C:\Commodore 64\KickAssembler\KickAss.jar
C:\Commodore 64\Relaunch64\Relaunc64.exe
C:\Documents and Settings\tomw\My Documents\Code\test\test.asm
since it compiles from CMD I recon it should not be any problems with java stuff (Wich is latest and greatest anyways).
However when i compiled from command i copied the test.asm file to the kickass folder due to lazyness in pathtyping :-)
so still stuck I'm afraid :( |
| |
chatGPZ
Registered: Dec 2001
Posts: 11300 |
the first thing i'd try would be ... use path names without spaces :) many programs fail on those, for some reason. |
| |
Slammer
Registered: Feb 2004
Posts: 416 |
I see that you have spaces in the filepath and that might be a problem. Unless Relaunch uses quotes around its arguments windows interpret the filepath as two arguments instead of one:
So this is bad:
java -jar C:\Commodore 64\KickAssembler\KickAss.jar
and this is ok:
java -jar "C:\Commodore 64\KickAssembler\KickAss.jar"
So try removing the space in Commodore 64 and place your sourcefile in a place like C:\source.
Edit: Seems Groepaz came first with the same reply :-) |
| |
TWW
Registered: Jul 2009
Posts: 543 |
Eureka.
I did the folowing after reading your posts:
instead of:
C:\Commodore 64\KickAssembler\KickAss.jar
i do a:
C:\Commod~1\KickAs~1\KickAss.jar
and now the code is compiled. However the file test.prg got stored in the kickass directory instead of the directory from wich it came from... maybee i need to use a c:\source as you said :)
thanx
|
| |
LOGAN
Account closed
Registered: Aug 2003
Posts: 71 |
I think I used something like quotes around the input output to accomidate spaces in pathnames plus relaunch64
maybe something like this:
-log c64error.txt "INPUT" -o "OUTPUT"
On a side note I think there was an option to choose where an prg file would be stored... |
| |
TWW
Registered: Jul 2009
Posts: 543 |
I saw that option too but this would mean it will always produce the .prg in that location and i have 'several' projects going and I want them to be generated in their respective folder. So i'll try the quotes trick. thanx for the advice!
Edit: I tried the qutes and quotes around input produced an error and around output made no difference.
Edit 2: I tried to launc the source file from C:\source\test.txt and the test.prg and the errorlog.txt file ends up in kickass directory. This ain't my day (yeah I have a fricking bad hang over too)... |
| |
Slammer
Registered: Feb 2004
Posts: 416 |
KickAssembler saves the prg file to the current directory unless a specific destination is given.
I find that naturally, but I'll change it if this is not the standard for Compilers / Assemblers around?
Btw. If I change it, I guess you will get in trouble with the autorun facility of relaunc, which can't find the prg file, so we will have to involve Daniel aswell. However, I guess having the prg-files in the KickAss dir is messy, but not a major problem.
|
| |
chatGPZ
Registered: Dec 2001
Posts: 11300 |
i would find it very strange if a compiler/assembler wouldnt save the output to current directory - or whatever destination is explictly given to the -o option .... and i dont think i have ever seen a compiler/assembler that behaves different in that respect :) |
| |
TWW
Registered: Jul 2009
Posts: 543 |
Right.
I guess it depends what you have been used to doing. B4 i used a ms-dos shortcut in the folder of my project which in turn generated the .prg in the same project folder.
But as you said Slammer, It probably isn't suck a big problem to have the .prg file(s) in the kickass directory. I just have to get used to it :) Thanx for a great tool btw.
ps. Headache is gone btw thanx to an execcive order of grease/salt from the local McDonalds ^^ |
| |
TWW
Registered: Jul 2009
Posts: 543 |
Question:
I am setting up 16 irq's with 5 splitts each and naturally I want to use macros to do this.
Here is what i have:
.var raster1 = 90
.var raster2 = 130
.var raster3 = 170
.var raster4 = 210
.var raster5 = 50
*setup irg here*
irq: :interupt(raster1,$1b,$78,$18,$02)
..code..
:endirq
!irq :interupt(raster2,$1b,$78,$18,$02)
..code..
:endirq
!irq :interupt(raster3,$1b,$78,$18,$02)
..code..
:endirq
!irq :interupt(raster4,$1b,$78,$18,$02)
..code..
:endirq
!irq :interupt(raster5,$1b,$08,$15,$03)
..code..
lda #<irq
sta $0314
lda #>irq
sta $0315
:endirq
and the macros look like this:
.macro interupt(d12,d11,d16,d18,dd0) {
dec $d019
lda #d12
sta $d012
lda #d11
sta $d011
lda #d16
sta $d016
lda #d18
sta $d018
lda #dd0
sta $dd00
lda #>!irq+
sta $0315
lda #<!irq+
sta $0314
}
.macro endirq() {
pla
tay
pla
tax
pla
rti
}
The "lda #>!irq+" inside the macro is reported as an error and it won't compile. Is there a way I can use the same macro including 0314/0315 "preconfigured" or do I have to set up 0314/0315 as passed parameters aswell? And if I need to pass the variables can I do a:
:interupt(raster4,$1b,$78,$18,$02,#<irqx,#>irqx)?
Or maybee there is even an easier method to the whole thing? |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | ... | 61 - Next |
