[Mono-list] io-layer naming issues on OSX.
Miguel de Icaza
miguel at ximian.com
Mon Oct 16 21:46:27 EDT 2006
> > I'd rather limit any renaming to the specific platform that
> > requires it.
> > In bug 77324 it's mentioned that we don't use a linker script on
> > macosx;
> > that should be the first part to be fixed imho.
> Apart from not yet getting Mono to compile for any local experiments
> whatsoever, I do know C but have no idea what a linker script is
> supposed to be... Obviously some part of the existing auto* jungle
> already leads to a linker being invoked. Sorry for my ignorance ...
> so would that be an additional shell script or simply Makefile
> changes or what? What does "we don't use a linker script on macosx"
> mean in cleartext?
I would probably go with some minimized set of defines myself.
The linker script is a way of controlling what the linker does, but
given the little knowledge among most of us about how to do this, its
implications and the need to maintain it on the long term, it seems like
the kind of hack that we might want to stay away from.
> In Visual C++ on Windows I used to have explicit export definition
> files for DLLs listing the symbols to be exported - is there no such
> easy way on other platforms to limit the exported symbols to those
> potentially invoked by developers embedding Mono?
The linker script would help here, but someone has to figure it out and
More information about the Mono-list