| |
FillmoreC
Account closed
Registered: Dec 2008
Posts: 7 |
Relaunch64 Help
Can anyone explain how to make the compile window stay open. If I have an error in my code, I don't know what line it is because the compile windows closes to fast.
I'm using 64tass with it.
|
|
| |
Marauder/GSS
Account closed
Registered: Jul 2006
Posts: 224 |
have you already read that thread about similar problem, maybe it helps?! (c; |
| |
Testa
Account closed
Registered: Oct 2004
Posts: 197 |
well... i am no pc expert.. but use a dosbox to compile your stuff when you have errors.. with kickass it works.....
succes...
|
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
i dont get it
compile window never closes
not when i use ACME
check your config in relaunch |
| |
FillmoreC
Account closed
Registered: Dec 2008
Posts: 7 |
@ Marauder: Yes I have and someone mentioned having the same problem. I looks like someone gave a solution, but it didn't work. So I still have the same problem.
@ Testa: That what I do when I'm not using Relaunch64. BUT someone introduced me to relaunch64 which is suppose to compile your source right from the relaunch64 text editor. It does this, but if you have an error, the dosbox opens and closes before you can see the error.
If I was to switch to compiling in a dosbox when I have an error, it would (almost) defeat my purpose of using reluanch64. Altough your idea, to date, is the best one I've seen and I might considering doing it if there is no other way around it.
@ Rambones. I don't use achme (how is that btw.) I'm using 64tass now. How do you keep your dosbox open with achme. I think in the other thread it mentions something like -v as an option. I don't think 64tass (or tass, the compiler I started with) have this option.
|
| |
Marauder/GSS
Account closed
Registered: Jul 2006
Posts: 224 |
the only way I got it working with 64Tass is:
create a batch-file, f.e. 64tass.bat with following:
@echo off
64tass.exe %1 %2 %3 %4 %5 %6 %7 %8 %9 2>c64error.txt
if %errorlevel% == 1 echo errors occured!>>c64error.txt
and then select the batch-file in the compiler settings for compiler instead of the 64tass.exe and use following parameters:
INPUT -o OUTPUT
the batch-file can use up to 9 parameters, in case you need some more parameters for 64tass.
I had 64tass.exe in same directory as the .bat, both were in the relaunch-directory!!
You could also try in another directory, and if you encounter problems you may need full qualified paths... Not sure if the 64error.txt must be created in same dir as relaunch. I haven't tested this.
I couldn't redirect all output from 64Tass, as it seems relaunch scans for the word 'error' which is also in the output when 64tass compiles fine (error messages: 0 or similar), and so the emulator would never start because it shows the error-window.
That's why I've redirected only the errors and write the text "errors occured" into the c64error.txt file when there are any.
give it a try, maybe it helps?! |
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
Quote: @ Marauder: Yes I have and someone mentioned having the same problem. I looks like someone gave a solution, but it didn't work. So I still have the same problem.
@ Testa: That what I do when I'm not using Relaunch64. BUT someone introduced me to relaunch64 which is suppose to compile your source right from the relaunch64 text editor. It does this, but if you have an error, the dosbox opens and closes before you can see the error.
If I was to switch to compiling in a dosbox when I have an error, it would (almost) defeat my purpose of using reluanch64. Altough your idea, to date, is the best one I've seen and I might considering doing it if there is no other way around it.
@ Rambones. I don't use achme (how is that btw.) I'm using 64tass now. How do you keep your dosbox open with achme. I think in the other thread it mentions something like -v as an option. I don't think 64tass (or tass, the compiler I started with) have this option.
Relaunch assembles, a dos window appears, then closes, and if error, the error log window pops up, so you can click the errors and go to that line.
The assembler is set up and called like this:
ACME
no parameters at all..
I noticed at jeffs place, that his dos window does not close, so he has to close it before it loads the prg into vice.
This does not happen here, it just loads immediately.
So all i can say is, update your windows XP! |
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
to Marauder:
ACME is like turbo assembler, and has macros and defination stuff.
64tass is a bit weird to use IMO. |
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
Oh 1 more post:
so what happens is that the assembler is called from dos, and the output it makes, ends up in the error log, if there are any errors.
Thats how its supposed to work anyway.
The error log is a window inside relaunch. |
| |
Marauder/GSS
Account closed
Registered: Jul 2006
Posts: 224 |
Quote: to Marauder:
ACME is like turbo assembler, and has macros and defination stuff.
64tass is a bit weird to use IMO.
Rambones, I'm software developer juggling bits & bytes every day at work, so I know what ACME, 64tass, Kickass etc. is! (c; btw, I use ACME for some stuff...
The problem here I have (and I guess Knoeki and FillmoreC) is that the Relaunch calls the compiler in DOS-box, but the output of the DOS-box doesn't get properly redirected to the c64error.txt file, where Relaunch reads the lines from and shows them in it's own error-log window then. So if it doesn't find that file, only DOS-box for compiling shows quickly up and closes immediatly and *no* error-log window appear.
Using the batch-files I've posted in the threads about Relaunch and 64tass/ACME it works fine for me. The error-Log window appears only when there are errors, if not emulator starts directly with the compiled program.
I guess it has to do with different output channels on the console, like STDOUT and STDERR... I don't know, Relaunch is a bit strange sometimes and no, my XP is working fine... (c;
|
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
i think the problem is that acme writes the error log in one dir, and relaunch reads it from another..
Set relaunch to "run from this dir",
and put acme in a subfolder in /relaunch/
i have
/relaunch/
/relaunch/acme
/relaunch/source
this works
|
... 3 posts hidden. Click here to view all posts....
|
| Previous - 1 | 2 - Next |
