[C++-sig] Re: boost.python compilation with STLport-4.5.3

[Vincent Rey]

First, thank you for your answer.
I downloaded the last beta version (4.5-0119) and found this fix in typeinfo
file :

# if defined(_STLP_MSVC) && (_STLP_MSVC >= 1300)
// In .NET, <typeinfo> actually includes <typeinfo.h>
#  undef _STLP_OLDSTD_typeinfo
# endif

With this version, it nearly compiled :
I had just 2 errors left, strcmp and fprintf not members of _STL.
It finally compiled defining BOOST_MSVC_STD_ITERATOR.


"David Abrahams" <dave at boost-consulting.com> wrote in message
news:uy90zdj1n.fsf at boost-consulting.com...
> "Vincent Rey" <v.rey at laposte.net> writes:
>
> > Boost.Python compiles very well with VC7 stl, but not with
STLport-4.5.3.
> > Already using STLport for other parts of my application, I would like to
> > compile with it.
> >
> > It makes about 200 errors, but all related with 'type_info' :
> > boost_1_30_0\boost\python\detail\msvc_typeinfo.hpp(23) : error C2039:
> > 'type_info' : is not a member of '_STL'
> >
> >
> >
> > I guess it's a problem of configuration of boost (version 1_30_0)... but
I
> > didn't find anything, nor in stlport forum.
>
> It's a problem with your use of STLPort, IIUC.  I think you're trying
> to use the native iostreams instead of the STLPort iostreams.  These
> lines in STLPort's <typeinfo.h> should be bringing the misplaced
> ::typeinfo into namespace _STL, unless you are using a configuration
> which doesn't put the stlport components into "std::" (i.e. _STL):
>
>     # if defined  (_STLP_USE_OWN_NAMESPACE) && ! (defined (_STLP_TYPEINFO)
&& !defined(_STLP_NO_NEW_NEW_HEADER))
>
>     _STLP_BEGIN_NAMESPACE
>
>     using /*_STLP_VENDOR_EXCEPT_STD */ :: type_info;
>     # if !(defined(__MRC__) || defined(__SC__))
>     using /* _STLP_VENDOR_EXCEPT_STD */ :: bad_typeid;
>     # endif
>     using /* _STLP_VENDOR_EXCEPT_STD */ :: bad_cast;
>
>     _STLP_END_NAMESPACE
>
>     #endif /* _STLP_OWN_NAMESPACE */
>
>
> I don't think I'm going to support any such configurations unless
> someone can show me that I'm mistaken and STLPort is just failing to
> put ::type_info into std:: erroneously.
>
> --
> Dave Abrahams
> Boost Consulting
> www.boost-consulting.com