Installing the required software on Windows

  1. Python tools: The majority of the Python dependencies are already included in the repository (pcty/MglToolsLibWin/pyCompilePkgs). However, it should be noted, that since these are bundled within the MglToolsLibWin package, access to them will not be provided until you run Continuity at least one time since Continuity needs to unzip and move the package to the proper destination. However, manually unzipping the package and putting it into pcty/MglToolsLibWin will also work. The only Python related things not included in the repository are Python 2.7 and pyWin32, both of which get installed by the released version of Continuity. So, either download the most recent version of Continuity, and then uninstall Continuity (Python and pyWin32 will remain). Or download them from:

  2. TortoiseSVN

  3. Windows SDK

  4. Microsoft Visual C++:

    Supposedly you can also use the linker provided with Microsoft Visual C++ Professional, although we have not tested this.
  5. SWIG

  6. A Text Editor: It would be a good idea to download a text editor to allow you to view/edit the python source files should you need to. While any editor will do, some examples are : SciTE or Komodo Edit

  7. Intel Visual Fortran: You will need Intel Visual Fortran Compiler for Windows to compile Continuity.

    • Version 10: This is the one we currently use. During installation, if there is a message about "Visual Studio not found", and you actually have installed one of the Visual C++ version listed above, you can ignore the message.
    • Version 8-9: We have used this in the past and it has worked too. It will first extract the setup files onto the hard drive, and then it will open a web page. Click the link "Install Intel® Visual Fortran Compiler" at the top right of this page to start the installer. If you are using the Visual C++ toolkit instead of Visual Studio, choose the option to "Continue installing" when it says command line support will not work. You should turn on the option "Automatically define Intel Fortran environment variables."
    • g95: I have not been able to get g95 to work on Windows either, although we use it for both Mac and Linux. If you do decide to try it this way, make sure to include --with-g95 when you run configure.