Difference between revisions of "Hugin SDK (MSVC 2010)"
(→Enblend and Enfuse: update to 4.0, brief Cmake notes.) |
(→wxWidgets: formatting) |
||
Line 374: | Line 374: | ||
</pre> | </pre> | ||
</li> | </li> | ||
− | <li>Enter each of the following two commands without any line break and press the Return key | + | <li>Enter each of the following two commands without any line break and press the Return key<br/> |
− | + | ||
− | + | 32-Bit Directions | |
− | + | <pre> | |
− | |||
− | |||
− | |||
nmake -f makefile.vc BUILD=debug UNICODE=1 SHARED=0 USE_OPENGL=1 RUNTIME_LIBS=static | nmake -f makefile.vc BUILD=debug UNICODE=1 SHARED=0 USE_OPENGL=1 RUNTIME_LIBS=static | ||
nmake -f makefile.vc BUILD=release UNICODE=1 SHARED=0 USE_OPENGL=1 RUNTIME_LIBS=static | nmake -f makefile.vc BUILD=release UNICODE=1 SHARED=0 USE_OPENGL=1 RUNTIME_LIBS=static | ||
</pre> | </pre> | ||
− | + | ||
+ | 64-Bit Directions | ||
+ | <pre> | ||
nmake -f makefile.vc BUILD=debug TARGET_CPU=AMD64 UNICODE=1 SHARED=0 USE_OPENGL=1 RUNTIME_LIBS=static | nmake -f makefile.vc BUILD=debug TARGET_CPU=AMD64 UNICODE=1 SHARED=0 USE_OPENGL=1 RUNTIME_LIBS=static | ||
nmake -f makefile.vc BUILD=release TARGET_CPU=AMD64 UNICODE=1 SHARED=0 USE_OPENGL=1 RUNTIME_LIBS=static | nmake -f makefile.vc BUILD=release TARGET_CPU=AMD64 UNICODE=1 SHARED=0 USE_OPENGL=1 RUNTIME_LIBS=static | ||
</pre> | </pre> | ||
− | |||
</li> | </li> | ||
<li>Close the Windows SDK command prompt window</li> | <li>Close the Windows SDK command prompt window</li> |
Revision as of 04:00, 8 July 2010
Hugin depends on different components like libraries and tools, which are not available on a common Windows system. All these components can be combined to a Hugin Software Development Kit (SDK). This article will eventually give step-by-step instructions to build such SDK for Hugin using Microsoft Visual C++ 2010 (MSVC 2010) Express Edition and precompiled dependencies.
Note: Work in Progress: The SDK, Hugin and enblend have all been built successfully with MSVC 2010 Express, on Windows 7 x64 Professional, as of July 6, 2010. However, the instructions below are probably not complete, and may be specific to Windows 7. This article has been copied wholesale from Hugin SDK (MSVC 2008), and has been updated as the steps were successfully completed.
This article will construct native 32-bit and 64-bit versions. When appropriate, steps that only apply to the 32-bit or 64-bit versions will be noted as (32-bit) or (64-bit), and you can safely ignore them if you are not targeting that particular version. In order to compile a 64-bit version of the Hugin SDK, one does not need a 64-bit computer. However, if they wish to test or debug the binaries, or for some projects (such as OpenEXR) which execute compiled binaries as part of their build step, this will not necessarily be possible on Win32.
First of all an overview is given over the contents of the SDK and the tools that are necessary to build the SDK.
The build steps for each component are written like a walk-through and annotated on the end of each section.
Maybe some of the described tools and packages, especially those fetched from Mercurial (Hg) repository, will change over time and/or become obsolete. Hence it is likely that some steps will become invalid or won't work any more.
The SDK is structured so that each component resides in its own subdirectory. This approach is different to other platforms like Linux, where some common directories are available to store include files, libraries and applications. The files of a component are spread over all these directories. Both approaches to structure the files in a file system have its assets and drawbacks.
The base directory of the SDK is denoted as <SDKHOME> in this article. Replace <SDKHOME> by directory name where you store the SDK on your system. In the examples <SDKHOME> is replaced by the directory name D:\usr\src\SDK.
Prerequisites
To build the SDK some tools are required that are listed in the table below. Download the tools and install them. The destination directory of each tool is arbitrary. If you are uncertain, choose the default given in the setup dialog of each tool.
Tool | Description |
---|---|
Microsoft Visual C++ 2010 Express Edition | Compiler, Debugger and IDE Visit Download page If compiling for 64-bit, you will need to download the SDK, listed next. |
(x64 Only) Microsoft Windows SDK for Windows 7 and .NET Framework 4 | x64 Compiler, Libraries, and Headers Visit [1] When installing, make sure to include the Visual C++ compilers for x64 (under Developer Tools) and the Header Files and x64 libraries (under Windows Headers and Libraries). Optionally consider installing all of the SDK, as it makes compiling generally easier. |
CMake 2.8.1 (2010-04-05) | Generator of solution and project files for MSVC 2010 Visit Download page or download cmake-2.8.1-win32-x86.exe Leave default 'Don't add Cmake to system path' Follow the note on the download page to replace CMakeVS10FindMake.cmake |
(skip) TortoiseSVN 1.6.1.16129 (2009-02-13) | (skip) Tool to handle source codes in Subversion repositories Visit Download page or download TortoiseSVN-1.6.1.16129-win32-svn-1.6.1.msi (32-bit) or TortoiseSVN-1.6.1.16129-x64-svn-1.6.1.msi (64-bit) |
TortoiseHg 1.0.4 (2010-06-11) | Tool to handle source codes in Mercurial repositories Visit Download page Choose x64 if appropriate for you. |
7-Zip 4.65 (2009-02-03) | Tool to decompress the source packages Visit Download page or download 7z465.exe (32-bit) or 7z465-x64.msi (64-bit) |
(skip - not required for Enblend 4.0) Java SE Development Kit 6 Update 20 | (skip) Java Development Kit (JDK) Visit Download page |
Contents of the Hugin SDK
Precompiled Version (32-bit only)
This is what we are working towards: For those who want to avoid to build the whole SDK from scratch, the last available precompiled SDK is for MSVC 2008, for an older version of Hugin.
Precompiled Hugin SDK (Win32) |
---|
Hugin-SDK-20090509-win32.exe (76 MiB, 2009-05-09) |
Building from Source
The contents of the Hugin SDK is shown in the following table. Download the packages, except the packages fetched from Hg/Subversion repository.
Directory | Description (Website) Download package (Date of the package) | ||||
---|---|---|---|---|---|
autopano-sift-C | Autopano-SIFT-C (http://hugin.sourceforge.net/) Subversion repository https://hugin.svn.sourceforge.net/svnroot/hugin/autopano-sift-C/trunk from Hugin_Compiling_Ubuntu(Note January 2010 / May 2010: Currently the autopano-sift-C SVN trunk, as well as Hg default tip, is unstable, use the 2.5.1 release tarball instead) | ||||
boost_1_43_0 | Boost C++ libraries 1.43.0
(http://www.boost.org/) | ||||
Deploy OpenEXR |
OpenEXR library 1.6.1 and IlmBase libraries 1.0.1 (http://www.openexr.com/) ilmbase-1.0.1.tar.gz (2007-10-22) openexr-1.6.1.tar.gz (2007-10-22) | ||||
enblend-enfuse-4.0 | Enblend 4.0 and Enfuse 4.0 (http://enblend.sourceforge.net/)
| ||||
exiftool | ExifTool 8.23 (http://www.sno.phy.queensu.ca/~phil/exiftool) exiftool-8.23.zip (2010-06-20) | ||||
exiv2-0.20.0 | Exiv2 C++ library 0.20 (http://www.exiv2.org/) exiv2-0.20.tar.gz (2010-05-30) | ||||
expat-2.0.1 | Expat XML Parser library 2.0.1 (http://sourceforge.net/projects/expat/) expat-2.0.1.tar.gz (2007-06-05) | ||||
gettext | GNU gettext 0.13.1 and iconv library 1.9.1 (http://www.gnu.org/)
| ||||
glew | OpenGL Extension Wrangler Library (GLEW) 1.5.1 (http://glew.sourceforge.net/) glew-1.5.1-src.zip (2008-11-03) | ||||
libpano\pano13 | Panorama Tools and pano13 library (http://panotools.sourceforge.net/) Release tar.gz, or Subversion repository https://panotools.svn.sourceforge.net/svnroot/panotools/trunk/libpano | ||||
libxml2-2.7.3 | XML C parser and toolkit (http://www.xmlsoft.org/) libxml2-sources-2.7.3.tar.gz (2009-01-18) | ||||
UnxUtils | (skip if you have cygwin) GNU utilities ported to win32 platform (http://sourceforge.net/projects/unxutils/) UnxUtils.zip (2007-03-01) | ||||
wxWidgets-2.8.11 | wxWidgets cross-platform GUI C++ framework 2.8.11 (http://www.wxwidgets.org/) wxMSW-2.8.11.zip (2009-03-17) | ||||
freeglut_2.6.0 | Freeglut (http://freeglut.sourceforge.net/index.php) freeglut-2.6.0.tar.gz | ||||
make_3.81 | GNU make 3.81 (http://www.gnu.org/software/make/) make-3.81.tar.gz This package replaces UnxUtils inside hugin. | ||||
Additional files only necessary for building a 64-bit SDK | |||||
Directory | Description (Website) Download package (Date of the package) | ||||
(64-bit Enblend only) libxmi-1.2-1 | GNU libxmi 2-D rasterization library (Win32 port) (http://gnuwin32.sourceforge.net) libxmi-1.2-1-src.zip (2004-04-16) | ||||
(64-bit Enblend only) STLport-5.2.1 | STLport Standard Library (http://stlport.sourceforge.net/) STLport-5.2.1.tar.gz (2008-12-10) | ||||
(64-bit Enblend only) lcms-1.18a | LittleCms Color management library (http://www.littlecms.com) lcms-1.18a.zip (2009-04-19) 2.0 has been released, but will require code updates to enblend. |
In the following subsections each component is discussed in detail. The order of the subsections seems random, but I describe the precompiled packages first, followed by the big packages, where some of the small packages depend on.
The decompress step of each component contains seemingly inconsistent namings of destination directories. These were chosen mostly to satisfy Cmake. To check the right locations, each result section of every component's description contains a summary of the expected files.
freeglut and gnu make were added after the 2009 SDK was constructed.
Diff Files
In order to make compilation simple, a series of patch files are included below that contain all the necessary changes, not only to compile the SDK, but to optionally compile an x64 version of the SDK. When directed, you will need to apply the patch file specified. If you are compiling for x64, there may be additional patches you need to apply.
The download link for the patches is http://sourceforge.net/tracker/?func=detail&aid=2789320&group_id=77506&atid=550443
In order to apply a patch, you will first have needed to follow directions for the UnxUtils step. You cannot apply any patches before that step.
Alternative: If you already have the Cygwin environment installed, you can install the 'patch' module and perform the patch commands at a cygwin prompt. Otherwise, UnxUtils is much simpler. However, cygwin patch seems to set the permissions of changed files so they can't be modified by normal users, so after patching do this:
Right-click the folder, Properties, Security tab, Advanced, Change Permissions, check Replace all child object perms...., click OK, OK, OK.
To apply a patch, follow these directions:
- Start a Command Prompt by choosing Start -> Run and typing in "cmd.exe"
- On the Command Prompt, change directory to <SDKHOME>
ExampleC:\Program Files\Microsoft\Windows SDK\v7.1>d: D:>cd \usr\src\SDK D:\usr\src\SDK>
- On the command prompt, enter the following commands without any line breaks and press the Return/Enter key, substituting <SDKHOME> where appropriate:
set PATH=%PATH%;<SDKHOME>\UnxUtils\usr\local\wbin
- On the command prompt, enter the following commands without any line breaks and press the Return/Enter key, substituting <PATCHFILE> with the name of the patch file to apply:
patch -p 0 -i <PATCHFILE>
NOTE: On Vista and later systems, the filename "patch.exe" is a protected file name which will always result in a UAC prompt if the file does not include a manifest (which UnxUtils version does not). This can be worked around by copying the file <SDKHOME>\UnxUtils\usr\local\wbin\patch.exe to another file not containing the name, such as <SDKHOME>\UnxUtils\usr\local\wbin\apply_diff.exe. Then substitute the command 'patch' in the above command with 'apply_diff'
Result
If everything worked, you should see a list of filenames that were patched. Example
D:\usr\src\SDK>patch -p 0 -i libiconv-1.9.1.diff patching file 'libiconv-1.9.1/srclib/error.c' D:\usr\src\SDK>
If there was an error, you may wish to consult the Hugin SDK (MSVC 2008) Patches page for instructions on what changes were contained in the patch.
UnxUtils
- Create the directory <SDKHOME>\UnxUtils
- Decompress the file UnxUtils.zip to created directory <SDKHOME>\UnxUtils
Result
The applications reside in <SDKHOME>\UnxUtils\bin and <SDKHOME>\UnxUtils\usr\local\wbin
ExifTool
- Create the directory <SDKHOME>\exiftool
- Decompress the file exiftool-8.23.zip to <SDKHOME>\exiftool
- Rename the file exiftool(-k).exe to exiftool.exe
Result
The application resides in <SDKHOME>\exiftool
GetText
Binary only, 32-bit binaries work for a 64-bit build.
- Create the directory <SDKHOME>\gettext
- Decompress the following files to created directory <SDKHOME>\gettext
- gettext-runtime-0.13.1.bin.woe32.zip
- gettext-tools-0.13.1.bin.woe32.zip
- libiconv-1.9.1.bin.woe32.zip
Result
The applications reside in <SDKHOME>\gettext\bin
The include files reside in <SDKHOME>\gettext\include
The libraries (unused) reside in <SDKHOME>\gettext\lib
STLport (64-bit Enblend Only)
- Decompress the file STLport-5.2.1.tar.gz to directory <SDKHOME>
- Open a Windows SDK prompt by choosing Start -> Programs -> Microsoft Windows SDK v7.1 -> Windows SDK v7.1 Cmd Prompt
- On the command prompt, enter the following command without any line breaks and press the Return/Enter key:
setenv /Release /x64 /xp
It should now refresh and say
Setting SDK environment relative to <path where you installed the SDK> Targeting Windows XP x64 RELEASE
- On the command prompt, change directory to <SDKHOME>\STLport-5.2.1
ExampleC:\Program Files\Microsoft\Windows SDK\v6.1>d: D:>cd \usr\src\SDK\STLport-5.2.1 D:\usr\src\SDK\STLport-5.2.1>
- On the command prompt, enter the following commands without any line breaks and press the Return/Enter key:
configure msvc9 --with-static-rtl cd build/lib nmake clean install
- Compilation will fail, complaining about
stlport\stl/_cstdlib.h(158) : error C2084: function '__int64 abs(__int64)' already has a body
Comment that line out, and compile again. It should succeed. - Close the Windows SDK command prompt window
Result
The includes reside in <SDKHOME>\STLport-5.2.1\stlport
The libraries reside in <SDKHOME>\STLport-5.2.1\lib
lcms-1.18 (64-bit Enblend Only)
- Decompress the file lcms-1.18a.tar.gz to directory <SDKHOME>
- Apply the lcms-1.18.diff patch
- Open the file <SDKHOME>\lcms-1.18\Projects\VC2008\lcms.sln. Allow conversion.
- Select project lcms, right-click Properties
- Select "Release" in the Solution Configuration pull-down menu. Select "x64" in the Solution Platform pull-down menu
- Select project lcms in Solution Explorer, and then choose Build > Project Only > Build Only lcms
- changes to output file and intermediate directory for x64
- Close Visual Studio C++ 2010 Express
Result
The library resides in <SDKHOME>\lcms-1.18\Lib\MS-x64
Note |
---|
During build process temporary object files are stored in following directories
Both directories may be deleted to save disk space. |
libxmi-1.2.1 (64-bit Enblend Only)
- Open the file libxmi-1.2-1.src.zip in 7-Zip
- Open the "src" folder by double-clicking
- Open the "libxmi" folder by double-clicking
- Open the "1.2" folder by double-clicking
- Extract "libxmi-1.2" to the directory <SDKHOME>
- Apply the libxmi-1.2.diff patch
- Open libxmi.vcproj. Allow conversion.
- Set default Output/Intermediate options for x64
- Build libxmi, x64 Debug and Release
Result
The libxmi-1.2 sources now reside in <SDKHOME>\libxmi-1.2 The libxmi-1.2 libs now reside in <SDKHOME>\libxmi-1.2\x64\Debug or Release
wxWidgets
- Decompress the file wxMSW-2.8.11.zip to directory <SDKHOME>
- Rename the directory <SDKHOME>\wxMSW-2.8.11 to <SDKHOME>\wxWidgets-2.8.11
- Apply the wxWidgets-2.8.11.diff patch Hugin SDK (MSVC 2008) Patches#wxWidgets
-
32-Bit Directions 64-Bit Directions To open a Visual Studio command prompt choose Start > Programs > Microsoft Visual Studio 2010 Express Edition > Visual Studio Command Prompt (2010) - Open a Windows SDK prompt by choosing Start -> Programs -> Microsoft Windows SDK v1.1 -> Windows SDK 7.1 Command Prompt
- On the command prompt, enter the following command without any line breaks and press the Return/Enter key:
setenv /Release /x64 /xp
It should now refresh and say
Setting SDK environment relative to <path where you installed the SDK> Targeting Windows XP x64 Release
- On command prompt change directory to <SDKHOME>\wxWidgets-2.8.11\build\msw
ExampleC:\Program Files\Microsoft Visual Studio 10.0\VC>d: D:\>cd \usr\src\SDK\wxWidgets-2.8.11\build\msw D:\usr\src\SDK\wxWidgets-2.8.11\build\msw>
- Enter each of the following two commands without any line break and press the Return key
32-Bit Directionsnmake -f makefile.vc BUILD=debug UNICODE=1 SHARED=0 USE_OPENGL=1 RUNTIME_LIBS=static nmake -f makefile.vc BUILD=release UNICODE=1 SHARED=0 USE_OPENGL=1 RUNTIME_LIBS=static
64-Bit Directions
nmake -f makefile.vc BUILD=debug TARGET_CPU=AMD64 UNICODE=1 SHARED=0 USE_OPENGL=1 RUNTIME_LIBS=static nmake -f makefile.vc BUILD=release TARGET_CPU=AMD64 UNICODE=1 SHARED=0 USE_OPENGL=1 RUNTIME_LIBS=static
- Close the Windows SDK command prompt window
Result
The include files reside in <SDKHOME>\wxWidgets-2.8.11\include and its subdirectories
Hugin also depends on following files
- <SDKHOME>\wxWidgets-2.8.11\src\jpg\*.h
- <SDKHOME>\wxWidgets-2.8.11\src\jpg\jconfig.vc
- <SDKHOME>\wxWidgets-2.8.11\src\png\*.h
- <SDKHOME>\wxWidgets-2.8.11\src\tiff\*.h
- <SDKHOME>\wxWidgets-2.8.11\src\zlib\*.h
The libraries reside in <SDKHOME>\wxWidgets-2.8.11\lib\vc_lib and/or <SDKHOME>wxWidgets-2.8.11\lib\vc_amd64_lib
Note | ||||
---|---|---|---|---|
During build process temporary object files are stored in following directories
Both directories may be deleted to save disk space. |
Boost
- Decompress the file boost_1_43_0.7z to directory <SDKHOME>
- (skip) Decompress the file boost-jam-3.1.17-1-ntx86.zip to an arbitrary directory and copy the application bjam.exe to <SDKHOME>\boost_1_39_0
- Open a Visual Studio command prompt, like you did with wxWidgets
- On command prompt change directory to <SDKHOME>\boost_1_43_0
ExampleC:\Dokuments and Settings\Guido>d: D:\>cd \usr\src\SDK\boost_1_43_0 D:\usr\src\SDK\boost_1_43_0>
- Enter the command 'bootstrap' to build bjam.exe
- Enter the following command without line breaks and press Return key
32-Bit Directions 64-Bit Directions bjam --with-date_time --with-thread toolset=msvc variant=debug variant=release link=static threading=multi runtime-link=static stage
After bjam.exe finishes a statement like the following should be printed in the command prompt window
...updated 56 targets... d:\usr\src\SDK\boost_1_43_0>
bjam --with-date_time --with-thread toolset=msvc variant=debug variant=release link=static threading=multi runtime-link=static address-model=64 stage
After bjam.exe finishes a statement like the following should be printed in the command prompt window
...updated 44 targets...
- To build both 32-bit and 64-bit directions, rename boost_1_43_0\stage\lib directory to lib_win32 after building 32-bit, and to lib_x64 after building the 64-bit targets
- Close the Windows command prompt window
Result
The include files reside in <SDKHOME>\boost_1_43_0 and its subdirectory boost
The libraries reside in <SDKHOME>\boost_1_39_0\stage\lib (or lib_win32 and lib_x64)
Notes |
---|
|
OpenEXR
OpenEXR depends on following SDK component:
- wxWidgets
Prepare this component before OpenEXR.
- Create the directory <SDKHOME>\OpenEXR
- Decompress the file ilmbase-1.0.1.tar.gz to created directory <SDKHOME>\OpenEXR
- Decompress the file openexr-1.6.1.tar.gz to the same directory <SDKHOME>\OpenEXR
After decompress there should only exist the two directories ilmbase-1.0.1 and openexr-1.6.1 in <SDKHOME>\OpenEXR - Apply the OpenEXR.diff patch Hugin SDK (MSVC 2008) Patches#OpenEXR
- Open solution file <SDKHOME>\OpenEXR\ilmbase-1.0.1\vc\vc8\IlmBase\IlmBase.sln
- Allow conversion to proceed. TODO is Batch Build better?
- Select Debug in Solutions Configuration pull-down menu, and then choose Build > Build Solution
- Select Release in Solutions Configuration pull-down menu, and then choose Build > Build Solution
- TODO is 64-bit needed? Change General .. Platform Toolset to Win 7.1 SDK for all x64 projects.
- Open solution file <SDKHOME>\OpenEXR\openexr-1.6.1\vc\vc8\OpenEXR\OpenEXR.sln
- Choose Build > Batch Build
- Select Build for Project IlmImf with Solution Config
32-Bit 64-Bit Solution Config: "Debug" with Platform: "Win32"
Solution Config: "Release" with Platform: "Win32"
Solution Config: "Debug" with Platform: "x64"
Solution Config: "Release" with Platform: "x64"
- Click Build
- Close Visual C++ 2010 Express
Result
The include files reside in <SDKHOME>\Deploy\include
The libraries reside in <SDKHOME>\Deploy\lib\Debug and <SDKHOME>\Deploy\lib\Release for win32, <SDKHOME>\Deploy\lib\x64\Debug and <SDKHOME>\Deploy\lib\x64\Release for x64.
Enblend and Enfuse
32-Bit Directions | 64-Bit Directions |
---|---|
|
Enblend & Enfuse depend on the following SDK components:
Prepare these components before Enblend & Enfuse.
|
Result
The applications reside in <SDKHOME>\enblend-enfuse-4.0 for 32-bit,
or <SDKHOME>\enblend-build-x64 for 64-bit.
Expat
- Decompress the file expat-2.0.1.tar.gz to directory <SDKHOME>
- Apply the expat-2.0.1.diff patch Hugin SDK (MSVC 2008) Patches#expat
- Open the file <SDKHOME>\expat-2.0.1\Source\expat.sln
- Right-click expat_static, and choose Properties
- Under Configuration Properties, General, change Output Dir to .\..\$(Platform)\bin\$(Configuration)\
- Change Intermediate Dir to .\..\$(Platform)\tmp\$(Configuration)_static\
- Change Target Name to libexpatMT
- Configuration Properties, Librarian, Output File, change Output File to inherit from parent or project defaults
- Configuration Properties, C++, Output File, change ASM List Location, Output File Name, and Program DB File Name to inherit from parent or project defaults
- Choose Build > Batch Build
- Select Build for Project expat_static with
32-Bit 64-Bit Solution Config: "Debug" with Platform: "Win32"
Solution Config: "Release" with Platform: "Win32"
Solution Config: "Debug" with Platform: "x64"
Solution Config: "Release" with Platform: "x64"
- Click Build
- Close Visual C++ 2010 Express
Result
The include files reside in <SDKHOME>\expat-2.0.1\lib
The libraries reside in
<SDKHOME>\expat-2.0.1\win32\bin\Debug and
<SDKHOME>\expat-2.0.1\win32\bin\Release
<SDKHOME>\expat-2.0.1\x64\bin\Debug and
<SDKHOME>\expat-2.0.1\x64\bin\Release
Exiv2
Exiv2 depends on following SDK components:
- wxWidgets
- GetText
- Expat
Prepare these components before Exiv2.
- Decompress the file exiv2-0.20.tar.gz to directory <SDKHOME>
- Apply the exiv2-0.20.diff patch Hugin SDK (MSVC 2008) Patches#exiv2
- (64-bit Only)Apply the exiv2-0.20.x64.diff patch
- Open solution file <SDKHOME>\exiv2-0.20\msvc\exiv2.sln
- In the Solution Explorer, select "exiv2lib"
- Right-click exiv2lib, and choose Properties, select All Configurations, and All Platforms
- Under Configuration Properties, General, change Output Dir and Intermediate Dir to inherit from parent or project defaults
- Change Target Name to exiv2
- Configuration Properties, C++, General, change Treat Warnings as Errors to No
- Configuration Properties, Librarian, Output File, change Output File to inherit from parent or project defaults
- Right-click exiv2lib, and choose Properties, select All Configurations, and All Platforms
- Under Configuration Properties, General, change Output Dir and Intermediate Dir to inherit from parent or project defaults
- Choose Build > Batch Build
- Select Build for Project exiv2lib with
32-Bit 64-Bit Solution Config: "Debug" with Platform: "Win32"
Solution Config: "Release" with Platform: "Win32"
Solution Config: "Debug" with Platform: "x64"
Solution Config: "Release" with Platform: "x64"
- Click Build
- Close Visual C++ 2010 Express
- Create the directory <SDKHOME>\exiv2-0.20\msvc\lib
- Copy the following files to this directory and rename them as specified in Destination column.
Source Destination <SDKHOME>\exiv2-0.20\msvc\bin\Debug\exiv2.lib <SDKHOME>\exiv2-0.20\msvc\lib\exiv2d.lib <SDKHOME>\exiv2-0.20\msvc\bin\Release\exiv2.lib <SDKHOME>\exiv2-0.20\msvc\lib\exiv2.lib <SDKHOME>\expat-2.0.1\win32\bin\Debug\libexpatMT.lib <SDKHOME>\exiv2-0.20\msvc\lib\libexpatd.lib <SDKHOME>\expat-2.0.1\win32\bin\Release\libexpatMT.lib <SDKHOME>\exiv2-0.20\msvc\lib\libexpat.lib - Similar for msvc\lib\x64\
Comment
When using exiv2 0.19 (which works better with bigger files), copy and rename also the following files:
Source | Destination |
---|---|
<SDKHOME>\exiv2-0.19\msvc\xmpsdk\Debug\xmpsdk.lib | <SDKHOME>\exiv2-0.19\msvc\lib\xmpsdkd.lib |
<SDKHOME>\exiv2-0.19\msvc\xmpsdk\Release\xmpsdk.lib | <SDKHOME>\exiv2-0.19\msvc\lib\xmpsdk.lib |
Similar for msvc\lib\x64\
Result
The include files reside in <SDKHOME>\exiv2-0.20\msvc\include
The libraries reside in <SDKHOME>\exiv2-0.20\msvc\lib and lib\x64
GLEW
- Decompress the file glew-1.5.1-src.zip to directory <SDKHOME>
- Apply the glew.diff patch Hugin SDK (MSVC 2008) Patches#glew
- Open the file <SDKHOME>\glew\build\vc6\glew.sln
- Let the conversion wizard run.
- (64-bit) For the glew_static project, right-click Properties, for each x64 configuration, change:
- Configuration Properties, General, Intermediate Dir, change .\static/debug\ to .\static\$(Platform)\debug\
- Configuration Properties, Librarian, Output File, change ../../lib/glew32sd.lib to ../../lib/glew64sd.lib and change Target Machine to X64
- Configuration Properties, C++, Output File, change ASM List Location, Output File Name, and Program DB File Name to inherit from parent or project defaults
- Choose Build > Batch Build
- Select Build for Project glew_static with Solution Config
32-Bit 64-Bit Solution Config: "Debug" with Platform: "Win32"
Solution Config: "Release" with Platform: "Win32"
Solution Config: "Debug" with Platform: "x64"
Solution Config: "Release" with Platform: "x64"
- Click Build
- Close Visual C++ 2010 Express
Result
The include files reside in <SDKHOME>\glew\include
The libraries reside in <SDKHOME>\glew\lib
Note |
---|
The GLEW include files are typically included by a statement like #include "GL/glew.h" Therefore the base directory of the GLEW include files is <SDKHOME>\glew\include |
Panorama Tools
Panorama Tools depends on following SDK component:
- wxWidgets
Prepare this component before Panoroma Tools.
- Set two windows environment variables:
- Set variable WXWIDGETS_HOME to wxWidgets base folder <SDKHOME>\wxWidgets-2.8.11
- Alternative: fix the LocalDefs.vsprops file next to the .sln file to point to wxWidgets base folder <SDKHOME>\wxWidgets-2.8.11
- (skip) Set variable JDK_HOME to Java SE Development Kit's destination directory name. This directory name was shown during the setup, e.g. C:\Program Files\Java\jdk1.6.0_13
To take effect on changes of environment variables you may have to logout and login.
- Create the directory <SDKHOME>\libpano\pano13
- In explorer right-click on created directory <SDKHOME>\libpano\pano13 , and then choose SVN Checkout from the shortcut menu. The Checkout dialog appears.
- In "URL of repository" field enter following address:
https://panotools.svn.sourceforge.net/svnroot/panotools/trunk/libpano
- Click OK
- After checkout has finished click OK
- Apply the libpano.diff patch Hugin SDK (MSVC 2008) Patches#Panorama Tools
- Open solution file <SDKHOME>\libpano\pano13\libpano.sln
- Select all projects, then right-click and choose Properties, select All Configurations, and All Platforms
- Under Configuration Properties, General, change Output Dir and Intermediate Dir to $(Configuration)\$(Platform)\
- Select your platform in the Solution Platform pull-down menu
- Select "Debug LIB CMD" in Solution Configuration pull-down menu
- Select project pano13 in Solution Explorer, and then choose Build > Project Only > Build Only pano13
- Select "Release LIB CMD" in Solution Configuration pull-down menu, and then choose Build > Build Solution
- Close Visual C++ 2010 Express
Result
The applications reside in <SDKHOME>\libpano\pano13\tools\Release CMD\Win32 or x64
The include files reside in <SDKHOME>\libpano\pano13
The libraries reside in <SDKHOME>\libpano\pano13\Debug CMD\Win32 or x64 and <SDKHOME>\libpano\pano13\Release CMD\Win32 or x64
Note |
---|
The applications have to be built in release version only. Therefore only pano13 library has to be built in Debug configuration. |
libxml2
- Decompress the file libxml2-sources-2.7.3.tar.gz to directory <SDKHOME>
-
32-Bit Directions 64-Bit Directions - To open a Visual Studio command prompt choose Start > Programs > Microsoft Visual C++ 2008 Express Edition > Visual Studio Tools > Visual Studio 2008 Command Prompt
- Open a Windows SDK prompt by choosing Start -> Programs -> Microsoft Windows SDK v6.1 -> CMD Shell
- On the command prompt, enter the following command without any line breaks and press the Return/Enter key:
setenv /Release /x64 /xp
It should now refresh and say
Setting SDK environment relative to <path where you installed the SDK> Targeting Windows XP x64 RELEASE
- On command prompt change directory to <SDKHOME>\libxml2-2.7.3\win32
ExampleSetting environment for using Microsoft Visual Studio 2008 x86 tools. C:\Program Files\Microsoft Visual Studio 9.0\VC>d: D:\>cd \usr\src\SDK\libxml2-2.7.3\win32 D:\usr\src\SDK\libxml2-2.7.3\win32>
- Enter each of the following two commands without any line break and press the Return key.
cscript configure.js ftp=no http=no iconv=no cruntime=/MT nmake -f makefile.msvc libxmla
Result
The include files reside in <SDKHOME>\libxml2-2.7.3\include
The libraries reside in <SDKHOME>\libxml2-2.7.3\win32\bin.msvc
Notes |
---|
|
autopano-sift-C
Autopano-SIFT-C depends on following SDK components:
- libxml2
- Panorama Tool's pano13 library
- wxWidgets
Prepare these components before Autopano-SIFT-C.
- Create the directory <SDKHOME>\autopano-sift-C-trunk
- In explorer right-click on created directory <SDKHOME>\autopano-sift-C-trunk, and then choose SVN Checkout from the shortcut menu. The Checkout dialog appears.
- In "URL of repository" field enter following address:
https://hugin.svn.sourceforge.net/svnroot/hugin/autopano-sift-C/trunk
- Click OK
- After checkout has finished click OK
- Start CMake (cmake-gui). The CMake dialog appears.
- In "Where is the source code" field enter
<SDKHOME>\autopano-sift-C-trunk
Alternatively click Browse Source to point to this directory - In "Where to build the binaries" field enter
<SDKHOME>\autopano-sift-C
- Click Configure
If a dialog appears, which asks to create the build directoy, click Yes.
A dialog appears, where you can specify the generator for the project. -
32-Bit Directions 64-Bit Directions Select "Visual Studio 9 2008" and select option "Use default native compilers" Select "Visual Studio 9 2008 Win64" and select option "Use default native compilers" - Click Finish
In the Name and Value list the entries are shown with red background. - Click Configure
- Click Generate
- Close CMake
- Open solution file <SDKHOME>\autopano-sift-C\autopano-sift-C.sln
- Select Release in Solution Configuration pull-down menu, and then choose Build > Build Solution
- Select project INSTALL in Solution Explorer, and then choose Build > Project Only > Build Only INSTALL
- Close Visual C++ 2008 Express Edition
- Copy the directories bin and shared from <SDKHOME>\autopano-sift-C\INSTALL\FILES to <SDKHOME>\autopano-sift-C
Result
The applications reside in <SDKHOME>\autopano-sift-C\bin
The manual pages reside in <SDKHOME>\autopano-sift-C\shared
Note |
---|
To save disk space you may delete all files and directories in <SDKHOME>\autopano-sift-C, except the subdirectories bin and shared. |
Freeglut
- Decompress the file freeglut-2.6.0.tar.gz to directory <SDKHOME>
- Open the file <SDKHOME>\freeglut-2.6.0\VisualStudio2008Static\freeglut.sln
- Select "Debug" in the Solution Configuration pull-down menu.
- Select project freeglut in Solution Explorer, and then choose Build > Project Only > Build Only freeglut
- Select "Release" in the Solution Configuration pull-down menu.
- Select project freeglut in Solution Explorer, and then choose Build > Project Only > Build Only freeglut
- Close Visual Studio C++ 2010 Express
Result
The library resides in <SDKHOME>\freeglut-2.6.0\VisualStudio2008Static\Debug and <SDKHOME>\freeglut-2.6.0\VisualStudio2008Static\Release
GNU Make
- Decompress the file make-3.81.tar.gz to directory <SDKHOME>
- Open the file <SDKHOME>\make-3.81\make_msvc_net2003.sln (Confirm conversion.)
- Select "Release" in the Solution Configuration pull-down menu.
- Select project make_msvc.net2003 Solution Explorer, and then choose Build > Project
- Close Visual Studio C++ 2010 Express
- Rename the file <SDKHOME>\make-3.81\Release\make_msvc.net2003.exe to <SDKHOME>\make-3.81\Release\make.exe
Result
The executable make.exe resides in <SDKHOME>\make-3.81\Release\
(All other files in this directory can be deleted to save space.)
--Created: Aron Helser 16:20, 29 June 2010 (UTC)