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


Am Mittwoch, 22. Februar 2012, 10:30:26 schrieb Michael Meeks:
On Tue, 2012-02-21 at 17:51 +0100, Stephan Bergmann wrote:
The problem here appears not be C-based sal but C++-based cppuhelper
("using ::cppu::bootstrap()"), which will only work if cppuhelper and
client code are compiled with the same compiler (either both MSVC or
both GCC).

      I wonder - is it possible to expose a C / salcall set of methods for
the basic bootstrapping, as is done in sal ?

      Helmar - I guess, if you're ambitious ;-) you could create such a
wrapper API that does the basic UNO setup / bootstrapping you want,
provide a C API for it, compile that with MSVC++ and then use it. If
that worked well, perhaps we could include it into LibreOffice.

      How does that sound ? How much API do you really need before we get to
raw sal / UNO-ness ?

      All the best,

              Michael.

Yes, Michael, that's what I am thinking of, too. Actually - as far as I am 
informed by my linker - only the entry points cppu::bootstrap(), 
cppu::BootstrapException::getMessage() and probably 
cppu::defaultBootstrap_InitialComponentContext() are missing - not too much to 
create a small compatibility library.

I think I will have to learn a little bit of how to create decent dll's ;-) , 
and - of course - once the code should work, you may include it to the normal 
distribution.

Helmar

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.