www.digitalmars.com         C & C++   DMDScript  

c++.stl - STLsoft installation

reply "jim p" <x y.com> writes:
When installing STLsoft, do I unzip the files to the existing \dm\stl
directory, or do I create \dm\stlsoft and unzip them there ??

Also, should the existing \dm\stl directory be placed in the include path ??

My current directory structure looks like:

07/07/2003  10:05    <DIR>          .
07/07/2003  10:05    <DIR>          ..
05/07/2003  18:55    <DIR>          _template PRJ
05/07/2003  18:55    <DIR>          bin
15/12/2002  14:00    <DIR>          Command Line Argument Fix
16/09/2002  18:27    <DIR>          ctools
08/07/2003  15:48    <DIR>          help
02/07/2003  17:46    <DIR>          html
04/06/2003  00:34    <DIR>          include
02/07/2003  19:53    <DIR>          lib
16/09/2002  18:26    <DIR>          mfc
16/09/2002  18:25    <DIR>          redist16
20/10/2002  21:52    <DIR>          redist32
16/09/2002  18:25    <DIR>          samples
16/09/2002  18:20    <DIR>          src
16/09/2002  18:20    <DIR>          stl
08/07/2003  19:22    <DIR>          stlport
Jul 08 2003
next sibling parent reply "Walter" <walter digitalmars.com> writes:
Please repost in the c++.stlsoft newsgroup! Matthew can help you there, I
don't know if he checks this group. Thanks!
Jul 09 2003
parent "Matthew Wilson" <matthew stlsoft.org> writes:
Far, far less regularly/rigorously. It was a bit of coincidence that I did
so just now. ;)

"Walter" <walter digitalmars.com> wrote in message
news:behea1$2m6h$1 digitaldaemon.com...
 Please repost in the c++.stlsoft newsgroup! Matthew can help you there, I
 don't know if he checks this group. Thanks!

Jul 09 2003
prev sibling parent reply "Matthew Wilson" <matthew stlsoft.org> writes:
stlsoft should probably be a peer of stlport. I can't think of any reason to
install it anywhere else, unless you are using it with multiple compilers
(as I do).


"jim p" <x y.com> wrote in message news:begbad$1l5s$1 digitaldaemon.com...
 When installing STLsoft, do I unzip the files to the existing \dm\stl
 directory, or do I create \dm\stlsoft and unzip them there ??

 Also, should the existing \dm\stl directory be placed in the include path

 My current directory structure looks like:

 07/07/2003  10:05    <DIR>          .
 07/07/2003  10:05    <DIR>          ..
 05/07/2003  18:55    <DIR>          _template PRJ
 05/07/2003  18:55    <DIR>          bin
 15/12/2002  14:00    <DIR>          Command Line Argument Fix
 16/09/2002  18:27    <DIR>          ctools
 08/07/2003  15:48    <DIR>          help
 02/07/2003  17:46    <DIR>          html
 04/06/2003  00:34    <DIR>          include
 02/07/2003  19:53    <DIR>          lib
 16/09/2002  18:26    <DIR>          mfc
 16/09/2002  18:25    <DIR>          redist16
 20/10/2002  21:52    <DIR>          redist32
 16/09/2002  18:25    <DIR>          samples
 16/09/2002  18:20    <DIR>          src
 16/09/2002  18:20    <DIR>          stl
 08/07/2003  19:22    <DIR>          stlport

Jul 09 2003
parent reply "Greg Peet" <admin gregpeet.com> writes:
As matt says, it would be a lot cleaner to just put stlsoft in its own
directory:
C:\dm\stlsoft

or place it in a global include directory (as us linux-addict users are
prone to do):
C:\include\stlsoft

and then add the path to sc.ini in c:\dm\bin\sc.ini

"Matthew Wilson" <matthew stlsoft.org> wrote in message
news:beid7o$jh2$3 digitaldaemon.com...
 stlsoft should probably be a peer of stlport. I can't think of any reason

 install it anywhere else, unless you are using it with multiple compilers
 (as I do).


 "jim p" <x y.com> wrote in message news:begbad$1l5s$1 digitaldaemon.com...
 When installing STLsoft, do I unzip the files to the existing \dm\stl
 directory, or do I create \dm\stlsoft and unzip them there ??

 Also, should the existing \dm\stl directory be placed in the include


 ??
 My current directory structure looks like:

 07/07/2003  10:05    <DIR>          .
 07/07/2003  10:05    <DIR>          ..
 05/07/2003  18:55    <DIR>          _template PRJ
 05/07/2003  18:55    <DIR>          bin
 15/12/2002  14:00    <DIR>          Command Line Argument Fix
 16/09/2002  18:27    <DIR>          ctools
 08/07/2003  15:48    <DIR>          help
 02/07/2003  17:46    <DIR>          html
 04/06/2003  00:34    <DIR>          include
 02/07/2003  19:53    <DIR>          lib
 16/09/2002  18:26    <DIR>          mfc
 16/09/2002  18:25    <DIR>          redist16
 20/10/2002  21:52    <DIR>          redist32
 16/09/2002  18:25    <DIR>          samples
 16/09/2002  18:20    <DIR>          src
 16/09/2002  18:20    <DIR>          stl
 08/07/2003  19:22    <DIR>          stlport


Jul 10 2003
parent "jim p" <x y.com> writes:
Thanks



"Greg Peet" <admin gregpeet.com> wrote in message
news:bej3il$19lv$1 digitaldaemon.com...
 As matt says, it would be a lot cleaner to just put stlsoft in its own
 directory:
 C:\dm\stlsoft

 or place it in a global include directory (as us linux-addict users are
 prone to do):
 C:\include\stlsoft

 and then add the path to sc.ini in c:\dm\bin\sc.ini

 "Matthew Wilson" <matthew stlsoft.org> wrote in message
 news:beid7o$jh2$3 digitaldaemon.com...
 stlsoft should probably be a peer of stlport. I can't think of any


 to
 install it anywhere else, unless you are using it with multiple


 (as I do).


 "jim p" <x y.com> wrote in message


 When installing STLsoft, do I unzip the files to the existing \dm\stl
 directory, or do I create \dm\stlsoft and unzip them there ??

 Also, should the existing \dm\stl directory be placed in the include


 ??
 My current directory structure looks like:

 07/07/2003  10:05    <DIR>          .
 07/07/2003  10:05    <DIR>          ..
 05/07/2003  18:55    <DIR>          _template PRJ
 05/07/2003  18:55    <DIR>          bin
 15/12/2002  14:00    <DIR>          Command Line Argument Fix
 16/09/2002  18:27    <DIR>          ctools
 08/07/2003  15:48    <DIR>          help
 02/07/2003  17:46    <DIR>          html
 04/06/2003  00:34    <DIR>          include
 02/07/2003  19:53    <DIR>          lib
 16/09/2002  18:26    <DIR>          mfc
 16/09/2002  18:25    <DIR>          redist16
 20/10/2002  21:52    <DIR>          redist32
 16/09/2002  18:25    <DIR>          samples
 16/09/2002  18:20    <DIR>          src
 16/09/2002  18:20    <DIR>          stl
 08/07/2003  19:22    <DIR>          stlport



Jul 10 2003