Re: [cc65] Forced imports by linker config

Hi!

On Fri, Nov 12, 2010 at 04:47:31PM +0100, Oliver Schmidt wrote:
> 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?

I would prefer to get some feedback and doing some experimenting with the new
features then discuss the possible changes in a few weeks or so.

[-o switch, order of command line arguments]
> That seems quite surprising to the ordinary user. Normally one tends
> to put the '-o' rather towards the end of a compiler / linker
> cmdline...

Unfortunately I don't see a way around it. The config file may contain
imports, so it must be read before the libraries that may contain the matching
exports. On the other side, the config file usually references the output file
name using %O, which in turn means, it must be known when it is read.

Since I felt into that pit myself (the library makefiles had the wrong order,
so the linker happily generated drivers with an output name of "a.out"), I've
added a warning to the linker. If %O has been used in the config, and -o is
given later on the command line, you will get a diagnostic.

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.