Closed GoogleCodeExporter closed 8 years ago
I have no involvement in this project, but I do know how WLA-DX works. I was
intreged
by the changes that they made, so I had a look.
I have no idea why the snes-sdk varient of WLA-DX is not working on your mac,
but I
do know of the changes made to WLA-DX
The first one incolves .RAMSECTIONS, which is handled in the first pass, so I
did a
quick look and found:
pass_1.c:
#if 0 /* bullshit: this is a _RAM_ section */
if (rombanks <= d && output_format != OUTPUT_LIBRARY) {
sprintf(emsg, "ROM banks == %d, selected bank %d.\n",
rombanks, d);
print_error(emsg, ERROR_DIR);
return FAILED;
}
#endif
sec_tmp->bank = d;
}
I've commented out the offending section in WLA-DX 9.5a, compiled it and
managed to
compile the snesc example with it.
There have been very little changes to wlalink, the only two being the
inclusion of
the -o and the -n parameter.
The -o parameter works as advertised.
If the -n parameter is not used (it should be the other way around), wlalink
appends
crt0_snes.obj,libm.obj, libtcc.obj & libc.obj to the list of objects to load.
---
hope this helps.
Original comment by undisbeliever@gmail.com
on 2 May 2009 at 1:08
Hey, i dissambled the linux and mac object to track down what the problem with
wla
on os x. Maybe you can have a look and see whats going wrong.
http://github.com/optixx/snes-sdk/tree/bad62d56343b007cffe59f01bca85c503c303b95/
test
Original comment by david.vo...@gmail.com
on 6 May 2009 at 9:32
This issue was closed by r16.
Original comment by ulrich.h...@gmail.com
on 30 Jul 2009 at 7:14
Fixed in r15/r17. The section sorting code in wlalink was broken. It sorted
sections
by name, but not by file ID, which is necessary to ensure that the TCC
pseudo-registers start at zero (I don't currently remember what precisely
relies on
that, but there is something somewhere...). It just so happens that on Linux,
the
sections are already in the right order, but not on OSX.
Original comment by ulrich.h...@gmail.com
on 30 Jul 2009 at 7:15
That was supposed to say r16/r17, of course.
Original comment by ulrich.h...@gmail.com
on 30 Jul 2009 at 7:17
Original issue reported on code.google.com by
david.vo...@gmail.com
on 28 Apr 2009 at 9:07