Re: [cc65] Problem with generating o65 files

From: Ullrich von Bassewitz <uz1musoftware.de>
Date: 2005-01-19 22:43:45
On Wed, Jan 19, 2005 at 10:17:17PM +0100, Spiro Trikaliotis wrote:
> What am I doing wrong?

Order is important here. FILES and FORMATS have to go to the end of the linker
config. The reason for the error message is, that output files are specified
in the MEMORY section. When the linker reads a filename in the FILES section
(%O in this case), it tries to find that file in the list of output files, but
since no output files have been defined, it cannot be found.

BTW: Why aren't you using -t lunix on the command line, or just use the Lunix
linker configuration as a starting point? This could have saved you quite some
trouble:-)

> BTW: Can ld65 handle such (André Fachat's) o65 files as inputs? I would
>      have tested myself, but as you see from above, I was not able yet
>      to generate such files. ;-)

ld65 cannot use o65 files as input, but co65 is able to translate o65 files
back into assembler files, which can then be passed through ca65 to generate
native object files, which in turn can be used with ld65. I haven't tested
this with o65 files generated with xa (André Fachats Assembler), and there may
be format limitations (no "large modell" o65 files), but I think it *should*
work. The program cascade gets rather long in this case,

                 xa             co65           ca65           ld65
        test.xa ----> test.o65 ------> test.s ------> test.o ------> a.out

but a Makefile should do wonders:-)

Regards


        Uz


-- 
Ullrich von Bassewitz                                  uz@musoftware.de
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.
Received on Wed Jan 19 22:43:51 2005

This archive was generated by hypermail 2.1.8 : 2005-01-19 22:44:02 CET