-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
neo6502: output runnable .neo files #344
Comments
I followed the standards (particularly in execution format) set by the cc65 example I found when I was working on the code, as I had no physical hardware to access and validate behavior on otherwise. I agree that if there's an executable file format now, this should be preferred. I haven't tested this, but the
As for the identifier, you're generally right, though I would probably just stick to |
Fixed by #345 |
neo6502 has file format for executable files which looks like it should be the default output for llvm-mos:
http://neo6502.com/reference/formats/#neo-load-file-format
I think it's a mostly simple change to the linker script
neo6502/link.ld
, but I'm a bit stuck on the details.Here's what I've got so far- the ???? bits are where I'm a bit hazy. I know there are probably some symbols defined somewhere I use to calculate things (
_start
,_end
kind of thing), but I really don't know what the conventions are.Any ideas?
The text was updated successfully, but these errors were encountered: