Hugin Compiling Windows with SDK - Revision history

Onomou: Change compiling category

2011-07-14T20:45:35Z

Change compiling category

Erik Krause: moved Build Hugin for Windows with SDK to Hugin Compiling Windows with SDK: To fit in naming scheme

2011-07-14T17:33:20Z

moved Build Hugin for Windows with SDK to Hugin Compiling Windows with SDK: To fit in naming scheme

Onomou: Add Compiling category

2011-07-11T19:10:40Z

Add Compiling category

Thomas: /* Get hugin SDK */

2011-01-25T19:45:59Z

‎Get hugin SDK

Thomas: Updated hugin build instructions for Mercurial

2010-06-11T19:48:38Z

Updated hugin build instructions for Mercurial

Thomas: Updated hugin build instructions for Mercurial

2010-06-11T19:45:59Z

Updated hugin build instructions for Mercurial

Arfgab: /* Get Tools */

2010-01-21T15:44:43Z

‎Get Tools

Nick at 03:56, 25 October 2009

2009-10-25T03:56:57Z

Nick at 03:45, 25 October 2009

2009-10-25T03:45:33Z

Nick at 03:28, 25 October 2009

2009-10-25T03:28:12Z

@@ Line 121: / Line 121: @@
 <small>--[[User:Tksharpless|Tksharpless]] 16:42, 23 January 2008 (CET)</small>
 [[Category:Software:Platform:Windows]]
-[[Category:Compiling:Hugin]]
+[[Category:Software:Hugin]]

← Older revision		Revision as of 19:10, 11 July 2011
Line 123:		Line 123:
	[[Category:Software:Hugin]]		[[Category:Software:Hugin]]
	[[Category:Software:Platform:Windows]]		[[Category:Software:Platform:Windows]]
		+	[[Category:Compiling:Hugin]]

← Older revision		Revision as of 19:45, 25 January 2011
Line 30:		Line 30:

	4) download the precompiled [http://hugin.panotools.org/sdk/MSVC/Hugin-SDK-20090509-win32.exe SDK] unpack it into new directory huginbase with winrar or 7zip.		4) download the precompiled [http://hugin.panotools.org/sdk/MSVC/Hugin-SDK-20090509-win32.exe SDK] unpack it into new directory huginbase with winrar or 7zip.
		+
		+	The SDK currently is outdated (January 2011). But for starting to compile Hugin for Windows it is a good start. Start with the provided SDK and see [[Hugin SDK (MSVC 2008)]] for details to get an up-to-date build environment.

	== Build enblend ==		== Build enblend ==

@@ Line 89: / Line 89: @@
 == Updating the hugin build ==
-To update your source tree to to the latest revision, right click on huginbase/hugin in Windows Explorer and select "SVN Update".  Remember to note the revision number.
+To update your source tree to to the latest revision, right click on huginbase/hugin in Windows Explorer and select "TortoiseHg/Synchronize".  Set "Post Pull" drop down box to "Update", then select Pull. This will pull all new changeset from central repository and update your working copy to current default tip.
 Check if there is a new release of the sdk, and if so, download and install it.

@@ Line 64: / Line 64: @@
 == Build hugin ==
-) check out hugin source tree into huginbase.  Make a new folder called hugin inside huginbase. Right click on huginbase/hugin in Windows Explorer, select "SVN Checkout...", enter this source URL, set target directory to "hugin" and click OK.
+) check out hugin source tree into huginbase.  Make a new folder called hugin inside huginbase. Right click on huginbase/hugin in Windows Explorer, select "TortoiseHg, Clone...", enter this source URL, set Destination path to "hugin" and click OK.
-    https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/trunk
+    http://hugin.hg.sourceforge.net:8000/hgroot/hugin/hugin
-The result should be a new directory, huginbase/hugin, containing the source tree.  Write down the reported SVN revision number, you will need it later.
+The result should be a new directory, huginbase/hugin, containing the source tree.
-−
-If you are working with the 2.7 version of the SDK, right-click on the huginbase/hugin folder. In the context menu select TortoiseSVN -> update to revision... and enter the revision number 3478. Make sure the radio button is set on Revision rather than on HEAD revision and click OK.
-) Start the cmake gui (cmakesetup.exe).  To ensure that the environment is set right, run cmakesetup.exe from the VC 2008 command shell (available under the Windows Start Menu) - essential if you have other compilers installed.  You might want to create a desktop shortcut that does this with one click.
+) Start the cmake gui (cmakesetup.exe).
 Set cmake's source code directory to huginbase/hugin and its build directory to huginbase/hugin-build (this will create a new directory for the build).  Click Configure and tell it to use Visual C++ 2008.  Cmake then checks the build tools and if that goes well does the first round of searching for components.  When done it displays a list of configuration variable settings, on a red background.  Click "Show Advanced Values" to display all of them.
-This is when you get to correct anything that needs correcting.  First, set HUGIN_WC_REVISION to the SVN revision number (which should be automatic but currently is not on Windows). And set CMAKE_BUILD_TYPE to "Release".  It is an error to leave HUGIN_WC_REVISION blank, and you will get a warning message later if CMAKE_BUILD_TYPE is "Debug".  Heed it.
+This is when you get to correct anything that needs correcting.
 Next, check that all component pathnames start at huginbase.  Cmake may have found some things installed in standard places on your system; but it should only be using the ones in the sdk.  To correct a pathname, click on it and either type in the right one or click '...' to pop a fileselector.  Look out for values with "_NOT_FOUND" in them; these may indicate problems with your directory names or structure. You will need to set ENBLEND_EXE_DIR to huginbase/enblend-3.1/INSTALLDIR that that was created when you built enblend. Also, you need to set HUGIN_BUILDER and HUGIN_BUILDATE -- this is you name and date of the build that will appear on application splash screen.

← Older revision		Revision as of 15:44, 21 January 2010
Line 24:		Line 24:

	3) install [http://tortoisesvn.net/downloads Tortoise SVN] and [http://bitbucket.org/tortoisehg/stable/downloads/ TortoiseHG] clients -- latest release recommended as the repositories are often upgraded in sync with the clients. If you know what you are doing, you may also want to install [http://bazaar-vcs.org/TortoiseBzr TortoiseBZR]		3) install [http://tortoisesvn.net/downloads Tortoise SVN] and [http://bitbucket.org/tortoisehg/stable/downloads/ TortoiseHG] clients -- latest release recommended as the repositories are often upgraded in sync with the clients. If you know what you are doing, you may also want to install [http://bazaar-vcs.org/TortoiseBzr TortoiseBZR]
		+
		+	3) Obtain [http://www.xmission.com/~nate/glut.html].

	== Get hugin SDK ==		== Get hugin SDK ==

@@ Line 44: / Line 44: @@
 Current list of broken links between enblend and SDK:
 * LCMS required but not part of SDK ->
@@ Line 54: / Line 56: @@
 * SDK provides boost 1.39.0 and enblend expects trunk -> in MSDev in the additional DLL menu, change all paths from boost_trunk to boost_1_39_0 - do the same for enblend and enfuse projects
 * In the enfuse property window -> Linker -> General -> Additional Library Directories, change the path for wxWidgets for the new one. Also change the folder for lcms. Do these 2 actions on the enblend project
-* In the enfuse property window -> Linker -> Input-> Additional Dependencies, change tifflib for wxtiff.lib and remove libxmi.lib. Do the same for enblend
+* In the enfuse property window -> Linker -> Input-> Additional Dependencies, change tifflib for wxtiff.lib. Do the same for enblend

@@ Line 50: / Line 50: @@
 ** inside lcms-1.18 there is a Projects folder. Select the MSVC2008 project. Start it.
 ** in the configuration manager, select to build lcms only. You do not need the other tools (that will raise an error because they don't find some dependencies)
-* SDK comes with wxMSW-2.8.10 but enblend expects versio 2.8.7 -> in MSDev in the additional DLL menu, change all paths to wxMSW-2.8.10 (don't forget, not only the version is different, the folder name is too)
+* SDK comes with wxMSW-2.8.10 but enblend expects versio 2.8.7 -> in MSDev in the additional DLL menu, change all paths to wxMSW-2.8.10 (don't forget, not only the version is different, the folder name is too) - do the same for enblend and enfuse projects
-* SDK provides tiff in wxMSW-2.8.10 while enblend searches in tiff-3.8.2 -> change that include for ..\..\..\wxWidgets-2.8.10\src\tiff
+* SDK provides tiff in wxMSW-2.8.10 while enblend searches in tiff-3.8.2 -> change that include for ..\..\..\wxWidgets-2.8.10\src\tiff - do the same for enblend and enfuse projects
-* SDK provides boost 1.39.0 and enblend expects trunk -> in MSDev in the additional DLL menu, change all paths from boost_trunk to boost_1_39_0
+* SDK provides boost 1.39.0 and enblend expects trunk -> in MSDev in the additional DLL menu, change all paths from boost_trunk to boost_1_39_0 - do the same for enblend and enfuse projects