Difference between revisions of "Install (MSVC)"

From Open Babel
Jump to: navigation, search
(Revise instructions based on my recent experience)
m (Correcting version number)
Line 23: Line 23:
 
=== Compiling wxWidgets ===
 
=== Compiling wxWidgets ===
  
To compile the Windows GUI, you will need to install and compile [http://www.wxwidgets.org/ wxWidgets]. We are currently using [http://downloads.sourceforge.net/wxwindows/wxWidgets-2.8.3.zip wxWidgets 2.6.1]. To compile it...
+
To compile the Windows GUI, you will need to install and compile [http://www.wxwidgets.org/ wxWidgets]. We are currently using [http://downloads.sourceforge.net/wxwindows/wxWidgets-2.8.3.zip wxWidgets 2.8.3]. To compile it...
 
* Unzip it into a folder that doesn't contain spaces
 
* Unzip it into a folder that doesn't contain spaces
 
* Read the install notes in the distribution
 
* Read the install notes in the distribution

Revision as of 22:51, 7 May 2007

Here we describe how to compile OpenBabel on Windows using the Microsoft Visual C++ compiler (MSVC). We recommend the following compiler which is available for free:

Microsoft would prefer you use the .NET framework, but they also support "native" code - it's just that they don't make it too easy.

You also need to install the Platform SDK to provide the Windows files. Don't be put off because it is called "Microsoft Platform SDK for Windows Server 2003 R2" Follow the instructions in [1]. At Step 4 when updating the corewin_express.vsprops file, the list of libraries should be "kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comctl32.lib rpcrt4.lib". Also just before this add a section:

  <Tool
    Name="VCCLCompilerTool" 
    PreprocessorDefinitions=
    "_CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE;_CRT_SECURE_CPP_OVERLOAD_STANDARD_NAMES"
  />

This (usually) avoids warnings about unsafe functions like sprintf for which Microsoft have provided "safe" alternatives. Read a critique of these here. They are not usable in cross-platform code because they are non-standard. Ignore any such warnings that have failed to be supressed.

At Step 5 the line numbers now seem to be pp478-481.

At this stage you should be able to compile the command-line version of OpenBabel. (Open openbabel.sln and build the project OBComLn. OpenBabelDLL.dll, which contains most of OpenBabel is built first.)

Compiling wxWidgets

To compile the Windows GUI, you will need to install and compile wxWidgets. We are currently using wxWidgets 2.8.3. To compile it...

  • Unzip it into a folder that doesn't contain spaces
  • Read the install notes in the distribution
  • Read more install notes on the web site
  • Set the environment variable WXWIN to the installation directory of wxWidgets, e.g. E:\wxWidgets-2.8.3, and restart MSVC.
  • In the file$(WXWIN)/include/wx/msw/setup.h change
#define wxUSE_STD_IOSTREAM  0

to

#define wxUSE_STD_IOSTREAM  1
  • In the file $(WXWIN)/include/wx/msw/wx.rc find the section "Manifest file for Windows XP" and add immediately after it:
//For Visual Studio 2005
#define wxUSE_NO_MANIFEST 1
#if defined(__WXMSW__) && !defined(__WXWINCE__)
#pragma comment(linker, "\"/manifestdependency:type='Win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='X86' publicKeyToken='6595b64144ccf1df'\"")
#endif
//

This ensures that the latest version of Common Controls is used.

  • Open "build\msw\wx.dsw" and answer "Yes to All" for the format conversion. (There is no need to save the converted project files.)
  • On the menu, choose "Batch Build", and sort by "Configuration". Select only those configurations of type "Release" and, possibly "Debug", and click on Build All.

The GUI can be built by opening openbabel.sln and building the project OBGUII.