On 7 Nov, John D'Orazio wrote: > Hello all, ss I continue building and debugging the next release of my > Writer add-on, in which I'm attempting to include the *Chrome Embedded > Framework* in it's Java flavoured build (I'm using the builds from this > release > <https://github.com/jcefbuild/jcefbuild/releases/tag/v1.0.10-84.3.8%2Bgc8a556f%2Bchromium-84.0.4147.105> > ), I've stumbled upon the following situation in my Linux build: > > The Chrome Embedded Framework is requiring a *libnss3.so* and > *libnssutil3.so* version of at least *3.22*, however OpenOffice also > utilizes these libraries and is packaging version *3.14*. Since the > OpenOffice libraries are the first ones picked up (I believe from the > *LD_LIBRARY_PATH* environment variable or similar), it is preventing my > add-on from building, complaining that CEF needs at least version 3.22. As > a test, I went and backed up the *libnss3.so* and *libnssutil3.so* found in* > /opt/openoffice4/program/* , and I copied my system's libraries to that > same folder. My system's libraries are at version *3.49* . After this I was > able to build the add-on and debug->run in OpenOffice, and at least at > first sight I didn't see any adverse effects in OpenOffice from the newer > NSS libraries. > > Would it be feasible to update the NSS libraries in a next release of > OpenOffice, say 4.1.9? Carl Marcum was just confirming that in the current > 4.1.8 release the packaged libraries are in fact at version 3.14.
4.1.8 was upgraded to nss 3.25. This pull request https://github.com/apache/openoffice/pull/100 will get us to 3.39, but it has not even been merged to trunk because we haven't had the resources to test it because of the push to get AOO 4.1.8 out the door. It should be possible to get it into 4.1.9. It would be nice to get fully up to date, but newer versions of nss use a lot of C99, which is not supported by the ancient Visual C++ that we use. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
