Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


Hi Tor, Michael,

I finally got it working with SAL_DLLPUBLIC_EXPORT as michael suggested.
If there is any possible trouble, let me know ;)

--
Cedric

On Wed, 2010-10-27 at 07:21 -0600, Tor Lillqvist wrote:
The question (for
Tor) is - if we have a __declspec(dllexport) on two identical symbols in
two shared libraries that link to each other: will we get some vile
linking conflict ? [ or not ] ;-)

As far as I could see by experimenting, yes, as long as you from a DLL don't both import and 
export a symbol with the same name, it should work.

Possibly using some clever tricks or useful options to the linker it might be possible to make 
the linker create a DLL that both imports a certain symbol from another DLL, and also exports the 
same symbol.

(If just you manage to create such a DLL, using it should not be problematic... After all, to the 
run-time linker, there should be nothing confusing going on.)

But of course, without actually trying, and considering C++ is involved, take all the above with 
a large grain of salt.

--tml





Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.