On 03/22/2012 02:13 PM, Caolán McNamara wrote:
On Thu, 2012-03-22 at 13:43 +0100, Michael Stahl wrote:
i don't care that much about which memory allocator we use, but well the
options are 1) link salcpprt into every executable (i.e. do it in
solenv) 2) link it just into soffice.bin 3) don't use it at all.
If we do it at all I guess just for soffice.bin is sufficient really.
The uno and unopkg executables come to mind.
iirc the custom allocator was only used on Linux anyway because given
the way Windows DLLs work it's not possible to override operator new for
the whole process
aha! I guess from the old solenv files then that libsalcpprt was linked
in for all the unix-gcc using platforms, except macosx. I wonder if
macosx was always a deliberate exclusion for some reason, or just
accidental.
I unfortunately lost track long ago which platforms we use our own
memory allocator on, which platforms we additionally use libsalcpprt on,
and what the rationale was for the exceptions.
Stephan
_______________________________________________
LibreOffice mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice
