Re: MinGW-Port: Problems with UnoUrlResolver

Am Mittwoch, 22. Februar 2012, 11:39:14 schrieb Stephan Bergmann:
> On 02/22/2012 11:30 AM, Michael Meeks wrote:
> > 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 ?
>
> I doubt that Helmar's application only uses C-based sal API after
> initial setup (how would it communicate with LO then? hand-crafted
> binary UNO calls? and in case it does not communicate with LO via UNO at
> all after setup, why set up the UNO connection in the first place)?  In
> which case that wrapper would buy you nothing.
>
> Stephan

My understanding of the whole subject still is too small - I thought, once I 
got the context bootstrapped, the whole communication to the office is done by 
a socket or a pipe. Is it too naive to think that when the context is 
available all the rest of the communication should work?

Helmar