Re: [cc65] Secondary linker configurations

On Thu, Sep 24, 2009 at 08:48:10AM +0200, Groepaz wrote:
> mmmh, would it also make it possible to link alternative libs? for example i
> have a few alternative conio implementations lying around:

In collaboration with Oliver, I've added support for "extra" library object
files. These are meant to replace standard modules in the library with
specially crafted replacement modules. It works similar to secondary linker
configurations: The modules are maintained together with the standard library,
but at build time they're not added to the library (which would not work
because they duplicate already existing external identifiers), but installed
into a subdirectory named "obj" inside the cc65 installation tree. The object
file search path is set to this directory (or must be set, depending on the
platform).

It is then possible to name the files on the command line before the library,
and they will get linked to the application. Because any externals in these
modules are already resolved, the linker won't fetch the original module from
the library.

If your conio implementations are contained within one file (for example,
because all they replace is putchar), they would definitely qualify for this
approach. If they're contained in multiple modules, this becomes too complex,
and I would rather suggest adding them as a project to the cc65 contrib
section.

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.