Changes between Initial Version and Version 1 of user-windows


Ignore:
Timestamp:
Aug 16, 2007 1:45:24 PM (14 years ago)
Author:
andreasw
Comment:

first version of windows install page

Legend:

Unmodified
Added
Removed
Modified
  • user-windows

    v1 v1  
     1= Windows Specific Installation Notes =
     2
     3This page is being set up.  Below just a first draft of the information (Lou's email message to the TLC mailing list)
     4
     5{{{
     6
     7 1) True MSVS, using the MSVS IDE.  No autotools or unix anywhere in the
     8    vicinity.  Now available (MSVS8) as a free download.  The usual source of
     9    MS cl, MS link, and other MS build tools.  No free Fortran compiler.
     10
     11 2) Full cygwin, which tries to be linux running on top of Windows.  From the
     12    buildtools point of view, the important things are that the GCC compilers
     13    are available and cygwin.dll (or some such name) will be needed when code
     14    is run, hence binaries will not run in the native Windows environment.
     15   
     16    Config.guess will show *-cygwin* as the build type.
     17   
     18    Requires no command line help when configuring. Configure is run in a
     19    cygwin shell.
     20
     21 3) Cygwin, but built with the -mno-cygwin flag.  Still uses GCC compilers,
     22    but avoids using anything that needs cygwin.dll.  The resulting binaries
     23    will run in the native Windows environment.
     24   
     25    Config.guess will show *-cygwin* as the build type.
     26   
     27    Specified with the --enable-doscompile=mingw command line flag when
     28    configuring.  Configure is run in a cygwin shell.
     29
     30 4) Cygwin, but Coin configuration will assume Microsoft cl/link used for
     31    compilation and linking.  The resulting binaries will run in the native
     32    Windows environment.  No free Fortran compiler, but you can try Andreas'
     33    compile_f2c.
     34
     35    Config.guess will show *-cygwin* as the build type.
     36   
     37    Specified with the --enable-doscompile=msvc command line flag when
     38    configuring.  Configure is run in a cygwin shell.  The user is responsible
     39    for making sure that PATH is properly set to include the relevant MSVS
     40    directories.
     41
     42 5) MinGW, a sort of minimalist cygwin.  I know it exists, but I have yet to
     43    try configuring in this environment.  My impression is that you get GCC
     44    plus all the utilities needed for build and configuration.  Autotools?
     45    Extras?
     46
     47    Config.guess will show *-mingw* as the build type.
     48   
     49    Should require no command line help? Configure is run in a mingw shell.
     50
     51 6) Msys, a sort of minimalist MinGW.  Does not include GCC.  Coin
     52    configuration will assume MS cl/link.  Just enough unix support to allow
     53    configure scripts to run.  No autotools.  No free Fortran compiler, but
     54    you can try compile_f2c.  At install, will helpfully ask if you want to
     55    synchronise with an existing mingw (and cygwin?)  installation, which
     56    hopelessly confuses the issue of what's actually available.
     57
     58    Config.guess will show *-mingw* as the build type.
     59   
     60    Now specified with the --enable-doscompile=mingw option.  Previously no
     61    option, but if we decide to support 5), may indeed by necessary.
     62    Configure is run in an msys shell.  The user is responsible for making
     63    sure that PATH is properly set to include the relevant MSVS directories.
     64
     65}}}