Home | History | Annotate | Download | only in doc
      1 The cygwin platform is used to build STLport with different compilers.
      2 
      3 - gcc (native compiler):
      4 
      5   Makefile : gcc.mak
      6 
      7   Notes:
      8 
      9     1. Static builds (archive)
     10 
     11     If you use the static version of the STLport libraries you have
     12   to define the _STLP_USE_STATIC_LIB macro in order to have your
     13   executable linked correctly.
     14 
     15     2. Link
     16 
     17     Under this platform STLport is complete replacement for libstdc++.
     18   It means that when you were linking with libstdc++ (-lstdc++) you only
     19   have to replace it with STLport (-lstlport.5.2 for instance). However
     20   default gcc behavior is to automatically link libstdc++ and a number of
     21   other system libs. To avoid this behavior you have to use the -nodefaultlibs
     22   compiler option and explicitely give all libraries by yourself. See build of
     23   unit tests to see what library you might need, here is the list when this
     24   note was written:
     25 
     26   without -mnocygwin option:
     27 
     28     -lstlportg.5.2 -lgcc -lm -lc -lpthread -lkernel32
     29 
     30   with -mno-cygwin option:
     31 
     32     -lstlportg.5.2 -lgcc -lmingw32 -lmingwex -lmsvcrt -lm -lmoldname
     33     -lcoldname -lkernel32
     34 
     35     3. No cygwin
     36 
     37     To build STLport libraries that do not depend on cygwin1.dll
     38   making them freely redistributable pass the following option to
     39   the configure script:
     40 
     41   ./configure --with-extra-cflags=-mno-cygwin --with-extra-cxxflags=-mno-cygwin
     42 
     43 - Borland C++ compiler
     44