I'm new to the udk and I'm trying to understand the issues of using STLPort.
I agree on not mixing the two (native STL and STLPort) and this is the
issue I'm trying to prevent.
Also, I'm planning to use both Windows and Intel/Linux enviroment.
In reading the coping with GCC notes:
7 That we have libstlport_gcc.so at all (and thus have to care about its
versioning) is rather unfortunate. In principle, STLport 4.5 (the version we
use on GNU Linux) can be set up either
to cover all of the C++ standard library except iostreams and locales (which
would come from libstdc++.so then), and have no library (because everything
is inline), or
to cover all of the C++ standard library, including iostreams and locales,
and to have libstlport_gcc.so. (In practice, however, I never managed to set
up a working STLport that excludes iostreams and locales.)
So, my goal is just to use native STL and not worry about these issues.
Also BOOST requires that you configure it to point to the STL library being
used, this is outlined in the build process.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]