Hugin SDK (MSVC 2008) - Revision history

Onomou: Add Compiling category

2011-07-16T23:30:06Z

Add Compiling category

Thomas: tclap

2011-03-06T19:47:38Z

tclap

Thomas: Added tclap

2011-03-06T19:43:20Z

Added tclap

Thomas: /* Diff Files */

2011-01-25T19:37:56Z

‎Diff Files

Thomas: /* Prerequisites */

2010-11-08T20:06:19Z

‎Prerequisites

Davidefa at 14:59, 6 November 2010

2010-11-06T14:59:56Z

Davidefa at 14:58, 6 November 2010

2010-11-06T14:58:36Z

Thomas: /* Boost */

2010-11-06T12:01:35Z

‎Boost

Thomas: /* Boost */

2010-10-10T09:12:52Z

‎Boost

Helser: spelling

2010-06-29T14:16:35Z

spelling

← Older revision		Revision as of 23:30, 16 July 2011
Line 1,004:		Line 1,004:

	[[Category:Software:Hugin]]		[[Category:Software:Hugin]]
		+	[[Category:Software:Hugin:Compiling]]
	[[Category:Software:Platform:Windows]]		[[Category:Software:Platform:Windows]]

← Older revision		Revision as of 19:47, 6 March 2011
Line 988:		Line 988:

	(All other files in this directory can be deleted to save space.)		(All other files in this directory can be deleted to save space.)
		+
		+	=== Templatized C++ Command Line Parser Library (tclap) ===
		+
		+	<ol>
		+	<li>Decompress the file <tt>tclap-1.2.0.tar.gz</tt> to directory <tt><SDKHOME>\tclap-1.2.0</tt></li>
		+	</ol>
		+
		+	'''Result'''
		+
		+	The include files reside in
		+	<tt><SDKHOME>\tclap-1.2.0\include\tclap</tt>

@@ Line 154: / Line 154: @@
 | style="padding:5px; text-align:left" | <tt>make_3.81</tt>
 | style="padding:5px; text-align:left" | GNU make 3.81 (http://www.gnu.org/software/make/) <br/>[http://ftp.gnu.org/pub/gnu/make/make-3.81.tar.gz <tt>make-3.81.tar.gz</tt>] <br/> This package replaces UnxUtils.
 |}

@@ Line 160: / Line 160: @@
 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 http://sourceforge.net/tracker/?func=detail&aid=2789320&group_id=77506&atid=550443]
+The download link for the patches is [https://bugs.launchpad.net/hugin/+bug/679695/+attachment/1741338/+files/hugin_patches.zip https://bugs.launchpad.net/hugin/+bug/679695/+attachment/1741338/+files/hugin_patches.zip]
 In order to apply a patch, you will first have needed to follow directions for the [[#UnxUtils|UnxUtils]] step. You cannot apply any patches before that step. To apply a patch, follow these directions:

@@ Line 42: / Line 42: @@
 | style="padding:5px; text-align:left" | Java SE Development Kit 6 Update 13
 | style="padding:5px; text-align:left" | Java Development Kit (JDK)<br/>Visit [http://java.sun.com/javase/downloads/index.jsp Download page]
 |}

@@ Line 498: / Line 498: @@
 </pre>
-Since September 2010 Hugin requieres also the boost libraries regex, filesystem, iostream, system and signals, since November 2010 also the boost library signals. If you want to compile this version you need to compile Boost lib with
+Since September 2010 Hugin requieres also the boost libraries regex, filesystem, iostream and system, since November 2010 also the boost library signals. If you want to compile this version you need to compile Boost lib with
 <pre>
 bjam --with-date_time --with-thread --with-regex --with-filesystem --with-iostreams --with-system --with-signals toolset=msvc variant=debug variant=release link=static threading=multi runtime-link=static stage

@@ Line 497: / Line 497: @@
 d:\usr\src\SDK\boost_1_39_0>
 </pre>
 | style="padding:5px; text-align:left" | <pre>
 bjam --with-date_time --with-thread toolset=msvc variant=debug variant=release link=static threading=multi runtime-link=static address-model=64 stage

@@ Line 1: / Line 1: @@
-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 Developmant Kit (SDK). This article gives step-by-step instructions to build such SDK for Hugin using Microsoft Visual C++ 2008 (MSVC 2008) Express Edition and precompiled dependencies.
+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 gives step-by-step instructions to build such SDK for Hugin using Microsoft Visual C++ 2008 (MSVC 2008) Express Edition and precompiled dependencies.
-While this article is designed for developing a native 32-bit version, adidtional instructions are provided so that a 64-bit version of the Hugin SDK can be compiled. 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.
+While this article is designed for developing a native 32-bit version, additional instructions are provided so that a 64-bit version of the Hugin SDK can be compiled. 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 walkthrough and annotated on the end of each section.
+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 Subversion (SVN) 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.