[fpc-devel]An idea how to fix lost exports in smart-linked

[Peter Vreman]

> It is possible, to supress splitting of .edata's into different modules by smartlinking?
If is it easy to keep all .edata's in one
> module, only one global name would be enough to prevent losing exports by smartlinking.
For example, it would be possible
> to introduce an obligatory module with standard label (e.g., .global $$EXPORTS$$) and
add
reference to this label directly to
> startup file or to PASCALMAIN. If output file must contain no exports, this module will
contain only this label. If linking is not
> smart, this label will also present in big .ow file. May be, it is a solution? But how
easy is supressing of .edata's splitting?

I've a fix for the current 1.0.5 compiler ready. I'll commit it tonight.