Re: [cc65] o65 generation bug?

Uz, Greg: Thanks for your replies.

On Thu, May 17, 2012 at 9:15 AM, Greg King <greg.king4@verizon.net> wrote:
> > 1.  I'd like some nice way to be able to switch between .o65 and binary
> > file formats w/o having to make temporary edits to my code.
>
> 1. You can tell ld65 to drop a memory area by giving that area an empty
> file-name:
>
> MEMORY {
>   HEADER: start = $0000, size = $02,   type = ro, file="";
>   HIRAM:  start = $CC00, size = $0400, type = rw, file="tools.o65";
> }
>
> You can make two configuration files, one that writes HEADER, and one
> that doesn't.  Then, your command-lines choose which cfg. file to give
> to ld65.

*sigh* I'm already not a big fan of having a different cfg file for
every single target I build, let alone multiple.  I don't know if
that's the expectation, but it's how it always ends up for me.  If I
could specify everything needed to correctly build a target, I don't
think I'd mind so much, but I don't think that's possible.  Oh well,
I guess that's a different issue.

> > 2.  Are the __segment_LOAD__ symbols supposed to still work?
>
> 2. The output format has no effect on the "define=" attribute.

OK, looks like there's a problem then.  I have not yet been able to
get a segment load address correctly into my code if I output to
o65.  I'll try some differenrt tests and see what I can learn.


On May 17, 2012, Ullrich von Bassewitz <uz@musoftware.de> wrote:
> If you look at the existing config files that cause the linker to
> emit o65 files, you will notice a few differences to the one you're
> using. I would suggest that you start with a config that is as
> similar as possible to an existing one and then change it step by
> step. This way you will be able to diagnose which change in the
> config file is causing your problems.

I did an ld65 --dump-config lunix... all I could think to do.  Are
there perhaps better starting points?

Thanks Uz, hope your have a great vacation.

// Agent Friday

----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.