[libvoikko] Changes to libreoffice-voikko for reliable (un)installation

Marko Wallin marko.wallin at iki.fi
Fri Sep 5 23:50:09 EEST 2014

On 4.9.2014 10.41, Sjur Moshagen wrote:
> 4. sep. 2014 kl. 10:09 skrev Sjur Moshagen <sjurnm at mac.com>:
>>> If the problem cannot be reproduced with these examples there is something wrong with libreoffice-voikko. Otherwise it is likely a bug in LibreOffice and should be reported to bugs.libreoffice.org
>> Based on the above, it looks like there is an issue in libreoffice-voikko.
> [...]
>> I am no C++ programmer, and I am afraid my efforts have to stop now - I really do not know what to do next, and what to look for. More knowledgeable people will certainly do this much, much better and faster than me (if I at all would be able to do it).
> I was wrong :)
> I did a last check of the generated xml files manifest.xml and *.components. The last one had no significant differences, but manifest.xml had a difference that could be relevant: the specification for the component file.
> The complextoolbarcontrols example had generated this:
>    <manifest:file-entry manifest:media-type="application/vnd.sun.star.uno-components;platform=MacOSX_x86_64"
>                         manifest:full-path="complextoolbarcontrols.components"/>
> The LO-voikko file had this entry:
>    <manifest:file-entry
>     manifest:media-type="application/vnd.sun.star.uno-components;type=native;platform=MacOSX_x86"
>     manifest:full-path="voikko.components”/>
> The crucial difference here is the part "type=native;” in the voikko manifest. I removed it, rebuilt the oxt, installed it - and after a restart of LibreOffice - it worked!

Thanks for figuring this out, got it also working with that change.

Did you have any problems with clang? With XCode 5.1.1 I had to remove 
"-malign-natural" on LO SDK settings.mk as clang's feature causes 
unknown compiler flags to hard error rather than warn.

// Marko

More information about the Libvoikko mailing list