Re: MinGW-Port: Problems with UnoUrlResolver

Am Dienstag, 21. Februar 2012, 15:15:56 schrieb Michael Meeks:
> Hi Helmar,
>
> On Tue, 2012-02-21 at 11:53 +0100, Helmar Spangenberg wrote:
> > I would love to use the MSVC version - however my application is based
> > on some essential MinGW parts, and until now I have not found a way to
> > link my application against the MSVC-DLLs coming with the LibreOffice
> > SDK.
>
>       Ho hum; so - in -theory- ;-) the SAL APIs are all in-line C++ wrappers
> around a native STDCALL C API (for libsal), so assuming you use just the
> sal/ code it could ('in theory') with my limited understanding of these
> things, etc. etc. work. But I'm clearly an optimist ;-)
>
>       What were your linking errors ?
>
>       Failing that, I forget if the MINGW cross-compile works well and runs
> even without UNO remote-control in the picture :-) did you find the
> snapshots worked adequately on Windows ? Then of course, to go deeper
> I'd try running the uno bridge tests (which lurk somewhere) on that
> version to be reasonably sure that UNO is working well.
>
>       Sorry it's a bit of a pain ...
>
>       HTH,
>
>               Michael.

Hi Michael,
 
actually the SAL C API seems to work nicely - after Tor's remarks I re-
installed the MSVC-SDK and tried to link my MinGW-code against ist. However, 
the CPPU interface denies the linking - I observe undefined references to 
cppu::bootstrap(), cppu::BootstrapException::getMessage(), and 
cppu::defaultBootstrap_InitialComponentContext() :-( - probably a tribute to 
the decorations of the c++-function names
 
I tested the 3.5 MinGW snapshots quite a lot on Windows - the only problem I 
found so far was a "General error" message during reading or writing odt-
documents (to my naive opinion, this message seems to be a lie, since I could 
work as usual with the documents ignoring that "error"). On the other hand, 
when using doc-Files the error message does not show up. Thus, the 
functionality of the MinGW port seems to be sufficient for my needs.
 
Unfortunately I am not able to crosscompile the code - I always get stuck in 
the modules sal and libexttextcat, both with the message
i686-w64-mingw32-windres: unexpected version string length 68 != 32 + 8
 
I have no idea what this will tell me...
 
BTW - in case you need some (limited) help in doing the tests, let me know 
what I could do ;-)
 
Thanks,
Helmar