| |
The Gothicman
Account closed
Registered: Aug 2011
Posts: 40 |
Relaunch64 #3 Beta1 released!
Relaunch64 #3 Beta1 released!
Now as JAR-file.
Looks promising to me :)
http://www.popelganda.de/ |
|
... 49 posts hidden. Click here to view all posts....
|
| |
Testicle
Account closed
Registered: Sep 2002
Posts: 131 |
There should be both error and standard output stream logging for both compiling (assembler) and running (emulator). I guess it has to do with the ProcessBuilder, i.e. the process itself... |
| |
soci
Registered: Sep 2003
Posts: 480 |
I straced this:
execve("/usr/bin/java", ["java", "-jar", "Relaunch64.jar"], [/* 37 vars */]) = 0
[pid 5196] execve("/usr/local/bin/64tass", ["/usr/local/bin/64tass", "-C", "-a", "-i", "/tmp/a.asm", "-o", "/tmp/a.prg"], [/* 37 vars */] <unfinished ...>
[pid 5198] execve("/usr/local/bin/open", ["open", "/usr/local/bin/x64", "/tmp/a.prg"], [/* 37 vars */]) = -1 ENOENT (No such file or directory)
[pid 5198] execve("/usr/bin/open", ["open", "/usr/local/bin/x64", "/tmp/a.prg"], [/* 37 vars */]) = -1 ENOENT (No such file or directory)
[pid 5198] execve("/bin/open", ["open", "/usr/local/bin/x64", "/tmp/a.prg"], [/* 37 vars */] <unfinished ...>
For some reason it tries to use "/bin/open". That's only working on a console, and that's why I get the "Couldn't get a file descriptor referring to the console" message.
The assembler execution is done directly without using "/bin/open". So there must be some difference between the two invocations. |
| |
Testicle
Account closed
Registered: Sep 2002
Posts: 131 |
Yes, I already removed the "open" from the process call. I originally included it, because on OS X you get an access denied error when running Vice without "open". So I thought using "open" would work for Unix in general. But Mac Users can use user scripts if Vice does not start.
On Linux, I now get following when I run this user script (note this only works for beta 12, not released yet).
My script:
java -jar /home/daniel/Schreibtisch/KickAss/KickAss.jar SOURCEFILE
x64 OUTFILE
The log from Vice:
getting symbol guess_format failed!
*** VICE Version 2.3 ***
OS compiled for: Linux
GUI compiled for: GTK+
CPU compiled for: 80386
Compiler used: GCC-4.7.1
Current OS: not yet implemented
Current CPU: Intel Pentium Pro/II/III/Celeron/Core/Core 2/Atom
Welcome to x64, the free portable C64 Emulator.
Current VICE team members:
D. Lem, A. Matthies, M. Pottendorfer, S. Trikaliotis, M. van den Heuvel,
C. Vogelgsang, F. Gennari, D. Kahlin, A. Lankila, Groepaz, I. Korb,
E. Smith, O. Seibert.
This is free software with ABSOLUTELY NO WARRANTY.
See the "About VICE" command for more info.
XRandR: XRandR reports current display: 1440x900@60
C64MEM: Error - Couldn't load kernal ROM `kernal'.
Error - Machine initialization failed.
Exiting...
hm... where is vice located? I can't find it after installing it from apt-get. :-/ I would like to see whether it works when I run and compile from the general settings. |
| |
soci
Registered: Sep 2003
Posts: 480 |
Use the "which" command to print where VICE is:
$ which x64
/usr/local/bin/x64
Don't forget to copy the ROMs to "/usr/lib/vice/*/". These are usually left out due to licensing or redistribution issues. |
| |
Testicle
Account closed
Registered: Sep 2002
Posts: 131 |
Thanks! The missing ROMs might be the reason for the error message... I guess I finish the "goto error" from compiler log this weekend and release beta 12 then... There won't be much beta releases from now on I think, feature list for first final release is almost implemented. |
| |
soci
Registered: Sep 2003
Posts: 480 |
Quoting TesticleYes, I already removed the "open" from the process call. I originally included it, because on OS X you get an access denied error when running Vice without "open". So I thought using "open" would work for Unix in general. But Mac Users can use user scripts if Vice does not start.
You could try "/bin/sh","-c",... instead of "open",.... |
| |
chatGPZ
Registered: Dec 2001
Posts: 11386 |
Quote:CPU compiled for: 80386
wat |
| |
Testicle
Account closed
Registered: Sep 2002
Posts: 131 |
Quote: Quote:CPU compiled for: 80386
wat
Not my fault, you are responsible for the log-stream of your applications. ;-) |
| |
Testicle
Account closed
Registered: Sep 2002
Posts: 131 |
Beta 12 released:
https://sourceforge.net/projects/relaunch64/files/Beta-Releases/
New functions, beside some bug fixes
- "jump to error line" is included (if compiling gave errors...)
- Preferences for fonts
- Preferences for tabs
- Insert basic start
- Change layout of dividers in main window (layout of logs/quick-run-options...)
Cruncher/packer can be used via user script, but are not implemented as general setting (thus the "crunch output file with"-menu does not work yet).
Best wishes
Daniel |
| |
soci
Registered: Sep 2003
Posts: 480 |
It's getting better with every release ;) Even if I mostly just write problems here.
For now:
- fonts are bigger in font selection preview then in editor e.g. size 19 = 24?
- font change does not affect editor window until restart
- different empty line height and line numbers getting cut off is still a problem
- tab size is still independent of font size
- if I use spaces for tabs all tab positions are off by one
- the insert sinus function is still wrong. When using the defaults it'll never reach 255, is rounded down overall and is still asymmetric.
- the insert basic line function is wrong, it should use *=$801, the line link should not be a constant but depends on the length of the number and there should be 3 trailing zeros after.
- couldn't get jump to error work with acme or 64tass
- the compiler log is not with a fixed font size, this makes the caret diagnosis of kick assembler mostly useless
- if the compilation failed the emulator is still started.
Some tips for reproducing the font size problems. Set up some higher DPI than the usual 96. I use 144, that's the correct value for my screen. No, I'm not blind yet ;) Then choose some reasonable font size like 24, this gives me a 160x50 console using 12x24 pixel characters. Unfortunately Relaunch64 does not seem to scale according to the DPI and some of the interface text is really tiny. |
| Previous - 1 | 2 | 3 | 4 | 5 | 6 - Next |
