Compiling on Windows with MSVC 2010

From Avogadro - Free cross-platform molecule editor
Revision as of 04:55, 21 April 2011 by Tim (talk | contribs)
Jump to: navigation, search

These instructions are to allow users to build Avogadro from the very latest code. Be aware that Avogadro may fail to build or work properly at any given time when built from the instructions below.

Compiling Avogadro for Windows is a complex task and it is recommended that you download the pre-made installer found on the download page. For the adventurous, here are Windows Visual Studio 2010 instructions that may or may not work. For various steps in the process, there may be downloadable binaries on the web. However, for completeness we build all dependencies.

There are also instructions for Linux and Mac OS X available.

DebugView

DebugView is a small program that allows you to view qDebug() output.

Windows Visual Studio 2010 (Express)

NOTE: The redistributable manifest and the version Avogadro compile against do not match. This means that the redistributable's manifest must be altered in order to successfully use the redistributable DLLs. Go to "C:\Program Files\Microsoft Visual Studio 9.0\VC\redist\x86\Microsoft.VC90.CRT" and edit the file called "Microsoft.VC90.CRT.manifest". I used the version string, 

version="9.0.21022.8"

After I changed that then the DLLs were successfully loaded and the mysterious error message stopped popping up. This was with the standard "free" version downloaded in January 2009.

Dependencies

Required:

CMake (>=2.6.0)
Qt4 (>=4.4.0)
Eigen
OpenBabel

For optional OpenGL shader support:

GLEW

For the optional Python console/bindings:

PyQt4
SIP
Boost libraries (tested with >=1.36.0, older versions likely work fine)
Boost

Building Qt4 (required)

The instructions below are based on Qt4 with Visual Studio. Extract and build Qt4 in the C:\src\qt-<version> directory (e.g. C:\src\qt-4.7.2 for version 4.7.2).

Compiling Qt takes some time and can require +10GB free disk space. Below are some options to run configure.exe that reduce compile time and disk space requirements. 

-release or -debug : default is -debug-and-release which takes more disk spcace.
Unused (by Avogadro) Qt components:
-no-webkit
-no-phonon
-no-phonon-backend
-no-qt3support

A full compile & installation could look like (in command prompt): 

cd c:\src\qt-4.7.2
configure.exe -opensource -no-webkit -release 
...
Do you accept the terms of the license?
y
nmake
nmake install
  • Add C:\src\qt-4.7.2\lib to your PATH. (Control Panel->System->Advanced Tab->Environment Variables)
  • Make sure qmake.exe is somewhere in your PATH (needed to build PyQt)

Building Eigen (required)

Download Eigen 2 here. There is no need to build Eigen since it's a template library consisting of headers only. We simply extract the files to C:\src\eigen-2.0.15. You should now have the Eigen headers in C:\src\eigen-2.0.15\Eigen

Building OpenBabel (required)

zlib 1.2.5

cd c:\src\zlib-1.2.5
mkdir build
cd build
del ..\zconf.h
cmake -DCMAKE_BUILD_TYPE=Release ..
nmake
copy zconf.h ..

The zlib library files are now in C:\src\zlib-1.2.5\build. The zlib.h header file is in C:\src\zlib-1.2.5.

libxml2 2.7.7 (recommended, MSVC 2010)

cd c:\src\libxml2-2.7.7\win32
cscript configure.js compiler=msvc prefix=c:\src\libxml2 iconv=no zlib=yes include=c:\src\zlib-1.2.5 lib=c:\src\zlib-1.2.5\build
  • Edit Makefile.msvc
    • line 75: remove /OPT:NOWIN98
    • line 94: change "zdll.lib" to "zlib.lib"
  • In command prompt again: 
nmake /f Makefile.msvc
nmake /f Makefile.msvc install

boost libraries (recommended)

Although boost is an optional dependency for OpenBabel, it is recommended to compile with boost. OpenBabel only needs headers from the boost libraries and extracting the source package to C:\src is enough for now. If you intend to build Avogadro with python support you need build boost python later (see below).

Running cmake

Download openbabel 2.3.0 if you haven't already and extract it to C:\src

Using the Visual Studio 2010 Command Prompt

Since we are using cmake 2.6, the installed boost libraries will be found automatically. If you downloaded the boost source, make sure to also set Boost_INCLUDE_DIR. OpenBabel only uses headers from boost, there is no need to compile any boost libraries before building OpenBabel. 

cd c:\openbabel
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release -DZLIB_INCLUDE_DIR=c:\src\zlib-1.2.5 -DZLIB_LIBRARY=c:\src\zlib-1.2.5\build\zlib.lib
-DLIBXML2_INCLUDE_DIR=c:\src\libxml2\include -DLIBXML2_LIBRARIES=c:\src\libxml2\lib\libxml2.lib 
-DLIBRARY_OUPUT_PATH=c:\src\openbabel -DEXECUTABLE_OUPUT_PATH=c:\src\openbabel -G "NMake Makefiles" ..
nmake
copy include\openbabel\babelconfig.h ..\include\openbabel

You should now have the library files in C:\src\openbabel. The include path is C:\src\openbabel-2.3.0\include.

Building Avogadro

For a minimal build (no python & GLSL shaders), you can now proceed to build Avogadro. If you want python and/or GLSL shader support, build these dependencies first and come back to this step later.

Download Avogadro trunk or a stable version and uncompress it to the C:\src\avogadro directory.

  • Edit the scripts\cmake-msvc2010.bat file to make sure all paths are correct.
  • Open the Visual Studio 2010 Command Prompt.
cd C:\src\avogadro
mkdir build
cd build
..\scripts\cmake-msvc2010.bat
nmake

Running Avogadro & Building the Installer

The easiest way to run avogadro is to build a binary zip file or NSIS installer.

If you have set the CPACK_BINARY_ZIP or CPACK_BINARY_NSIS variable when running cmake (see scripts/cmake-msvc2008.bat), all you have to do is:

  • In command prompt:
nmake PACKAGE

If there are any errors, check the cmake/modules/AvoCPack.cmake file in the avogadro directory and ensure that all paths are correct.

This will generate a zip file or .exe installer in your build dir. Simply extract or install and run avogadro.exe.

GLSL Shader Support (Optional)

Python Support (Optional)

Building Python

  • Python 2.6.2: http://www.python.org/ftp/python/2.6.2/Python-2.6.2.tar.bz2
    • Extract to C:\src
    • Open c:\src\Python-2.6.2\PCbuild\pcbuild.sln (note: when using VC++ 2008 express, you'll get an error message saying "solution folders" aren't supported. You can safely ignore this.)
    • Select Release
    • Build (F7)
    • You now have the files in the PCBuild directory
    • Copy the exe, lib, dll & pyd files to c:\src\Python-2.6.2\libs
    • Copy C:\src\Python-2.6.2\PC\pyconfig.h to C:\src\Python-2.6.2\Include

Some targets (7 for 2.6.2) fail because they need additional libraries (encryption, sqlite3, ...). This is not a problem since we don't use these parts.

Building Boost.Python

using python
  : 2.6
  : C:/src/Python-2.6.2/libs/python # cmd
  : C:/src/Python-2.6.2/Include     # include
  : C:/src/Python-2.6.2/libs ;      # libraries

In command promt: 

cd C:\src\boost_1_38_0
mkdir build
bjam --build-dir="build" --toolset=msvc --with-python stage

You now have the following files in $BOOST_ROOT/stage/lib: 

boost_python-vc90-mt.lib               185kB
boost_python-vc90-mt-1_38.dll          210kB
boost_python-vc90-mt-1_38.lib          185kB  # same as 1
libboost_python-vc90-mt.lib            5173kB 
libboost_python-vc90-mt-1_38.lib       5173kB # same as 4

Copy the files above to $BOOST_ROOT/lib, the CPack script expects to find them there

Building SIP

In command prompt: 

cd c:\src\sip-4.7.9
C:\src\Python-2.6.2\libs\python.exe configure.py
nmake

You now have these files: 

C:\src\sip-4.7.9\sipconfig.py
C:\src\sip-4.7.9\siplib\sip.h
C:\src\sip-4.7.9\siplib\sip.pyd
C:\src\sip-4.7.9\siplib\sip.pyd.manifest
C:\src\sip-4.7.9\sipgen\sip.exe
C:\src\sip-4.7.9\sipgen\sip.exe.manifest
  • Copy sipconfig.py, sip.pyd and sip.pyd.manifest to C:\src\Python-2.6.2\lib\site-packages\
  • Copy file sip.h to C:\src\Python-2.6.2\Include
  • Copy files sip.exe and sip.exe.manifest to C:\src\Python-2.6.2

Notes:

  • sip.exe[.manifest] is only needed to build PyQt4, no need to include it in the installer
  • sip.h is also needed to build Avogadro

Building PyQt4

Assumes Qt is in C:\Qt\4.4.3, change this if needed...

In command prompt: 

cd C:\src\PyQt-win-gpl-4.4.4
mkdir release
copy C:\Qt\4.4.3\lib\QtCore4.dll release\QtCore4.dll
C:\src\Python-2.6.2\libs\python.exe configure.py
nmake

You now have the .pyd files and their manifests in the Qt* dirs: 

C:\src\PyQt-win-gpl-4.4.4\Qt\Qt.pyd(.manifest)
C:\src\PyQt-win-gpl-4.4.4\QtCore\QtCore.pyd(.manifest)
C:\src\PyQt-win-gpl-4.4.4\QtGui\QtGui.pyd(.manifest)
C:\src\PyQt-win-gpl-4.4.4\QtOpenGL\QtOpenGL.pyd(.manifest)
...

You can leave the files there, the CPack script will include them in the package.

Building numpy

In command prompt: 

cd c:\src\numpy-1.3.0
c:\src\Python-2.6.2\libs\python.exe setup.py install

This will install numpy to the C:/src/Python-2.6.2/lib/site-packages directory

numpy/arrayobject.h is in C:/src/Python-2.6.2/lib/site-packages/numpy/core/include (You'll need this to build Avogadro)

Retrieved from "http://avogadro.cc/w/index.php?title=Compiling_on_Windows_with_MSVC_2010&oldid=3133"