This document provides some information pertaining to the Windows version of Pure, available from the Pure website in the form of an MSI package. Please note that the Windows version has a custom directory layout which is more in line with standard Windows applications, and will by default be installed in the standard Program Files directory on your system.
Normally, most things should be set up properly after you installed the MSI package, but here are a few things that you should know when running the Windows version:
Optional Bits and Pieces
The Windows package contains all that’s needed to run Pure programs with the interpreter. However, in order to make full use of the batch compiler and the Pure/C interface on Windows, you may need to install some third-party programming tools:
mingw is a full version of the GNU C/C++ compiler for Windows systems. You’ll need this in order to create native executables and libraries with the Pure batch compiler. It is also needed for running the pure-gen utility included in this package, which can be used to create Pure interfaces to C libraries from the corresponding C headers. And, last but not least you can also use mingw to compile the LLVM tools and the Pure interpreter yourself, if you prefer that.
Using mingw 4.4 or later is recommended. There’s an installer available at the mingw website, see http://www.mingw.org/wiki/Getting_Started for details. You’ll want to install both the C/C++ compilers and the MSYS environment. You’ll also have to modify the PATH environment variable so that it points to the directory containing the mingw binaries, usually c:\mingw\bin.
In order to use the C/C++ code inlining feature of the Pure interpreter, you’ll also need an LLVM-enabled C/C++ compiler, i.e., clang. This Pure release has been built and tested with LLVM 3.5, so this is the version of clang that you should get. Windows binaries for clang 3.5 can be found on the LLVM download page:
Finally, the Pure program directory needs to be added to the gcc LIBRARY_PATH environment variable, so that some Windows-specific addon libraries are found when linking compiled programs. This should be done automatically during installation, but it’s a good idea to check the value of LIBRARY_PATH after installation and edit it as needed.