Re: [hugin-ptx] hugin Einführung bei Frankfurt am M ain gesucht

[Guido Kohlmeyer]

Leider wohne ich in NRW, knappe 2,5 Stunden von Frankfurt entfernt.
Ansonsten gibt es aber recht einfache Einleitungen im Web, z.B. startend
von der Hugin-Homepage.

Guido

> Hallo,
>
> jemand aus der Nähe von Frankfurt am Main hier?
>
> Irgendwie kriege ich den Dreh mit Hugin nicht raus.
> Wer mag mir in einer persönlichen Einführung zeigen wie es geht?
>
> Danke,
> Jan
>
> English:
> Looking for hands-on hugin introduction nearby Frankfurt am Main, Germany.
>
>
> --
> http://www.DIY-streetview.org
>
> --
> 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 hugin-ptx@googlegroups.com
> To unsubscribe from this group, send email to
> hugin-ptx+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/hugin-ptx


-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: [hugin-ptx] Windows SDK + trunk = ?

[Guido Kohlmeyer]

Dear all,

It seems the right way to build hugin as described by Brian.
So far as I know my SDK is outdated since some months, but lacks mainly 
of a missing glut component which can be easily added as described in an 
old post by me.
To build an installation package was not my task for long time. I only 
built the 0.7.0 release package with a patched iss file from repository. 
I suppose there are some other guys around who are more familiar with 
current state of building an installation.

Guido

Am 18.12.09 10:32, schrieb brian_ims:
>
> Oskar,
>
> As I stated I am not a C/C+ programmer, make files cause my eyes to
> glazeover and I don't understand subversion/trunks etc (but I have been
> writing fortran for the best part of 35 years and still am). This was my
> first attempt to build Hugin. I used the precompiled SDK and just followed
> the instructions for building, downloading adding the compiled GLUT as
> described some time ago, picking up the missing GLUT references manually
> when running cmake and also putting glut.dll in the bin folder that is
> produced by visual studio. I also had to rename a couple of the files in the
> enblend folder (eg  readme to readme.txt - I had copied enblend 4 into the
> enblend3.2 folder by mistake some time ago and am not sure now if I had
> overwritten some files or not)
>
> I have no idea how to create installer files
>
> Cheers
>
>
>
> Oskar Sander wrote:
>>
>> Hi Brian,
>>
>> How far off is the SDK for building hugin from trunk? I suppose enblend
>> does
>> not need to be built as described here [1] as there is a released (or RC)
>> 4.0 now, right?
>>
>> [1] http://wiki.panotools.org/Build_Hugin_for_Windows_with_SDK
>>
>> Cheers
>>
>>
>> 2009/12/13 brian_ims
>>
>>>
>>> I am not a C/C+ programmer but have managed to build a windows version
>>> using
>>> SVN 4782 following the SDK and various other pointers given in this forum
>>> and I can confirm that with the introduction of the autocrop button a
>>> previously viewable button has essentially disappeared from my screen. If
>>> Bruno is corrrect the culprit is the 'show control points' button and
>>> presumably this needs shortening
>>>
>>> Cheers
>>>
>>> Brian
>>>
>>>
>>
>> --
>> 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 hugin-ptx@googlegroups.com
>> To unsubscribe from this group, send email to
>> hugin-ptx+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/hugin-ptx
>>
>

-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: [hugin-ptx] [OSX] hugin-mac-2009.4.0-RC3 available for download

[Guido Kohlmeyer]

Dear Tony,

I cannot rate whether you interested in development or simply use hugin. 
The later one can use a pre-compiled version. Personally I cared about 
the windows SDK for hugin for some time and made some bug fixes. To do 
this in the future it is mandatory to build hugin on my machine. I 
suppose this not the common user profile. You can contibute to hugin as 
well by simply testing it with a pre-compiled version.

Guido

Tony schrieb:
> Is there a benefit to building Hugin on my Mac (as opposed to using the 
> pre-compiled version)?
>
> --
> Tony
>
>
>
> On Dec 8, 2009, at 7:18 AM, Guido Kohlmeyer wrote:
>
>   
>> Thanks for the short hints. I'm realy new on that platform but little
>> familiar on linux. Therefore my starting point is a dev tools free snow
>> leopard system, which has to be armed now. I have more free time next
>> week, thus I get back to you and Skip if I run into the pitfalls.
>>
>> Guido
>>
>> 
>>> Hi Guido,
>>>
>>> Yes, it is documented.
>>> The normal "linux like" cmake route is documented here: <
>>> http://wiki.panotools.org/Hugin_Compiling_OSX>
>>> The "complicated" route to build a portable bundle is here:
>>> http://wiki.panotools.org/Build_a_MacOSX_Universal_Hugin_bundle_with_Xcode
>>>
>>> note: If you are on a new Apple I assume you are on Snow Leopard. This
>>> brings some changes to building the bundle. We, that is Skip Gaede,
>>> already
>>> encountered that as he is also on Snow Leopard. We, again that is mostly
>>> skip Gaede, are working to incorporate this in the bundle build.
>>> Even though I can't tell for sure, I assume the cmake build hasn't
>>> changed.
>>>
>>> If you have questions then please let us know.
>>>
>>> Harry
>>>
>>> 2009/12/8 Guido Kohlmeyer 
>>>
>>>   
>>>> Dear Harry,
>>>>
>>>> is it documented somewhere how to build hugin on mac? Meanwhile I own
>>>> one
>>>> and want to test it during my holidays.
>>>>
>>>> Thank,
>>>> Guido
>>>>
>>>> 
>>>>> Hi all,
>>>>>
>>>>> I posted the link to Skips 2009.4.0-RC3 bundle on my
>>>>> website<
>>>>>   
>>>> http://panorama.dyndns.org/index.php?lang=en&subject=Hugin&texttag=Hugin>
>>>> 
>>>>> .
>>>>>
>>>>> I want to give a big *THANK YOU* to Skip. Skip put a lot of effort
>>>>>   
>>>> into
>>>> 
>>>>> this. Not only did he build the bundle, he also improved the build
>>>>>   
>>>> scripts
>>>> 
>>>>> for the underlying libraries Hugin depends on and made them better
>>>>>   
>>>> "cross
>>>> 
>>>>> OSX versions". He did a great job. He also had to face new
>>>>>   
>>>> "challenges"
>>>> 
>>>>> because he builds on Snow Leopard which turns out to be a changed and
>>>>> different build environment (This asked for a few changes after Skips
>>>>> first
>>>>> announcement).
>>>>>
>>>>> Skip also teamed up with Allan Seidel and Robert Campbell and helped
>>>>>   
>>>> them
>>>> 
>>>>> in
>>>>> their learning process to build a bundle as well.
>>>>> Allan built the first bundle yesterday.
>>>>> For me it was also a learning process as questions were asked about
>>>>> certain
>>>>> things I had never thought about (why bother if it works, but
>>>>>   
>>>> sometimes
>>>> it
>>>> 
>>>>> doesn't). And new issues arose as well.
>>>>>
>>>>> Please test the bundle.
>>>>>
>>>>> Kind regards,
>>>>> Harry
>>>>>
>>>>>
>>>>>
>>>>> 2009/12/5 skip 
>>>>>
>>>>>   
>>>>>> Hi Mac users,
>>>>>>
>>>>>> With coaching from Harry, I just built and uploaded the new 32bit
>>>>>> Hugin 2009.4.0-RC3 bundle.
>>>>>>
&g

Re: [hugin-ptx] [OSX] hugin-mac-2009.4.0-RC3 available for download

[Guido Kohlmeyer]

Thanks for the short hints. I'm realy new on that platform but little
familiar on linux. Therefore my starting point is a dev tools free snow
leopard system, which has to be armed now. I have more free time next
week, thus I get back to you and Skip if I run into the pitfalls.

Guido

> Hi Guido,
>
> Yes, it is documented.
> The normal "linux like" cmake route is documented here: <
> http://wiki.panotools.org/Hugin_Compiling_OSX>
> The "complicated" route to build a portable bundle is here:
> http://wiki.panotools.org/Build_a_MacOSX_Universal_Hugin_bundle_with_Xcode
>
> note: If you are on a new Apple I assume you are on Snow Leopard. This
> brings some changes to building the bundle. We, that is Skip Gaede,
> already
> encountered that as he is also on Snow Leopard. We, again that is mostly
> skip Gaede, are working to incorporate this in the bundle build.
> Even though I can't tell for sure, I assume the cmake build hasn't
> changed.
>
> If you have questions then please let us know.
>
> Harry
>
> 2009/12/8 Guido Kohlmeyer 
>
>> Dear Harry,
>>
>> is it documented somewhere how to build hugin on mac? Meanwhile I own
>> one
>> and want to test it during my holidays.
>>
>> Thank,
>> Guido
>>
>> > Hi all,
>> >
>> > I posted the link to Skips 2009.4.0-RC3 bundle on my
>> > website<
>> http://panorama.dyndns.org/index.php?lang=en&subject=Hugin&texttag=Hugin>
>> > .
>> >
>> > I want to give a big *THANK YOU* to Skip. Skip put a lot of effort
>> into
>> > this. Not only did he build the bundle, he also improved the build
>> scripts
>> > for the underlying libraries Hugin depends on and made them better
>> "cross
>> > OSX versions". He did a great job. He also had to face new
>> "challenges"
>> > because he builds on Snow Leopard which turns out to be a changed and
>> > different build environment (This asked for a few changes after Skips
>> > first
>> > announcement).
>> >
>> > Skip also teamed up with Allan Seidel and Robert Campbell and helped
>> them
>> > in
>> > their learning process to build a bundle as well.
>> > Allan built the first bundle yesterday.
>> > For me it was also a learning process as questions were asked about
>> > certain
>> > things I had never thought about (why bother if it works, but
>> sometimes
>> it
>> > doesn't). And new issues arose as well.
>> >
>> > Please test the bundle.
>> >
>> > Kind regards,
>> > Harry
>> >
>> >
>> >
>> > 2009/12/5 skip 
>> >
>> >> Hi Mac users,
>> >>
>> >> With coaching from Harry, I just built and uploaded the new 32bit
>> >> Hugin 2009.4.0-RC3 bundle.
>> >>
>> >> See the Changelog: <http://groups.google.com/group/hugin-ptx/
>> >> browse_thread/thread/e52c5f85f4a9edeb<
>> http://groups.google.com/group/hugin-ptx/%0Abrowse_thread/thread/e52c5f85f4a9edeb
>> >
>> >> >
>> >>
>> >> *Note: This build features the new Autopano generator setup.*
>> >>
>> >> Please test and give feedback.
>> >>
>> >> Information and binaries via Harry's website > >> panorama.dyndns.org/index.php?lang=en&subject=Hugin&texttag=Hugin>.
>> >> (The binaries itself are, as always, served from hugin.panotools.org
>> >> who kindly provide the disk space and bandwidth). Harry should be
>> >> posting a link shortly. Those who wish may download it using this
>> >> direct link: <http://hugin.panotools.org/testing/hugin/hugin-
>> >> mac-2009.4.0-RC3.dmg<
>> http://hugin.panotools.org/testing/hugin/hugin-%0Amac-2009.4.0-RC3.dmg>
>> >> >
>> >>
>> >> Happy testing, skip
>> >>
>> >> --
>> >> 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 hugin-ptx@googlegroups.com
>> >> To unsubscribe from this group, send email to
>> >> hugin-ptx+unsubscr...@googlegroups.com
>> 
>> >
>> >> For more options, visit this group at
>> >> http://groups.google.com/gr

Re: [hugin-ptx] [OSX] hugin-mac-2009.4.0-RC3 available for download

[Guido Kohlmeyer]

Dear Harry,

is it documented somewhere how to build hugin on mac? Meanwhile I own one
and want to test it during my holidays.

Thank,
Guido

> Hi all,
>
> I posted the link to Skips 2009.4.0-RC3 bundle on my
> website
> .
>
> I want to give a big *THANK YOU* to Skip. Skip put a lot of effort into
> this. Not only did he build the bundle, he also improved the build scripts
> for the underlying libraries Hugin depends on and made them better "cross
> OSX versions". He did a great job. He also had to face new "challenges"
> because he builds on Snow Leopard which turns out to be a changed and
> different build environment (This asked for a few changes after Skips
> first
> announcement).
>
> Skip also teamed up with Allan Seidel and Robert Campbell and helped them
> in
> their learning process to build a bundle as well.
> Allan built the first bundle yesterday.
> For me it was also a learning process as questions were asked about
> certain
> things I had never thought about (why bother if it works, but sometimes it
> doesn't). And new issues arose as well.
>
> Please test the bundle.
>
> Kind regards,
> Harry
>
>
>
> 2009/12/5 skip 
>
>> Hi Mac users,
>>
>> With coaching from Harry, I just built and uploaded the new 32bit
>> Hugin 2009.4.0-RC3 bundle.
>>
>> See the Changelog: > browse_thread/thread/e52c5f85f4a9edeb
>> >
>>
>> *Note: This build features the new Autopano generator setup.*
>>
>> Please test and give feedback.
>>
>> Information and binaries via Harry's website > panorama.dyndns.org/index.php?lang=en&subject=Hugin&texttag=Hugin>.
>> (The binaries itself are, as always, served from hugin.panotools.org
>> who kindly provide the disk space and bandwidth). Harry should be
>> posting a link shortly. Those who wish may download it using this
>> direct link: > mac-2009.4.0-RC3.dmg
>> >
>>
>> Happy testing, skip
>>
>> --
>> 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 hugin-ptx@googlegroups.com
>> To unsubscribe from this group, send email to
>> hugin-ptx+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/hugin-ptx
>
> --
> 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 hugin-ptx@googlegroups.com
> To unsubscribe from this group, send email to
> hugin-ptx+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/hugin-ptx


-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Re: Compiling Hugin on Windows using MSVC_2008

[Guido Kohlmeyer]

Dear Bob,

The HUGIN_BUILDER and HUIGIN_BUILDDATE are two variables in CMake files 
that are not set by default. You have to set them manually. This is 
currently not documented on the wiki, because the wiki page is quite 
outdated in this area. I documented the SDK very precise but not did not 
update the build on windows page. Thus set the variables manually in 
CMake GUI and build it. Please do not touch the CMake files in the 
sources. Once set the variables remain in the CMake cache and you can 
recycle them in further builds.

Thank,
Guido

Bob schrieb:
> Hi Guido,
>
> I really very much appreciate your help！
> I pass the compiling error using your glut.txt. Thanks!
> But now I got a new error when the Hugin compiling progress reach 70%
> using CMake , It says
>CMake Error at platforms/windows/installer/CMakeLists.txt:6
> (Message):
>  Need to set builder  (HUGIN_BUIDER) manually
>
> How to overcome this problem?
>
> Thanks again!
>
> Bob
>
> PS: I will settle the solutions I used to overcome these problem into
> a document, and post to the mailing list after I successfully compile
> Hugin.
>
> On 9月12日, 下午2时31分, Guido Kohlmeyer  wrote:
>   
>> Dear Bob,
>>
>> 1.  The current state of the SDK is not valid to compile current SVN
>> versions of hugin, because the package glut is missing in the SDK. The
>> glut component was add to support GPGPU (general purpose computation on
>> graphics processing unit). This library is not in the SDK. There is a
>> discussion in the mailing list how to overcomde this drawback
>> Please find attached a small SDK extension. Simply rename the file
>> glut.txt to glut.zip and extract it to the SDK directory. There should
>> be a directory glut afterwards.
>>
>> 2.  The (my 32bit version) SDK is not intended to compile enblend, but
>> rather to compile hugin. I used a pre-compiled version of enblend.
>> Please try to follow the guidence for 64bit made by Ryan Sleevi. I
>> suppose it is similar to build a 32bit version. I not followed the
>> discussion about building enblend for long time.
>>
>> Guido
>>
>> boo...@gmail.com schrieb:
>>
>>
>>
>> 
>>> Dear Guido,
>>>   
>>> Two problem occured when I Compiled Hugin on Windows following the 
>>> instruction on these there website below:
>>>http://wiki.panotools.org/Hugin_SDK_(MSVC_2008)
>>>http://wiki.panotools.org/Hugin_Compiling_Windows
>>>http://wiki.panotools.org/Hugin_SDK_(MSVC_2008)_Patches
>>>   
>>> 1.When I used CMake 2.6 to generate the hugin.sln,one error occured
>>>CMake Error at CMakeModules/FindGLUT.cmake:77  (MESSAGE):Could not find 
>>> GLUT
>>>   
>>> 2.When I used VS2008 to compile enblend-enfuse-3.2,
>>> a bunch of errors occured when compile the icc34.h (lcms-1.18) included in 
>>> enblen.cc and enfuse.cc
>>>   VS2008 can not recognize these code in icc34.h
>>> .
>>> typedef @UINT8_T@  icUInt8Number;
>>> typedef @UINT16_T@ icUInt16Number;
>>> ...
>>>   But no error occured when I compile lcms using lcms.sln in directory 
>>> lcms-1.18\Projects\VC2008
>>>   
>>> How to solve these two problem?
>>> Or Is there any other way to complie Hugin on Windows?
>>>   
>>> Thanks!!
>>>   
>>> Bob
>>>   
>>
>> [glut.txt182K ]PK  
>>  ZZ ;glut/PK  
>>  ]Z ;   glut/include/PK  
>>  aZ ;glut/include/GL/PKÚ  )÷°'Õ
>> l  glut/include/GL/glut.hÅ=érÛÈÑ¿í*¿ÃÄ[å µ²$ ºâ$_Q$$qÍ«HÊ’ó   # 1 0 
>> h™›|ïžî90 08$Û‰jW"1}OOO÷ ð/ΣgÓGbš w ™KÓ|óú xàx4ñìÍë£}Òñ×ÛÀY,#²7¯‘  |!¿ ’ 
>> Ž»° û€Ô/.Zì÷û}Ê~Ÿ ’ý# ?[:!Y þ"°V >> ”º[b;a 8 ›Èzp)yr¢¥¿‰ˆëÌ© :Þ‚> by6à¼yM ’øêØÔŽa  +°¼ˆRâ äÉ
>> Ä úm Ð0 @xLœÕÚu¨} bH:J”÷ž ½'ŽG¢%%ëÍ p'¶¿² OÊ –"Ü0öžy× 6 5¡ÖuÿvFš‡gÄóŸ h 
>> ÒF>±¾úŽ çîÆF-þòäx¶ÿ  .ÿ†Ì ˆg­(   ×Ö  û.XÜñ½ ò jÝ9^³ñkHþrÝ?Z¸€H ¦G© ’ö¸g 
>> g“ÏÌ0 Ïu·  ¤ˆ¨Ûš î–‹ÿ  é  ¶ì‡' ã  °‰|/$þ#YYóÀ  ½y`­Ñ þ& s—ZÞŽ”’¢`E 
>> 3†Ù7ÚC³=ìš ø€íBwº«9>§nH¥$÷÷÷L î þJªÌp€> HnÜQcµñ™  õ€)[Ì®qÕ  ]  
>> ziÇüdLÈßþJÎ  käßÿV]9 u;í~ߜގǣÉÌè&›ÍËѤ juL3ÕÐïà3ÎE> á£øTÉB^”5 *sÙî|TêÇ" ÌÁäþX @=íÝŸŸ¦Ÿµûã›vúáxÜ©ÕÈ»wäOòá ×í›ãötZÁ8R²rËHÈRËÜXó/ä 
>> F·;Ÿ“¹¿Z;.   éE0zièý ‘p³^ûA Lm:wÃ5 ïÙ®ë¬ðaí€üc FJ Ø·w ; Ú ¡Î ͬFÜ®#ª§I 
>> «ûüÂv Kq f: …ʲN ‚¸-1
>> ²òéÍQjo½Üóh»¦YO4ï:7í‰9S¢  ¶l °/0J…K욧ùÒ
>> ÌèC”Yì_”hüƒœV|œBØäam" Ú‘3‡éã!°‚-Ù„Ö‚¢‹0û $Œ5 ™ýÞ¥9ž´¯ mT CÞ bžt%

[hugin-ptx] Re: Windows Hugin SDK and documentation

[Guido Kohlmeyer]

Hallo Yuv,

Yuval Levy schrieb:
>> 1. Pre-build package to give an easy starting point to build hugin from
>> scratch.
>> 2. Update mechanism to keep up with hugin development branch.
>> 
>
> To be really perfect the updated mechanism should keep up with *any* 
> state of Hugin and match a combination of "branch" and revision number. 
> (I prefer to call it a "codeline" - to branch is for me the action of 
> splitting one codeline from the other).
>   
Sorry, I even thought about the term "branch", cause it is often 
understood as a real branch which is a sideline of the main branch 
(=trunk). I suppose the "trunk" is your "codeline"?
>> 3. Good documentation of the SDK to simplify the maintenance of the SDK. A
>> hand over to another person in charge can be easily done.
>>
>> Requirements 1 and 2 contradict slightly and this is mainly the reason why
>> Yuv and I have different point of view about the SDK. Neither of us is
>> really wrong.
>> 
>
> a. Stable Hugin against stable SDK => public distributed releases
> b. Bleeding edge Hugin against stable SDK => testing snapshots
> c. Bleeding edge Hugin agains bleeding edge SDK => developers feedback
>
> (a) and (c) are the two extremes of the range, while (b) is the middle.
>
> The reason why I am so keen on (c) is because it lays in the future. It 
> gives us early warning when an upstream change affects Hugin. And it 
> gives us the possibility to feed back to them. It's a development and 
> communication tool, the first goal of which would be to help push 
> upstream what is currently in foreign.
>
> And (a) is what I recommend for the general public, to be used in a 
> production environment.
>
> Some users are keen on (b) and that's good too, because this is where we 
> get most bug reports from.
>
>   
Good analyzation of the different flavours of a SDK and hugin build. (a) 
is mandatory for release, (b) is my favour for the majority of users how 
want to build their own version from SVN sources. I even started with 
such version in the past and went a member of this community. It was not 
painful to build. (c) is for the developers that are on the bleeding 
edge.  Maybe some common user wants to taste this flavour too, but we 
have to mark it "use at your own risk" ;-)
>> I thought about an automated SDK builder, like Ryan already mentioned
>> about. Some kind of batch script which loads the packages e.g. using wget,
>> 
>
> The script would have to discern the four categories of packages I 
> described earlier:
> - (F)IX: has not been changing for years and is unlikely to change any 
> time soon (e.g. GetText)
> - (S)TABLE: evolves regularly and is worth updating to the latest 
> stable, but is not critical (e.g. Boost)
> - (D)YNAMIC: evolves continuously and is worth updating continuously 
> (e.g. ExifTool)
> - DE(V): is critical to bleeding edge Hugin functionality, and it is 
> worth following it in between releases when making test builds (e.g. 
> libpano or Enblend and Enfuse)
>
> We'd need three fetching ("loading") mechanisms:
> 1. binaries - preferred for (F),(S),(D) packages when building target 
> (a) *if* the upstream dependency provides binaries that are known to work.
> 2. tarballs - alternative for (F),(S),(D) packages when building target 
> (a) and patches need to be applied. Also preferred for (V) when building 
> target (A)
> 3. repository - alternative if no tarballs are published; or if we need 
> a feature that is in between releases (e.g. Hugin-0.7.0 that needs 
> Enblend-3.2 but there was no Enblend-3.2 at the time of the 0.7.0 
> release). This would also be the preferred way for (V) packages when 
> building target (b); and the preferred way for all packages when 
> building target (c).
>
>   
Yes, I agree that an automatic builder must handle simple download of 
pre-built packages as well as fetching from SVN or whatever repository.
>> The script can be
>> stored in the hugin repository and therefore it will be possible to build
>> past versions of the SDK and hugin as well.
>> 
>
> very good point. One of the problems now is the disconnect. The .iss 
> files for the installer are from the 0.7.0 beta / RC time. There are 
> modified versions around but I don't know where they are nor who has the 
> last ones. They need to be synchronized against the result of the script.
>
> The build script itself (once the SDK is in place) has been already 
> posted here by Ad in the past. I don't know if he has improved on it.
>
> We need to keep all of these scripts and files in sync and a repository 
> is the way to go. This could be a folder in Hugin's SVN repository, or 
> it could be a new repository. I was going to open a Mercurial (Hg) 
> repository in the Hugin project to learn it and understand its features 
> and limitations. Enblend has already migrated to Hg. Maybe it would be 
> an idea to put the Windows SDK + Build work in one such Hg repository?
>
>   
Well, we can divide it in two steps:
1. Build environm

[hugin-ptx] Re: Windows Hugin SDK and documentation

[Guido Kohlmeyer]

Hi,

I retired for some time, cause died machine, but ordered some new, thus
work on SDK can start again in some time.

I'm not happy whith the current SDK. There are some requirements that have
to be fulfilled:
1. Pre-build package to give an easy starting point to build hugin from
scratch.
2. Update mechanism to keep up with hugin development branch.
3. Good documentation of the SDK to simplify the maintenance of the SDK. A
hand over to another person in charge can be easily done.

Requirements 1 and 2 contradict slightly and this is mainly the reason why
Yuv and I have different point of view about the SDK. Neither of us is
really wrong.

I thought about an automated SDK builder, like Ryan already mentioned
about. Some kind of batch script which loads the packages e.g. using wget,
applies the patches and builds the SDK. Simply does all steps which are
documented e.g. on the wiki.
The documentation is mandatory, thus you can read what's going on during
build of the SDK. The batch script (and the patch files) can be downloaded
at the same web page. Some pre-build packages as well. The script can be
stored in the hugin repository and therefore it will be possible to build
past versions of the SDK and hugin as well. Otherwise a good revision
management won't work.

Check of versions and automatic update of SDK packages is possible the
second step.

Some other thoughts?

Guido

>
> Ryan Sleevi wrote:
>> Or we can go the easier route (for end users) that I've been pursuing:
>>
>> An "automatable" that handles it all for you ;-)
>
> makes sense - just make sure that it is documented well enough so that:
> a) a monkey like me can build the automatable from scratch
> b) *when* things evolve and change, a slightly more expert hand can fix it
>
> when I work on the project, I try to make myself redundant by
> documenting what I do and trying to pass on the knowledge to what will
> be our next generation of maintainers long after I'm gone.
>
> 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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: [OSX] Howto build a Hugin bundle on MacOSX

[Guido Kohlmeyer]

> /Off topic: I'm still without mac and after 3½ weeks on Ubuntu linux 
> again (not mentioning my webserver and using it within virtualbox on 
> my mac) I'm still not sure whether I will buy a new Mac. For the 
> absolute ease of use, "connect whatever you want and it works" and 
> great software like the OS itself and iLife: absolutely! The fact that 
> I can buy 2-3 pc laptops for one macbook makes me hesitate. Not for 
> the money itself (I have a nice job with a nice salary), but whether 
> it's worth the money: Why buy an expensive mac if I can do exactly 
> what I want (maybe not exactly how I want it) with a much cheaper 
> laptop. But I'm also still very much tempted so probably I will 
> convince myself that I can't do without./
>
Off topic comment:
I even mourn my dying laptop and thought about buying a MacBook Pro 
although I never used OSX before. I looked for a lightweight solid 
long-run laptop with good display resolution. I found a macbook which 
fulfill nearly all my requirements. I looked for a similar hardware but 
it is not much cheaper. Particular when I take only big manufactures 
into acount. Now that a matt display is available for a 15 inch macbook 
too, I didn't see any drawbacks. Ok, the trackpoint of my thinkpad was 
very ergonomic and I will miss it.

Guido


--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Error while building enblend: GL/glut.h not found

[Guido Kohlmeyer]

Dear Ad,

The windows SDK is currently outdated and not in sync with the cmake 
configuration. I'm on the way to prepare a new SDK. Read the thread " 
The way to 2009.2" and you will find a post from me (2009-08-04) which 
contains the needed components as an attachment.

Guido

Dedalus schrieb:
> Hi, back from holiday, and running my build script again on Windows
> Vista. CMake reports that
> GLUT_INCLUDE_DIR variable needs to be set 
>
> looks like a dependency has been added ... going to check out if there
> was an hugin SDK update.
>
> Ad Huikeshoven
>
> On Aug 11, 9:09 am, Supriyo  wrote:
>   
>> I am trying to install hugin-app on Mac OS-X using ports
>> when I use port install hugin-app, it throws an error while building
>> enblend - "GL/glut.h not found". While doing some search I realised
>> that others have also encountered the same 
>> issue..http://trac.macports.org/ticket/19828
>>
>> Does anyone know how to go around this issue. The other dependencies
>> for hugin-app (e.g. boost, lcms etc ) are successfully installed.
>>
>> Thanks
>> Supriyo
>> 
> >
>   

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: nona-gpu - has anybody got it working?

[Guido Kohlmeyer]

Dear Zoran,

Zoran Zorkic schrieb:
>> Ryan is so far the only one who has reported success, with his
>> self-built version. I wonder if one of the pre-compiled (from Guido or
>> from me) yield the same result. This would exclude building errors.
>>
>> His video card is a GeForce 8800 GTS (256 mb) - anybody else with that
>> same video card who can run nona -g successfully? and other video cards?
> 
> I have a 9800GT which is pretty much the same card (just renamed, love
> the marketing guys :).
> If you can post a 32-bit windows binary, I'd love to test it out.

You can find one here (built by me):
http://hugin.panotools.org/testing/hugin/nona.zip

Another one can be found here (I suppose Yuval has built it)
http://www.photopla.net/hugin/nona_4169.7z

Guido

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: nona-gpu - has anybody got it working?

[Guido Kohlmeyer]

Yuval Levy schrieb:
> Guido Kohlmeyer wrote:
>   
>> I commited an updated CMakeLists.txt file to find GLUT in the SDK.
>> 
>
> Thank you, dear Guido and Ryan.
>
> any update of <http://wiki.panotools.org/Hugin_SDK_(MSVC_2008)> needed?
>   
Yes of course, I have to add the description how to generate the library 
from source package with MSVC 2008 EE. An updated SDK package is 
mandatory too. I wanted to wait until some developers approve the 
functionality of nona based on the static library. Due to the fact that 
my graphic card is too old I cannot do such tests. Based on first 
impressions in this thread it seams that the lib works or other way 
around there are situations where it works thus it is no general broken 
build of nona.
I will update the SDK in few days or hours ...

Guido

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: nona-gpu - has anybody got it working?

[Guido Kohlmeyer]

Dear Ryan,

I commited an updated CMakeLists.txt file to find GLUT in the SDK. Here 
I set only the root search path of GLUT.
In my current working environment I created a base directory "glut" in 
the root of the SDK directory tree. The include file glut.h resides in 
.\glut\include\GL\glut.h which is the default from the sources. The 
library glut32.lib resides in .\glut\Release\glut32.lib which is the 
location where the default FindGLUT from CMake 2.6.4 searches for the 
library.  Thats all on win32 platfrom to work. I used the same sources 
from Nate Robins to build the static GLUT library (see also thread "Re: 
The way to 2009.2").

Guido

Ryan Sleevi schrieb:
> Compiled my own x64 version (using the Glut For Win32 sources -
> http://www.xmission.com/~nate/glut.html ), as I wanted to see if there was
> going to be any headache on Windows. Some wonky macros, but nothing fatal.
> In order to get CMake to find Glut, I had to touch my FindGLUT macro, but I
> imagine that's because of the use of Glut for Win32.
>
> I'll see what other video cards I can scrape up and see how they handle.
>
> Is there some particular set of test data to use? Just threw some simple
> stuff at it, nothing complex, but it all turned out fine.
>
> Test System: Vista x64 (SP2)
> Video Card: GeForce 8800 GTS (256 mb)
> Video BIOS: 60.80.0D.00.01
> Video Driver: 186.18
> RAM: 8GB
> Proc: C2D 6600 @ 2.40 GHz
>
> SVN: 4169
> Summary: No problems - Image was adjusted as expected
>
> Log:
>
> nona: using graphics card: NVIDIA Corporation GeForce 8800 GTS/PCI/SSE2
> destStart=[17, 50]
> destEnd=[3001, 2600]
> destSize=[(2984, 2550)]
> srcSize=[(4296, 2856)]
> srcBuffer=05DB0040
> srcAlphaBuffer=09DF0040
> destBuffer=080D0040
> destAlphaBuffer=096A0040
> destGLInternalFormat=GL_RGBA8
> destGLFormat=GL_RGB
> destGLType=GL_UNSIGNED_BYTE
> srcGLInternalFormat=GL_RGBA8
> srcGLFormat=GL_RGB
> srcGLType=GL_UNSIGNED_BYTE
> srcAlphaGLType=GL_UNSIGNED_BYTE
> destAlphaGLType=GL_UNSIGNED_BYTE
> warparound=0
> needsAtanWorkaround=0
> maxTextureSize=8192
> Source chunks:
> [(0, 0) to (4296, 2856) = (4296x2856)]
> Dest chunks:
> [(0, 0) to (1492, 1275) = (1492x1275)]
> [(1492, 0) to (2984, 1275) = (1492x1275)]
> [(0, 1275) to (1492, 2550) = (1492x1275)]
> [(1492, 1275) to (2984, 2550) = (1492x1275)]
> Total GPU memory used: 181856208
> Interpolator chunks:
> [(0, 0) to (4, 4) = (4x4)]
> #version 110
> #extension GL_ARB_texture_rectangle : enable
> uniform sampler2DRect SrcTexture;
> float sinh(const in float x) { return (exp(x) - exp(-x)) / 2.0; }
> float cosh(const in float x) { return (exp(x) + exp(-x)) / 2.0; }
> float atan2_xge0(const in float y, const in float x) {
> return atan(y, x);
> }
> float atan2_safe(const in float y, const in float x) {
> return atan(y, x);
> }
> float atan_safe(const in float yx) {
> return atan(yx);
> }
> void main(void)
> {
> float discardA = 1.0;
> float discardB = 0.0;
> vec2 src = gl_TexCoord[0].st;
> src -= vec2(1500., 1300.);
>
> // rotate_erect(18000.000, -13.34104824210840)
> {
> src.s += -13.34104824210840;
> float w = (abs(src.s) > 18000.000) ? 1.0 : 0.0;
> float n = (src.s < 0.0) ? 0.5 : -0.5;
> src.s += w * -36000.000 * ceil(src.s /
> 36000.000 + n);
> }
>
> // sphere_tp_erect(5729.5779513082325000)
> {
> float phi = src.s / 5729.5779513082325000;
> float theta = -src.t / 5729.5779513082325000 +
> 1.5707963267948966000;
> if (theta < 0.0) {
> theta = -theta;
> phi += 3.1415926535897931000;
> }
> if (theta > 3.1415926535897931000) {
> theta = 3.1415926535897931000 - (theta - 3.1415926535897931000);
> phi += 3.1415926535897931000;
> }
> float s = sin(theta);
> vec2 v = vec2(s * sin(phi), cos(theta));
> float r = length(v);
> theta = 5729.5779513082325000 * atan2_safe(r, s * cos(phi));
> src = v * (theta / r);
> }
>
> // persp_sphere(5729.5779513082325000)
> {
> mat3 m = mat3(0.86726875127917369000, 0.49776314112882103000,
> -0.0087617571429537341000,
>   -0.49784024852824299000, 0.86713442538204355000,
> -0.015263527203445419000,
>   0., 0.017599535531440003000,
> 0.99984511618003991000);
> float r = length(src);
> float theta = r / 5729.5779513082325000;
> float s = 0.0;
> if (r != 0.0) s = sin(theta) / r;
> vec3 v = vec3(s * src.s, s * src.t, cos(theta));
> vec3 u = v * m;
> r = length(u.st);
> theta = 0.0;
> if (r != 0.0) theta = 5729.5779513082325000 * atan2_safe(r, u.p) /
> r;
> src = theta * u.st;
> }
>
> // rect_sphere_tp(5729.5779513082325000)
> {
> float r = length(src

[hugin-ptx] Re: Hugin win32 build problem: Cmake wxwidgets problem

[Guido Kohlmeyer]

The SDK which I built and refering in my last post is not appropriate to
build enblend/enfuse. It contains a pre-build version from enblend
homepage. It was discussed to extend the SDK to even build
enblend/enfuse, but so far there is no such SDK version available which
fits all build use scenarios on Win platform.

Guido
> Dear Guido
>
> Thank you so much,
>
> I will run the process again with updated environment immediatelly.
>
> I have a question,
>
> Should I rebuild Enblend with updated SDK?
>
> or it doesn't manner that Enblend is built with elder SDK, and Hugin
> is builted with updated SDK ?
>
> I really appreciate your help.
>
> Best regards
>
> Elvis
>
>
>   

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Hugin win32 build problem: Cmake wxwidgets problem

[Guido Kohlmeyer]

Dear Elvis,

If you want to build a current revision of hugin you have to use another 
SDK. You will find it here:
http://hugin.panotools.org/sdk/MSVC/Hugin-SDK-20090509-win32.exe

Due to the fact that the guide to build hugin is quite outdated I can 
give you some rough hints to build it on win32 platform.

1. Download the SDK and run the file. Decompress it to a directory you 
like, e.g. D:\hugin\SDK
2. Create a directory e.g. D:\hugin\SDK\hugin-trunk
3. Right-click > SVN Checkout ...
4. Enter URL of reposity: 
https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/trunk
5. Click the radio button "Revision" and enter 4094 in the entry
6. Press ok
7. Run current CMake, which is version 2.6.4. If you have an older 
version, please update
8. In entry "Where is the source code:" enter your directory for the 
sources, e.g. D:\hugin\SDK\hugin-trunk
9. In entry "Where to build the binaries:" enter your directory for the 
applications, e.g. D:\hugin\SDK\hugin
10. Press Configure button.
11. A dialog appears, choose "Visual Studio 9 2008", and press Finish.
12. An error dialog appears, click OK
13. Click the value cell of the line HUGIN_BUILDER, and enter your name, 
e.g. "Elvis"
14. Press Configure button.
15. An error dialog appears, click OK
13. Click the value cell of the line HUGIN_BUILDDATE, and enter the 
current date, e.g. "2009-08-05"
14. Press Configure, maybe twice until the Generate button is active.
15. Press Generate and your done
16. Open the solution file D:\hugin\SDK\hugin\hugin.sln and build hugin.

Due to the fact the the SDK is not up-to-date, the build process is 
broken for some newer revisions as 4094. We are currently investigating 
how to extend the SDK to match the hugin sources on win32 platform.
If a new SDK is available I will provide it on the panotools wiki:
http://wiki.panotools.org/Hugin_SDK_%28MSVC_2008%29

Regards,
Guido

Elvis schrieb:
> Dear all
>
> I follow the steps building hugin for windows with sdk, to setup the
> Cmake configuration.
>
> I set wxWidgets_LIB_DIR to /hugin_enblend_sdk_msvc2008_v2/
> wxMSW-2.8.7/lib/vc_lib
>
> then I click "Show Advanced Values", about half of WX_xx libary are
> found.
>
> Still half are not found, like WX_advd, WX_based. I delete them all
> and configure again.
>
> But 4 libarys come back to list automatically, althogh I delete them.
>
> They are WX_dbgrid, WX_gl, WX_mono, WX_odbc.
>
> I try to delete, ignore them, but error message keeps showing
> "wxWidgets required, please specify it's location",
>
> and I cant find them in my whole dictionary.
>
>
> I have build hugin for a month, and now I can't go any further, what
> should I do ?
>
> Thank you so much.
>
>
>
>
>
> >
>   

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: The way to 2009.2

[Guido Kohlmeyer]

Hi Yuval,

I uploaded an archived version of nona to the panotools webspace:
http://hugin.panotools.org/testing/hugin/nona.zip

It is based on my current build environment.

Due to the fact that a lot of progress is done using GPU power it is 
time to get a new machine. My laptop is more and more unstable (maybe 
broken motherbord) and my desktop is much older.
> nona -o output.tif project.pto
> vs.
> nona -g -o output.tif project.pt

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Hugin build Error: can't find IGNORE.lib ?

[Guido Kohlmeyer]

This is maybe a problem of the currently broken build chain on win32/64 
due to a missing glut library in the SDK. I expect SVN 4094 should be 
built without problems based on the SDK on win32.

Guido

Elvis schrieb:
> By the way,
>
> if i cant find paths in Cmake configuration, I set it to "IGNORE"
>
>  I trying to figure out that if  this error relates to the Cmake
> configuration,
>
>
> On 8月4日, 上午10時42分, Elvis  wrote:
>   
>> Hi all,
>>
>> I spent lots of time on Cmake configuration, to create hugin.sln
>>
>> but there is still lots of error message when building hugin.sln,
>>
>> most of them are file or lib path errors,
>>
>> so I kept on spenting more time setting pathes manaully.
>>
>> but after I compile most projects one by one successfully,
>>
>> most of them shows link error message:
>>
>> 
>>> LINK : fatal error LNK1104: Cannot Open File 'IGNORE.lib'
>>>   
>> I searches huginbase and whole project, there is no such file,
>>
>> I also checked project setting if IGNORE.lib will be generated  after
>> compiling of some project, but it is not.
>>
>> does anybody know what is happening and how to fix it ?
>>
>> Thank you so much.
>>
>> Elvis
>> 
> >
>   


--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: The way to 2009.2

[Guido Kohlmeyer]

Yuval Levy schrieb:
> Guido Kohlmeyer wrote:
>   
>> the DLL is currently not copied to INSTALL/FILES/bin.
>> 
>
> you will need to tell Cmake to copy it from a folder in the SDK to 
> INSTALL/FILES/bin
>
> something like:
>
> INSTALL(glew.dll DESTINATION ${BINDIR})
>
>
>   
Thanks for the hint. My comment was not intended to ask for this hint 
but rather only to note about the current status of build configuration 
in current trunk. :-)
>> test szenario to check to build result. I didn't followed the discussion 
>> about the broken build in depth.
>> 
>
> the build is fixed now. to test the build, just cd to the binaries 
> folder and start nona with GPU and with a test project:
>
> nona -g -o output.tif project.pto
>   
Thanks.
>> 2.b. Or should we use a static lib instead?
>> 
>
> I would prefer static libs first. Once 2009.2 is out, we can look into 
> moving the Windows version from full static build to either full dynamic 
> or mixed build.
>   
ok, I'll try to generate a static lib configuration.
> There is already enough on the plate for 2009.2. And for Windows.
>
> I committed today Ryan's Visual Studio 2008 x64 compile fixes. That's 
> half of the patches to produce a Windows 64bit version - a request that 
> has been in the air for quite some time and which has more significant 
> impact on the users than how libraries are linked.
>
> If I am not mistaken the second half of his patches [0] are for the SDK, 
> that will need an update.
>   
> Speaking of the SDK, I don't like the current status. Unless my memory 
> betrays me, the original SDK had all the binaries to build Hugin *and* 
> Enfuse-Enblend. Even if it didn't, I think a proper SDK should because 
> Hugin requires Enfuse-Enblend.
>   
I only maintan the 32-bit part of the SDK, cause I don't have a 64-bit 
OS. I don't mind if Ryan will provide an extended/modified SDK for 
64-bit. For instance in terms of an archive that will contain all 
additional files which can easily be copied into my base SDK. The second 
point (enblend/enfuse) is likely religious :-) I followed the approach 
to use stable releases of all additional applications and libraries. 
Thus I take the maybe meanwhile outdated stable version of 
enblend/enfuse. If there is any other version which is likely stable I 
can integrate it. Currently I cannot see such version on the 
enblend/enfuse homepage. I know you prefer another build chain approach 
in terms of a bleeding edge environment.
> So bottom line: there is a lot of pent-up work and I don't think that 
> we'll do ourselves or our Windows users a favor by venturing now into 
> changing how libraries are linked.
>
>   
Well that's right, but I know about the library problems on windows (DLL 
hell), and before I choose one of two ways I wanted to get some 
impressions which way would be prefered.


--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: The way to 2009.2

[Guido Kohlmeyer]

I run a small build test based on my SDK with an integrated fresh built 
dynamic glut library.
The build works for a dynamic library, but the DLL is currently not 
copied to INSTALL/FILES/bin.
Before I start to modify some cmake files I want to ask about a test 
szenario to check to build result. I didn't followed the discussion 
about the broken build in depth.
Therefore I have these questions:
1. How can I test whether glut integration is working well?
2. a. Where should the glut dynamic library be copied?
2.b. Or should we use a static lib instead?

Guido

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Boost not found

[Guido Kohlmeyer]

Dear Allard,

As Ryan already noted the linker is searching for a data base with 
symbol information which are needed for debugging. Such information is 
stored in dedicated files. The warning you mentioned about is related to 
external libraries like libexpat. Such symbol databases are not provided 
in the SDK, because I assumed that the external libraries are valid 
(i.e. error free) and don't need any debug information. I even though 
about to perfect the SDK with debug databases as well, but this is only 
a cosmetic purpose and it will bloat the SDK.
Hence it is a minor point on my task list.

Guido

allard schrieb:
> That seems to have worked for me. No more CMAKE error messages, and it
> looks like the build succeeds too. Thanks
>
> completely unrelated, but what is vc90.pdb? I suddenly see enormous
> numbers of this same warning:
>
> "Warning LNK4099: PDB 'vc90.pdb' was not found with 'C:\HuginSDK
> \exiv2-0.18.1\msvc\lib\libexpatd.lib' or at 'C:\HuginSDK
> \hugin_build2\src\hugin1\ptbatcher\Debug\vc90.pdb'; linking object as
> if no debug info"
>
> It does not matter, the build is ok, but after the 1000'th time I
> started to wonder.
>
> Allard
>
> On Jul 29, 1:49 pm, Guido Kohlmeyer  wrote:
>   
>> Dear Thomas,
>>
>> Sorry for the delay, I was on vacation for some days.
>> It is not advisable to add the line as supposed. As I understand the
>> deletion of the FindBoost component in the trunk, it was intended to be
>> free of some fixed components, e.g. the SDK, and to change the Boost
>> dependency if more than one instance is available.
>> If you set the variable BOOST_ROOT in cmake script the environment
>> variable is not evaluated any more.
>> I think it is better to use a similar pattern as in the original
>> FindBoost script as shipped with cmake:
>>
>> # If BOOST_ROOT was defined in the environment, use it.
>> if (NOT BOOST_ROOT AND NOT $ENV{BOOST_ROOT} STREQUAL "")
>>   set(BOOST_ROOT $ENV{BOOST_ROOT})
>> else(NOT BOOST_ROOT AND NOT $ENV{BOOST_ROOT} STREQUAL "")
>>   set(BOOST_ROOT ${SOURCE_BASE_DIR}/boost_1_39_0)
>>  endif(NOT BOOST_ROOT AND NOT $ENV{BOOST_ROOT} STREQUAL "")
>>
>> In this case the variable is only set with value that matches with the
>> SDK (let say as fall back) if the variable is not set before or
>> available as windows environment variable.
>> I didn't tested the pattern, but I expect it will work.
>>
>> Guido
>>
>> T. Modes schrieb:
>>
>>
>>
>> 
>>> On 24 Jul., 11:43, Guido Kohlmeyer  wrote:
>>>   
>>>> I commited a small fix in CMakeLists.txt to find the static libraries in
>>>> the SDK.
>>>> I don't know how do you start CMake. You can even pass this as a
>>>> parameter at call of CMake "-D BOOST_ROOT=D:/usr/src/SDK/boost_1_39_0"
>>>> For instance I do a build based in batch files which call CMake and all
>>>> other tools. Here it is possible to set the environment variable right
>>>> before the call of CMake or to pass the path as a parameter.
>>>> 
>>> Hi Guido,
>>>   
>>> thank for your help.
>>>   
>>> After adding the line (about line 180, in the IF(WIN32)-ENDIF
>>> condition)
>>> SET(BOOST_ROOT ${SOURCE_BASE_DIR}/boost_1_39_0)
>>> to CMakeList.txt it works without problems.
>>> So I don't need to change a environment variable when the library gets
>>> updated, because then I forgot that I have to change the environment
>>> variable.
>>>   
>>> Does this line breaks something other (maybe in your batch files)?
>>> If not, we can commit it to trunk.
>>>   
>>> Thomas
>>>   
> >
>   

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Boost not found

[Guido Kohlmeyer]

Dear Thomas,

Sorry for the delay, I was on vacation for some days.
It is not advisable to add the line as supposed. As I understand the 
deletion of the FindBoost component in the trunk, it was intended to be 
free of some fixed components, e.g. the SDK, and to change the Boost 
dependency if more than one instance is available.
If you set the variable BOOST_ROOT in cmake script the environment 
variable is not evaluated any more.
I think it is better to use a similar pattern as in the original 
FindBoost script as shipped with cmake:

# If BOOST_ROOT was defined in the environment, use it.
if (NOT BOOST_ROOT AND NOT $ENV{BOOST_ROOT} STREQUAL "")
  set(BOOST_ROOT $ENV{BOOST_ROOT})
else(NOT BOOST_ROOT AND NOT $ENV{BOOST_ROOT} STREQUAL "")
  set(BOOST_ROOT ${SOURCE_BASE_DIR}/boost_1_39_0)
 endif(NOT BOOST_ROOT AND NOT $ENV{BOOST_ROOT} STREQUAL "")

In this case the variable is only set with value that matches with the 
SDK (let say as fall back) if the variable is not set before or 
available as windows environment variable.
I didn't tested the pattern, but I expect it will work.

Guido

T. Modes schrieb:
>
> On 24 Jul., 11:43, Guido Kohlmeyer  wrote:
>   
>> I commited a small fix in CMakeLists.txt to find the static libraries in
>> the SDK.
>> I don't know how do you start CMake. You can even pass this as a
>> parameter at call of CMake "-D BOOST_ROOT=D:/usr/src/SDK/boost_1_39_0"
>> For instance I do a build based in batch files which call CMake and all
>> other tools. Here it is possible to set the environment variable right
>> before the call of CMake or to pass the path as a parameter.
>> 
>
> Hi Guido,
>
> thank for your help.
>
> After adding the line (about line 180, in the IF(WIN32)-ENDIF
> condition)
> SET(BOOST_ROOT ${SOURCE_BASE_DIR}/boost_1_39_0)
> to CMakeList.txt it works without problems.
> So I don't need to change a environment variable when the library gets
> updated, because then I forgot that I have to change the environment
> variable.
>
> Does this line breaks something other (maybe in your batch files)?
> If not, we can commit it to trunk.
>
> Thomas
>
> >
>   

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Windows Users: please test

[Guido Kohlmeyer]

Hi Yuv,

I tested my own snapshot of SVN 4012 on WinXP SP2 and it works without 
any problems. German language settings on german machine. Made some 
workflow like pictures load in wizard, CP search, vignetting correction, 
fast preview etc. No crash at all.
It's the same with current snapshot of SVN 4094.

Guido

Yuval Levy schrieb:
> https://sourceforge.net/tracker/?func=detail&atid=550441&aid=2824416&group_id=77506
>
> can a few windows users confirm the above report that the SVN4007 
> http://adhuikeshoven.pbworks.com/f/hugin-SVN4007-setup.exe and SVN4012 
> snapshots http://adhuikeshoven.pbworks.com/f/hugin-SVN4012-setup.exe 
> quit on start? and that 
> http://adhuikeshoven.pbworks.com/f/hugin-SVN3975-setup.exe works fine?
>
> please try on both Windows 64bit and Windows 32bit.
>
> Are there any builds around, particularly of SVN4008, that are not from 
> Ad's site?
>
> we need to establish if the problem is specific to the bug report, or if 
> it is generic; and if it is generic we need to establish if it is in 
> Ad's builds, or if other builds fail as well.
>
> This would be particularly embarassing because SVN4008 = 0.8.0 release 
> and the error was introduced between SVN3975 and SVN4007 at the RC4/RC5 
> stage.
>
> Developers: Potentially in one of the following commits:
>
> http://hugin.svn.sourceforge.net/viewvc/hugin?view=rev&revision=3978
> http://hugin.svn.sourceforge.net/viewvc/hugin?view=rev&revision=3980 *
> http://hugin.svn.sourceforge.net/viewvc/hugin?view=rev&revision=3993
> http://hugin.svn.sourceforge.net/viewvc/hugin?view=rev&revision=3999 *
> http://hugin.svn.sourceforge.net/viewvc/hugin?view=rev&revision=4005
> http://hugin.svn.sourceforge.net/viewvc/hugin?view=rev&revision=4007 *
>
> two of them are translations and one of them is an image, so highly 
> unlikely - marked with asterisk.
>
> 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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Boost not found

[Guido Kohlmeyer]

Dear Thomas,

CMake configuration is broken, because Bruno deleted the file 
FindBoost.cmake from trunk in SVN 4084, which was likely asked by 
Tiziano Müller.
I commited a small fix in CMakeLists.txt to find the static libraries in 
the SDK.
Furthermore maybe it is needed to set the windows environment variable 
BOOST_ROOT to the path of the boost library in the SDK, e.g. set this in 
your windows settings.
I don't know how do you start CMake. You can even pass this as a 
parameter at call of CMake "-D BOOST_ROOT=D:/usr/src/SDK/boost_1_39_0"
For instance I do a build based in batch files which call CMake and all 
other tools. Here it is possible to set the environment variable right 
before the call of CMake or to pass the path as a parameter.

Guido


T. Modes schrieb:
> Since svn4084 the boost library is not found (using Windows with
> current SDK, CMake 2.6.4)
>
> CMake 2.6.4/FindBoost has only the version up to 1.38, the windows SDK
> contains Boost 1.39. Adding the version 1.39 to findboost did not
> help.
> Can somebody have a look on it?
>
> Thomas
>
> >
>   


--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: What's in a Version Number?

[Guido Kohlmeyer]

Hi Yuv,

What do you propose to deal with development steps for patches?
The naming .mm.n, with n > 1 is o.k. for a release of a patch, but 
how to distinguish development snapshots of patches? I expect a patch 
will be done on a branch rather than on the trunk, and the fixes will be 
integrated in the trunk as well.  I guess this is not often needed, but 
if there is a process, we can use it.
So, should we proceed with .mm.0.SVN? Unfortunately you cannot see, 
whether this shnapshot is taken before of after .mm.1 if .mm are 
the same. Futhermore is is not visible whether it is a snapshot of 
branch or trunk. A developer can trace back the SVN number to trunk or 
branch using SVN. Maybe this is sufficent and end-users should only take 
the non-SVN versions into account, which were numbered increasingly. I 
expect patches are based on the year and month of their corresponding 
final version although they may be relased at least a month later.
I don't want to start a big discussion about it. Maybe you already 
discussed such szenario already with Pablo.

Guido

> Hi all,
>
> During a private discussion after LGM Pablo had this idea which I think 
> now is the time to implement. Details at
>
> 
>
>  From now on let's use the major version number (padded to four digits) 
> for the year, the minor version number for the month (padded to two 
> digits) and the third version number to distinguish snapshots (.0) final 
> (.1) and bug fixes (>.2)?
>
> so Hugin 0.8.0 becomes Hugin 2009.07.1
>
> If there is no opposition to this suggestion we shall move quickly to 
> make the changes in SVN and release 2009.07.1 before new features make 
> the trunk unstable again.
>
> future snapshots become Hugin .MM.0.SVN
>
> 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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: OpenGL slow because of reloading

[Guido Kohlmeyer]

Dear David,

regarding your comment "albeit it took approximately 5 hours to render", I
expect you can speed up the calculation with more RAM. After upgrade my
machine from 512MB to 2GB RAM the process was very quick compared to the
less RAM configuration, especially enblend benefits from lot of free
memory.
My panos are commonly 14000x7000px built from about 32 pictures in
eqirectangular projection. The enblend step needs about 1.5 to 1.7GB RAM
to run quickly, otherwise enblend goes to disk with slows down the
process.

Guido

>
> On 07.06.2009, at 18:45, Harry van der Wolf wrote:
>
>>
>>
>> 2009/6/5 David Haberthür 
>>
>>
>>
>> i could help with providing a test-case, the panorama i shot last
>> saturday evening [1] contains +100 images and +7000 control points
>> generated with pan-o-matic. i'm still struggling with stitching it
>> with full resolution, somehow i chokes at the fusing-step when trying
>> to stitch it in sizes bigger than 1px wide, now i've stitched it
>> in "only" 2694 x 635 px (os x, with harrys newest svn-builld).
>>
>> Hi Habi,
>>
>> Nice pano.
>> You are saying that it chokes on 1px wide (1 by ?).
>> What error message do you get?
>>
>> Harry
>
> Dear all.
> I'm happy to say that  with hugin 0.8.0-RC5 I no longer have the
> problem with this panorama it stitched fine (with a size of
> 17806x4346, albeit it took approximately 5 hours to render :)
> Thanks for all the effort of all involved people!
> Habi
>
>
>
> >
>



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Release rc4 as 'final'?

[Guido Kohlmeyer]

There is still the review of the german translation on my task list.
I suppose there are no huge changes needed. Is there a dead line available
for check-in?

Guido

>
> Hi all, my mail has been down for a few days, so I'm not completely
> up-to-date.
>
> Can anyone think of a really good reason why we should not release
> the current hugin rc4 as a 'final' 0.8.0?
>
> --
> Bruno
>
> >
>



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Hugin Windows SDK -- wxWidgets not found

[Guido Kohlmeyer]

Dear Tom,

The repository corresponds to the current SDK. I update the repository
every time when I update the SDK, thus I modified the CMakeLists.txt in
revision 3842 to match wxWidgets 2.8.10, which is in the current SDK. I
updated the SDK in May (2009-05-09) with boost 1.39.0, exiv2-0.18.1 and
wxWidgets 2.8.10.

Maybe you installed SDK is not up to date as already noted.
You will find the latest one on panotools wiki:
http://wiki.panotools.org/Hugin_SDK_%28MSVC_2008%29

Guido


>
> Hi
>
> Have been building Hugin on Windows now and then, using the SDK that
> was put together by Guido K. about 6 months ago.
>
> Just updated my Hugin source to SVN 4017, and get CMake error "cant'f
> find REQUIRED package wxWidgets.".  This is coming from the standard
> findwxwidgets.cmake script that is distributed with CMake, not from a
> hugin custom script -- as I think it should be if the Windows SDK were
> being properly supported  and wxWidgets really was missing (actually
> on my system there would be no error message, because wxWidgets is
> indeed in the SDK).
>
> I'm sure I can find & fix the problem, but I'm posting to ask all
> Hugin developers to be aware that there are special problems with
> finding packages in the Windows Hugin build environment, and special
> CMake code to handle them.  So please  be careful about rearranging
> FIND_PACKAGE calls and related code in the CMake scripts -- preferably
> test with a Windows builder before committing.
>
> -- Tom
>
> >
>



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Enblend error: Mask is entirely black, but white image was not identified as redundant

[Guido Kohlmeyer]

Dear  Thomas

It is a known problem or rather a drawback of enblend. I have a test 
case available too. Due to the fact that enblend is an external tool and 
not a component of hugin it is not a show stopper for the release. 
Anyway this is my impression of the case.
It is always a trade off between memory consumption and accuracy. Maybe 
the author of enblend can inplement a switch function to prevent the 
problem.  I'm not familiar with the algorithm and don't know whether it 
is possible or not.

Guido

>> The error is a common problem. Try to use the additional enblend
>> parameter "--fine-mask" to ged rid of the error.
>> 
>
> I tried it and it worked. Thanks! :)
>
> If I can help somehow to get closer to the problem to avoid the error
> in the future, please let me know (test case, bug report -
> dontknow...)
> Thomas
>
>
> >
>   

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Enblend error: Mask is entirely black, but white image was not identified as redundant

[Guido Kohlmeyer]

Dear  Thomas,

The error is a common problem. Try to use the additional enblend
parameter "--fine-mask" to ged rid of the error. The parameter will 
result in generation of masks in higher resolution which may may fix the 
problem, but sometimes may result in memory errors cause not enough 
memory available for bigger masks.

Guido

finbref.2006 schrieb:
> I just got the same error with SVN 3966 on Vista.
> The 10 jpeg-images are made with a 350D and they are well connetced. I
> can post them if this helps.
> Perhaps the message close to the end helps:
>
> Optimizing 0 distinct seams.
> Strategy 2:
>
> Thank you for providing help – if needed I can do tests to help to
> find out why it fails.
> Thomas
>
> full error message:
>
> D:\Program\ Files\Hugin\bin\nona -z PACKBITS  -r ldr -m TIFF_m -o
> IMG_1787-IMG_1796 -i 0 C:\Users\Trommler\AppData\Local\Temp
> \hugC2B3.tmp
> D:\Program\ Files\Hugin\bin\nona -z PACKBITS  -r ldr -m TIFF_m -o
> IMG_1787-IMG_1796 -i 1 C:\Users\Trommler\AppData\Local\Temp
> \hugC2B3.tmp
> D:\Program\ Files\Hugin\bin\nona -z PACKBITS  -r ldr -m TIFF_m -o
> IMG_1787-IMG_1796 -i 2 C:\Users\Trommler\AppData\Local\Temp
> \hugC2B3.tmp
> D:\Program\ Files\Hugin\bin\nona -z PACKBITS  -r ldr -m TIFF_m -o
> IMG_1787-IMG_1796 -i 3 C:\Users\Trommler\AppData\Local\Temp
> \hugC2B3.tmp
> D:\Program\ Files\Hugin\bin\nona -z PACKBITS  -r ldr -m TIFF_m -o
> IMG_1787-IMG_1796 -i 4 C:\Users\Trommler\AppData\Local\Temp
> \hugC2B3.tmp
> D:\Program\ Files\Hugin\bin\nona -z PACKBITS  -r ldr -m TIFF_m -o
> IMG_1787-IMG_1796 -i 5 C:\Users\Trommler\AppData\Local\Temp
> \hugC2B3.tmp
> D:\Program\ Files\Hugin\bin\nona -z PACKBITS  -r ldr -m TIFF_m -o
> IMG_1787-IMG_1796 -i 6 C:\Users\Trommler\AppData\Local\Temp
> \hugC2B3.tmp
> D:\Program\ Files\Hugin\bin\nona -z PACKBITS  -r ldr -m TIFF_m -o
> IMG_1787-IMG_1796 -i 7 C:\Users\Trommler\AppData\Local\Temp
> \hugC2B3.tmp
> D:\Program\ Files\Hugin\bin\nona -z PACKBITS  -r ldr -m TIFF_m -o
> IMG_1787-IMG_1796 -i 8 C:\Users\Trommler\AppData\Local\Temp
> \hugC2B3.tmp
> D:\Program\ Files\Hugin\bin\nona -z PACKBITS  -r ldr -m TIFF_m -o
> IMG_1787-IMG_1796 -i 9 C:\Users\Trommler\AppData\Local\Temp
> \hugC2B3.tmp
> D:\Program\ Files\Hugin\bin\enblend.exe --compression 92 -
> f10139x2258+0+1041 -o IMG_1787-IMG_1796.jpg IMG_1787-IMG_1796.tif
> IMG_1787-IMG_17960001.tif IMG_1787-IMG_17960002.tif IMG_1787-
> IMG_17960003.tif IMG_1787-IMG_17960004.tif IMG_1787-IMG_17960005.tif
> IMG_1787-IMG_17960006.tif IMG_1787-IMG_17960007.tif IMG_1787-
> IMG_17960008.tif IMG_1787-IMG_17960009.tif
> Loading next image: IMG_1787-IMG_1796.tif
> Loading next image: IMG_1787-IMG_17960001.tif
> Creating blend mask: 1/4 2/4 3/4 4/4
> Optimizing 1 distinct seam.
>
> Strategy 1, s0: 1/4 2/4 3/4 4/4
> Strategy 2: s0
> Using 8 blending levels
> Generating Gaussian pyramid:  g0 g1 g2 g3 g4 g5 g6 g7
> Generating Gaussian pyramid:  g0 g1 g2 g3 g4 g5 g6 g7
> Generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7
> Generating Gaussian pyramid:  g0 g1 g2 g3 g4 g5 g6 g7
> Generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7
> Blending layers:  l0 l1 l2 l3 l4 l5 l6 l7
> Collapsing Laplacian pyramid: l7 l6 l5 l4 l3 l2 l1 l0
> Loading next image: IMG_1787-IMG_17960002.tif
> Creating blend mask: 1/4 2/4 3/4 4/4
> Optimizing 1 distinct seam.
>
> Strategy 1, s0: 1/4 2/4 3/4 4/4
> Strategy 2: s0
> Using 8 blending levels
> Generating Gaussian pyramid:  g0 g1 g2 g3 g4 g5 g6 g7
> Generating Gaussian pyramid:  g0 g1 g2 g3 g4 g5 g6 g7
> Generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7
> Generating Gaussian pyramid:  g0 g1 g2 g3 g4 g5 g6 g7
> Generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7
> Blending layers:  l0 l1 l2 l3 l4 l5 l6 l7
> Collapsing Laplacian pyramid: l7 l6 l5 l4 l3 l2 l1 l0
> Loading next image: IMG_1787-IMG_17960003.tif
> Creating blend mask: 1/4 2/4 3/4 4/4
> Optimizing 1 distinct seam.
>
> Strategy 1, s0: 1/4 2/4 3/4 4/4
> Strategy 2: s0
> Using 8 blending levels
> Generating Gaussian pyramid:  g0 g1 g2 g3 g4 g5 g6 g7
> Generating Gaussian pyramid:  g0 g1 g2 g3 g4 g5 g6 g7
> Generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7
> Generating Gaussian pyramid:  g0 g1 g2 g3 g4 g5 g6 g7
> Generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7
> Blending layers:  l0 l1 l2 l3 l4 l5 l6 l7
> Collapsing Laplacian pyramid: l7 l6 l5 l4 l3 l2 l1 l0
> Loading next image: IMG_1787-IMG_17960004.tif
>
> Creating blend mask: 1/4 2/4 3/4 4/4
> Optimizing 1 distinct seam.
>
> Strategy 1, s0: 1/4 2/4 3/4 4/4
> Strategy 2: s0
> Using 8 blending levels
> Generating Gaussian pyramid:  g0 g1 g2 g3 g4 g5 g6 g7
> Generating Gaussian pyramid:  g0 g1 g2 g3 g4 g5 g6 g7
> Generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7
> Generating Gaussian pyramid:  g0 g1 g2 g3 g4 g5 g6 g7
> Generating Laplacian pyramid: l0 l1 l2 l3 l4 l5 l6 l7
> Blending layers:  l0 l1 l2 l3 l4 l5 l6 l7
> Collapsing Laplacian pyramid: l7 l6 l5 l4 l3 l2 l1 l0
> Loading next image: IMG_1787-I

[hugin-ptx] Re: some minor GUI ideas

[Guido Kohlmeyer]

I know only one drawback of using the lossless compression methods of 
TIF file format: Some applications do not support all three methods, but 
I expect "Packbits" and "LZW" are supported by many ones. A preselection 
in the preferences would be fine to match the own workflow.

Guido

Andreas Metzler schrieb:
> Better: Add some way to set the prefered output format. (I wonder why
> tif with *no* compression is used by default. Is there any downside for
> using tif with any of the three lossless compression methods?)
> cu andreas
>
>   

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Interface consistency

[Guido Kohlmeyer]

Bruno Postle schrieb:
> Just had a discussion with Pablo about the text on the Stitcher tab 
> and realised that it makes much more sense in the German translation 
> than the English original.
>   
Thanks, at that time I spent a lot of time to find adequate german terms.

Guido


--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin-0.8.0_rc3 released

[Guido Kohlmeyer]

I made a fresh rebuild with complete empty destination folder, hence 
without any cached data from CMake. This works. Following the last mails 
in this thread this seems a significant point.

Guido

T. Modes schrieb:
>   
>> Hi Allard,
>> have you done a clean build? I've found out that it gets cached every
>> time. Unfortunately I don't know how to avoid this caching. You can
>> bypass it by removing the CMakeCache file or by running cmake with
>> -DENABLE_LAPACK=NO
>>
>> You also must use at least svn rev 3925.
>> 
>
>   

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: OpenGL slow because of reloading

[Guido Kohlmeyer]

The additional option is only a workaround that may work, but as you 
already percieved it will yield to higher memory consumption to generate 
the mask in a higher resolution.
I guess the process runs out of memory.

Guido

David Haberthür schrieb:
> Dear Guido,
> That only helped a bit, now enblend crashes lateron in the process.
> The relevant lines of the stitching window are below:
>
> ---
> DSC_2284-DSC_24160114.tif DSC_2284-DSC_24160115.tif 
> DSC_2284-DSC_24160116.tif DSC_2284-DSC_24160117.tif 
> DSC_2284-DSC_24160118.tif DSC_2284-DSC_24160119.tif 
> DSC_2284-DSC_24160120.tif DSC_2284-DSC_24160121.tif 
> DSC_2284-DSC_24160122.tif 
> enblend(5937) malloc: *** mmap(size=2097152) failed (error code=12)
> *** error: can't allocate region
> *** set a breakpoint in malloc_error_break to debug
> enblend(5937) malloc: *** mmap(size=2097152) failed (error code=12)
> *** error: can't allocate region
> *** set a breakpoint in malloc_error_break to debug
> enblend(5937) malloc: *** mmap(size=2097152) failed (error code=12)
> *** error: can't allocate region
> *** set a breakpoint in malloc_error_break to debug
> enblend(5937) malloc: *** mmap(size=2097152) failed (error code=12)
> *** error: can't allocate region
> *** set a breakpoint in malloc_error_break to debug
> terminate called recursively
> gnumake: *** [DSC_2284-DSC_2416.png] Abort trap
> gnumake: *** Deleting file `DSC_2284-DSC_2416.png'
> ---
> using hugin svn-3888, will try tomorrow with harrys freshly compiled rc3.
> have a good night.
> habi/david
>
>>
>>
>> David Haberthür schrieb:
>>>
>>> On 07.06.2009, at 18:45, Harry van der Wolf wrote:
>>>


 2009/6/5 David Haberthür >>> 
 >




i could help with providing a test-case, the panorama i shot last
saturday evening [1] contains +100 images and +7000 control points
generated with pan-o-matic. i'm still struggling with stitching it
with full resolution, somehow i chokes at the fusing-step when 
 trying
to stitch it in sizes bigger than 1px wide, now i've stitched it
in "only" 2694 x 635 px (os x, with harrys newest svn-builld).


 Hi Habi,

 Nice pano.
 You are saying that it chokes on 1px wide (1 by ?).
 What error message do you get?

 Harry
>>>
>>> Hoi Harry.
>>> Thanks, i've tried to make a night-version of the panorama i've shot
>>> some weeks ago.
>>> I've failed to thorougly investivate it, but the panorama fails to
>>> stitch for sizes 1x4122 and 12000x4946 px. It actually fails with
>>> an enblend warning:
>>> "enblend: warning: failed to detect any seam
>>> enblend: mask is entirely black, but white image was not identified as
>>> redundant
>>> gnumake: *** [DSC_2284-DSC2416.png] Error 1"
>>> are the last entries in the log window. The complete log is attached
>>> to this mail as "log.txt"
>>>
>>> I'm a bit confused, since the stitch to the smaller size worked
>>> without a hitch...
>>> Have a nice start into the week.
>>> Habi
>>> ---
>>>
>>> 
>>>
>>>
>>
>>
>>
>>
>
>
> >


--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: OpenGL slow because of reloading

[Guido Kohlmeyer]

Dear David,

The error is a common problem. Try to use the additional enblend 
parameter "--fine-mask" to ged rid of the error.

Guido

David Haberthür schrieb:
>
> On 07.06.2009, at 18:45, Harry van der Wolf wrote:
>
>>
>>
>> 2009/6/5 David Haberthür > >
>>
>>
>>
>>
>> i could help with providing a test-case, the panorama i shot last
>> saturday evening [1] contains +100 images and +7000 control points
>> generated with pan-o-matic. i'm still struggling with stitching it
>> with full resolution, somehow i chokes at the fusing-step when trying
>> to stitch it in sizes bigger than 1px wide, now i've stitched it
>> in "only" 2694 x 635 px (os x, with harrys newest svn-builld).
>>
>>
>> Hi Habi,
>>
>> Nice pano.
>> You are saying that it chokes on 1px wide (1 by ?).
>> What error message do you get?
>>
>> Harry 
>
> Hoi Harry.
> Thanks, i've tried to make a night-version of the panorama i've shot 
> some weeks ago.
> I've failed to thorougly investivate it, but the panorama fails to 
> stitch for sizes 1x4122 and 12000x4946 px. It actually fails with 
> an enblend warning: 
> "enblend: warning: failed to detect any seam
> enblend: mask is entirely black, but white image was not identified as 
> redundant
> gnumake: *** [DSC_2284-DSC2416.png] Error 1"
> are the last entries in the log window. The complete log is attached 
> to this mail as "log.txt"
>
> I'm a bit confused, since the stitch to the smaller size worked 
> without a hitch...
> Have a nice start into the week.
> Habi
> ---
>
> 
>
>   


--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin-0.8.0_rc3 released

[Guido Kohlmeyer]

Just a note:
I built SVN3923 wich is quite the same as RC3 without any problems based 
on my SDK, which does not contain any LAPACK lib.
Guido

Lukáš Jirkovský schrieb:
> 2009/6/8 Tom Sharpless :
>   
>> Hi allard
>>
>> LAPACK is a FORTRAN package, and Microsoft does not support FORTRAN.
>> On Windows, you have to use CLAPACK, a C version generated largely by
>> automatic translation.  CLAPACK still acts like FORTRAN, though, so
>> you need several special headers and libraries to mediate between the
>> C and FORTRAN environments (you also have to get used to 1-origin
>> array indexing).  And you need a couple of "blas" libraries that
>> provide the low-level arithmetic routines on which LAPACK depends
>> (typically the blas codes are processor-specific, for speed, but there
>> are generic versions too).
>>
>> And as with all Windows builds, you have to deal with the fact that
>> you need separate debug and release versions of every library, that
>> must have been built with the same compiler version that builds your
>> app.
>>
>> So you would have to do a whole lot of preparative work before you
>> could build Hugin with LAPACK on Windows.  The resulting gain of
>> optimizer speed would be of little value, since stitching throughput
>> is hardly limited by the optimizer.
>>
>> So in short, you will be much happier if you build without LAPACK.
>>
>> Indeed, LAPACK should be removed from Hugin, as it offers only
>> trouble.  There are alternative hgih performance Levenberg-Marquardt
>> codes in C++ (for example at AlgLib) if one really needed to tune up
>> the optimizer.
>>
>> -- Tom
>> 
>
> Hi, Tom,
> as I've said I've no idea why MSVC requires LAPACK when it's clearly
> optional. Moreover in current svn LAPACK have to be enabled explicitly
> so it will not use LAPACK by default even when there is a LAPACK
> library installed on system.
>
> More to the speed. LAPACK is in fact a bit slower on my machine and on
> Bruno's it's much slower. This lead to the disabling the LAPACK by
> default even when there are necessary libraries.
>
> I've explained why I've added LAPACK support under the rc2
> announcement. In short because it gives me a bit better (not so bad as
> without LAPACK) results with one of my test panoramas and doesn't
> change results with the other ones. Moreover it's recommended to use
> LAPACK in LEVMAR because it's more stable than it LU-decomposition or
> whatever it uses.
>
> >
>   


--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: temp dir

[Guido Kohlmeyer]

The temp dir is first fetched from hugin's registry settings. Maybe they 
are not completely deleted. Please have a look in 
HKEY_CURRENT_USER\Software\hugin > tempDir
If there is no setting in registry given, hugin uses the Windows API 
method GetTempPath which evaluates the windows environment variables 
TMP, TEMP, USERPROFILE and windows directory (see 
http://msdn.microsoft.com/en-us/library/aa364992(VS.85).aspx). Maybe 
some of that variables points to the directory noted in the error message.

Guido

Thomas Steiner schrieb:
> Hi,
> I use Version 0.8.0.3811 by Ad Huikeshoven under Windows Vista. before
> I had some 0.7.0 version by Yuv installed and because my C drive is
> full, I changed the temp-path in the settings to D:\... (I don't know
> where on D is such a temp dir. when I stitch, it works fine.
> Then I uninstalled hugin and installed Ad's version and during the
> installation I chose the option to remove all setting and set the
> defaults.
> Nevertheless when I started hugin, it complained twice, that the
> temp-folder does not exist: once in german, one in english. You find
> the message log below.
> Thomas
>
> PS: in the startup screen it gives the version and then it says
> "...by" but does not indicate your name Ad.
>
>
> 00:55:00: Directory 'D:\Users\Trommler\AppData\Local\Temp' couldn't be
> created (error 3: das System kann den angegebenen Pfad nicht finden.)
> 00:55:00: ERROR:
> (..\..\..\..\hugin\src\hugin1\hugin\huginApp.cpp:304)
> huginApp::OnInit(): Tempdir could not be created:
> D:\Users\Trommler\AppData\Local\Temp
> 00:55:00: ERROR:
> (..\..\..\..\hugin\src\hugin1\hugin\huginApp.cpp:308)
> huginApp::OnInit(): could not change to temp. dir:
> D:\Users\Trommler\AppData\Local\Temp
>
> >
>   

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin-0.8.0_rc1 released

[Guido Kohlmeyer]

>
> I had a second machine where hugin segfaulted at startup as reported
> by others.  It seems that glewInit() can only be called once
> depending on how glew is built:
>
> http://glew.sourceforge.net/advanced.html
>
> So I removed the call to glewInit() in GLPreviewFrame.cpp and it
> seems to work ok.
>
> I've committed this, though probably there is a better solution.
>
> In particular I still don't have 'difference mode' available in the
> fast preview, even though this did work about a month ago.  Both
> machines have no hardware acceleration, so the difference mode
> worked fine with Mesa software rendering, but now it is disabled.
>

I applied the approach to check whether the difference feature is
available in OpenGL implementation on the current machine. If so, I add
the difference feature to the drop-down list of the Preview window. Due to
the fact the detection didn't work as expected I can turn clock back and
create the drop-down list as before and leave only a check during runtime
of difference tool. Then hugin won't crash but the difference tool has no
function. Maybe better than a crash ...

Guido


--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Fixes to "Add time-series of images" button, removal of jhead library

[Guido Kohlmeyer]

> We are due another release candidate, though I've lost track and 
> would like to hear opinions on which critical bugs we still have 
> unsolved?
>   
I'm working still on the OpenGL capability detection. Currently the 
Difference View on windows platform is broken, more precisely you cannot 
select it. I've encountered problems to detect the OpenGL methodes 
before the OpenGL frame is generated, but this information is needed to 
create the drop-down list of blend methods.
I can roll back and let both blend methods in the list, but then the 
viewer may crash. One simple solution would be to remain the two modes, 
but to check the OpenGL method in the frames methods. This is 
implemented as well as a fall back to prevent a crash.
Nevertheless does anybody know how to detect whether the the OpenGL 
method "glBlendEquation" is supported on win32 platform. Especially I 
need a method to detect the support before the OpenGL context is created 
by the OpnGL render widget.

Guido

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin installer for Windows Vista/XP SVN 3845 *new SDK*

[Guido Kohlmeyer]

Hi Ryan,

>   I did update the documentation per your request. You should see a
> clean separation wherever possible about the x32 v x64 differences using
> parallel tables. Short of breaking it into it's own page, I'm not sure what
> ideas you're thinking layout.

It's ok to separate the different platforms using tables. Other 
approaches would be possible too, e.g. sub-chapter. The only thing that 
I wanted to point out was to use the same separation in every situation 
with the same notation.

Guido

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin installer for Windows Vista/XP SVN 3845 *new SDK*

[Guido Kohlmeyer]

Hi,

It seems that the new SDK works not only on my machine. Thanks for testing.

There is a documentation available how to build a x64 SDK. See on
panotools wiki and search for "MSVC 2008".

I have not tested the build of the x64 SDK due to lack of such machine and
I have made some complains about the layout of the x64 additions, but
maybe it works.

Guido

> Hi,
>
> A new hugin-SDK, just downloaded and extracted over my existing SDK
> directory. Ended up with some duplicate subdirectories (boost, exiv and
> wxWidgets append version number to subdir name). Removed the old subdirs
> from the local SDK. Deleted the hugin build directory. Emptied the trash.
> Started a fresh build forcing CMake to find the new versions of SDK files
> in
> new directories and forcing a new build against updated hugin SDK. (AS you
> guess, I didn't do these steps at first, noticing the build wasn't against
> the new SDK for some parts ...)
>
> So a midway update for the installer (I like Yuval's encouragements).
> There
> are some people who find the way to my download
> site.
> In a previous post I posted a https URL, which didn't work. So, without
> the
> security s it does work. Off list, some one asked me to cross compile to
> x64
> and publish x64 installers as well. I do notice multiple people are busy
> updating the SDK to be x64 ready - maybe there are even more people
> working
> on it than you are aware off. I might be willing to publish x64 installers
> in the future, however, I don't have an x64 machine, so maybe I can
> crosscompile when the toolchain is ready, but I can never test it.
>
> The new hugin installer for Windows Vista/XP based on SVN 3845 (jump from
> 3827 - a lot of work has been done the last week!) can be found at:
> hugin installer for Windows
> Vista
> .
>
> Dedalus
>
> >
>



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: [Win32] Updated Hugin SDK

[Guido Kohlmeyer]

Dear Ryan,

ryan+hu...@sleevi.com schrieb:
> Nice work Guido, you beat me too it. I've been working for the past week on
> documenting directions for compiling the Hugin SDK in x64, and had already
> adopted the new versions. I just updated the wiki page with the directions,
> and hopefully I didn't clobber any of your changes along the way. I did
> break out some of the solution conversion steps into
> http://wiki.panotools.org/Hugin_SDK_(MSVC_2008)_Patches, which I hope you
> don't mind - the page was already approaching 40K, was just trying to keep
> it slim.
> 


To cover the x64 platform on windows is a good enrichment for the SDK. I 
didn't checked every point, but my first impression was, that the 
differentiation of the 32-bit and 64-bit is not straight forward from 
the standpoint of layout. I followed the approach to use a strict layout 
and speak which is now slightly cluttered. I think this is mainly a task 
to layout the information more precisely. I'm little pedantic here, but 
due to the fact that I deal every day with customers and documentation 
it is mandatory to present information in a clear and syntacticaly way. 
  This helps to percept information, due to the fact the you will find 
it in the same ordering and layout.

Guido

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin-0.8.0_rc1 released

[Guido Kohlmeyer]

Dear Thomas,

> your patch doesn't work right.

meanwhile I see ...

> 
> * You check after glewInit():
>if (GLEW_OK != err)
>So your test will only run when glewInit failed. I think it should
> be
>   if (GLEW_OK==err)

Right

> * In constructor GLPreviewFrame glewInit() fails on my machine (return
> code is 1), but the call to glewInit() in GLViewer::GLViewer returns
> Ok.

Right, I guess the missing OpenGL context is a problem. The GLViewer 
seems to have a context and glewInit() will work properly. I have to 
analyse it ...

> * The check if GL_ARB_imaging is available fails on my system, but the
> difference tool works without problems (on my machine the subset
> GL_EXT_blend_subtract is available which implements the necessary
> difference function on OpenGL). So a check for GL_ARB_imageing or
> GL_EXT_blend_substract should be done.

I thought a simple check of the extension which covers the method is 
sufficient, but after some investigations this is not the case.

OK, I have to go back to start and find a new solution. I will revert to 
the old revision as recently as I have no other ideas.

Guido

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] [Win32] Updated Hugin SDK

[Guido Kohlmeyer]

Hi,

I updated some components in the SDK:

autopano-sift-c (svn revision 3480)
boost 1.39.0
exiftool 7.74
exiv2-0.18.1
libpano13-2.9.14_rc1 (svn revision 966)
wxWidgets 2.8.10

The documentation is updated too:
http://wiki.panotools.org/Hugin_SDK_(MSVC_2008)

You will find the download link on the wiki page

Guido

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: b4/rc1 undefined reference to ...::calcCtrlPointErrors

[Guido Kohlmeyer]

I had the same linker error on win32 platform too
After a clean new build (cmake etc.) no error occured any more.

Guido


--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin-0.8.0_rc1 released

[Guido Kohlmeyer]

>
> I find it a little bit nervous with the hiding and showing the buttons
> when moving the mouse.
> What's about adding a wxPanel (for each button), putting the
> wxToggleButton inside that wxPanel and change the backgroundcolor of
> wxPanel? So you get a colored border around the button. This would
> also allow to distinguish the different images under the mouse
> pointer.
>

I didn't tested the patch so far. My idea was to use a bitmap on the
buttons which content depends on the on/off state, mouse over and the
identify state. Following this approach it is possible to use some kind of
icons instead of simply description on the button. Quite similar to a film
strip.

Guido


--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin-0.8.0_rc1 released

[Guido Kohlmeyer]

Dear Bruno,

There is still a bug in the OpenGL-Preview, in particular on detecting
OpenGL capabilities to do the difference view. On my OpenGL 1.3 system
(win32) it results in a crash of hugin if I move my mouse pointer over an
image part. I have a fix already on disk but not commited so far, see
below.

Furthermore the identify feature in OpenGL preview won't work properly on
Windows. The images are surrounded with a colored line but the buttons to
enable the images are not colored accordingly. So far as I know this is a
limitation of wxWidgets on Windows platform. After fixing the OpenGL
detection bug (see above) I tried to find a way to overcome this
limitation, cause it's in the same sources. Unfortunately there is no
simple solution available. I have some ideas to implement a button array
that is capable to show colored buttons, but this will take some
development time ... Damn I need some more free time.

To cut a long story short I guess the bug fix for OpenGL detection is
mandatory for the release. I will commit it probably on weekend. The
problem on identify tool is not a show stopper, although it is a little
drawback.

Guido



>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> A hugin-0.8.0_rc1 (release candidate 1) tarball is available here:
>
> https://sourceforge.net/project/showfiles.php?group_id=77506&package_id=311429
>
> This is a release candidate, i.e. The final release may be
> identical.
>
> Changes since 0.8.0 beta4:
>
> * Updated German and Simplified Chinese translations.
>
> * Fix for photometric optimisation crash bug #2629418.
>
> * Batch Processor now uses a socket for communication on Unix
> systems.
>
> * 'Save project and send to batch' now launches the Batch Processor
> if it isn't already running.
>
> * Batch Processor uses the Hugin language preference setting.
>
> * Various other Batch Processor bugfixes.
>
> * OS X minor XCode updates.
>
> See README, ChangeLog and INSTALL_cmake for more information.
>
> SHA1SUM: df0e871363c5e732e9d917ba096dca1400aa0f64  hugin-0.8.0_rc1.tar.gz
>
> This release is equivalent to svn 3827, recent hugin binary
> installers for testing can be found here:
>
> http://panospace.wordpress.com/downloads/
>
> - --
> Bruno
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.6 (GNU/Linux)
>
> iD8DBQFKAKhzFqOhwCjyCLoRAmItAKCYCDKxD6bym3JsxjqBYRlYLgHBigCfTotZ
> jJj+AcN6lcvsVSO3jzlTuic=
> =5n5h
> -END PGP SIGNATURE-
>
> >
>



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: German translation: a few questions about original strings

[Guido Kohlmeyer]

Dear Joachim,

J. Schneider schrieb:
> Hi,
> I can take care of this. Although some of Guido's translations were a 
> lot better; I think he did a very good job at "harmonizing" the 
> expressions.
> As I am currently having time (or procrastinating on other things by 
> translating ...) I think I'll do what I can and if somebody else is 
> going to review what I am not content with (I'll leave those strings 
> marked as fuzzy) this will improve things.

Let me know if you finished with rough translations. I would like to 
review them afterwards to avoid double work done by you and me.

> 2.
> On the camera and lens tab there is a "Reset..." button (which should 
> read "Reset ..." I believe) and in the following dialogue there is a 
> string "Lens parameters" that is translated in the PO file but still 
> displayed in English.

The tripple points are commonly used to note about a following dialog 
and no direct action. I used the notation without space so far.

> 6.
> Among the untranslated strings there are mostly projection names. For 
> these I am not quite sure about the translations. I believe we should 
> stick to keeping the English expressions in brackets behind the 
> translations because in conversations (e.g. on the net) even German 
> speakers mostly use them.
> Suggestions (German speakers: please comment!):
> Lambert Cylindrical Equal Area =? Lambert flächengleiche/flächentreue P.
> Lambert Equal Area Azimuthal =? Lambert flächengleiche Azimutalproj.
> Albers Equal Area Conic =? Albers flächengleiche Kegelprojektion
> Equisolid =? raumwinkelgleiche Projektion
> Biplane =? Zwei-Ebenen-Projektion (Triplane: analogue)
>

The naming of the projections ... Well, I have currently no idea how to 
handle them especially I don't know about the commonly used naming in 
german. Maybe the supposed translations are fine or there is a special 
terminology available. If it dawns on me I let you know.

Guido



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: libpano13-2.9.14_beta2 released

[Guido Kohlmeyer]

Dear Bruno,

there is currently no negative feedback regarding my Albers projection 
fix, thus please commit the attached file to the trunk. I have no write 
access to the repository. The file includes the main fix and additional 
code simplifications in the function that was touched.

Kind regards,
Guido

Bruno Postle schrieb:
> A question:  libpano13-2.9.14_beta2 was released seven weeks ago and 
> there have been no bug reports, can I assume that this version is ok 
> for a 'stable' release?
> 
> Who is using it?  Is it in the any of the current hugin binary 
> snapshot bundles?
> 

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

/* Panorama_Tools   -   Generate, Edit and Convert Panoramic Images
   Copyright (C) 1998,1999 - Helmut Dersch  d...@fh-furtwangen.de
   
   This program is free software; you can redistribute it and/or modify
   it under the terms of the GNU General Public License as published by
   the Free Software Foundation; either version 2, or (at your option)
   any later version.

   This program is distributed in the hope that it will be useful,
   but WITHOUT ANY WARRANTY; without even the implied warranty of
   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
   GNU General Public License for more details.

   You should have received a copy of the GNU General Public License
   along with this program; if not, write to the Free Software
   Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.  */

/**/


#include "filter.h"
#include 
#include "f2c.h"

#define R_EPS  1.0e-6   
#define MAXITER 100

#include 


#ifndef abs
#define abs(a) ( (a) >= 0 ? (a) : -(a) )
#endif

#ifdef _MSC_VER
#define isnan(a) _isnan(a)
#define isinf(a) (_fpclass(a) == _FPCLASS_NINF || _fpclass(a) == _FPCLASS_PINF)
#endif

voidmatrix_matrix_mult  ( double m1[3][3],double m2[3][3],double 
result[3][3]);
int polzeros_();


//- Some auxilliary math functions 


// atanh is not available on MSVC. Use the atanh routine from gsl
#ifdef _MSC_VER

#define GSL_DBL_EPSILON2.2204460492503131e-16
#define GSL_SQRT_DBL_EPSILON   1.4901161193847656e-08 

static double
log1p (const double x)
{
  volatile double y;
  y = 1 + x;
  return log(y) - ((y-1)-x)/y ;  /* cancels errors with IEEE arithmetic */
} 

static double
atanh (const double x)
{
  double a = fabs (x);
  double s = (x < 0) ? -1 : 1;

  if (a > 1)
{
  //return NAN;
  return 0;
}
  else if (a == 1)
{
  //return (x < 0) ? GSL_NEGINF : GSL_POSINF; 
  return (x < 0) ? -1e300 : 1e300;
}
  else if (a >= 0.5)
{
  return s * 0.5 * log1p (2 * a / (1 - a));
}
  else if (a > GSL_DBL_EPSILON)
{
  return s * 0.5 * log1p (2 * a + 2 * a * a / (1 - a));
}
  else
{
  return x;
}
} 
#endif

void matrix_mult( double m[3][3], double vector[3] )
{
register int i;
register double v0 = vector[0];
register double v1 = vector[1];
register double v2 = vector[2];


for(i=0; i<3; i++)
{
vector[i] = m[i][0] * v0 + m[i][1] * v1 + m[i][2] * v2;
}
}

void matrix_inv_mult( double m[3][3], double vector[3] )
{
register int i;
register double v0 = vector[0];
register double v1 = vector[1];
register double v2 = vector[2];

for(i=0; i<3; i++)
{
vector[i] = m[0][i] * v0 + m[1][i] * v1 + m[2][i] * v2;
}
}

void matrix_matrix_mult( double m1[3][3],double m2[3][3],double result[3][3])
{
register int i,k;

for(i=0;i<3;i++)
{
for(k=0; k<3; k++)
{
result[i][k] = m1[i][0] * m2[0][k] + m1[i][1] * 
m2[1][k] + m1[i][2] * m2[2][k];
}
}
}

// Set matrix elements based on Euler angles a, b, c

void SetMatrix( double a, double b, double c , double m[3][3], int cl )
{
double mx[3][3], my[3][3], mz[3][3], dummy[3][3];


// Calculate Matrices;

mx[0][0] = 1.0 ;mx[0][1] = 0.0 ;
mx[0][2] = 0.0;
mx[1][0] = 0.0 ;mx[1][1] = cos(a) ; 
mx[1][2] = sin(a);
mx[2][0] = 0.0 ;mx[2][1] =-mx[1][2] ;   

[hugin-ptx] Re: German translation: a few questions about original strings

[Guido Kohlmeyer]

Dear Thomas and all others,

is there any deadline for commiting language inspections?

In the last release I reviewed all strings and tried to find a conform 
speak to get a harmonious appearance. I can do this job again for the 
comming release, but due to limited time I need to know about the string 
freeze and a planned release date. Is there any known so far? Sorry I 
didn't followed the mail traffic in the last time.

Thanks,
Guido

T. Modes schrieb:
> Hi,
> 
> the german translation needs some polishing for the release of 0.8
> 
> Some strings are still missing or marked as fuzzy (so they are not
> translated). For instance: "Run PTBatcherGUI", some strings on reset
> dialog (Color, text in combo box: Reset to exif value/Reset to zero),
> some status messages of PTBatcherGUI: e.g. Complete
> 
> There is also a typo (in PTBatcherGUI, main frame): Ausführliche
> Fortschreittanzeige -> Fortschittsanzeige
> 
> Could the translators please check the translations?
> 
> Thomas
> > 


--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: libpano13-2.9.14_beta2 released

[Guido Kohlmeyer]

Dear Bruno,

I've made a change in math.c (see my mail "Re: GSoC patch ideas" from
2009-03-26), but I didn't checked in the patch so far, because I'm waiting
for some feedback, especially from Daniel German, who has noted that he is
familar with that library and may give some hints.

The patch worked for me and I dind't get a crash any more when setting
invalid values on the Albers projection.

Should I commit the patch to the repository?

Guido

>
> A question:  libpano13-2.9.14_beta2 was released seven weeks ago and
> there have been no bug reports, can I assume that this version is ok
> for a 'stable' release?
>
> Who is using it?  Is it in the any of the current hugin binary
> snapshot bundles?
>
> --
> Bruno
>



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Doxygen and GSOC

[Guido Kohlmeyer]

Dear all,

> Yet, as new code is added, it would be great if the students kept
> doxygen in mind for future students and coders.
>

I would appreciate to make it a mandatory step to document the new code
with comments for doxygen.

Some time ago I searched for a bug in the OpenGL preview parts of Hugin
and a better documentation would be helpful for that task.

Documenting the code with doxygen is quite simple and does not generate
much overhead, because all documentation is done in the source code. Some
changes in a function can be documentaion immediately in the comment block
on begin of that function.

Although all students of the summer of code spend their time on coding and
developing new things it is indead a crucial part to document such work
for following developers. Otherwise their knowledge gets lost in few
moths, because nobody knows about the functionality.

Guido


--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin-0.8.0_beta3 released

[Guido Kohlmeyer]

A test built for windows platform is available on panotools.org:

   http://hugin.panotools.org/testing/hugin/

As usual I prepared only a self-extracting archive without any installer.

Guido

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: GSoC patch ideas

[Guido Kohlmeyer]

Well I cannot rate whether it is too difficult to fix this. I'm too old 
:-) and have know overview knowledge about lib's or hugin's sources. I 
simply follow the approach to narrow a crash down and I wanted to avoid 
double effort.

I digged some hours in the code and hopefully found the reason for the 
crash. For Albers Equal Area projection there are some parameter 
combinations that are prohibited, phi1 = phi1 = 0 and phi1 = -phi2. The 
later one is not handled correctly.

First of all, the calculation of precomputed values does not handle 
these combinations. I implemented checks and simplyfied the calculation.
Additionally the distance calculation does not catch the second 
combination. I removed the error message because many many dialogs 
appear. It is better to catch the prohibited combinations directly in 
Hugin with only one dialog rather than in the lib.

Please find attached a patch for review. I tested it on Win32 (MSVC) and 
no crash occured any more.

Comments are highly appreciated,
Guido


Yuval Levy schrieb:
> Guido Kohlmeyer wrote:
>>> A simple division by zero error in libpano13:
>>>
>>> http://sourceforge.net/tracker/?func=detail&aid=2002617&group_id=96188&atid=613954
>>>
>> I'm currently working on a fix. Maybe it's not wise to do the same.
> 
> do you mean it is too difficult for a student, or are you worried about 
> duplicate effort?
> 
> no worries about duplicate efforts.
> 
> for you it is a bug hunt, for the students it is about showing us that 
> they can hack the code base. There is no requirement for the student 
> patch to be useful or to be applied to the code base when considering 
> them for GSoC.
> 
> 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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

Index: math.c
===
--- math.c  (revision 955)
+++ math.c  (working copy)
@@ -1036,7 +1036,12 @@
 {
 
 //Parameters: phi1, phi2, phi0, n, C, rho0, yoffset
-double phi1, phi2, n, C, rho0, phi0, y1, y2, y, twiceN;
+double phi1, phi2, n, C, rho0, phi0, y1, y2, y;
+double Aux_2N;
+double Aux_sin_phi0; /* value of sinus(phi0) */
+double Aux_sin_phi1; /* value of sinus(phi1) */
+double Aux_sin_phi2; /* value of sinus(phi2) */
+double Aux_1; /* auxiliary variables */
 double phi[] = {-PI/2, 0, PI/2};
 double lambda[] = {-PI, 0, PI};
 int i, j, first;
@@ -1090,11 +1095,21 @@
 
// The stability of these operations should be improved
phi0 = 0;
-   twiceN = sin(phi1) + sin(phi2);
-   n = twiceN /2.0;
-   C = cos(phi1) * cos(phi1) + 2.0 * n * sin(phi1);
-   rho0 = sqrt(C - 2.0 * n * sin(phi0)) / n;
+// precompute sinus functions
+Aux_sin_phi0 = sin(phi0);
+Aux_sin_phi1 = sin(phi1);
+Aux_sin_phi2 = sin(phi2);
 
+   Aux_2N = Aux_sin_phi1 + Aux_sin_phi2;
+n = Aux_2N / 2.0;
+
+// C = cos(phi1) * cos(phi1) + 2.0 * n * sin(phi1);
+C = 1.0 + Aux_sin_phi1 * Aux_sin_phi2;
+// rho0 = sqrt(C - 2.0 * n * sin(phi0)) / n;
+Aux_1 = (C - (Aux_2N * Aux_sin_phi0));
+Aux_1 = ( (Aux_1 > 0) ? (sqrt(Aux_1)) : (0.0) );
+rho0 = ( (n != 0) ? (Aux_1 / n) : (1.7E+308) );
+
im->precomputedValue[0] = phi1;
im->precomputedValue[1] = phi2;
im->precomputedValue[2] = phi0;
@@ -1103,8 +1118,8 @@
im->precomputedValue[5] = rho0;
im->precomputedValue[6] = y;
im->precomputedValue[7] = n*n;
-   im->precomputedValue[8] = sin(phi1) + sin(phi2);
-   im->precomputedValue[9] = twiceN;
+   im->precomputedValue[8] = Aux_2N;
+   im->precomputedValue[9] = Aux_2N;
 
//  printf("Parms phi1 %f phi2 %f pho0 %f, n %f, C %f, rho0 %f, 
%f\n", 
// phi1, phi2, phi0, n, C, rho0, y);
@@ -1258,13 +1273,14 @@
 phi2 = mp->pn->precomputedValue[1];
 
 //lambda where x is a maximum.
-if (phi1 == phi2  &&
-   phi1 == 0.0) {
+if ( (phi1 == phi2 && phi1 == 0.0) 
+|| (phi1 == -phi2) )
+{
// THIS IS A HACK...it needs to further studied
// why this when phi1==phi2==0 
// this functions return 0
// Avoid approximation error
-   PrintError("The Albers projection cannot be used for phi1==phi2==0. Use 
Lambert Cylindrical Equal Area instead");
+   // PrintError("The Albers projection cannot be used for phi1==phi2==0. 
Use Lambert Cylindrical Equal Area instead");
 
*x_src = PI;
return 0;

[hugin-ptx] Re: GSoC patch ideas

[Guido Kohlmeyer]

> A simple division by zero error in libpano13:
>
> http://sourceforge.net/tracker/?func=detail&aid=2002617&group_id=96188&atid=613954
>

I'm currently working on a fix. Maybe it's not wise to do the same.

Guido


--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin crashes when phi1=-phi2 in albers conical

[Guido Kohlmeyer]

I found code in math.c of pano13, namely in function 
albersEqualAreaConic_ParamCheck which is error prone and already 
commented with "The stability of these operations should be improved".
A protection against division by zero is not implemented which may 
result in invalid parameter values.
There exist an additional check whether all parameters are valid, but 
this is not reasonable, because the operations before should only be 
processed if the result will be valid.
I implemented a simply solution but Hugin will still crash when moving 
the sliders for phi1 and phi2. Some additional fix seems to be needed.

Guido

Bruno Postle schrieb:
> On Fri 13-Mar-2009 at 16:12 -0700, allard wrote:
>> Any time, fast or normal preview.Select Albers Conical projection. If
>> phi=-phi2 (even if I just pass the slider through that value), I crash
>> hugin.
> 
> I can't get hugin to crash, both previews just go blank when 
> phi=-phi2.  Note this was first reported a year ago:
> 
> https://sourceforge.net/tracker2/index.php?func=detail&aid=2000332&group_id=77506&atid=550441
> 

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin crashes when phi1=-phi2 in albers conical

[Guido Kohlmeyer]

I tested it only with fast OpenGL preview and it seems that a similar
behaviour occurs on MacOSX. Unfortunately I have no free time until this
weekend. I hope I will find the problem then.

Guido

> Addition: On MacOSX it makes the OpenGL fast preview crash.
> So, on MacOSX it works on standard preview, but it crashes hugin in the
> OpenGL preview.
>
> Harry
>
> 2009/3/17 Harry van der Wolf 
>
>> I can't reproduce it either on MacOSX. However, if I reach phi=-phi2 my
>> preview image "disappears" any other value makes it reappear. I don't
>> know
>> if this behaviour is correct or not.
>>
>> Harry
>>
>>
>> 2009/3/17 Guido Kohlmeyer 
>>
>>
>>> Dear Bruno,
>>>
>>> Thanks for the hint of old bug report.
>>>
>>> Due to the fact that you cannot reproduce the crash, I will try to fix
>>> the
>>> problem in libpano and test whether the crash can be prevented.
>>>
>>> Guido
>>>
>>> >
>>> > On Fri 13-Mar-2009 at 16:12 -0700, allard wrote:
>>> >>
>>> >>Any time, fast or normal preview.Select Albers Conical projection. If
>>> >>phi=-phi2 (even if I just pass the slider through that value), I
>>> crash
>>> >>hugin.
>>> >
>>> > I can't get hugin to crash, both previews just go blank when
>>> > phi=-phi2.  Note this was first reported a year ago:
>>> >
>>> >
>>> https://sourceforge.net/tracker2/index.php?func=detail&aid=2000332&group_id=77506&atid=550441
>>> >
>>> > --
>>> > Bruno
>>> >
>>> > >
>>> >
>>>
>>>
>>>
>>> >>
>>>
>>
>
> >
>



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin crashes when phi1=-phi2 in albers conical

[Guido Kohlmeyer]

Dear Bruno,

Thanks for the hint of old bug report.

Due to the fact that you cannot reproduce the crash, I will try to fix the
problem in libpano and test whether the crash can be prevented.

Guido

>
> On Fri 13-Mar-2009 at 16:12 -0700, allard wrote:
>>
>>Any time, fast or normal preview.Select Albers Conical projection. If
>>phi=-phi2 (even if I just pass the slider through that value), I crash
>>hugin.
>
> I can't get hugin to crash, both previews just go blank when
> phi=-phi2.  Note this was first reported a year ago:
>
> https://sourceforge.net/tracker2/index.php?func=detail&aid=2000332&group_id=77506&atid=550441
>
> --
> Bruno
>
> >
>



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin crashes when phi1=-phi2 in albers conical

[Guido Kohlmeyer]

I can reproduce the case.

What I found so far is the following:
The violation is initiated by call of
transform.transformImgCoord(x, y, 0.0, 90.0) (see OutputProjectionInfo 
(line 38))

This method calls execute_stack_new of panotool library.

I expect during processing of the transformation function stack one 
function will fail and raise the violation.

@Bruno, maybe you will find more ...

Guido

allard schrieb:
> Any time, fast or normal preview.Select Albers Conical projection. If
> phi=-phi2 (even if I just pass the slider through that value), I crash
> hugin.
> WinXP, happens in older versions too, 0.7 maybe even older iirc.
> 
> More details on the error message: 
> http://www.allardkatan.net/misc/hugin/crash-albers-conical.jpg
> 
> Allard
> > 

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin-0.8.0_beta2 released

[Guido Kohlmeyer]

Yuval Levy schrieb:
> I've been fiddling with it for months and have not come to a conclusion. 
> Guido has been more pragmatic and hence was able to publish an SDK. His 
> definition of SDK is what it takes to build the Hugin binary.
> 
> On the other hand, the installer is meant to install all what it takes 
> to run Hugin. This is different from what it takes to build Hugin.
> 
> Strictly speaking, Enblend-Enfuse is needed to run Hugin but not to 
> build it. The same applies to the different control point generators, 
> including Match-n-Shift.
> 
> The SDK is not geared toward the installer. Maybe it should?

Yes, the SDK should contain control point generators as well, but I 
mainly focused on a system to build Hugin. Meanwhile Enblend is nearly 
mandatory for Hugin and Autopano-SIFT-C is a common component as well, 
altough it is patended, which currently doesn't matter for private use.
The control point generators may be provided as an additional package 
well, because there are like "plugins".

Actually I didn't deal with the control point generators and have know 
knowledge which generators are available on windows platform, whether 
there are patended and of which quality there are. I expect there is an 
overview given anywhere, but I didn't searched so far.

If there is a good documentation to build the generators let me know and 
I will integrate them in the SDK too. in case I will

Guido

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: md5 checksums

[Guido Kohlmeyer]

I will consider it, when I prepare the next development shapshot. My build
toolchain is stable since some time and some modification will be a
welcome change.

Guido

>
> Hi all,
>
> a reader of my blog asks me where to find the checksums for a package he
> downloaded, probably from sourceforge or maybe from hugin.panotools.org.
>
> could those who publish packages - whether it is a self-decompressing
> file or a fully fledged installer - also calculate and publish the md5
> checksums?
>
> 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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin-0.8.0_beta2 released

[Guido Kohlmeyer]

At first please look at the tracker on sourceforge if there is any simlar
case already reported. If not please create a new issue with a detailed
description how to reproduce the segmentation fault. Information about the
platform (linux, macos and windows etc.) is mandatory. Messages that were
output in command window are mandatory. I small example is highly
recommended for reproduction and debugging.

Guido

>
> i built this from svn (build 3714) today, along with autopano-sift-c
> and enblend.  during stitching enblend is segfaulting.  are there any
> known issues?  i can post more details on the enblend crash tomorrow
> if needed.
>
> thanks!
>



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin-0.8.0_beta2 released

[Guido Kohlmeyer]

A windows snapshot (SV3714) for testing is available on panotools:
see http://hugin.panotools.org/testing/hugin/index.html

Guido

Bruno Postle schrieb:
> Hi all, this release process has consumed nearly all my spare time 
> for the last few weeks, so I need to slow down a bit.  Even so, it 
> would be nice to get hugin 0.8.0 out, an April release would be six 
> months since 0.7.0.
> 
> What else needs to be done?
> 
> There have been lots of recent changes, so I'd expect these to 
> generate some new bugs.
> 
> I have no idea how near the Windows and OS X packages are.
> 
> There is lots of translation work needed.
> 

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Zone Alarm and Hugin.exe

[Guido Kohlmeyer]

Hugin was detected as a virus in the past, but hugin setup on 
sourceforge contains no virus.
I observed that many virus protection programs will detect a virus, 
although there is no virus is the program. This is a bad trend in the 
last months. For instance you can try to get informations about the 
detected viruses in zone alarm. If they cannot give a detailed 
explanation of the detected virus, it is likely that they simply use 
virus signatures from elsewhere without any check of the validity.

Guido

Incony schrieb:
> I tried to use Hugin today, its been running fine for sometime, but
> the latest update of Zone Alarm has provoked a virus threat, and
> quarantined hugin.exe because it says that hugin has win32.kme in it.
> 
> So.. i  removed hugin and the downloaded again from Sourceforge but
> still the same problem..
> 
> what is it about hugin that virus programs cant deal with?  and
> therefore what can be done..?
> 
> i know that it is unlikely that SourceForge would let loose such a
> virus in free download.. unless it really wanted its own quick
> demise...:)
> 
> so.. can i ignore Zone Alarm and release hugin.exe?  or what?  and how
> can one ensure that the problem can be eliminated?
> 
> else i am back on ptviewer.
> 
> 
> 
> 
> > 

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: OpenGL flicker effect on redraw

[Guido Kohlmeyer]

The flicker effect problem on MSW (Win32) is fixed.
I found some notes in the net to overload the method OnEraseBackground 
to reduce the flickering on MSW (Win32) platform. This is implemented in 
penguin samples project of wxWidgets as well.
Updated files included in SVN3706.
Please test whether is has drawbacks on linux and OSX.

Thanks,
Guido

Guido Kohlmeyer schrieb:
> Maybe will will find here an approach to overcome that annoying effect.
> The display as is seems fine, but I didn't tested all projections so far.


--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Celeste.model is not found on win32

[Guido Kohlmeyer]

A good explanation about the usage of MainFrame and huginApp. I prefered 
  huginApp, because it is the main application, it set the internal 
variables and provides the get function. MainFrame acts only as a 
wrapper for huginApp.

Thanks to Pablo for the clarification of my impressions and Yuv to 
change the calls. I will simplify the pattern in question for celeste 
file name.

Guido


Pablo d'Angelo schrieb:
> Yuval Levy schrieb:
>> Guido Kohlmeyer wrote:
>>> Meanwhile I found huginApp::Get()->GetXRCPath(), which is the same.
>> is there a reason to have twice the same thing, or is this a redundancy? 
>> if it is, from which class does it make sense to get the XRCPath? from 
>> huginApp.h or from MainFrame.h?
> 
> Hmm, I don't remember why I did this. Probably because initially the 
> path was handled by MainFrame and not by HuginApp. Probably 
> MainFrame::GetXRCPath() can now be removed and replaced with 
> HuginApp::GetXRCPath(), which I probably intended to do by somehow 
> forgot to actually do.
> 
> ciao
>Pablo


--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Celeste.model is not found on win32

[Guido Kohlmeyer]

Thanks Yuv,

Meanwhile I found huginApp::Get()->GetXRCPath(), which is the same.
I will check the new code if I'm back at home and modify it if doesn't
match my requirements. Dealing with simple char buffer in the code pattern
seams obsolete, cause wxString and string are available.

Guido

> Guido Kohlmeyer wrote:
>> On win32 the celecte.model file is searched on the path
>> INSTALL_XRC_DIR/data, but the macro INSTALL_XRC_DIR is replaced by
>> "${CMAKE_INSTALL_PREFIX}/share/hugin/xrc" during compiling. Hence the
>> path is fixed, which contradicts the approach to copy the application
>> during setup to a directory chosen by the user.
>> OK, how to solve? I need a variable that holds the current path of hugin
>> application to build a the path to the celeste.model.
>> Any suggestions?
>
> MainFrame::Get()->GetXRCPath()
>
> should be fixed in SVN3702, though I did not test if it breaks Linux. If
> it does, apology.
>
> 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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: OpenGL flicker effect on redraw

[Guido Kohlmeyer]

Sorry, James, that I didn't mentioned the operation system.
I'm dealing only in my Windows world :-)

After some research in the net, it seems that it is a specific problem on
windows, but currently I didn't found any sufficient solution.

Maybe will will find here an approach to overcome that annoying effect.
The display as is seems fine, but I didn't tested all projections so far.

Guido

>
> On Tue, 2009-03-03 at 22:36 +0100, Guido Kohlmeyer wrote:
>> I tested the OpenGL preview. I observed the effect that the redraw
>> flickers heavily during paint. It seems that the background and the
>> foreground of the widget are displayed alternating. I checked the source
>> and the redraw should use the double buffering, but it seems it doesn't
>> work.
>> Are there any others who observed the same effect?
>> I have an old ATI Mobility Radeon 7500 Mobility with OpenGL 1.3 in my
>> Laptop.
>>
>> Any suggestions, what I can test? Maybe some modifications in the
>> source?
>>
>> Guido
>
> What operating system is this on?
> I had a similar system (laptop with old ATI Mobility Radeon and OpenGL
> 1.3) and I got correct double buffering on Linux and OSX.
>
> Under Linux you might be able to get the flickering you describe if
> using a compositing window manager. If this is the case, try with a
> different window manager.
>
>
> James
>
>
>
>
> >
>



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Celeste.model is not found on win32

[Guido Kohlmeyer]

Hi,

On win32 the celecte.model file is searched on the path
INSTALL_XRC_DIR/data, but the macro INSTALL_XRC_DIR is replaced by 
"${CMAKE_INSTALL_PREFIX}/share/hugin/xrc" during compiling. Hence the 
path is fixed, which contradicts the approach to copy the application 
during setup to a directory chosen by the user.
OK, how to solve? I need a variable that holds the current path of hugin 
application to build a the path to the celeste.model.
Any suggestions?

Thanks,
Guido

PS: The following files are affected:
- AssistantPanel.cpp
- CPEditorPanel.cpp
- ImagesPanel.cpp

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] OpenGL flicker effect on redraw

[Guido Kohlmeyer]

I tested the OpenGL preview. I observed the effect that the redraw 
flickers heavily during paint. It seems that the background and the 
foreground of the widget are displayed alternating. I checked the source 
and the redraw should use the double buffering, but it seems it doesn't 
work.
Are there any others who observed the same effect?
I have an old ATI Mobility Radeon 7500 Mobility with OpenGL 1.3 in my 
Laptop.

Any suggestions, what I can test? Maybe some modifications in the source?

Guido

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: New Hugin SDK (MSVC 2008)

[Guido Kohlmeyer]

It is intended to use the precompiled version. Therefore I provided the
precompiled package.
The documentation in the wiki is for those who want to know in detail
what's in and what is changed compared to original packages, or for those
who will create a new SDK. For instance I benefit from the old
documentation to get a basic position for my work.

Guido

>
> Hi Guido,
>
> Thanks for doing all this work. I will try it out when I have time.
> I'm going to use the precompiled version, but it's great that you have
> detailed all the steps so that anyone can build the SDK if they want..
>
> allard
>
> On Mar 1, 4:22 am, Guido Kohlmeyer  wrote:
>> Thanks, the next step will be to update the pages regarding compiling
>> Hugin on Windows. I made some notes during building and will use this
>> infos.



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Changed Enblend/Enfuse options have no effect

[Guido Kohlmeyer]

Ok, now it's clear. I didn't find the properties on the sticher tab, 
more precisely I didn't searched there. In general it is fine to have 
global settings as a template and additionally some project specific.
I think the main problem is, that it is not clear which settings are 
active. The project specific settings can be combined on a separate 
Settings tab. Maybe a task for a GUI redesign in the future.

Guido

Bruno Postle schrieb:
> On Mon 02-Mar-2009 at 00:40 +0100, Guido Kohlmeyer wrote:
>> I changed the options of Enblend and Enfuse in the properties dialog of 
>> Hugin, but these options are not taken into account for the current 
>> project. Neither Save nor Save as write the options to the project file. 
>> If I start a new project, then the options are taken into account and 
>> written to the PTO file as well as the makefile.
> 
> The Properties settings define stuff for new projects, there is a 
> separate place to add enblend/enfuse options for the current project 
> in the Stitcher tab.
> 
> It isn't well explained in the manual and isn't very intuitive 
> anyway.  Maybe changing it in the Preferences should change it for 
> the current project too.
> 

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Changed Enblend/Enfuse options have no effect

[Guido Kohlmeyer]

I changed the options of Enblend and Enfuse in the properties dialog of 
Hugin, but these options are not taken into account for the current 
project. Neither Save nor Save as write the options to the project file. 
If I start a new project, then the options are taken into account and 
written to the PTO file as well as the makefile.
Is this the intent behaviour? If so I didn't see the reason for this 
behavior. Or is it even a bug?

Guido

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: German translation: a few questions about original strings

[Guido Kohlmeyer]

Suggestion see below.

J. Schneider schrieb:
> Hi,
> I'm currently updating the German translation and again I have a few 
> questions about where some original strings appear and so on:

> "Add application"

Something like to add the call of an application. If you click the 
button, you a dialog appears to enter the command. I guess the button 
label is not well chosen. It's the call not the application itself which 
is added. Should be something like: "Add application call" or "Call 
application":
"Aufruf hinzufügen"

> "Remove complete"
> ="Remove those projects which are completed"?

Yes, I even wondered about the button label. I think the original 
english text must be "Remove completed" or "Remove finished". I thought 
that I can delete the whole list with this button, but it removes only 
the completed projects.
Some suggestions for translation:
"Entferne beendete" (klingt etwas steif)
"Entferne erledigte" (finde ich ganz gut)
"Entferne abgeschlossene" (bisschen lang?)

Guido



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: [Win32] hugin-0.8.0.3690-dev-win32.exe for download

[Guido Kohlmeyer]

Sorry for the second mail.
Google was very slow to deliver the mails and I though they were sorted 
out due to the exe link, or they were lost.

Guido


--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] [Win32] hugin-0.8.0.3690-dev-win32.exe for download

[Guido Kohlmeyer]

For testing a current development build of Hugin can be found on
http://hugin.panotools.org/testing/hugin/hugin-0.8.0.3690-dev-win32.exe

The file is a self-extracting archive, no installer (see below)!

Revision information

Hugin  : SVN 3690
Enblend/Enfuse : 3.2 (precompiled)
Autopano-sift-C: SVN 3677 (similar to version 2.5.0)

Contents

The archive contains the Hugin build directory INSTALL/FILES
/bin
/doc
/share

How to install

1) Simply execute hugin-0.8.0.3690-dev-win32.exe
2) Enter a destination path in dialog and click Extract
3) Execute hugin.exe in bin directory

Guido








--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] [Win32] hugin-0.8.0.3690-dev-win32.exe for download

[Guido Kohlmeyer]

For testing a current development build of Hugin can be found on
http://hugin.panotools.org/testing/hugin/hugin-0.8.0.3690-dev-win32.exe

The file is a self-extracting archive, no installer (see below)!

Revision information

Hugin  : SVN 3690
Enblend/Enfuse : 3.2 (precompiled)
Autopano-sift-C: SVN 3677 (similar to version 2.5.0)

Contents

The archive contains the Hugin build directory INSTALL/FILES
/bin
/doc
/share

How to install

1) Simply execute hugin-0.8.0.3690-dev-win32.exe
2) Enter a destination path in dialog and click Extract
3) Execute hugin.exe in bin directory

Guido








--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: New Hugin SDK (MSVC 2008)

[Guido Kohlmeyer]

Thanks, the next step will be to update the pages regarding compiling 
Hugin on Windows. I made some notes during building and will use this infos.

Guido

Tom Sharpless schrieb:
> PS I really wanted to say, magnificent job!  Your SDK and turorial
> make it as easy to build Hugin on Windows as on Linux, perhaps easier.
> 
> Regards, Tom
> 


--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: New Hugin SDK (MSVC 2008)

[Guido Kohlmeyer]

I expected no problems with the SDK, thus it is surprising that the link 
raise problems. Work with thunderbird and firefox.
Try the following link:
http://wiki.panotools.org/Hugin_SDK_%28MSVC_2008%29

Guido

Tom Sharpless schrieb:
> Nope.  I guess you may have to change the title of this page :-<
> 
> -- Tom
> 


--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] [win32] New Hugin SDK (MSVC 2008)

[Guido Kohlmeyer]

Dear all,

I finished the new Hugin SDK and I hope all teething troubles of my 
first attempt are sort out.
You will find the documentation of the SDK on panotools wiki:
http://wiki.panotools.org/Hugin_SDK_(MSVC_2008)
A link to the precompiled SDK is available on this wiki page too.

Have fun and good night,
Guido

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Problem compiling on Windows -- wxWidgets not found

[Guido Kohlmeyer]

Hi Tom,

enblend is the second pitfall to trip into. I included it not in the 
SDK, but I know this was a fault.
You can download it here:
http://downloads.sourceforge.net/enblend/enblend-enfuse-3.2.zip

Decompress it to SDK's directory, that the application is in directory 
"enblend-enfuse-3.2".

Autopano-sift-C is missing too, but the install script will work without 
it. You can simply use the version 2.5.0 that was already included in 
hugin 0.7.0 distribution.

Guido



Tom Sharpless schrieb:
> PS I guess the faulty script is hugin/CMakeModules/win-bundle.cmake.
> 
> 
> On Feb 26, 1:18 pm, Tom Sharpless  wrote:
>> But now another problem.  The install script is failing because there
>> is no enblend in my build.
>>
>> There now seems to be conditional code in cmake_install.cmake for
>> various "components", such as enblend; however it doesn't seem to
>> work.  Here is the block for enblend:
>>
>> IF(NOT CMAKE_INSTALL_COMPONENT OR "${CMAKE_INSTALL_COMPONENT}"
>> STREQUAL "Unspecified")
>>   FILE(INSTALL DESTINATION "${CMAKE_INSTALL_PREFIX}/doc/enblend" TYPE
>> FILE FILES
>> "J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/AUTHORS"
>> "J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/ChangeLog"
>> "J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/COPYING"
>> "J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/NEWS"
>> "J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/README"
>> "J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/README_WINDOWS.txt"
>> "J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/TODO"
>> "J:/HuginSDK/hugin/ENBLEND_EXE_DIR-NOTFOUND/VIGRA_LICENSE"
>> )
>> ENDIF(NOT CMAKE_INSTALL_COMPONENT OR "${CMAKE_INSTALL_COMPONENT}"
>> STREQUAL "Unspecified")
>>
>> That "DIR-NOTFOUND" suggests that something higher up in the script
>> generating chain is not doing its job.
>>
>> Either CMake support for installing is not good enough, or we aren't
>> using it right.  Or both.
>>
>> BTW where am I supposed to get enblend, and how integrate it in the
>> build?  Could I do somethng similar for autopano-sift-c?
>>
>> -- Tom
>>
>> On Feb 26, 9:14 am, Tom Sharpless  wrote:
>>
>>> Thanks Guido
>>> Installing CMake 2.6.3 did the trick.
>>> Thank you very much for setting up this build environment.  I know how
>>> much work it took!
>>> -- Tom
> > 

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Problem compiling on Windows -- wxWidgets not found

[Guido Kohlmeyer]

Dear Tom,

I should be sufficient to copy the attached file to directory
\share\cmake-2.6\Modules and to rename it to
FindwxWidgets.cmake

Guido

>
> With Guido's new SDK and the current Hugin svn, I get a basic
> cmakesetup configuration error: "wxWidgets not found"; plus a lot of
> consequential ones if I try to fix by hand -- and if I do that until
> cmakesetup says "OK", the wxWidgets include directory is still not in
> the MSVC projects, so hugin1 etct won't build.
>
> I always use a separate build tree, so as to keep the source tree
> clean.  Both are rooted in the same directory that contains the SDK.
>
> Does anybody know what is wrong?
>
> Thanks, -- Tom
> >
>

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

# - Find a wxWidgets (a.k.a., wxWindows) installation.
# This module finds if wxWidgets is installed and selects a default
# configuration to use. wxWidgets is a modular library. To specify the
# modules that you will use, you need to name them as components to
# the package:
# 
# FIND_PACKAGE(wxWidgets COMPONENTS base core ...)
# 
# There are two search branches: a windows style and a unix style. For
# windows, the following variables are searched for and set to
# defaults in case of multiple choices. Change them if the defaults
# are not desired (i.e., these are the only variables you should
# change to select a configuration):
#
#  wxWidgets_ROOT_DIR  - Base wxWidgets directory
#(e.g., C:/wxWidgets-2.6.3).
#  wxWidgets_LIB_DIR   - Path to wxWidgets libraries
#(e.g., C:/wxWidgets-2.6.3/lib/vc_lib).
#  wxWidgets_CONFIGURATION - Configuration to use
#(e.g., msw, mswd, mswu, mswunivud, etc.)
# 
# For unix style it uses the wx-config utility. You can select between
# debug/release, unicode/ansi, universal/non-universal, and
# static/shared in the QtDialog or ccmake interfaces by turning ON/OFF
# the following variables:
#
#  wxWidgets_USE_DEBUG
#  wxWidgets_USE_UNICODE
#  wxWidgets_USE_UNIVERSAL
#  wxWidgets_USE_STATIC
#  
# The following are set after the configuration is done for both
# windows and unix style:
#
#  wxWidgets_FOUND- Set to TRUE if wxWidgets was found.
#  wxWidgets_INCLUDE_DIRS - Include directories for WIN32
#   i.e., where to find "wx/wx.h" and
#   "wx/setup.h"; possibly empty for unices.
#  wxWidgets_LIBRARIES- Path to the wxWidgets libraries.
#  wxWidgets_LIBRARY_DIRS - compile time link dirs, useful for
#   rpath on UNIX. Typically an empty string
#   in WIN32 environment.
#  wxWidgets_DEFINITIONS  - Contains defines required to compile/link
#   against WX, e.g. -DWXUSINGDLL
#  wxWidgets_CXX_FLAGS- Include dirs and ompiler flags for
#   unices, empty on WIN32. Esentially
#   "`wx-config --cxxflags`".
#  wxWidgets_USE_FILE - Convenience include file.
#
# Sample usage:
#   FIND_PACKAGE(wxWidgets COMPONENTS base core gl net)
#   IF(wxWidgets_FOUND)
# INCLUDE(${wxWidgets_USE_FILE})
# # and for each of your dependant executable/library targets:
# TARGET_LINK_LIBRARIES( ${wxWidgets_LIBRARIES})
#   ENDIF(wxWidgets_FOUND)
#
# If wxWidgets is required (i.e., not an optional part):
#   FIND_PACKAGE(wxWidgets REQUIRED base core gl net)
#   INCLUDE(${wxWidgets_USE_FILE})
#   # and for each of your dependant executable/library targets:
#   TARGET_LINK_LIBRARIES( ${wxWidgets_LIBRARIES})

#
# FIXME: check this and provide a correct sample usage...
#Remember to connect back to the upper text.
# Sample usage with monolithic wx build:
#
#   FIND_PACKAGE(wxWidgets COMPONENTS mono)
#   ...


# NOTES
#
# This module has been tested on the WIN32 platform with wxWidgets
# 2.6.2, 2.6.3, and 2.5.3. However, it has been designed to
# easily extend support to all possible builds, e.g., static/shared,
# debug/release, unicode, universal, multilib/monolithic, etc..
#
# If you want to use the module and your build type is not supported
# out-of-the-box, please contact me to exchange information on how
# your system is setup and I'll try to add support for it.
#
# AUTHOR
#
# Miguel A. Figueroa-Villanueva (miguelf at ieee dot org).
# Jan Woetzel (jw at mip.informatik.uni-kiel.de).
#
# Based on previous works of:
# Jan Woetzel (FindwxWindows.cmake),
# Jorgen Bod

[hugin-ptx] Re: Problem compiling on Windows -- wxWidgets not found

[Guido Kohlmeyer]

Dear Tom,

please use CMake 2.6.3 which has an updated script to find wxWidgets.
The script in CMake 2.6.2 searched for only some of the libraries, but in
the SDK the Unicode libs are only available. In the new CMake version the
script will find all varaints of libs. Additionally the old script has
problems to find the libs, if they are generated using the Visual Studio
GUI, becuase some files are not created, which are build if you use the
command line approach.
Nevertheless, currently I prepare a detailed description to build the
Hugin SDK with Visual C++ 2008. I hope that this information will be
available on panotools wiki until this weekend.

Guido

>
> With Guido's new SDK and the current Hugin svn, I get a basic
> cmakesetup configuration error: "wxWidgets not found"; plus a lot of
> consequential ones if I try to fix by hand -- and if I do that until
> cmakesetup says "OK", the wxWidgets include directory is still not in
> the MSVC projects, so hugin1 etct won't build.
>
> I always use a separate build tree, so as to keep the source tree
> clean.  Both are rooted in the same directory that contains the SDK.
>
> Does anybody know what is wrong?
>
> Thanks, -- Tom
> >
>



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Question about autopano-sift-c repository

[Guido Kohlmeyer]

Bruno Postle schrieb:
> 
> Go ahead and commit it, I assume that the build just uses wxwidgets 
> for the bundled image libraries.
> 
Thanks for the feedback. Your right, only the image libraries from 
wxWdgets are needed.

Guido

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Question about autopano-sift-c repository

[Guido Kohlmeyer]

One question to the old hands :-)

I made some updates on CMake files of autopano-sift-C to find and use 
current versions of wxWidgets (2.8.9) and libxml2 (2.7.3). Furthermore I 
add search directory of pano13 as stored in my SDK.
Due to the fact that the current stable version 2.5.0 can be checked out 
based in the according label, may I commit the changes to the trunk?

Guido

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Hugin 0.8 SVN3649 Windows installer available

[Guido Kohlmeyer]

Bruno Postle schrieb:
> 
> Note that we don't expect Linux packagers to ask permission to 
> release snapshots, so there is no problem doing the same for 
> Windows, just please point people who don't want to participate in 
> testing to the 'stable' installer on sourceforge.
> 
> Slightly off-topic, does hugin still build with mingw?  Fedora now 
> has most of the hugin dependencies as mingw-* cross-compiler 
> packages, it is potentially possible to build an NSI Windows 
> installer entirely on Linux using the same tools used to build RPMs.
> 

I provided shapshots of 0.7.0 only through hugin-ptx list, because the 
developers should test the software before release. If some shapshots or 
unstable versions are provided via sourceforge is must be clear for the 
user, that it is a version under development which may not work as 
expected. Otherwise a (windows) user may be disapointed about this great 
peace of software. I even remember of the release of 0.7.0. Right after 
the release some users complained about crash during makefile export, 
although they saved their work without any picture selected. Such misuse 
was not covered by the exporter module. Therefore I suppose to release 
windows builds in a nearly stable state. My impression is that windows 
users are not familiar with software that may have small problems. 
Actually astonishing 'cause they are using windows :-)

I never build with mingw, only Visual C++ 2008 EE.

Guido

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Hugin 0.8 SVN3649 Windows installer available

[Guido Kohlmeyer]

During labor pains of hugin 0.7.0 I prepared shapshots without any
installer for the development community in loose intervals. This was done
by some other developers too. I used the panotools server which was kindly
provided by the guys here and published the new download link here in the
group, like I've done for the SDK.
Additionaly I prepared the windows setup for 0.7.0 which can be downloaded
on sourceforge. As you mentioned, some modifications were necessary to
build a setup, but if you have any questions about the original files,
maybe ask Yuval for support. He built the initially files in SVN.

Guido

>
> Hi guys,
>
> I also made my build available for the world. See
> http://www.allardkatan.net/misc/hugin/index.html . I built an
> installer from the 'package' in the SDK. I had to change a few minor
> things in the CMAKELISTS.TXT file because it would name the program
> and install directory Cmake, instead of hugin. And it does not install
> the start menu items correctly, only the uninstaller is included in
> the menu. But for the rest it works fine..
>
> BTW, what is the policy regarding making development snapshots
> available to the public? I had not made my build available because I
> (wrongly?) assumed earlier you'd prefer to keep this limited until a
> stable release is planned. If not, why are there no development
> snapshots or betas available from SF?
> >
>



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Hugin Build Version 3649 for Windows

[Guido Kohlmeyer]

Dear Yuv,

I seems that lxegs used my SDK, thus exiv2 0.18 and wxWidgets 2.9.8.

Guido

>
> lxegs wrote:
>> i have compiled hugin with Visual Studio 2008 under Vista x86 and
>> tested in Vista x86/x64.I suppose it will work under XP
>
> good job! which version of exiv2 and of wxWidgets did you use?
>
>
>> if someone has an idea how to compile enblend svn (problems with lcms)
>> and autopano-sift-c svn , i can try it
>
> http://wiki.panotools.org/Build_Hugin_for_Windows_with_SDK#Build_enblend_3
>
> autopano-sift-c has a CMake build. Just grab it from SVN at
> https://hugin.svn.sourceforge.net/svnroot/hugin/autopano-sift-C/trunk/,
> start the Visual Studio command promt, run cmakesetup.exe.
>
>
>> I will try to update this package once a week or when changes are
>> significative.
>
> THANK YOU!
> 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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Hugin Build Version 3649 for Windows

[Guido Kohlmeyer]

The complete package of all files incl. autopano-sift and enblend/enfuse 
will be 100MB. 7-zip can compress this amount down to about 14MB (use 
ultra compression and solid archive).

Guido

Bart.van.Andel schrieb:
> Hi,
> 
> First of all, thanks for sharing your effort! That said, I'd like to
> make a little suggestion. It seems like free.fr is not a blazingly
> fast host (either that or a huge amount of people are all downloading
> your file ;) To speed up things, a smaller file size would help a lot,
> especially if you're really planning to do a weekly update. To this
> end, 7-Zip does a far better job than standard (Win)Zip. And it's free
> too (see 7-zip.org). Last time I checked with a Hugin build, the 7z
> archive was less than half the size of the zip archive holding the
> exact same contents! If you're afraid people don't have 7-zip, you can
> add a sfx-part to create a self-extracting 7z file (this can be done
> from the 7-zip compress dialog).
> 
> I'm curious for the build... just another 11 minutes... :)
> 
> Cheers,
> Bart
> > 

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin SDK for windows

[Guido Kohlmeyer]

Some comments about the "NOTFOUNDS" in cmake.

PANO12_*
This is not a probelm and can be neglected, because pano13 is found and
pano13 is the newer one. PANO12_* is only used if PANO13 is not found.
Therefore no error comes up.

AP_SIFT_DIR
ENBLEND_EXE_DIR
Enblend as well as Autopano-SIFT are standalone tools that are not
included in the SDK so far. They are available on my machine and this is
obviously the reason why I got no error. I even though that hugin will
build and install without enblend. Well, seems not the case.

wxWidgets_wxrc_EXECUTABLE
This variable is set by the FindwxWidgets module of cmake, but hugin
doesn't need it. The missing variable can be neglected.

Except for the ENBLEND_EXE the SDK seems to work. Thank you for testing. I
will improve my environment and maybe release an updated one.

Guido

>
> I succesfully built and ran SVN nr 3640. Cmake comes with a few errors/
> missing directories but only the Enblend directory has to be set
> manually to be able to built. The rest apparently does not matter.
> These are the 'notfounds'
>
> PANO12_INCLUDE_DIR-NOTFOUND
> PANO12_LIBRARY-NOTFOUND
> ENBLEND_EXE_DIR-NOTFOUND
> AP_SIFT_DIR-NOTFOUND
> wxWidgets_wxrc_EXECUTABLE-NOTFOUND
>
> The only thing that I had to do that was not in the 'manual' (Guido's
> post), was to set the Enblend directory in Cmake. Without that the
> INSTALL will not build.
> No bugs encountered in the program. I could stitch two images and save
> the output, work with fast preview, etc. I tried to make an HDR, and
> although there were no bugs the output looked all funny with colors
> that should not be there. But I've never done HDR in hugin (and hardly
> elsewhere) before and haven't consulted manuals so I suspect user
> error.
>
> So, as far as I can tell, we have a winner here.
>
> I forgot to mention: I'm on Win XP SP3, 2Gb Ram, Intel T2300 1.66 GHz.
> >
>



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin SDK for windows

[Guido Kohlmeyer]

Dear allard,

The backslash before the space character is mandatory to escape the space
charater. Otherwise the space will be a separator and only the part until
the space is assigned to the variable on the left hand side of the
equation sign.
The backslash between the drive letter and the colon is the main problem.

By the way the makefile is generated automatically when you start a stich
process. If you want to play with makefiles you can even start the
makefile using the tool make: make -f 

Guido

>
> I tried to manually change the makefile, but this did not work,
> because hugin overrides that somehow. The makefile is only saved when
> saving the project, but if you manually edit the makefile and press
> 'stitch now', you still get the same error. So i cannot check if the
> whole stitching process works, but at least the paths are correct if
> the backslashes between C and : , and before the space, are removed.
> So
>
> "NONA=C\:\Program\ Files\hugin\homebuild\hugin_build\INSTALL\FILES\bin
> \nona "
> should be
> "NONA=C:\Program Files\hugin\homebuild\hugin_build\INSTALL\FILES\bin
> \nona "
>
>
>>
>> So If I understand it correctly removing backslashe from C\: makes it
>> work?
> >
>



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin SDK for windows

[Guido Kohlmeyer]

Yes, this should work. On windows platform the syntax of an absolute path is:
:\path\to\file\
For example:
C:\My Photos\Ireland 2008\DSCN0012.jpg

As you see spaces are possible and were already supported in hugin 0.7.0.
I expect omitting the (back)slash between drive letter and colon will fix
the problem.

Guido

>
> So If I understand it correctly removing backslashe from C\: makes it
> work?
>
> >
>



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin SDK for windows

[Guido Kohlmeyer]

I appologize about the missing information about the SDK and the other
tools that are needed to work with hugin.
The SDK has (should have) currently all components to build, but there are
some additional tools needed to run. These tools are e.g. autopanao-sift-c
and enblend/enfuse. I decided not to include them in the SDK, but to store
them in an additional package. Maybe the wrong decision.
Therefore the discussion here to get rid of the teething troubles and to
find a good solution what should be in and out.

So far, thank you for your comments. I'm looking forward for other's
feedback, too

Guido

>
> allard wrote:
>> It builds! I needed to add a bunch of empty files named README, TODO
>> etc because building INSTALL won't work
>
> Guido's SDK is short of what it needs to build the install target.
> You'll need at least enblend-enfuse, and also autopano-sift-c IIRC.
>
> Your best bet is to take a previous version of the SDK and overwrite it
> with Guido's newer components.
>
>
>> make: *** No rule to make target `FILENAME REMOVED BY ME, EXISTING
>> FILE', needed by `pano8v.tif'.  Stop.
>
> May be related to the above.
>
> 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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin SDK for windows

[Guido Kohlmeyer]

The libpano12 is not needed if libpano13 is found, which should be the
case. libpano12 is the old version of the panotools library and libpano13
is the current version.
I will check the problem with wxrc later.

>
> I'm also using CMake 2.6.2. I got the latest revision of hugin after
> your previous post, but I just updated and got version 3635. In fact,
> the build yesterday finished, but the program does not work, I think
> it has to do with the wxrc executable that cannot be found in
> wxwidgets. I can't find it either, not even in the downloaded and
> installed version I have (2.8.9). It tried building the wxrc project
> in wxwidgets using VS2008 but that only gave me a  .obj file, not an
> executable. I'm messing around here and I don't really know what I'm
> doing half the time but it's fun.
> Cmake also looks for a libpano12 directory and library, which is not
> included in the SDK. Is that correct? I'll try again see what happens
>
> allard
>
> On Feb 10, 1:06 pm, "Guido Kohlmeyer"  wrote:
>> Dear Allard,
>>
>> I used cmake 2.6.2 to build hugin and tested the build process with this
>> version.
>> It is mandatory to get the latest revision of hugin from SVN, because I
>> changed some cmake files to find wxWidgets, boost and exiv2.
>> I even read about problems. I trapped into one pitfall, because I
>> started
>> to build the wxWidgets package in Visual Studio. Doing this some files
>> where not generated, which are search for by the find module of cmake.
>> I updated this module in my cmake installation.
>> After switching the build process of wxWidgets to the command line, I
>> expected that the old cmake module will work too. Maybe this is not the
>> case.
>>
>> I have to test it and to note about it in my build diary.
>>
>> Guido
>>
>>
>>
>> > Hi Guido,
>>
>> > Thanks for this! I'm trying it right now. In fact, VC is building as
>> > I'm typing. Never done this before. Well not entirely true. Tried once
>> > before to build hugin from an older SDK. It did not work for me at
>> > that time. This time i got similar errors from Cmake about not being
>> > able to find a tiff package. I found a patch to Cmake's finding thingy
>> > here:
>> >http://public.kitware.com/cgi-bin/viewcvs.cgi/Modules/FindwxWidgets.c...
>> > That got me past the configuration stage, further than I came last
>> > time.
>>
>> > I know only a tiny bit of programming and I am a total newbie at this
>> > Cmake stuff, I just have my general computer skills to help me. So I
>> > guess I'm a good testcase.
>>
>> > VC is compiling fulla now... Let's see what comes out
>>
>> > thanks,
>> > Allard
> >
>



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin SDK for windows

[Guido Kohlmeyer]

Dear Allard,

I used cmake 2.6.2 to build hugin and tested the build process with this
version.
It is mandatory to get the latest revision of hugin from SVN, because I
changed some cmake files to find wxWidgets, boost and exiv2.
I even read about problems. I trapped into one pitfall, because I started
to build the wxWidgets package in Visual Studio. Doing this some files
where not generated, which are search for by the find module of cmake.
I updated this module in my cmake installation.
After switching the build process of wxWidgets to the command line, I
expected that the old cmake module will work too. Maybe this is not the
case.

I have to test it and to note about it in my build diary.

Guido

>
> Hi Guido,
>
> Thanks for this! I'm trying it right now. In fact, VC is building as
> I'm typing. Never done this before. Well not entirely true. Tried once
> before to build hugin from an older SDK. It did not work for me at
> that time. This time i got similar errors from Cmake about not being
> able to find a tiff package. I found a patch to Cmake's finding thingy
> here:
> http://public.kitware.com/cgi-bin/viewcvs.cgi/Modules/FindwxWidgets.cmake?root=CMake&view=markup
> That got me past the configuration stage, further than I came last
> time.
>
> I know only a tiny bit of programming and I am a total newbie at this
> Cmake stuff, I just have my general computer skills to help me. So I
> guess I'm a good testcase.
>
> VC is compiling fulla now... Let's see what comes out
>
> thanks,
> Allard
>
> >
>



--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: hugin SDK for windows

[Guido Kohlmeyer]

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  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 \hugin
2) Select the folder, right-click > SVN Checkout...
4) In entry  enter 
https://hugin.svn.sourceforge.net/svnroot/hugin/hugin/trunk
5) Select HEAD revision
6) Press OK
7) Start cmake
8) In entry  enter: \hugin
9) In entry  enter: \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  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 -MM-DD
Press Configure button
14) Press OK
15) Open the generated Visual Studio solution file 
\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 \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 downlo

[hugin-ptx] Re: llibpano (SVN944) won't built on windows

[Guido Kohlmeyer]

Dear Bruno,

Thank you for the fix. The bug report 2577715 about the same case was 
not written by me:

http://sourceforge.net/tracker/index.php?func=detail&aid=2577715&group_id=96188&atid=613954

If I create a bug report I use me account name, e.g. if discussion about 
the bug and expected behaviour is necessary.

Guido

Bruno Postle schrieb:
> On Sun 08-Feb-2009 at 01:17 +0100, Guido Kohlmeyer wrote:
>> You commited the modified file "filter.c". The only modification is an 
>> additional include of "unistd.h". Typically this file is not available 
>> on windows and the include is not needed to compile. What are the 
>> reasons to include this header file?
> 
> I went through the tracker and applied any patches that looked 
> reasonable, this change was this one:
> 
> http://sourceforge.net/tracker/index.php?func=detail&aid=2163691&group_id=96188&atid=613956
> 
> I've just committed the fix (I assume) you left on the tracker.
> 

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] llibpano (SVN944) won't built on windows

[Guido Kohlmeyer]

Dear Bruno,

You commited the modified file "filter.c". The only modification is an 
additional include of "unistd.h". Typically this file is not available 
on windows and the include is not needed to compile. What are the 
reasons to include this header file?

Guido

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] hugin SDK for windows

[Guido Kohlmeyer]

Good morning,

I prepared a SDK to build hugin on windows platform. It is based on 
current releases of boost, wxwindows, libpano and other tools.
I applied the aproach to bundle only the necessary includes and libs, 
without any documentation. The result is a 350MB package (34MB archive).
Currently I run only a build test with hugin. Before I'll release the 
package I want to give the chance to test it. Are there any developers 
interessted to do a test.
The other point is web-space. Any suggestions, where I can upload the 
package?

Guido

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Installer?

[Guido Kohlmeyer]

So far as I know MSI is the recommended type of installer on Vista, more 
precisely it is the only supported kind of installer. But I expect the 
old EXE type will work as well. Didn't tested it, because I own only 
Windows XP.

Guido

Yuval Levy schrieb:
> what is the advantage of using MSI installer over the currently 
> supported InnoSetup?
> 
> When I took on the task of making the Windows installer, I looked into 
> the MSI code in SVN and it was very uninviting to learn. I decided to 
> use InnoSetup, which is Open Source and is used by a large number of 
> free and commercial projects to distribute their code to Windows.
> 
> Yuv
> 
> 
> 
> John McAllister wrote:
>> Really looking forward to the upcoming release of the Windows MSI 
>> release of Huggy 7.
>> Will be the the first time I upgrade my Hugin installation since the 
>> release of Vista, and John Nava's working, properly made,  Windows 
>> installer of Hugin (paleolithic version).
>> Can't wait.
>> Happy new year...
>>
> 
> 
> > 

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Installer?

[Guido Kohlmeyer]

Dear John,

An installer for windows platform can be found here:
http://sourceforge.net/project/showfiles.php?group_id=77506&package_id=78426

It is not a MSI package, but rather a simple EXE setup file. Currently I 
have neither time or need (only windows XP :-) to generate a MSI installer.

Guido

John McAllister schrieb:
> Really looking forward to the upcoming release of the Windows MSI 
> release of Huggy 7.
> Will be the the first time I upgrade my Hugin installation since the 
> release of Vista, and John Nava's working, properly made,  Windows 
> installer of Hugin (paleolithic version).
> Can't wait.
> Happy new year...
>
> >

--~--~-~--~~~---~--~~
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---