Topic: Anybody successfully compiled SGI STL 3.11 with VC5?


Author: "Lee, Jin Woo" <jwlee@mmrnd.sec.samsung.co.kr>
Date: 1998/10/12
Raw View
I'm trying to use SGI STL 3.11 with VC++ 5.0 instead of STL bundled with it.
But I get too many error messages when compiling the project.
If anybody successfully compiled them, please let me know how.
Thanks in advance.

Regards,
Jin

-----
Lee, Jin Woo

Visual Communications Group
Multimedia Lab.
Samsung Electronics Co., Ltd.
South Korea

Email: jwlee@mmrnd.sec.samsung.co.kr
WWW: http://inote.com/~jinulee/
Phone: +82.18.237.4737 (PCS)
---
[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html              ]





Author: AllanW@my-dejanews.com
Date: 1998/10/13
Raw View
In article <6vgvk1$bmk$1@news.kren.nm.kr>,
  "Lee, Jin Woo" <jwlee@mmrnd.sec.samsung.co.kr> wrote:
> I'm trying to use SGI STL 3.11 with VC++ 5.0 instead of STL bundled with it.
> But I get too many error messages when compiling the project.
> If anybody successfully compiled them, please let me know how.

The problem is that Microsoft's <iostreams> and/or <strings> conflicts
with various things in SGI's STL. The only way I've found to deal with
this so far is to isolate all the routines that use STL from those
that use any other library.

This gets awkwards at times. Every "mainstream" function that needs
to do anything STL-ish needs to call an out-of-line function to do
it. And things like ostream_iterator<T> are right out.

I'm certain that SGI didn't intend for this. Can anyone from SGI
shed some light on this? Is there a simple workaround?

--
AllanW@my-dejanews.com is a "Spam Magnet" -- never read.
Please reply in USENET only, sorry.

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own


[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html              ]






Author: saroj@bear.com
Date: 1998/10/14
Raw View
In article <700b8s$dhe$1@nnrp1.dejanews.com>,
  AllanW@my-dejanews.com wrote:

> In article <6vgvk1$bmk$1@news.kren.nm.kr>,
>   "Lee, Jin Woo" <jwlee@mmrnd.sec.samsung.co.kr> wrote:
> > I'm trying to use SGI STL 3.11 with VC++ 5.0 instead of STL bundled with it.
> > But I get too many error messages when compiling the project.
> > If anybody successfully compiled them, please let me know how.

> The problem is that Microsoft's <iostreams> and/or <strings> conflicts
> with various things in SGI's STL. The only way I've found to deal with
> this so far is to isolate all the routines that use STL from those
> that use any other library.

> This gets awkwards at times. Every "mainstream" function that needs
> to do anything STL-ish needs to call an out-of-line function to do
> it. And things like ostream_iterator<T> are right out.

> I'm certain that SGI didn't intend for this. Can anyone from SGI
> shed some light on this? Is there a simple workaround?


I ported SGI STL 3.1 to work with VC++ 5.0. I have contributed several
changes to the STL team at SGI to make it more VC++ and SUNpro C++ 4.2
friendly. Hopefully, those changes will appear in the next release. I
used the string, stdexcept files from VC++ to avoid any conflict between
user code (using SGI STL) and the DLL code.  Other files were from SGI
3.1 distribution.

 -- Saroj Mahapatra

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own


[ comp.std.c++ is moderated.  To submit articles, try just posting with ]
[ your news-reader.  If that fails, use mailto:std-c++@ncar.ucar.edu    ]
[              --- Please see the FAQ before posting. ---               ]
[ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html              ]