https://bugs.documentfoundation.org/show_bug.cgi?id=91966
--- Comment #6 from Victor Laskurain <[email protected]> ---
The problem is still there with LibreOffice 5.2.1.2.
testdruide's diagnostic is not quite right though. The problem is not that
LibreOffice does not recognize msci, rather that msci is not the right value.
The right value for windows_x86_64 happens to be mscx. The
CPPU_CURRENT_LANGUAGE_BINDING_NAME should the correct value at any time but in
the 64 bit sdk for Windows its value is msci instead of the correct mscx.
For the time being I have been able to fix my extensions changing the
component_getImplementationEnvironment function from this:
SAL_DLLPUBLIC_EXPORT void SAL_CALL component_getImplementationEnvironment(
const sal_Char ** ppEnvTypeName, uno_Environment ** ppEnv )
{
*ppEnvTypeName = CPPU_CURRENT_LANGUAGE_BINDING_NAME;
}
to this:
SAL_DLLPUBLIC_EXPORT void SAL_CALL component_getImplementationEnvironment(
const sal_Char ** ppEnvTypeName, uno_Environment ** ppEnv )
{
#if _WIN64
*ppEnvTypeName = "mscx";
#else
*ppEnvTypeName = CPPU_CURRENT_LANGUAGE_BINDING_NAME;
#endif
}
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
