Dear all,

I prepared a SDK based on following components ...

Contents of the hugin SDK [2009-02-09]

/boost_1_37_0 [http://www.boost.org/]
      boost libraries date-time and threads
/Deploy [http://www.openexr.com/]
      OpenEXR libraries ilmbase 1.0.1 + openexr 1.6.1
/exiftool [http://www.sno.phy.queensu.ca/~phil/exiftool]
      [pre-build] ExifTool 7.67
/exiv2-0.18 [http://www.exiv2.org/][http://sourceforge.net/projects/expat/]
      Exiv2 0.18 + Expat 2.0.1
/gettext [http://ftp.gnu.org/gnu/]
      [pre-build] gettext runtime 0.13.1 + gettext tools 0.13.1 + 
libiconv 1.9.1
/glew
       glew library 1.5.1
/libpano 
[https://panotools.svn.sourceforge.net/svnroot/panotools/trunk/libpano]
      libpano SVN 944
/UnxUtils [http://sourceforge.net/projects/unxutils/]
      [pre-build] UnxUtils
/wxWidgets-2.8.9 [http://www.wxwidgets.org/]
      wxWidgets 2.8.9

Some of the components are pre-build versions that are already built by 
their responsible developers. All other libs were built based on the 
current released version. The only exception is libpano (panotools), 
which was built from current SVN version 944.

Therefore this SDK is a snapshot of the tools and libs that hugin needs 
to be build. Some of them may change over time.

Sure, this is only a snapshot, but I guess that some windows developers 
will find it helpful. You approach, Yuv, seems to be more sophisticated, 
i.e. to establish a build environment that is flexible over time and can 
be rolled back due to usage of configuration management. It is good for 
the "core-crew", but maybe a little bit oversized for the guys and/or 
girls that want to play with hugin and to get their first steps ...

At that time I was very pleased to find a small SDK package as a good 
starting point. Hopefully a small honey pod to get more developers :-)

Ok, let's start with this package a new round of windows builds.

Some questions have to be answered:

Q: Where can I download the SDK?
A: http://hugin.panotools.org/testing/hugin/Hugin_SDK-20090209.exe

Q: How to install the SDK?
A: Execute the file and enter a directory to store the SDK files, e.g. 
C:\src. This directory is called <src> in the next answer.

Q: How to build hugin?
A: You can get the latest hugin source code from subversion repository
https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/trunk
1) Create folder <src>\hugin
2) Select the folder, right-click > SVN Checkout...
4) In entry <URL of repository> enter 
https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/trunk
5) Select HEAD revision
6) Press OK
7) Start cmake
8) In entry <Where is the source code> enter: <src>\hugin
9) In entry <Where to build the binaries> enter: <src>\hugin_build
Note: It is recommended to build the project in another folder then the 
source code resides in. Applying this procedure the source and build 
files are not mixed in one folder stucture.
10) Press Configure
11) In combo box <Build For> select "Visual Studio 9 2008"
12) Press OK
Note: CMake searches for several components to build the solution files. 
If some required components are not found, CMake throws error messages 
and marks the missing components in red color in the list. The following 
error message comes up:
CMake Error at platforms/windows/installer/CMakeLists.txt:6 (MESSAGE):
Need to set builder (HUGIN_BUILDER) manually
Confirm the dialogs with OK
In the list of cached values select the currently empty value of 
property HUGIN_BUILDER
Enter you name.
Press Configure button.The following error message comes up:
CMake Error at platforms/windows/installer/CMakeLists.txt:13 (MESSAGE):
Need to set build date (HUGIN_BUILDDATE) manuallyConfirm the dialogs with OK
In the list of cached values select the currently empty value of 
property HUGIN_BUILDDATE
Enter the current date in format YYYY-MM-DD
Press Configure button
14) Press OK
15) Open the generated Visual Studio solution file 
<src>\hugin_build\hugin.sln
16) Select Build > Configuration Manager
17) Choose Release in Active solution configuration and confirm with Close
18) Select Build > Build Solution
Note: The build process may take some time ...
19) Right-click on project INSTALL, select Build

The files are stored in <src>\hugin_build\INSTALL\FILES
The application in sub-directory bin

Have fun. Feedback is welcome.

Guido

Yuval Levy schrieb:
> Hi Guido,
> 
> Guido Kohlmeyer wrote:
>> I prepared a SDK to build hugin on windows platform.
> 
> great. I'd be interested to know if you can open network files with 
> Hugin compiled with your SDK, to understand if it is a problem of my SDK.
> 
>> It is based on 
>> current releases of boost, wxwindows, libpano and other tools.
> 
> current as in SVN/CVS, or current as in latest releases?
> 
> my approach is to use svn:externals properties to "suck in" the latest 
> dependencies. It takes a full day to build boost on my 3GHz dual core 
> AMD box, but eventually, when all bits and pieces are in place, I will 
> commit it to SVN so that people will download their SDK from SVN. It 
> will give us the ability to easily maintain references to different SDKs 
> (e.g. against different versions of wxWidgets and other external 
> dependencies) and to "quickly" (will need some optimizations to compile 
> only those parts of boost that are needed by Hugin) test if a regression 
> is due to a dependency or to a change in the Hugin code. Also it should 
> make it possible for people who are using non-latin language to have 
> their own SDK-branch with support for the appropriate toolchain.
> 
> 
>> The other point is web-space. Any suggestions, where I can upload the 
>> package?
> 
> Thomas Rauscher has kindly given some space on panotools.org. I suggest 
> using that. I think Harrie uses it for the OSX builds and has the 
> credentials to access it.
> 
> Yuv
> 
> > 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

Reply via email to