<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Tor,<br>
<br>
On 06/08/13 12:58, Tor Lillqvist wrote:<br>
<blockquote
cite="mid:CANGFS+-XeE25HjaY1tVS1ZJRoJJQhTwVmLGHpybLjCRdmo1oig@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
that means that we need to compile add-ins using the same
C++ compiler as the UNO libraries were compiled with. What
compiler is that, in the case of binary releases of LO for
Windows? </blockquote>
<div><br>
</div>
<div style="">Visual Studio 2010. Using other Visual Studio
versions (2008, 2012) might work fine, too.</div>
<div style=""><br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Thanks for that. Do you know how often we would need to recompile
extensions for Calc? Every major release, or every minor release, or
less often? Does it matter that the API changes at all, or only if
the bits used by the add-in have changed? Is there a way, without
careful re-testing, to determine whether or not one can expect a
simple Calc Add-In to be compatible with a given version of
LibreOffice?<br>
<br>
Cheers<br>
JP<br>
<br>
</body>
</html>