Return to README.woe32 CVS log

Up to [ELWIX - Embedded LightWeight unIX -] / embedaddon / libiconv

libiconv v1.14

    1: Installation on Woe32 (WinNT/2000/XP/Vista/7, Win95/98/ME):
    2: 
    3: Building requires the mingw or cygwin development environment (includes gcc).
    4: MS Visual C/C++ with "nmake" is no longer supported.
    5: 
    6: This file explains how to create binaries for the mingw execution environment.
    7: For how to create binaries for the cygwin environment, please see the normal
    8: INSTALL file.  MS Visual C/C++ with "nmake" is no longer supported.
    9: 
   10: I recommend to use the cygwin environment as the development environment
   11: and mingw only as the target (runtime, deployment) environment.
   12: For this, you need to install
   13:   - cygwin,
   14:   - the mingw runtime package, also from the cygwin site.
   15: 
   16: You must not install cygwin programs directly under /usr/local -
   17: because the mingw compiler and linker would pick up the include files
   18: and libraries from there, thus introducing an undesired dependency to
   19: cygwin. You can for example achieve this by using the
   20: configure option --prefix=/usr/local/cygwin each time you build a
   21: program for cygwin.
   22: 
   23: Building for mingw is then achieved through the following preparation
   24: and configure commands:
   25: 
   26:    PATH=/usr/local/mingw/bin:$PATH
   27:    export PATH
   28:    ./configure --host=i586-pc-mingw32 --prefix=/usr/local/mingw \
   29:      CC="gcc-3 -mno-cygwin" \
   30:      CXX="g++-3 -mno-cygwin" \
   31:      CPPFLAGS="-Wall -I/usr/local/mingw/include" \
   32:      LDFLAGS="-L/usr/local/mingw/lib"
   33: 
   34: The -mno-cygwin tells the cygwin compiler and linker to build for mingw.
   35: The -I and -L option are so that packages previously built for the
   36: same environment are found. The --host option tells the various
   37: tools that you are building for mingw, not cygwin.