On 10/21/2011 02:06 AM, Kevin Hunter wrote:
At 4:52pm -0400 Thu, 20 Oct 2011, Michael Meeks wrote:
http://wiki.documentfoundation.org/Development/LibreOffice4
+ getting stuck into Windows / mingw build etc.
From the wiki page, one of the concerns is "binary incompatibility". I
assume this is in reference to extensions?
Question: is there merit to moving toward an enforced sub-process model
for extensions? My first thought is that this would do a couple of things:
[...]
5. That API definition will be a *lot* of work, but hopefully somewhat
thought out already through only a mild reengineering of the current
binary API.
The UNO API is already there. Or what do you mean?
[...]
The upside is that if we're talking a major version change, /now/ would
be the time to do this.
A downside is that you would still need to maintain (and build!) the UNO
runtime for the MSVC ABI.
-Stephan
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.