Re: [cc65] Forced imports by linker config

Hi Uz,

> I reworked linker config parsing and processing, so it is now possible to
> force imports of symbols by using the linker config.

Cool :-)

> It is no longer the compiler that must force
> the import of startup code, this can be done in the linker. Using this method,
> the linker config can also define, which headers get included in the output
> file(s).

Are you going to modify the startup code / default linker config for
one target (i.e. c64) to serve as an example on how to leverage the
new model for the "usual" scenario?

> This allows to do so complicated things that I'm not even
> able to guess what is finally possible:-)

Me too...

> The changes had some effects on order of command line arguments [...].
> For examples, the output
> file (-o switch) must now be defined before using -t or -C, because the config
> file is read when -t or -C is found on the command line. Changing the output
> file name using -o when the config is already read will cause the name be
> ignored in most cases.

That seems quite surprising to the ordinary user. Normally one tends
to put the '-o' rather towards the end of a compiler / linker
cmdline...

I.e. here:
http://www.cc65.org/snapshot-doc/using-make-3.html
http://wiki.cc65.org/doku.php?id=cc65:project_setup

Or from:
http://www.gnu.org/software/make/manual/make.html

    tar:    $(OBJS)
             $(CC) $(LDFLAGS) -o $@ $(OBJS) $(LIBS)

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