Hi Stephan,
Stephan Bergmann a écrit :
> No, you do not need to generate the headers every time
you use them.
> However, when you compiled your software against (some
milestone of)
> URE/OOo/SDK version X, and you now want to compile your
software against
> (some milestone of) another URE/OOo/SDK version X+Y,
you should do a
> clean rebuild (e.g., regenerate all headers) in any
case (and this time,
> you not only *should* do that, but you *must* do that).
Do not confuse
> this with the scenario where you compiled your software
against
> URE/OOo/SDK version X, and now want to run your
software against
> URE/OOo/SDK version X+Y; that will work fine, without
any recompilation.
> What has changed in the generated headers is that they
now include
> definitions of new function overloads
cppu_detail_getUnoType. Those
> overloads are used by the new cppu::UnoType class,
which in turn is now
> used in some places were formerly getCppuType was used
(e.g., for
> Any::operator <<= and Any::operator >>=).
What is problematic is that
> some code that now (indirectly) calls cppu::UnoType
still compiles if
> the new cppu_detail_getUnoType overloads are missing
from the generated
> headers (i.e., if the headers have not been
regenerated), but will fail
> miserably at runtime.
Ok thank you for your explanation: it's clearer in my mind
now.
Cedric
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe api.openoffice.org
For additional commands, e-mail: dev-helpapi.openoffice.org
|