Eike Rathke wrote:
Hi CLAIRE,,
On Monday, 2006-10-23 16:16:09 +0100, CLAIRE, Narinder, Group Risk Mgmt wrote:
When Building an uno component in C++ with a Makefile taken from one of the
examples in SDK, which STL is visible, the native STL or STLport ?
STLport.
If STLport , then if the uno component links to a third-part library calling
funtions that return or recieve STL containers, must that third party
library also be built with STLport ?
Yes. Generally you can't mix container objects of different STL
implementations, as their implementation details may differ and
especially iterators of one implementation working on containers of
another implementation will most probably not work, or crash at its
best.
- If you can separate the third-party library STL usage from the
SDK-related STL usage (e.g., by introducing an additional library that
wraps the third-party library and does not use STL in its API), it
*might* work to have two different STL implementations in the same process.
- Similarly, if you do not need any of the STL-using API of UNO (parts
of cpppuhelper, IIRC), it *might* work to tweak your SDK-based project
to not use the SDK's STLport, but use another STL implementation instead.
But all that is rather fragile and there are no guarantees.
-Stephan
Eike
P.S.: As you're not subscribed to the mailing list you were posting to,
you will miss replies that are directed to the list only. When answering,
please reply only to the list (Reply-To header is set), not to my
personal account. Thanks.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
