cyclus/core — Issue #13: Windows Build Instructions
Author: rwcarlsen
Created: 2012-02-03 19:25:34+00:00
State: open

Target Date :
ASAP

Feature Description :
Our instructions for getting and building Cyclus are very unix/linux centric. As our first potential developers on Windows platforms are trickling in, it has become clear that we need detailed instructions (STEP-BY-STEP) for getting and building Cyclus on a windows machine. This will require stepping through the entire process on a windows machine (or two).

Subtasks :
Describe tasks that are necessary for this feature to be implemented. If
there is an associated issue describing the subtask, report it as a related
issue below.

1. Step through the process of getting and building Cyclus on a windows machine (or two)
2. If there are build system fixes that will simplify the process, APPLY THOSE FIXES
3. Record each step of the process, and update the GettingAndBuildingCyclus wiki page
4. Suggest GUIs and tools that work well for GUI-oriented developers (TortoiseSVN, the CMake GUI, etc.)

Comment 2 by project member katyhuff, Nov 22, 2011
Update....

As this documentation is written, it is worth noting that windows makes every step of this process more difficult.

- SVN,, CMake hdf5, boost, and libxml all must be downloaded and put in a reasonable place.
- Clarifying the locations of these libraries within CMake's configuration script is made necessary and occaisionally complicated since windows OBEYS NO FILE HIERARCHY CONVENTION FOR LIBRARY PLACEMENT. Include directories full of header files might have been put anywhere by the user.
- command prompt instructions will not work for individuals avoiding the command line.
- Users of Visual Studio will have compiler errors that are not seen in the gnu or intel compilers.
- Some linking issues caused by windows incompatibility with dlfcn.h have been fixed by revision 483. . . probably.
Labels: OpSys-Windows

Comment 6 by project member uwgonuke, Jan 11, 2012
Cygwin only for Release 0.1