[hugin-ptx] Re: Compiling lens calibrate

[Kornel Benko]

Am Thursday 10 September 2009 schrieb T. Modes:
> 
> Hi Tim,
> 
> I tried to run lens_calibrate.
> But it crashed because there are no folder named "output". After
> creating the output folder it run, but it did not check the output.
> 
> Could you fix the code, so that
> a) save the output on a other place (e. g. temp folder)
> or b) check if the output folder exists and create it if necessary

Ok, it should not crash. I think a warning were reasonable. But creating folder 
(which may well not be desired)
can also make some trouble.

> Thomas

Kornel
-- 
Kornel Benko
kornel.be...@berlin.de


signature.asc
Description: This is a digitally signed message part.

[hugin-ptx] Re: [OSX] hugin-mac-2009.2-Beta3 for download

[Harry van der Wolf]

2009/9/9 Carl von Einem 

>
> nona crashed almost instantly on my G5 / OSX 10.4.11
>
> I'll submit a bug report. Wow, SF's interface is always changing, and
> everytime it seems to get worse...
>
> The Bug tracker is at
> 
> then search for "add new" and I hope that works...
>
>
Hi Carl,

Thanks for testing. In the bug ticket you specify that nona with GPU
immediately crashes. I assume that nona wthout GPU usage does work
correctly?

Harry

--~--~-~--~~~---~--~~
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 lens calibrate

[T. Modes]

Hi Tim,

I tried to run lens_calibrate.
But it crashed because there are no folder named "output". After
creating the output folder it run, but it did not check the output.

Could you fix the code, so that
a) save the output on a other place (e. g. temp folder)
or b) check if the output folder exists and create it if necessary

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: Installer for SVN 4352 / 2009.2

[T. Modes]

On 9 Sep., 11:45, Ad Huikeshoven  wrote:
> Hi,
>
> Yuval asked me to build an installer based on 2009.2 branch in stead of
> trunk. This morning I succeeded in packaging something. It should be up 
> athttp://hugin.huikeshoven.org/now.
>
> Ad Huikeshoven

Hi Ad,

did you also updated the way the cp generators are installed?

So you could add settings for only these cp generators which are
installed with the correct paths.

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: cleaning up the Hugin-Libpano link

[T. Modes]

On 9 Sep., 05:23, Yuval Levy  wrote:
> Hello developers,
>
> I have not had any negative feedback about my patch to remove references
> to libpano12 from the Hugin code base. I will commit it before issuing
> the next tarball in the 2009.2.0 release cycle, which I intend to make a
> release candidate.
>

Hi Yuv,

you were to fast for me ;-)
I was at testing your patch as you have commited it yet.

It works on windows, but you have removed the progress windows of the
optimiser (ptwxdlg.h and ptwxdlg.cpp).
This windows are helpfull when optimising big or problematic project.
Now there is no feedback when hugin is optimising, this is not nice.
The progress windows showed that hugin was still working. So someone
impatient could think hugin has crashed.
Could you restore the progress windows?

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: Tilt transformation...

[Gerry Patterson]

On Sep 9, 2009, at 10:56 PM, dmg  wrote:

>
>> Hello,
>>
>> I am confused.  Would one not be able to continue development in the
>> same branch that Dev made the initial changes in? Why is another
>> branch needed? I apologize if I am missing something obvious.
>>
>> Gerry
>
> are you talking libpano or hugin?
>
> -dmg
>
> -~--~---
>

Hello,

And that would be the obvious something that I was missing.  Again, my  
apologies.  It is my understanding that this code currently lives in  
libpano.  Correct?

So you are looking for changes to be made to hugin to allow for  
selecting these new parameters in the images tab for optimization.   
The optimization itself would be continued to be handled by a call to  
libpano.  Correct?

Best Regards,

Gerry

--~--~-~--~~~---~--~~
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: Tilt transformation...

[Yuval Levy]

dmg wrote:
>> Hello,
>>
>> I am confused.  Would one not be able to continue development in the
>> same branch that Dev made the initial changes in? Why is another
>> branch needed? I apologize if I am missing something obvious.
>>
>> Gerry
> 
> are you talking libpano or hugin?

Dev never committed anything to 
http://hugin.svn.sourceforge.net/viewvc/hugin/hugin/branches/gsoc2009_mosaic/

:-(
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: Tilt transformation...

[dmg]

> Hello,
>
> I am confused.  Would one not be able to continue development in the
> same branch that Dev made the initial changes in? Why is another
> branch needed? I apologize if I am missing something obvious.
>
> Gerry

are you talking libpano or hugin?

-dmg

--~--~-~--~~~---~--~~
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: Tilt transformation...

[Gerry Patterson]

On Sep 9, 2009, at 4:03 PM, D M German  wrote:

>
>
>
> Now, the real question for hugin developers: can somebody create a
> branch of hugin that supports these new parameters during the
> optimization? shearX, shearY, tiltX, tiltY, tiltZ and tiltScale?
>
>
> I haven't committed my code but will do soon. in its current state the
> optimizer nor the cropping works (we need the forward transform for  
> that).
>

Hello,

I am confused.  Would one not be able to continue development in the  
same branch that Dev made the initial changes in? Why is another  
branch needed? I apologize if I am missing something obvious.

Gerry 
  

--~--~-~--~~~---~--~~
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-2009.2.0_beta3 released

[Tduell]

Hullo Yuv, All,

On Sep 8, 2:41 am, Yuval Levy  wrote:
> Panorama stitching and more. A powerful software package for creation
> and processing of panoramic images.
>
> A hugin-2009.2.0_beta3 (beta release 3) tarball is available here:
>
> 
>
> This is a beta release, i.e. it may not work for you.
[snip]

I can report that the beta release 3 builds OK on Fedora 11 x86_64 and
that all appears to be working OK (Nvidia 9600GT gpu 512 MB, using
Nvidia's 185.18.36 drivers and libs).
If anyone would like these Fedora 11 x86_64 packages (Hugin, Hugin-
base) please let me know.
I may also be able to build Fedora 11 i386 packages as well.

Cheers,
Terry




--~--~-~--~~~---~--~~
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: Tilt transformation...

[Bruno Postle]

On Wed 09-Sep-2009 at 19:27 -0400, Yuval Levy wrote:
>dmg wrote:
>>> how does this interact with James' new layout (the "j" parameters in the
>>> .pto files) ?
>>
>> Is this read by libpano tools? I doubt it. In that case, not at all.
>
>should it be read by libpano tools?

The 'j' parameter is really a hint for future tools that don't exist 
yet.  Currently in hugin we define a 'stack' purely by looking at 
positions - Images that overlap by 90% are a 'stack', the 'j' 
parameter would allow this relationship to be explicit rather thn 
implicit.

-- 
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: Tilt transformation...

[dmg]

Remember that the PTO files are not compatible with libpano. One needs
to use the export feature in
hugin.

On Wed, Sep 9, 2009 at 4:27 PM, Yuval Levy  wrote:
>
> dmg wrote:
>>> how does this interact with James' new layout (the "j" parameters in the
>>> .pto files) ?
>>
>> Is this read by libpano tools? I doubt it. In that case, not at all.
>
> should it be read by libpano tools?
>
> Yuv
>
> >
>



-- 
--dmg

---
Daniel M. German
http://turingmachine.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
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Tilt transformation...

[Yuval Levy]

dmg wrote:
>> how does this interact with James' new layout (the "j" parameters in the
>> .pto files) ?
> 
> Is this read by libpano tools? I doubt it. In that case, not at all.

should it be read by libpano tools?

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: [PanoTools-devel] Mailing List

[Yuval Levy]

Tom -

my statement about the PanoTools-devel *mailing list* being obsolete is 
*not tantamount* to saying that libpano no longer has a valid role 
outside of Hugin. These are your words below, to which I do not subscribe.

Ditching a mailing list that is practically dead and is hosted on a less 
than optimal infrastructure is *NOT* a statement about the code 
discussed, its relevance, or its life-cycle.

Hugin-PTX is *not* a Hugin-only list. It is a list for *all* open source 
panoramic tools. Historically it started with Hugin and PTX, but there 
is no limit and the folks here are not only tolerant, they are also 
welcoming developers talk.

Consolidating the dev-talk for different but related tools into a single 
place will benefit each single tool. Libpano talk will be exposed to 
more eyeballs, will gain more mindshare and maybe even contributors.

Yuv


Thomas Sharpless wrote:
> On Wed, Sep 9, 2009 at 6:07 PM, dmg wrote:
> 
>> I don't think it is a good idea. libpano is independent of hugin. but
>> I agree that nobody outside hugin
>> cares for libpano.
>>
> 
> I guess many of us feel that dropping PanoTools-devel is tantamount to
> saying that libpano no longer has a valid role as a shared platform.  Is
> that true, or not true?
> 
> Though I find it sad, it does seem to me that libpano, having spawned some
> of the best stitchers around, is nearing the end of its life cycle.  Its
> progeny are diverging pretty fast, and for the most part do not add new
> technology via libpano.  However it is still true that PTAssembler, Hugin
> and PTGui (and perhaps others I don't know about) interoperate with
> PanoTools to some degree, and all use libpano for at least some things.  So
> it may be too early to say that libpano has become purely a Hugin library.
> 
> However it does look as though the most likely future for libpano is as a
> kind of parts bin for Hugin developers.  Some of its better parts can
> undoubtedly be recycled, along with more useful replacements for some of its
> not better but nevertheless necessary parts (hmm, I'm starting to sound
> German...).  And a lot of it can just be scrapped.
> 
> IMHO the main thing wrong with libpano is its rather primitive parameter and
> scripting facilities, and the relative difficulty of improving them within
> the C language context -- at least by programmers accustomed to C++.  Not
> that there is any law against adding C++ modules to libpano, but basically
> it would need a major redesign and reimplementation to turn it into a
> platform for the best stitchers of the 20-teens.  And it is unlikely the
> authors of those stitchers would see any advantage in creating a shared
> platform.
> 
> Regards, Tom
> 
> 
> 
>> On Tue, Sep 8, 2009 at 7:48 PM, Yuval Levy wrote:
>>> Hi all,
>>>
>>> since most (if not all) people here are also on
>>>  and the people there seems
>>> inclined to accept more dev talk...
>>>
>>> and since this list has only the occasional message...
>>>
>>> may I suggest that we close/archive this list and continue talking
>>> panotools development on hugin-ptx?
>>>
>>> the advantages:
>>> - one mailing list less to follow
>>> - an improved infrastructure
>>> - more critical mass = more potential contributors
>>>
>>> Yuv
>>>
>>>
>> --
>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> 30-Day
>>> trial. Simplify your report design, integration and deployment - and
>> focus on
>>> what you do best, core application coding. Discover what's new with
>>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>>> ___
>>> PanoTools-devel mailing list
>>> panotools-de...@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/panotools-devel
>>>
>>>
>>
>>
>> --
>> --dmg
>>
>> ---
>> Daniel M. German
>> http://turingmachine.org
>>
>>
>> --
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
>> trial. Simplify your report design, integration and deployment - and focus
>> on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
>> ___
>> PanoTools-devel mailing list
>> panotools-de...@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/panotools-devel
>>
> 


--~--~-~--~~~---~--~~
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://group

[hugin-ptx] Re: Tilt transformation...

[dmg]

On Wed, Sep 9, 2009 at 3:09 PM, Yuval Levy  wrote:
>
> D M German wrote:
>> Now, the real question for hugin developers: can somebody create a
>> branch of hugin that supports these new parameters during the
>> optimization? shearX, shearY, tiltX, tiltY, tiltZ and tiltScale?
>
> how does this interact with James' new layout (the "j" parameters in the
> .pto files) ?

Is this read by libpano tools? I doubt it. In that case, not at all.

>
> Yuv
>
> >
>



-- 
--dmg

---
Daniel M. German
http://turingmachine.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
-~--~~~~--~~--~--~---

[hugin-ptx] Re: Tilt transformation...

[Yuval Levy]

D M German wrote:
> Now, the real question for hugin developers: can somebody create a
> branch of hugin that supports these new parameters during the
> optimization? shearX, shearY, tiltX, tiltY, tiltZ and tiltScale?

how does this interact with James' new layout (the "j" parameters in the 
.pto files) ?

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] hugin-mac-2009.2-Beta3 for download

[Yuval Levy]

Carl von Einem wrote:
> Wow, SF's interface is always changing, and
> everytime it seems to get worse...

Having worked quite intensively lately with it, I can confirm. I start 
to belive that their chief designer must be Dogbert.

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: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Yuval Levy]

Harry van der Wolf wrote:
> Fortunately there is a great community of enblend builders on OSX  :-(
> (I think I'm currently the only one as others use my builds also in their
> bundles/plugins and so on.).

no intention to put pressure on you. you actually laid out a pretty nice 
and clear plan.

I hope your description of what could be done generated some itching 
around our OSX users, the same way my CMake talk generated the itch with 
Kornel, Ryan, yourself.

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] hugin-mac-2009.2-Beta3 for download

[Carl von Einem]

nona crashed almost instantly on my G5 / OSX 10.4.11

I'll submit a bug report. Wow, SF's interface is always changing, and
everytime it seems to get worse...

The Bug tracker is at

then search for "add new" and I hope that works...

Harry van der Wolf wrote:
> 
> Specific items for OSX:
> *- GPU use is very experimental. *(Hugin->Preferences->Stitching).
> Try this and if you have errors let us now including the "log". If
> you are succesful let us know as well as we need to know what
> configuration is succesful (OSX version *and* About this Mac->More
> info->Video/Screens)

--~--~-~--~~~---~--~~
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: Tilt transformation...

[Dale Beams]

Thank you sooo much Dev and Daniel.  I've been waiting for this for s long.

> From: d...@uvic.ca
> To: hugin-ptx@googlegroups.com
> To: panotools-de...@lists.sourceforge.net
> Subject: [hugin-ptx] Tilt transformation...
> Date: Wed, 9 Sep 2009 14:03:06 -0700
> 
> 
> 
> (this code was brought to you by Google :)
> 
> As you might know, Dev Gosh was one of Google Summer of Code
> students. Unfortunately he only completed part of his project. 
> 
> His idea was to allow for the rotation of the camera plane in two axis:
> around x, and around y. He did a good job with the math and, except for
> some very minor bugs, his code worked as expected.
> 
> For example, for the tilt on X, imagine you take a photo, then you apply
> a "pitch" rotation (rotation around x), then a translation to recenter
> the image on (0,0). the same applies for rotation around Y.
> 
> When I integrated his code I discovered that it would be good to add the
> ability to rotate around Z, and implemented it accordingly.
> 
> Here is in example of the input:
> 
> http://turingmachine.org/~dmg/temp/floorInput.jpg
> 
> and the output:
> 
> http://turingmachine.org/~dmg/temp/floorOutput.jpg
> 
> and this is a photo of the same place taken:
> 
> http://turingmachine.org/~dmg/temp/floorInput.jpg
> 
> In this case, there is a tiltX of 32 degrees, and a tiltZ of -11 and a
> shear of -125 pixels.
> 
> I have also added 3 parameters to the parser: Tx, Ty, and Tz, which are
> angles to rotate in degrees; and Ts, which is a scaling factor.
> 
> I have the inverse transformations done. they are described here:
> 
> http://turingmachine.org/~dmg/temp/tiltEq.pdf
> 
> I am struggling with the inverse ones. If anybody wants to help, I'll be
> grateful. This is the only roadblock to have an alpha version of it.
> 
> Now, the real question for hugin developers: can somebody create a
> branch of hugin that supports these new parameters during the
> optimization? shearX, shearY, tiltX, tiltY, tiltZ and tiltScale?
> 
> 
> I haven't committed my code but will do soon. in its current state the
> optimizer nor the cropping works (we need the forward transform for that).
> 
> 
> --
> Daniel M. German  
> http://turingmachine.org/
> http://silvernegative.com/
> dmg (at) uvic (dot) ca
> replace (at) with @ and (dot) with .
> 
> > 

_
Hotmail® is up to 70% faster. Now good news travels really fast. 
http://windowslive.com/online/hotmail?ocid=PID23391::T:WLMTAGL:ON:WL:en-US:WM_HYGN_faster:082009
--~--~-~--~~~---~--~~
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: Tilt transformation...

[D M German]

> 
> and this is a photo of the same place taken:
> 
> http://turingmachine.org/~dmg/temp/floorInput.jpg

sorry:


http://turingmachine.org/~dmg/temp/floor.jpg

And we should thank Dev and Google for this feature. I think it will go
a long way into making the nadir photos easier.


--
Daniel M. German  
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .

--~--~-~--~~~---~--~~
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] Tilt transformation...

[D M German]

(this code was brought to you by Google :)

As you might know, Dev Gosh was one of Google Summer of Code
students. Unfortunately he only completed part of his project. 

His idea was to allow for the rotation of the camera plane in two axis:
around x, and around y. He did a good job with the math and, except for
some very minor bugs, his code worked as expected.

For example, for the tilt on X, imagine you take a photo, then you apply
a "pitch" rotation (rotation around x), then a translation to recenter
the image on (0,0). the same applies for rotation around Y.

When I integrated his code I discovered that it would be good to add the
ability to rotate around Z, and implemented it accordingly.

Here is in example of the input:

http://turingmachine.org/~dmg/temp/floorInput.jpg

and the output:

http://turingmachine.org/~dmg/temp/floorOutput.jpg

and this is a photo of the same place taken:

http://turingmachine.org/~dmg/temp/floorInput.jpg

In this case, there is a tiltX of 32 degrees, and a tiltZ of -11 and a
shear of -125 pixels.

I have also added 3 parameters to the parser: Tx, Ty, and Tz, which are
angles to rotate in degrees; and Ts, which is a scaling factor.

I have the inverse transformations done. they are described here:

http://turingmachine.org/~dmg/temp/tiltEq.pdf

I am struggling with the inverse ones. If anybody wants to help, I'll be
grateful. This is the only roadblock to have an alpha version of it.

Now, the real question for hugin developers: can somebody create a
branch of hugin that supports these new parameters during the
optimization? shearX, shearY, tiltX, tiltY, tiltZ and tiltScale?


I haven't committed my code but will do soon. in its current state the
optimizer nor the cropping works (we need the forward transform for that).


--
Daniel M. German  
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (at) with @ and (dot) with .

--~--~-~--~~~---~--~~
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: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Kornel Benko]

Am Mittwoch 09 September 2009 schrieb Ryan Sleevi:
> Kornel,
>
>
>
> At the lowest level, you can always MESSAGE(STATUS
> "Message")
>
>

Ryan, I knew all of this.  I only said, its missing at the moment. And as we 
agreed, no change until all things are in the repo.

> so
>
> IF(${SOME_FLAG})
>
> MESSAGE(STATUS "Project will be built with
> some_flag disabled. If you prefer to build without some_flag support, you
> may use -DSOME_FLAG=0")
>
> ELSE(${SOME_FLAG})
>
> MESSAGE(STATUS "Project will be built with
> some_flag enabled. If you prefer to build with some_flag support, you may
> use -DSOME_FLAG=1")
>
> ENDIF(${SOME_FLAG})
>
>
>
> Of course, that get's wildly inefficient for more than a
> few options. Not to mention there are two presumptions - that the
> description messages will containing meaningful context for non-native
> speakers of that language - and that people are building through a
> command-line or means that expects flags like -DSOME_FLAG. I know the
> CMake-gui actually exposes OPTIONs as boolean checkboxes in the interface,
> and while I suspect it probably would support args on the command-line,
> they don't exactly make it obvious (especially for those in the Windows
> world)
>

I imagine here some preconfigured option groups. If someone wishes to have 
enblend without image_cache,
 then the other options like glew or glut will be set. But I have no clear 
picture of what should be done, or if it is
worth the effort.

Sure not for me. I have my scripts.

>
> The "better/preferred/consistent" alternative would be to
> use ccmake / cmake-gui to provide users with options
>
>
>
> More details are available via cmake --help-command SET and
> cmake --help-command OPTION
>
> eg:
>
> SET(SOME_VAR "def value" PATH "path to put awesome stuff")
>
> OPTION(BOOL_VAR "enable me to turn on the awesome stuff"
> ON)
>
>
>
> In the default view for ccmake/cmake-gui, only those
> options NOT flagged MARK_AS_ADVANCED will be shown. Since all of our
> FindXXX* code uses MARK_AS_ADVANCED, the default view shows only basic/core
> CMake arguments and the options we have defined explicitly (such as the
> ENABLE_SSE2 stuff). No consulting of the CMakeLists.txt necessary!
>
>
>
> ccmake/cmake-gui is to cmake what ./configure --help is to
> ./configure :)
>
>

I am using cmake-gui.

Kornel

-- 
Kornel Benko
kornel.be...@berlin.de


signature.asc
Description: This is a digitally signed message part.

[hugin-ptx] Re: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Harry van der Wolf]

2009/9/9 Yuval Levy 

>
> Harry van der Wolf wrote:
> > OpenMP is not an issue as it is not available on OSX (apart from some
> > extremely bleeding edge source packages)
>
> bummer! I guess you know about http://hpc.sourceforge.net/ ?
>
> Yuv
>
>
Yes, I know it. He does a good job but it requires me to install a new
GCC/GCC++ environment (in /usr/local which is not a default on OSX). I have
no idea what that will do to my current installation and all the tools I use
and build.
Secondly: OpenMP is benificial on Multicore. G5 is a ppc dual-core as are
most Intels currently. There are some high-end quad-core Xeon Macs as well.
When running on Dual-Core you don't want to use both cores (at least I
won't. It will stop your system from doing anything else). On a high-end
Quad-Core Xeon you might want to use 2-3 cores.
Thirdly: Gaurav's packages are not universal, which means that I might have
to do an awful lot of work of making it universal.
Fourthly: Currently I have no idea how to package that into a portable
bundle (Hugin), let alone a universal bundle. This last might not be
necessary. It is also for mac users possible to use an enblend/enfuse from
"outside" the bundle which would simplify the job.

Being very busy currently with quite some things going on, I don't want to
start another project. It might be relatively easy, but maybe not at all.
Maybe later.
Next to the other "projects" my goals for enblend are (in this order):
- Make it work with cmake.
- Patch it so that enblend/enfuse can create >2GB tiff files which is
currently not possible due to a TIFF/OSX incompatibility.
- Try to build 64bit stand-alone enblends/enfuses. The later versions have
currently problems with that (that is: I have problems with it).
- Make enblend/enfuse work on Snow Leopard. Currently there seem to be
problems with that.

Fortunately there is a great community of enblend builders on OSX  :-(
(I think I'm currently the only one as others use my builds also in their
bundles/plugins and so on.).


Harry

--~--~-~--~~~---~--~~
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: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Ryan Sleevi]

Kornel,

 

At the lowest level, you can always MESSAGE(STATUS "Message")

 

so 

IF(${SOME_FLAG})

MESSAGE(STATUS "Project will be built with 
some_flag disabled. If you prefer to build without some_flag support, you may 
use -DSOME_FLAG=0")

ELSE(${SOME_FLAG})

MESSAGE(STATUS "Project will be built with 
some_flag enabled. If you prefer to build with some_flag support, you may use 
-DSOME_FLAG=1")

ENDIF(${SOME_FLAG})

 

Of course, that get's wildly inefficient for more than a few 
options. Not to mention there are two presumptions - that the description 
messages will containing meaningful context for non-native speakers of that 
language - and that people are building through a command-line or means that 
expects flags like -DSOME_FLAG. I know the CMake-gui actually exposes OPTIONs 
as boolean checkboxes in the interface, and while I suspect it probably would 
support args on the command-line, they don't exactly make it obvious 
(especially for those in the Windows world)

 

The "better/preferred/consistent" alternative would be to use 
ccmake / cmake-gui to provide users with options

 

More details are available via cmake --help-command SET and 
cmake --help-command OPTION

eg:

SET(SOME_VAR "def value" PATH "path to put awesome stuff")

OPTION(BOOL_VAR "enable me to turn on the awesome stuff" ON)

 

In the default view for ccmake/cmake-gui, only those options 
NOT flagged MARK_AS_ADVANCED will be shown. Since all of our FindXXX* code uses 
MARK_AS_ADVANCED, the default view shows only basic/core CMake arguments and 
the options we have defined explicitly (such as the ENABLE_SSE2 stuff). No 
consulting of the CMakeLists.txt necessary!

 

ccmake/cmake-gui is to cmake what ./configure --help is to 
./configure :)

 

 

 

From: hugin-ptx@googlegroups.com [mailto:hugin-...@googlegroups.com] On Behalf 
Of Kornel Benko
Sent: Wednesday, September 09, 2009 3:39 PM
To: hugin-ptx@googlegroups.com
Subject: [hugin-ptx] Re: cmake compilation of enblend [was: Enblend bug tracker 
and developer mailing list]

 

Am Mittwoch 09 September 2009 schrieb Pablo d'Angelo:
> > What is missing now, is the control from command line for this.
>
> Do you mean:
> cmake -DCMAKE_BUILD_TYPE=Release



 

Yes, I know. But I prefer something which will be more recognised. And which 
will print some suggestions.



 

Like this one (in another project)
cmake 
Project will be built with nls support enabled. If you prefer build without nls 
select -Dnls=0 on commad line



 

...
cmake -Dnls=1 
Project will be built with nls support disabled. If you prefer build with nls 
support select -Dnls=1 on commad line
...
This way I am not supposed to remember the settings. (Or to look into 
CMakeLists.txt to find out)



 

> If I remember correctly, the enblend autoconf script does use more
> aggressive optimisation options than most other packages.



 

We are pretty good now.



 

Kornel
-- 
Kornel Benko
kornel.be...@berlin.de


--~--~-~--~~~---~--~~
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: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Yuval Levy]

Harry van der Wolf wrote:
> OpenMP is not an issue as it is not available on OSX (apart from some
> extremely bleeding edge source packages)

bummer! I guess you know about http://hpc.sourceforge.net/ ?

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: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Yuval Levy]

Ryan Sleevi wrote:
> Seconded - any further modifications should happen in the repo. I'm holding 
> off

the "time-out" is over. thanks to Andrew who has changed the way the 
project is administered. Full steam ahead!

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: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Kornel Benko]

Am Mittwoch 09 September 2009 schrieb Pablo d'Angelo:
> > What is missing now, is the control from command line for this.
>
> Do you mean:
> cmake -DCMAKE_BUILD_TYPE=Release

Yes, I know. But I prefer something which will be more recognised. And which 
will print some suggestions.

Like this one (in another project)
cmake 
  Project will be built with nls support enabled. If you prefer build without 
nls select -Dnls=0 on commad line

...
cmake -Dnls=1 
  Project will be built with nls support disabled. If you prefer build with nls 
support select -Dnls=1 on commad line
...
This way I am not supposed to remember the settings. (Or to look into 
CMakeLists.txt to find out)

> If I remember correctly, the enblend autoconf script does use more
> aggressive optimisation options than most other packages.

We are pretty good now.

Kornel
-- 
Kornel Benko
kornel.be...@berlin.de


signature.asc
Description: This is a digitally signed message part.

[hugin-ptx] Re: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Pablo d'Angelo]

Kornel Benko wrote:
> Am Mittwoch 09 September 2009 schrieb Ryan Sleevi:
> 
>  >
>  > As you indicated in your follow-up, the CMAKE_BUILD_TYPE is what controls
>  > whether or not the compiler is set to be optimized for release mode. For
>  > the Windows platforms, all the build types are exported into a single 
> .sln
>  > and can be chosen within the MSVC ide / vcbuild command-line (CMake tries
>  > to preserve the native build semantics, and that's how it is done on
>  > Windows). FindLibraryWithDebug further eases this process for the Windows
>  > world.
> 
> 
> What is missing now, is the control from command line for this.

Do you mean:
cmake -DCMAKE_BUILD_TYPE=Release

If I remember correctly, the enblend autoconf script does use more 
aggressive optimisation options than most other packages.

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: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Kornel Benko]

Am Mittwoch 09 September 2009 schrieb Harry van der Wolf:
> 2009/9/9 Harry van der Wolf 
> Soory: should say.
> Now the results are slightly better than the previous autoconf version.

At least not shocking anymore :)

Kornel

-- 
Kornel Benko
kornel.be...@berlin.de


signature.asc
Description: This is a digitally signed message part.

[hugin-ptx] Re: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Kornel Benko]

Am Mittwoch 09 September 2009 schrieb Ryan Sleevi:
> Seconded - any further modifications should happen in the repo. I'm holding
> off on my 'cleanup' of my additions/macros until the code can at least be
> based there

Thanks, so will I.

Having a base, it will easy to check if someone's modification don't break 
anything on other platforms.
Then, if we agree, it may be commited. OK? I for one, can check on ubuntu and 
openSuse.

Kornel
-- 
Kornel Benko
kornel.be...@berlin.de


signature.asc
Description: This is a digitally signed message part.

[hugin-ptx] Re: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Harry van der Wolf]

2009/9/9 Harry van der Wolf 
Soory: should say.
Now the results are slightly better than the previous autoconf version.


> /usr/local/bin/enblend --version
> enblend 4.0-11ca5b567bc9
>
> And: should say.
 /usr/bin/time /usr/local/bin/enblend --gpu -o pipo.jpg 1222-02*.tif

> enblend: info: writing final output
>13.19 real10.32 user 1.35 sys
>
>
> /usr/local/bin/enblend -o pipo.jpg 1222-02*.tif
> enblend: info: writing final output
>12.10 real10.69 user 0.85 sys
>
> Now this is what I would have expected. Thanks Kornel.
>
> Harry
>
>

--~--~-~--~~~---~--~~
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: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Harry van der Wolf]

2009/9/9 Harry van der Wolf 

> Hi all,
>
> Here are the results from the OSX jury.
> OpenMP is not an issue as it is not available on OSX (apart from some
> extremely bleeding edge source packages)
>
>
> enblend via cmake compiles and works now too on OSX.
> however, on doing some tests I had some shocking results.
>
> enblend pre 4.0 via cmake. with openGL, GLEW and GLUT
> /usr/local/bin/enblend --version
> enblend 4.0-11ca5b567bc9
>
> /usr/bin/time /usr/local/bin/enblend --gpu -o pipo.tif 1222-02*.tif
> : info: using graphics card: NVIDIA Corporation
> : info:renderer: NVIDIA GeForce 9600M GT OpenGL Engine
> 
> enblend: info: writing final output
>   103.61 real   100.38 user 1.39 sys
> 
> /usr/bin/time /usr/local/bin/enblend --gpu -o pipo.tif 1222-02*.tif
> enblend: info: writing final output
>   106.16 real   104.16 user 0.91 sys
> 
> enblend pre 4.0 via autoconf. No openGL, no GLEW, no GLUT
> enblend --version
> enblend 4.0-8d38f4ffc03c
> /usr/bin/time
> /Applications/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/enblend
> -o pipo.tif 1222-02*.tif
>12.88 real11.80 user 0.45 sys
>
> The autoconf version is almost 10X faster!
>
> Harry
>
> With set(CMAKE_BUILD_TYPE Release CACHE STRING "Choose the type of build,
options are: None Debug Release RelWithDebInfo MinSizeRel." FORCE) added to
CMakeLists.txt I recompiled. Now the results are slightly better than the
previous version

/usr/local/bin/enblend --version
enblend 4.0-11ca5b567bc9

enblend: info: writing final output
   13.19 real10.32 user 1.35 sys


/usr/local/bin/enblend -o pipo.jpg 1222-02*.tif
enblend: info: writing final output
   12.10 real10.69 user 0.85 sys

Now this is what I would have expected. Thanks Kornel.

Harry

--~--~-~--~~~---~--~~
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: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Ryan Sleevi]

Seconded - any further modifications should happen in the repo. I'm holding off 
on my 'cleanup' of my additions/macros until the code can at least be based 
there

 

From: hugin-ptx@googlegroups.com [mailto:hugin-...@googlegroups.com] On Behalf 
Of Harry van der Wolf
Sent: Wednesday, September 09, 2009 1:50 PM
To: hugin-ptx@googlegroups.com
Subject: [hugin-ptx] Re: cmake compilation of enblend [was: Enblend bug tracker 
and developer mailing list]

 

What is missing now, is the control from command line for this.

 

Since we don't have the same cmake-base we should search for some way to 
exchage changes only.

 

The version here is mostly your modified version with corrections from me. 
Should we really be forced to send
each time all the data? What do you think Ryan?


I'm not Ryan, but Harry ;-)

We (at least one of us) need access to the repository.  It is completely 
harmless for the autoconf build to add the cmake stuff. From that moment on we 
can uses diff's to patch the repository

Harry




--~--~-~--~~~---~--~~
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: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Harry van der Wolf]

What is missing now, is the control from command line for this.

>
> Since we don't have the same cmake-base we should search for some way to
> exchage changes only.
>
>
> The version here is mostly your modified version with corrections from me.
> Should we really be forced to send
> each time all the data? What do you think Ryan?
>

I'm not Ryan, but Harry ;-)

We (at least one of us) need access to the repository.  It is completely
harmless for the autoconf build to add the cmake stuff. From that moment on
we can uses diff's to patch the repository

Harry

--~--~-~--~~~---~--~~
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: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Kornel Benko]

Am Mittwoch 09 September 2009 schrieb Ryan Sleevi:
> FindLibraryWithDebug is "safe" for Release calls. It's just a special
> handler for Windows platforms that tend to have libraries with debug file
> suffices (and with my modifications, also handles situations where x86 and
> x64 libs are "side-by-side", sharing 1 include dir, but having their own
> unique lib dirs, and potentially their path suffixes - eg
> Release/x86/libfoo.lib vs Debug/x86/libfoo.lib or x64/libbard.lib vs
> x64/libbar.lib). On other platforms, it just passes through to
> FIND_LIBRARY, which on the non-Win platforms is more an issue with the
> CMAKE_BUILD_TYPE.
>

Good to know. Thanks.

>
> As you indicated in your follow-up, the CMAKE_BUILD_TYPE is what controls
> whether or not the compiler is set to be optimized for release mode. For
> the Windows platforms, all the build types are exported into a single .sln
> and can be chosen within the MSVC ide / vcbuild command-line (CMake tries
> to preserve the native build semantics, and that's how it is done on
> Windows). FindLibraryWithDebug further eases this process for the Windows
> world.

What is missing now, is the control from command line for this.

Since we don't have the same cmake-base we should search for some way to 
exchage changes only.

The version here is mostly your modified version with corrections from me. 
Should we really be forced to send
each time all the data? What do you think Ryan?

Kornel
-- 
Kornel Benko
kornel.be...@berlin.de


signature.asc
Description: This is a digitally signed message part.

[hugin-ptx] Re: [OSX] hugin-mac-2009.2-Beta3 for download

[Harry van der Wolf]

Sorry,

I did a copy&paste of my previous beta2 message with too few corrections.
Being lazy and being busy with all kind of other things is very error prone.
See below a corrected message.

Harry

2009/9/9 Harry van der Wolf 

> Hi Mac users,
>
> *Note:* please also read the "Howto build a Hugin bundle on MacOSX" below,
> instead of just skipping that and downloading the bundle.
>
> I just published a new 32bit Hugin 2009.2 beta3 bundle. This release is
> equivalent to svn 4351. In case you wonder: "WOW, Hugin goes from version
> 0.8 to version 2009!", you should read
> more about this versioning at [2] [3].
>
> See changelog for 2009.2 Beta3 at [4].
>
>
> Specific items for OSX:
> *- GPU use is very experimental. *(Hugin->Preferences->Stitching). Try
> this and if you have errors let us now including the "log". If you are
> succesful let us know as well as we need to know what configuration is
> succesful (OSX version *and* About this Mac->More info->Video/Screens)
>


>
> Information and binaries via my website
>  >.
> (The binaries itself are, as always, served from hugin.panotools.org who
> kindly provide the disk space and bandwidth).
>
>
> == On August 12 I posted the mail *"Howto build a Hugin bundle on MacOSX"*[1].
> Please read it if you don't know what I'm typing about. It was a request
> for volunteers to start learning how to build a Hugin bundle on MacOSX. I
> wrote that as at that moment I had no longer a Mac for 4-5 weeks.
>  Until now the response to that mail was really overwhelming: Only one
> (possible) volunteer! That might be due to the fact that it was still
> holiday time, but that's now over for everyone.
> So that's why I now repeat the request.
> It is really important that if the OSX community wants to survive without
> the current two builders, we need more builders.
> Hey, it's not that difficult. How would I have ever learned it when it was
> that difficult?
> If you are not a total technical NoNo (close to Dodo and they are extinct
> as well), join the team and learn how to build a bundle.
>
> Hoi,
> Harry
>
> [1]:
> http://groups.google.com/group/hugin-ptx/browse_thread/thread/dec891b020aa7629
> [2]:
> http://groups.google.com/group/hugin-ptx/browse_thread/thread/fce69536a1dd1a8a
> [3]: http://wiki.panotools.org/Development_of_Open_Source_tools
> [4]:
> http://groups.google.com/group/hugin-ptx/browse_thread/thread/41095f1e008b575d
>
>
>
>
>
> 
> Download 
> ImageFuser(
> Nederlands
> )
> ImageFuser manual
> Download 
> Hugin
> My website 
>
>
> --- @ WiseStamp Signature . Get it
> now 
>
>

--~--~-~--~~~---~--~~
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] [OSX] hugin-mac-2009.2-Beta3 for download

[Harry van der Wolf]

Hi Mac users,

*Note:* please also read the "Howto build a Hugin bundle on MacOSX" below,
instead of just skipping that and downloading the bundle.

I just published a new 32bit Hugin 2009.2 beta3 bundle. This release is
equivalent to svn 4351. In case you wonder: "WOW, Hugin goes from version
0.8 to version 2009!", you should read
more about this versioning at [2] [3].

See changelog for 2009.2 Beta3 at [4].
The changelog forgets to mention James Legg's patch in the Fast Preview
window which shows the CP distance by means of orange lines. This is a fast
and easy way to spot bad CP's.

Specific items for OSX:
- You cannot use GPU on MacOSX yet. Hugin->Preferences->Stitching: Do NOT!
use GPU.
- The images pane now has a setting for the AutoControlPoint creator. Too
bad they didn't look at the MacOSX solution as they invented the wheel twice
(slightly different). But the new method is more flexible than the OSX way.
However, the new solution is useless for OSX as OSX still uses the plugin
structure as before.


Information and binaries via my website
.
(The binaries itself are, as always, served from hugin.panotools.org who
kindly provide the disk space and bandwidth).


== On August 12 I posted the mail *"Howto build a Hugin bundle on MacOSX"*[1].
Please read it if you don't know what I'm typing about. It was a request for
volunteers to start learning how to build a Hugin bundle on MacOSX. I wrote
that as at that moment I had no longer a Mac for 4-5 weeks.
 Until now the response to that mail was really overwhelming: Only one
(possible) volunteer! That might be due to the fact that it was still
holiday time, but that's now over for everyone.
So that's why I now repeat the request.
It is really important that if the OSX community wants to survive without
the current two builders, we need more builders.
Hey, it's not that difficult. How would I have ever learned it when it was
that difficult?
If you are not a total technical NoNo (close to Dodo and they are extinct as
well), join the team and learn how to build a bundle.

Hoi,
Harry

[1]:
http://groups.google.com/group/hugin-ptx/browse_thread/thread/dec891b020aa7629
[2]:
http://groups.google.com/group/hugin-ptx/browse_thread/thread/fce69536a1dd1a8a
[3]: http://wiki.panotools.org/Development_of_Open_Source_tools
[4]:
http://groups.google.com/group/hugin-ptx/browse_thread/thread/41095f1e008b575d






Download 
ImageFuser(
Nederlands
)
ImageFuser manual 
Download 
Hugin
My website 


--- @ WiseStamp Signature . Get it
now 

--~--~-~--~~~---~--~~
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: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Ryan Sleevi]

FindLibraryWithDebug is "safe" for Release calls. It's just a special handler 
for Windows platforms that tend to have libraries with debug file suffices (and 
with my modifications, also handles situations where x86 and x64 libs are 
"side-by-side", sharing 1 include dir, but having their own unique lib dirs, 
and potentially their path suffixes - eg Release/x86/libfoo.lib vs 
Debug/x86/libfoo.lib or x64/libbard.lib vs x64/libbar.lib). On other platforms, 
it just passes through to FIND_LIBRARY, which on the non-Win platforms is more 
an issue with the CMAKE_BUILD_TYPE.

 

As you indicated in your follow-up, the CMAKE_BUILD_TYPE is what controls 
whether or not the compiler is set to be optimized for release mode. For the 
Windows platforms, all the build types are exported into a single .sln and can 
be chosen within the MSVC ide / vcbuild command-line (CMake tries to preserve 
the native build semantics, and that's how it is done on Windows). 
FindLibraryWithDebug further eases this process for the Windows world.

 

 

 

From: hugin-ptx@googlegroups.com [mailto:hugin-...@googlegroups.com] On Behalf 
Of Kornel Benko
Sent: Wednesday, September 09, 2009 12:28 PM
To: hugin-ptx@googlegroups.com
Subject: [hugin-ptx] Re: cmake compilation of enblend [was: Enblend bug tracker 
and developer mailing list]

 

Am Mittwoch 09 September 2009 schrieb Harry van der Wolf:
> Hi all,
>
> Here are the results from the OSX jury.
> OpenMP is not an issue as it is not available on OSX (apart from some
> extremely bleeding edge source packages)
>
>
> enblend via cmake compiles and works now too on OSX.
> however, on doing some tests I had some shocking results.
>
> enblend pre 4.0 via cmake. with openGL, GLEW and GLUT
> /usr/local/bin/enblend --version
> enblend 4.0-11ca5b567bc9
>
> /usr/bin/time /usr/local/bin/enblend --gpu -o pipo.tif 1222-02*.tif
>
> : info: using graphics card: NVIDIA Corporation
> : info: renderer: NVIDIA GeForce 9600M GT OpenGL Engine
>
> 
> enblend: info: writing final output
> 103.61 real 100.38 user 1.39 sys
> 
> /usr/bin/time /usr/local/bin/enblend --gpu -o pipo.tif 1222-02*.tif
> enblend: info: writing final output
> 106.16 real 104.16 user 0.91 sys
> 
> enblend pre 4.0 via autoconf. No openGL, no GLEW, no GLUT
> enblend --version
> enblend 4.0-8d38f4ffc03c
> /usr/bin/time
> /Applications/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/
>MacOS/enblend -o pipo.tif 1222-02*.tif
> 12.88 real 11.80 user 0.45 sys
>
> The autoconf version is almost 10X faster!
>
> Harry



 

I see.
1.) In this version we are not optimizing
2.) We are using "FindLibraryWithDebug.cmake"



 

Kornel



 

-- 
Kornel Benko
kornel.be...@berlin.de


--~--~-~--~~~---~--~~
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: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Kornel Benko]

Am Mittwoch 09 September 2009 schrieb Kornel Benko:
> Am Mittwoch 09 September 2009 schrieb Harry van der Wolf:
> > Well, Some "debugging"  statement was exactly what I was looking for but
> > I couldn't find it so I assumed (incorrectly) that I was in Release mode
> > or so. Where is this being set?
>
> I am searching too ...
>
>   Kornel

Found it.
One has to set
set(CMAKE_BUILD_TYPE Release CACHE STRING
"Choose the type of build, options are: None Debug Release 
RelWithDebInfo MinSizeRel."
FORCE)
somwhere at the start of CMakeLists.txt to get optimized version.

Compiling now.

Kornel

-- 
Kornel Benko
kornel.be...@berlin.de


signature.asc
Description: This is a digitally signed message part.

[hugin-ptx] Re: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Kornel Benko]

Am Mittwoch 09 September 2009 schrieb Harry van der Wolf:
> Well, Some "debugging"  statement was exactly what I was looking for but I
> couldn't find it so I assumed (incorrectly) that I was in Release mode or
> so. Where is this being set?

I am searching too ...

Kornel

-- 
Kornel Benko
kornel.be...@berlin.de


signature.asc
Description: This is a digitally signed message part.

[hugin-ptx] Re: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Harry van der Wolf]

2009/9/9 Kornel Benko 

> Am Mittwoch 09 September 2009 schrieb Harry van der Wolf:
>
> > The autoconf version is almost 10X faster!
> >
> > Harry
>
>
> I see.
> 1.) In this version we are not optimizing
> 2.) We are using "FindLibraryWithDebug.cmake"
>
>
> Kornel
>

Well, Some "debugging"  statement was exactly what I was looking for but I
couldn't find it so I assumed (incorrectly) that I was in Release mode or
so. Where is this being set?

Harry

--~--~-~--~~~---~--~~
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: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Kornel Benko]

Am Mittwoch 09 September 2009 schrieb Harry van der Wolf:
> Hi all,
>
> Here are the results from the OSX jury.
> OpenMP is not an issue as it is not available on OSX (apart from some
> extremely bleeding edge source packages)
>
>
> enblend via cmake compiles and works now too on OSX.
> however, on doing some tests I had some shocking results.
>
> enblend pre 4.0 via cmake. with openGL, GLEW and GLUT
> /usr/local/bin/enblend --version
> enblend 4.0-11ca5b567bc9
>
> /usr/bin/time /usr/local/bin/enblend --gpu -o pipo.tif 1222-02*.tif
>
> : info: using graphics card: NVIDIA Corporation
> : info:renderer: NVIDIA GeForce 9600M GT OpenGL Engine
>
> 
> enblend: info: writing final output
>   103.61 real   100.38 user 1.39 sys
> 
> /usr/bin/time /usr/local/bin/enblend --gpu -o pipo.tif 1222-02*.tif
> enblend: info: writing final output
>   106.16 real   104.16 user 0.91 sys
> 
> enblend pre 4.0 via autoconf. No openGL, no GLEW, no GLUT
> enblend --version
> enblend 4.0-8d38f4ffc03c
> /usr/bin/time
> /Applications/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/
>MacOS/enblend -o pipo.tif 1222-02*.tif
>12.88 real11.80 user 0.45 sys
>
> The autoconf version is almost 10X faster!
>
> Harry

I see.
1.) In this version we are not optimizing
2.) We are using "FindLibraryWithDebug.cmake"

Kornel

-- 
Kornel Benko
kornel.be...@berlin.de


signature.asc
Description: This is a digitally signed message part.

[hugin-ptx] Re: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Harry van der Wolf]

Hi all,

Here are the results from the OSX jury.
OpenMP is not an issue as it is not available on OSX (apart from some
extremely bleeding edge source packages)


enblend via cmake compiles and works now too on OSX.
however, on doing some tests I had some shocking results.

enblend pre 4.0 via cmake. with openGL, GLEW and GLUT
/usr/local/bin/enblend --version
enblend 4.0-11ca5b567bc9

/usr/bin/time /usr/local/bin/enblend --gpu -o pipo.tif 1222-02*.tif
: info: using graphics card: NVIDIA Corporation
: info:renderer: NVIDIA GeForce 9600M GT OpenGL Engine

enblend: info: writing final output
  103.61 real   100.38 user 1.39 sys

/usr/bin/time /usr/local/bin/enblend --gpu -o pipo.tif 1222-02*.tif
enblend: info: writing final output
  106.16 real   104.16 user 0.91 sys

enblend pre 4.0 via autoconf. No openGL, no GLEW, no GLUT
enblend --version
enblend 4.0-8d38f4ffc03c
/usr/bin/time
/Applications/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS/enblend
-o pipo.tif 1222-02*.tif
   12.88 real11.80 user 0.45 sys

The autoconf version is almost 10X faster!

Harry



2009/9/9 Kornel Benko 

> Am Mittwoch 09 September 2009 schrieb Ryan Sleevi:
> > This calls CMakeModules/FindPackageHandleStandardArgs.cmake, which will
> set
> > OpenMP_FOUND if both OpenMP_C_FLAGS and OpenMP_CXX_FLAGS are defined.
>
>
> And exactly here seems something not correct.
> I have this code:
> find_package(OpenMP REQUIRED)
> message(STATUS "OpenMP_C_FLAGS = ${OpenMP_C_FLAGS}")
> message(STATUS "OpenMP_CXX_FLAGS = ${OpenMP_CXX_FLAGS}")
> message(STATUS "OpenMP_FOUND = ${OpenMP_FOUND}")
> ...
>
>
> and this output:
> -- Found OpenMP: -fopenmp
> -- OpenMP_C_FLAGS = -fopenmp
> -- OpenMP_CXX_FLAGS = -fopenmp
> -- OpenMP_FOUND =
> ...
> So ok, you should have been right, but something went wrong.
>
>
> Kornel
>
>
> P.S.
> I appreciate your working, don't get me wrong
>
>
> --
> Kornel Benko
> kornel.be...@berlin.de
>

--~--~-~--~~~---~--~~
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: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Kornel Benko]

Found it. The package defines "OPENMP_FOUND". Should have known ...

Kornel

-- 
Kornel Benko
kornel.be...@berlin.de


signature.asc
Description: This is a digitally signed message part.

[hugin-ptx] Re: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Kornel Benko]

Am Mittwoch 09 September 2009 schrieb Ryan Sleevi:
> This calls CMakeModules/FindPackageHandleStandardArgs.cmake, which will set
> OpenMP_FOUND if both OpenMP_C_FLAGS and OpenMP_CXX_FLAGS are defined.

And exactly here seems something not correct.
I have this code:
  find_package(OpenMP REQUIRED)
  message(STATUS "OpenMP_C_FLAGS = ${OpenMP_C_FLAGS}")
  message(STATUS "OpenMP_CXX_FLAGS = ${OpenMP_CXX_FLAGS}")
  message(STATUS "OpenMP_FOUND = ${OpenMP_FOUND}")
 ...

and this output:
-- Found OpenMP: -fopenmp
-- OpenMP_C_FLAGS = -fopenmp
-- OpenMP_CXX_FLAGS = -fopenmp
-- OpenMP_FOUND =
...
So ok, you should have been right, but something went wrong.

Kornel

P.S.
I appreciate your working, don't get me wrong

-- 
Kornel Benko
kornel.be...@berlin.de


signature.asc
Description: This is a digitally signed message part.

[hugin-ptx] Re: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Ryan Sleevi]

Hrm... The flow is supposed to go:

 

CMakeLists.txt

IF(ENABLE_OPENMP)

  find_package(OpenMP REQUIRED)

  add_definitions(${OpenMP_CXX_FLAGS})

ENDIF(ENABLE_OPENMP)

 

This calls CMakeModules/FindOpenMP.cmake, which as the second-to-last 
execution, runs

find_package_handle_standard_args(OpenMP DEFAULT_MSG 

  OpenMP_C_FLAGS OpenMP_CXX_FLAGS )

 

This calls CMakeModules/FindPackageHandleStandardArgs.cmake, which will set 
OpenMP_FOUND if both OpenMP_C_FLAGS and OpenMP_CXX_FLAGS are defined.

 

When dealing with the MSVC compiler, the flag candidate (/openmp) works 
successfully for both the C and the C++ source code. Perhaps GCC is only 
setting OpenMP_CXX_FLAGS and not detecting anything for OpenMP_C_FLAGS? If so, 
that would explain why OpenMP_FOUND was not being set to true, but how the 
define could end up getting set. If both _C_FLAGS and _CXX_FLAGS are set, then 
that really is odd, because FindPackageHandleStandardArgs is used pretty 
extensively and seems to be well-tested.

 

I suppose the 'better' resolution to handle that case is to check the check in 
src/CMakeLists from IF(${OpenMP_FOUND}) to IF(${OpenMP_CXX_FLAGS}), since it 
really is that variable (and not the _C_FLAGS or the _FOUND) that is 
controlling whether or not it compiles with OpenMP.

 

 

From: hugin-ptx@googlegroups.com [mailto:hugin-...@googlegroups.com] On Behalf 
Of Kornel Benko
Sent: Wednesday, September 09, 2009 11:34 AM
To: hugin-ptx@googlegroups.com
Subject: [hugin-ptx] Re: cmake compilation of enblend [was: Enblend bug tracker 
and developer mailing list]

 

Am Mittwoch 09 September 2009 schrieb Ryan Sleevi:
> > > I try to correct
> > > Kornel
>
> The flag OpenMP_FOUND doesn't really matter as much, at least not in the
> code.



 

Not in the code, but you introduced it in src/CMakeLists.txt. And there it 
matters.



 

> All that matters is whether or not _OPENMP is defined, and that
> should only be defined if your compiler has run with -fopenmp (in the case
> of GCC). There is no need for OpenMP_FOUND - if you select OpenMP, then
> OpenMP is marked as required, and if it's not found, compilation will stop
> right there. I suspect this could be a cache issue as well, of older object
> files.



 

I selected OPENMP, therefore the source was compiled with the corresponding 
flag.
But on the linker stage it was missing, beacuse OpenMP_FOUND was not set.



 

Kornel



-- 
Kornel Benko
kornel.be...@berlin.de


--~--~-~--~~~---~--~~
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: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Kornel Benko]

Am Mittwoch 09 September 2009 schrieb Ryan Sleevi:
> > > I try to correct
> > > Kornel
>
> The flag OpenMP_FOUND doesn't really matter as much, at least not in the
> code.

Not in the code, but you introduced it in src/CMakeLists.txt. And there it 
matters.

> All that matters is whether or not _OPENMP is defined, and that
> should only be defined if your compiler has run with -fopenmp (in the case
> of GCC). There is no need for OpenMP_FOUND - if you select OpenMP, then
> OpenMP is marked as required, and if it's not found, compilation will stop
> right there. I suspect this could be a cache issue as well, of older object
> files.

I selected OPENMP, therefore the source was compiled with the corresponding 
flag.
But on the linker stage it was missing, beacuse OpenMP_FOUND was not set.

Kornel

-- 
Kornel Benko
kornel.be...@berlin.de


signature.asc
Description: This is a digitally signed message part.

[hugin-ptx] Re: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Ryan Sleevi]

> -Original Message-
> From: hugin-ptx@googlegroups.com [mailto:hugin-...@googlegroups.com] On
> Behalf Of Kornel Benko
> Sent: Wednesday, September 09, 2009 9:02 AM
> To: hugin-ptx@googlegroups.com
> Subject: [hugin-ptx] Re: cmake compilation of enblend [was: Enblend bug
> tracker and developer mailing list]
> 
> It compiles now.
> We have to set OpenMP_FOUND  somewhere. Maybe in FindOpenMP.cmake?
> 
> But why do you prefer image_cache and no openmp be default?
> 

As we're already seeing on the list, without the image cache, a number of 
perfectly valid tests in the past (if not perfectly common), no longer run. The 
OpenMP version really is a specialized version for those concerned with speed 
or 'bleeding edge', but does not represent a feature necessarily ready for 
mainstream use without understanding the trade-offs/caveats. Hence, an ideal 
non-feature

> 
> Am Wednesday 09 September 2009 schrieb Kornel Benko:
> > Am Wednesday 09 September 2009 schrieb Kornel Benko:
> > > I try to compile now on OpenSuSE.
> > >
> > CMake Error at CMakeLists.txt:131 (FIND_PACKAGE):
> >   Could not find module Findlibxmi.cmake or a configuration file for
> package
> >   libxmi.
> >
> > This is because on linux you have to search for "LibXMI"  ==>
> > FIND_PACKAGE(LibXMI REQUIRED)

Sorry, this was an unfinished non-Win32 stub that I was hoping to be filled in 
by someone more knowledgeable in the nescessary CMake incantations.

> > CMake Error at CMakeLists.txt:130 (FIND_PACKAGE):
> >   Could not find module Findlcms.cmake or a configuration file for
> package
> >   lcms.
> >
> > there is only FindLCMS.cmake in CMakeModules ==> FIND_PACKAGE(LCMS
> > REQUIRED)

I'm guessing CMake on other platforms opts for a different capitalization 
scheme. This one would be impossible to test except on other systems. Win32 is 
less-concerned with it.

> > Apart from that, it compiled, but the linking stage was erroneous.
> >
> > cd /usr/BUILD/BuildEnblend/src && /usr/bin/cmake -E cmake_link_script
> CMakeFiles/enblend.dir/link.txt --verbose=1
> > /usr/local/bin/c++ -fPIC CMakeFiles/enblend.dir/gpu.o
> CMakeFiles/enblend.dir/filenameparse.o CMakeFiles/enblend.dir/enblend.o
> -o
> > ../bin/enblend -rdynamic vigra_impex/libvigra_impex.a -lboost_thread
> > -lboost_date_time -ljpeg -ltiff -lpng -lz -llcms -lxmi -lImath -l
> > IlmImf -lIex -lHalf -lIlmThread -ltiff -lpng -lz
> > CMakeFiles/enblend.dir/gpu.o: In function `checkFramebufferStatus()':
> > gpu.cc:(.text+0xb): undefined reference to
> `__glewCheckFramebufferStatusEXT'
> > CMakeFiles/enblend.dir/gpu.o: In function `clearGPUTextures()':
> > gpu.cc:(.text+0x21a): undefined reference to
> `__glewDeleteFramebuffersEXT'
> > gpu.cc:(.text+0x235): undefined reference to `glDeleteTextures'
> > 
> >
> > Missing -lglew, even when _not_ enabling ENABLE_GPU
> >

Could this be an issue of a stale cache? All of the GPU code depends on 
HAVE_LIBGLEW being set, which is added as a pre-processor definition if you 
select ENABLE_GPU and the checks for GLEW and GLUT succeed. 

> >
> >
> > But even then I got
> > cd /usr/BUILD/BuildEnblend/src && /usr/bin/cmake -E cmake_link_script
> CMakeFiles/enblend.dir/link.txt --verbose=1
> > /usr/local/bin/c++ -fPIC CMakeFiles/enblend.dir/gpu.o
> CMakeFiles/enblend.dir/filenameparse.o CMakeFiles/enblend.dir/enblend.o
> -o ../bin/enblend -rdynamic vigra_impex/libvigra_impex.a -lglut -lXmu -
> lXi -lGLEW -lboost_thread -lboost_date_time -ljpeg -ltiff -lpng -lz -
> llcms -lxmi -lImath -lIlmImf -lIex -lHalf -lIlmThread -ltiff -lpng -lz
> > CMakeFiles/enblend.dir/enblend.o: In function
> `printVersionAndExit()':
> > enblend.cc:(.text+0x2652): undefined reference to `omp_get_nested'
> > ...
> > which means, the OpenMP Flags (-fopenmp on my system) were not set on
> > linking stage, which impiles, that OpenMP_FOUND were not set.
> >
> > .
> > I try to correct
> > Kornel

The flag OpenMP_FOUND doesn't really matter as much, at least not in the code. 
All that matters is whether or not _OPENMP is defined, and that should only be 
defined if your compiler has run with -fopenmp (in the case of GCC). There is 
no need for OpenMP_FOUND - if you select OpenMP, then OpenMP is marked as 
required, and if it's not found, compilation will stop right there. I suspect 
this could be a cache issue as well, of older object files.



--~--~-~--~~~---~--~~
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 for SVN 4352 / 2009.2

[Yuval Levy]

Seb Perez-D wrote:
> What would be great is a version of the Installer that does not need
> administrator rights. Since Hugin "just works" if you install it in a
> folder, I don't think that would cause (much) problems.
> 
> The fact is that I only have Hugin 0.7 (SVN 3407) on this (locked) machine...

It's most likely in the code generating the installer.

IIRC Ad is using a version that was already modified by Allard. I don't 
(yet) have access to it.

Ad, can you post your *.iss files? even better: I would suggest giving 
you SVN write access so that they can be put in there and kept in sync.

Ideally we'd have two sets of maintained *.iss files there - one for 
snapshots and one for releases.

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: Installer for SVN 4352 / 2009.2

[Yuval Levy]

Oskar Sander wrote:
> not worse than 0.8

that's what I need to hear for a release :-)


> GLpreview shows some crazy triangles and stuff, that are not visible in the
> standard preview and in final result. This is bug reported already, and no
> need for further bugreport/trace info, right?

if you have *detailed* trace info, more detail than what is the bug 
tracker already, you're most welcome to add it there.

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: Updated extended enfuse and enblend documentation

[Yuval Levy]

Harry van der Wolf wrote:
>conversion from texi to wiki (whatever rout you choose) is very cumbersome
> and very labour intensive.

and IMO the wrong way to go about the issue. Wiki format only makes 
sense if you want the pages to be editable in the Wiki. Good luck 
syncing with the official documentation if you do.

IIRC it is possible to put HTML markup inside a Wiki page (which would 
need to be write-protected anyway). And maybe it is also possible to 
forward a Wiki page to a static HTML URL?

I'd go the route of generating automatically non-editable versions of 
the official documentation.

How about parsing the generated HTML and put around it a wiki "skin", 
with the same links (e.g. navigation/tools/search/toolbox) on the side?


> I support both Christoph's point of view for having the latest up-to-date
> versions with the source

+2

> Klaus' point of view where it comes to easy access for a broad audience.

+1 - a static HTML page is easy access enough. A PDF is an added bonus. 
A wiki page has no benefit IMO.

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: Installer for SVN 4352 / 2009.2

[Yuval Levy]

Hi Ad,

Ad Huikeshoven wrote:
> Yuval asked me to build an installer based on 2009.2 branch in stead of
> trunk. This morning I succeeded in packaging something. It should be up at
> http://hugin.huikeshoven.org/ now.

thanks a lot!

can you check which version of autopano-SIFT-C is shipped with your 
installers?

details in the bug report ticket at:




You may have to replace Autopano-SIFT-C - IIRC the one in the SDK is 
still the old one.



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: cmake compilation of enblend prelease version 4.0

[Harry van der Wolf]

You are completely right. In the the target_link_library section were a
couple of X libs. I removed them for Apple but I removed libxmi as well and
that was stupid. now it works.

Harry

2009/9/9 Ryan Sleevi >

>  miNewGC is from libxmi. I'm guessing that cmake isn't quite finding it.
> Presumably, libxmi (and lcms) need to be set to REQUIRED in the find_library
> calls, as they are necessary. That should allow CMake to bubble the error up
> if it's having trouble resolving where you put it.
>
>
>
>
>
>
>
> *From:* hugin-ptx@googlegroups.com [mailto:hugin-...@googlegroups.com] *On
> Behalf Of *Harry van der Wolf
> *Sent:* Wednesday, September 09, 2009 7:50 AM
> *To:* hugin-ptx@googlegroups.com
> *Subject:* [hugin-ptx] cmake compilation of enblend prelease version 4.0
>
>
>
> All,
>
>
>
> I have lifted this discussion to the hugin-ptx list to make it available
> for everyone. I also skipped the rest of the conversation to remove all the
> email addresses from the "private" conversation.
>
>
>
> *...@christoph*: Please implement the attached "gpu_patch.diff" patch to the
> repository. It is necessary for OSX, both for autoconf and cmake.
>
>
>
> *...@kornel:* You write that we don't need Boost. As such you are right as
> you can compile without Boost. However, when boost-filesystem is available
> enblend/enfuse will use it. That's why I had Boost detection in my cmake
> stuff (but it didn't work correctly in compilation)
>
>
>
> I can now compile against GLUT and GLEW, so I have a gpu enabled
> enblend/enfuse. I had to modify config.h.cmake, configurechecks.cmake and
> src/CMakelists.txt for correct detection of openGL.framework on apple and
> for linking against the correct libraries. These three files are attached in
> the "mod-KB-cmakefiles.tgz". I did not have to change anything else.
>
>
>
> Note: The compilation via cmake is really very, very fast compared with
> the current autoconf method.
>
> When running either "enblend --gpu -o pipo.tif " or  "enblend
> -o pipo.tif ", I do get the following error.
>
>
>
> /usr/local/bin/enblend --gpu -v -o pipo.tif 1222-021*.tif
> : info: using graphics card: NVIDIA Corporation
> : info:renderer: NVIDIA GeForce 9600M GT OpenGL Engine
> enblend: info: loading next image: 1222-021-1222-025.tif 1/1
> enblend: info: loading next image: 1222-021-1222-0250001.tif 1/1
> enblend: info: creating blend mask: 1/3 2/3 3/3
> enblend: info: optimizing 1 distinct seam
> enblend: info: strategy 1, s0: 1/4 2/4 3/4 4/4
> enblend: info: strategy 2: s0
> dyld: lazy symbol binding failed: Symbol not found: _miNewGC
>   Referenced from: /usr/local/bin/enblend
>   Expected in: flat namespace
>
> dyld: Symbol not found: _miNewGC
>   Referenced from: /usr/local/bin/enblend
>   Expected in: flat namespace
>
> Trace/BPT trap
> Antares-4:enblend harryvanderwolf$ /usr/local/bin/enblend  -v -o pipo.tif
> 1222-021*.tif
> enblend: info: loading next image: 1222-021-1222-025.tif 1/1
> enblend: info: loading next image: 1222-021-1222-0250001.tif 1/1
> enblend: info: creating blend mask: 1/3 2/3 3/3
> enblend: info: optimizing 1 distinct seam
> enblend: info: strategy 1, s0: 1/4 2/4 3/4 4/4
> enblend: info: strategy 2: s0
> dyld: lazy symbol binding failed: Symbol not found: _miNewGC
>   Referenced from: /usr/local/bin/enblend
>   Expected in: flat namespace
>
> dyld: Symbol not found: _miNewGC
>   Referenced from: /usr/local/bin/enblend
>   Expected in: flat namespace
>
> Trace/BPT trap
>
>
>
> It's referenced from mask.h where it's used but that's as far as I come.
>
>
> Harry
>
>
>   2009/9/8 Kornel Benko
>
> Am Dienstag 08 September 2009 schrieb Yuval Levy:
> ...
>
>
> > *I* am a code-monkey :-) Kornel did most of the hard job on the CMake
> > build and deserves all the credits.
>
>
>
> I feel GOOD
>
>
>
>
>
> > > OK, so we may create something working on more then one platform.
> >
> > reminds me that I did not yet even try on Windows. I'm stuck with not
> > being able to build lcms-1.18a inside the Hugin SDK (which has 1.17). It
> > does find the TIFF and JPEG headers; and when I manually edit the source
> > code to find the TIFFs .h (I have not yet tried with the JPEG) it does
> > not link.
> >
> > > Sorry for the extra work to bring the files together.
> >
> > no need to apologize. thank you everybody for your contribution and
> > patience. maybe we should continue talking on hugin-ptx? whoever
> > transfers the thread, make sure email addresses are *not* transferred,
> > and do not CC (at least not me) the email addresses currently on this
> > thread.
>
>
>
> I lookud at the cmake-files from Harry. I may have overseen something, but
> most of things we not had were not needed.
>
>
>
> (e.g. definition of BINDIR, DATADIR or LOCALEDIR)
> "src/win32helpers/CMakeLists.txt" were included, but the is essentially
> empty. There may come something later,
> so I integrated it.
>
>
>
> Also I added the definitions for APPLE.
>
>
>
> We do not need boost, nor do we need KDE.
>
>
>

[hugin-ptx] Re: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Kornel Benko]

It compiles now.
We have to set OpenMP_FOUND  somewhere. Maybe in FindOpenMP.cmake?

But why do you prefer image_cache and no openmp be default?

Kornel

Am Wednesday 09 September 2009 schrieb Kornel Benko:
> Am Wednesday 09 September 2009 schrieb Kornel Benko:
> > I try to compile now on OpenSuSE.
> > 
> CMake Error at CMakeLists.txt:131 (FIND_PACKAGE):
>   Could not find module Findlibxmi.cmake or a configuration file for package
>   libxmi.
> 
> This is because on linux you have to search for "LibXMI"  ==> 
> FIND_PACKAGE(LibXMI REQUIRED)
> 
> 
> 
> 
> CMake Error at CMakeLists.txt:130 (FIND_PACKAGE):
>   Could not find module Findlcms.cmake or a configuration file for package
>   lcms.
> 
> there is only FindLCMS.cmake in CMakeModules ==> FIND_PACKAGE(LCMS REQUIRED)
> 
> Apart from that, it compiled, but the linking stage was erroneous.
> 
> cd /usr/BUILD/BuildEnblend/src && /usr/bin/cmake -E cmake_link_script 
> CMakeFiles/enblend.dir/link.txt --verbose=1
> /usr/local/bin/c++ -fPIC CMakeFiles/enblend.dir/gpu.o 
> CMakeFiles/enblend.dir/filenameparse.o CMakeFiles/enblend.dir/enblend.o  -o
> ../bin/enblend -rdynamic vigra_impex/libvigra_impex.a -lboost_thread 
> -lboost_date_time -ljpeg -ltiff -lpng -lz -llcms -lxmi -lImath -l
> IlmImf -lIex -lHalf -lIlmThread -ltiff -lpng -lz
> CMakeFiles/enblend.dir/gpu.o: In function `checkFramebufferStatus()':
> gpu.cc:(.text+0xb): undefined reference to `__glewCheckFramebufferStatusEXT'
> CMakeFiles/enblend.dir/gpu.o: In function `clearGPUTextures()':
> gpu.cc:(.text+0x21a): undefined reference to `__glewDeleteFramebuffersEXT'
> gpu.cc:(.text+0x235): undefined reference to `glDeleteTextures'
> 
> 
> Missing -lglew, even when _not_ enabling ENABLE_GPU
> 
> 
> 
> But even then I got
> cd /usr/BUILD/BuildEnblend/src && /usr/bin/cmake -E cmake_link_script 
> CMakeFiles/enblend.dir/link.txt --verbose=1
> /usr/local/bin/c++ -fPIC CMakeFiles/enblend.dir/gpu.o 
> CMakeFiles/enblend.dir/filenameparse.o CMakeFiles/enblend.dir/enblend.o  -o 
> ../bin/enblend -rdynamic vigra_impex/libvigra_impex.a -lglut -lXmu -lXi 
> -lGLEW -lboost_thread -lboost_date_time -ljpeg -ltiff -lpng -lz -llcms -lxmi 
> -lImath -lIlmImf -lIex -lHalf -lIlmThread -ltiff -lpng -lz
> CMakeFiles/enblend.dir/enblend.o: In function `printVersionAndExit()':
> enblend.cc:(.text+0x2652): undefined reference to `omp_get_nested'
> ...
> which means, the OpenMP Flags (-fopenmp on my system) were not set on linking 
> stage, which impiles, that 
> OpenMP_FOUND were not set.
> 
> .
> I try to correct
>   Kornel



-- 
Kornel Benko
kornel.be...@berlin.de


signature.asc
Description: This is a digitally signed message part.

[hugin-ptx] Re: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Kornel Benko]

Am Wednesday 09 September 2009 schrieb Kornel Benko:
> I try to compile now on OpenSuSE.
> 
CMake Error at CMakeLists.txt:131 (FIND_PACKAGE):
  Could not find module Findlibxmi.cmake or a configuration file for package
  libxmi.

This is because on linux you have to search for "LibXMI"  ==> 
FIND_PACKAGE(LibXMI REQUIRED)




CMake Error at CMakeLists.txt:130 (FIND_PACKAGE):
  Could not find module Findlcms.cmake or a configuration file for package
  lcms.

there is only FindLCMS.cmake in CMakeModules ==> FIND_PACKAGE(LCMS REQUIRED)

Apart from that, it compiled, but the linking stage was erroneous.

cd /usr/BUILD/BuildEnblend/src && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/enblend.dir/link.txt --verbose=1
/usr/local/bin/c++ -fPIC CMakeFiles/enblend.dir/gpu.o 
CMakeFiles/enblend.dir/filenameparse.o CMakeFiles/enblend.dir/enblend.o  -o
../bin/enblend -rdynamic vigra_impex/libvigra_impex.a -lboost_thread 
-lboost_date_time -ljpeg -ltiff -lpng -lz -llcms -lxmi -lImath -l
IlmImf -lIex -lHalf -lIlmThread -ltiff -lpng -lz
CMakeFiles/enblend.dir/gpu.o: In function `checkFramebufferStatus()':
gpu.cc:(.text+0xb): undefined reference to `__glewCheckFramebufferStatusEXT'
CMakeFiles/enblend.dir/gpu.o: In function `clearGPUTextures()':
gpu.cc:(.text+0x21a): undefined reference to `__glewDeleteFramebuffersEXT'
gpu.cc:(.text+0x235): undefined reference to `glDeleteTextures'


Missing -lglew, even when _not_ enabling ENABLE_GPU



But even then I got
cd /usr/BUILD/BuildEnblend/src && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/enblend.dir/link.txt --verbose=1
/usr/local/bin/c++ -fPIC CMakeFiles/enblend.dir/gpu.o 
CMakeFiles/enblend.dir/filenameparse.o CMakeFiles/enblend.dir/enblend.o  -o 
../bin/enblend -rdynamic vigra_impex/libvigra_impex.a -lglut -lXmu -lXi -lGLEW 
-lboost_thread -lboost_date_time -ljpeg -ltiff -lpng -lz -llcms -lxmi -lImath 
-lIlmImf -lIex -lHalf -lIlmThread -ltiff -lpng -lz
CMakeFiles/enblend.dir/enblend.o: In function `printVersionAndExit()':
enblend.cc:(.text+0x2652): undefined reference to `omp_get_nested'
...
which means, the OpenMP Flags (-fopenmp on my system) were not set on linking 
stage, which impiles, that 
OpenMP_FOUND were not set.

.
I try to correct
Kornel
-- 
Kornel Benko
kornel.be...@berlin.de


signature.asc
Description: This is a digitally signed message part.

[hugin-ptx] Re: cmake compilation of enblend [was: Enblend bug tracker and developer mailing list]

[Kornel Benko]

Am Wednesday 09 September 2009 schrieb Ryan Sleevi:
> Ok, so a sleepless night later, and I've got a rough-and-tumble 
> feels-like-a-hack just-learned-cmake build on Win32 going up. 
> 
>  
> 
> Lots of CMake hacking. Makes me miss SCons, Gyp, and qmake, all of which I 
> find less frustrating :) Much appreciation for Kornel and Yuval for the 
> heavy-lifting!
> 
>  
> 
> I apologize if the documentation isn't correct for the modules (In fact, I 
> know several of the ones I wrote are a bit lacking ATM), but I wanted to try 
> to get it into others' hands so they could give the build a go. 
> 
>  
> 
> There are still numerous build warnings (mostly around config.h wonkiness), 
> and some nasty hacks presently (eg: STLport), but hey, compiling is 
> compiling, right? 
> I did remove several pieces from the config.h.cmake that I could not find any 
> usage of in any of the included files,
> which I suspect may have been automake cruft that was never actually used.

This may well be. I did'nt check, it this variables were used. Instead I 
concentrated on creating config.h  similar to automake.

> If I'm wrong, and I broke something, sincerest apologies.   
> 

Not too happy about this.
The advantage with my way _was_ that I could compare the config.h to see if 
something changed.

> 
> I also introduced options for the four variables - OpenMP, Image Cache, GPU, 
> and SSE2 - if someone can double check that I appropriately interpreted
> the defines/exclusions and such, as I only had the Visual Studio project to 
> go by. 
> 

I wanted to wait with this, butt ok... 
> 
> Hopefully these files will be checked in the repo, so diffs/changes can be 
> managed easier and we can work more collaboratively. On that note, would 
> someone mind granting access, sourceforge id ryansleevi? :)
> 

Good work.

I try to compile now on OpenSuSE.

Kornel
-- 
Kornel Benko
kornel.be...@berlin.de


signature.asc
Description: This is a digitally signed message part.

[hugin-ptx] Re: hugin installation issue

[sebastien delcoigne]

I know the symbolic link option is not optimal. It was just meant to test if
hugin was working and as I predicted somethings aren't. I've encountered a
crash when trying to create a panorama. i'll keep investigating. Thank you
very much for the help.

> I guess I'm missing a environment variable ...
>
> Or your ld-configuration is not up to date. Look in /etc/ld.so.conf and at
> /etc/ld.so.conf.d/*
> Correct it and then
>sudo ldconfig
> to make the system loader know.
>
> > As a fix, I've created symbolic links in that folder to all the libraries
> in
> > my hugin-build/hugin-2009.07.1-Linux/lib folder. Now I have a running
> > interface.
>
> I woul'd not recommend it.
>
> > I'll be conducting several tests to see if everything works.
> >
> >
>
> Kornel
>
> --
> Kornel Benko
> kornel.be...@berlin.de
>



-- 
Sébastien

--~--~-~--~~~---~--~~
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: Updated extended enfuse and enblend documentation

[Erik Krause]

michael crane wrote:

> I converted enblend.texi to html ok with texi2html then the perl
> thingy HTML::WikiConverter::MediaWiki seemed to hang  converting to
> mediawiki so maybe I did something wrong not having used perl much.
> I found an webbased converter for html2wiki but when I paste the
> result into a mediawiki page some of the links work and some show the
> links as html.It might be me not having used mediawiki 'till just now.

Thanks for your efforts. The current wiki pages where converted from the 
HTML version using one of this online converters and then manually 
corrected using TeX for the formulas taken directly from the texi docs. 
The PDF version was used to proof the formula layout (wiki TeX is a bit 
different to texi).

It seems as if there is some information lost in any conversion step. 
Hence my hope was, that all this should be possible to do automatically 
with texi2html and the help of mediawiki.init

If the result isn't usable without manual tweaking and if you decide to 
not use he wiki version for proof reading and user contributions it 
probably would be best to have the wiki page pointing to the versions on 
panorama.dyndns.org (or any other up to date version).

However, I think you should consider it: The wiki has a nice DIFF tool 
with the possibility to revert to any previous versions easily, it has 
section editing and a related discussion page. And it's much easier to 
use than a source control system, at least for a non-programmer.

best regards
-- 
Erik Krause
http://www.erik-krause.de

--~--~-~--~~~---~--~~
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 installation issue

[Kornel Benko]

Am Wednesday 09 September 2009 schrieb sebastien delcoigne:
> Thanks Kornel,
> 
> No there weren't any deb files. Which is surprinsing given the command line.
> 
> 
> Anyway, I have uncompressed the tar archive and taken a closer look at the
> output of strace and found where it was looking for the libs in question. It
> was looking in directory : /usr/lib/x86_64-linux-gnu
> 
> I guess I'm missing a environment variable ...

Or your ld-configuration is not up to date. Look in /etc/ld.so.conf and at 
/etc/ld.so.conf.d/*
Correct it and then
sudo ldconfig
to make the system loader know.

> As a fix, I've created symbolic links in that folder to all the libraries in
> my hugin-build/hugin-2009.07.1-Linux/lib folder. Now I have a running
> interface.

I woul'd not recommend it.

> I'll be conducting several tests to see if everything works.
> 
> 

Kornel

-- 
Kornel Benko
kornel.be...@berlin.de


signature.asc
Description: This is a digitally signed message part.

[hugin-ptx] Re: cmake compilation of enblend prelease version 4.0

[Ryan Sleevi]

miNewGC is from libxmi. I'm guessing that cmake isn't quite finding it. 
Presumably, libxmi (and lcms) need to be set to REQUIRED in the find_library 
calls, as they are necessary. That should allow CMake to bubble the error up if 
it's having trouble resolving where you put it.

 

 

 

From: hugin-ptx@googlegroups.com [mailto:hugin-...@googlegroups.com] On Behalf 
Of Harry van der Wolf
Sent: Wednesday, September 09, 2009 7:50 AM
To: hugin-ptx@googlegroups.com
Subject: [hugin-ptx] cmake compilation of enblend prelease version 4.0

 

All,

 

I have lifted this discussion to the hugin-ptx list to make it available for 
everyone. I also skipped the rest of the conversation to remove all the email 
addresses from the "private" conversation.

 

@Christoph: Please implement the attached "gpu_patch.diff" patch to the 
repository. It is necessary for OSX, both for autoconf and cmake.

 

@Kornel: You write that we don't need Boost. As such you are right as you can 
compile without Boost. However, when boost-filesystem is available 
enblend/enfuse will use it. That's why I had Boost detection in my cmake stuff 
(but it didn't work correctly in compilation)

 

I can now compile against GLUT and GLEW, so I have a gpu enabled 
enblend/enfuse. I had to modify config.h.cmake, configurechecks.cmake and 
src/CMakelists.txt for correct detection of openGL.framework on apple and for 
linking against the correct libraries. These three files are attached in the 
"mod-KB-cmakefiles.tgz". I did not have to change anything else.

 

Note: The compilation via cmake is really very, very fast compared with the 
current autoconf method.

When running either "enblend --gpu -o pipo.tif " or  "enblend -o 
pipo.tif ", I do get the following error.

 

/usr/local/bin/enblend --gpu -v -o pipo.tif 1222-021*.tif
: info: using graphics card: NVIDIA Corporation
: info:renderer: NVIDIA GeForce 9600M GT OpenGL Engine
enblend: info: loading next image: 1222-021-1222-025.tif 1/1
enblend: info: loading next image: 1222-021-1222-0250001.tif 1/1
enblend: info: creating blend mask: 1/3 2/3 3/3
enblend: info: optimizing 1 distinct seam
enblend: info: strategy 1, s0: 1/4 2/4 3/4 4/4
enblend: info: strategy 2: s0
dyld: lazy symbol binding failed: Symbol not found: _miNewGC
  Referenced from: /usr/local/bin/enblend
  Expected in: flat namespace

dyld: Symbol not found: _miNewGC
  Referenced from: /usr/local/bin/enblend
  Expected in: flat namespace

Trace/BPT trap
Antares-4:enblend harryvanderwolf$ /usr/local/bin/enblend  -v -o pipo.tif 
1222-021*.tif
enblend: info: loading next image: 1222-021-1222-025.tif 1/1
enblend: info: loading next image: 1222-021-1222-0250001.tif 1/1
enblend: info: creating blend mask: 1/3 2/3 3/3
enblend: info: optimizing 1 distinct seam
enblend: info: strategy 1, s0: 1/4 2/4 3/4 4/4
enblend: info: strategy 2: s0
dyld: lazy symbol binding failed: Symbol not found: _miNewGC
  Referenced from: /usr/local/bin/enblend
  Expected in: flat namespace

dyld: Symbol not found: _miNewGC
  Referenced from: /usr/local/bin/enblend
  Expected in: flat namespace

Trace/BPT trap

 

It's referenced from mask.h where it's used but that's as far as I come.


Harry




2009/9/8 Kornel Benko

Am Dienstag 08 September 2009 schrieb Yuval Levy:
... 


> *I* am a code-monkey :-) Kornel did most of the hard job on the CMake
> build and deserves all the credits.

 

I feel GOOD 

 

 

> > OK, so we may create something working on more then one platform.
>
> reminds me that I did not yet even try on Windows. I'm stuck with not
> being able to build lcms-1.18a inside the Hugin SDK (which has 1.17). It
> does find the TIFF and JPEG headers; and when I manually edit the source
> code to find the TIFFs .h (I have not yet tried with the JPEG) it does
> not link.
>
> > Sorry for the extra work to bring the files together.
>
> no need to apologize. thank you everybody for your contribution and
> patience. maybe we should continue talking on hugin-ptx? whoever
> transfers the thread, make sure email addresses are *not* transferred,
> and do not CC (at least not me) the email addresses currently on this
> thread.

 

I lookud at the cmake-files from Harry. I may have overseen something, but most 
of things we not had were not needed.

 

(e.g. definition of BINDIR, DATADIR or LOCALEDIR)
"src/win32helpers/CMakeLists.txt" were included, but the is essentially empty. 
There may come something later,
so I integrated it.

 

Also I added the definitions for APPLE.

 

We do not need boost, nor do we need KDE.

 

> Yuv

 

The CMakeModules is now part of enblend. But I would like to use the hugin 
directory.
Chritoph, is it possible in mercurial to add a directory which references 
another project?
I saw something in this direction in mplayer project, but this was with svn.

 

 

Attaching my version of cmakefiles ...
which again compiles on ubuntu, after someone added "DEFAULT_VERBOSITY" 

 

 

Kornel

 




--~--~-~--~~---

[hugin-ptx] cmake compilation of enblend prelease version 4.0

[Harry van der Wolf]

All,

I have lifted this discussion to the hugin-ptx list to make it available for
everyone. I also skipped the rest of the conversation to remove all the
email addresses from the "private" conversation.

*...@christoph*: Please implement the attached "gpu_patch.diff" patch to the
repository. It is necessary for OSX, both for autoconf and cmake.

*...@kornel:* You write that we don't need Boost. As such you are right as you
can compile without Boost. However, when boost-filesystem is available
enblend/enfuse will use it. That's why I had Boost detection in my cmake
stuff (but it didn't work correctly in compilation)

I can now compile against GLUT and GLEW, so I have a gpu enabled
enblend/enfuse. I had to modify config.h.cmake, configurechecks.cmake and
src/CMakelists.txt for correct detection of openGL.framework on apple and
for linking against the correct libraries. These three files are attached in
the "mod-KB-cmakefiles.tgz". I did not have to change anything else.

Note: The compilation via cmake is really very, very fast compared with
the current autoconf method.

When running either "enblend --gpu -o pipo.tif " or  "enblend
-o pipo.tif ", I do get the following error.

/usr/local/bin/enblend --gpu -v -o pipo.tif 1222-021*.tif
: info: using graphics card: NVIDIA Corporation
: info:renderer: NVIDIA GeForce 9600M GT OpenGL Engine
enblend: info: loading next image: 1222-021-1222-025.tif 1/1
enblend: info: loading next image: 1222-021-1222-0250001.tif 1/1
enblend: info: creating blend mask: 1/3 2/3 3/3
enblend: info: optimizing 1 distinct seam
enblend: info: strategy 1, s0: 1/4 2/4 3/4 4/4
enblend: info: strategy 2: s0
dyld: lazy symbol binding failed: Symbol not found: _miNewGC
  Referenced from: /usr/local/bin/enblend
  Expected in: flat namespace

dyld: Symbol not found: _miNewGC
  Referenced from: /usr/local/bin/enblend
  Expected in: flat namespace

Trace/BPT trap
Antares-4:enblend harryvanderwolf$ /usr/local/bin/enblend  -v -o pipo.tif
1222-021*.tif
enblend: info: loading next image: 1222-021-1222-025.tif 1/1
enblend: info: loading next image: 1222-021-1222-0250001.tif 1/1
enblend: info: creating blend mask: 1/3 2/3 3/3
enblend: info: optimizing 1 distinct seam
enblend: info: strategy 1, s0: 1/4 2/4 3/4 4/4
enblend: info: strategy 2: s0
dyld: lazy symbol binding failed: Symbol not found: _miNewGC
  Referenced from: /usr/local/bin/enblend
  Expected in: flat namespace

dyld: Symbol not found: _miNewGC
  Referenced from: /usr/local/bin/enblend
  Expected in: flat namespace

Trace/BPT trap
It's referenced from mask.h where it's used but that's as far as I come.

Harry



2009/9/8 Kornel Benko

> Am Dienstag 08 September 2009 schrieb Yuval Levy:
> ...
> > *I* am a code-monkey :-) Kornel did most of the hard job on the CMake
> > build and deserves all the credits.
>
>
> I feel GOOD
>
>
> > > OK, so we may create something working on more then one platform.
> >
> > reminds me that I did not yet even try on Windows. I'm stuck with not
> > being able to build lcms-1.18a inside the Hugin SDK (which has 1.17). It
> > does find the TIFF and JPEG headers; and when I manually edit the source
> > code to find the TIFFs .h (I have not yet tried with the JPEG) it does
> > not link.
> >
> > > Sorry for the extra work to bring the files together.
> >
> > no need to apologize. thank you everybody for your contribution and
> > patience. maybe we should continue talking on hugin-ptx? whoever
> > transfers the thread, make sure email addresses are *not* transferred,
> > and do not CC (at least not me) the email addresses currently on this
> > thread.
>
>
> I lookud at the cmake-files from Harry. I may have overseen something, but
> most of things we not had were not needed.
>
>
> (e.g. definition of BINDIR, DATADIR or LOCALEDIR)
> "src/win32helpers/CMakeLists.txt" were included, but the is essentially
> empty. There may come something later,
> so I integrated it.
>
>
> Also I added the definitions for APPLE.
>
>
> We do not need boost, nor do we need KDE.
>
>
> > Yuv
>
>
> The CMakeModules is now part of enblend. But I would like to use the hugin
> directory.
> Chritoph, is it possible in mercurial to add a directory which references
> another project?
> I saw something in this direction in mplayer project, but this was with
> svn.
>
>
>
> Attaching my version of cmakefiles ...
> which again compiles on ubuntu, after someone added "DEFAULT_VERBOSITY"
>
>
> Kornel
>
>
>

--~--~-~--~~~---~--~~
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 installation issue

[sebastien delcoigne]

Thanks Kornel,

No there weren't any deb files. Which is surprinsing given the command line.


Anyway, I have uncompressed the tar archive and taken a closer look at the
output of strace and found where it was looking for the libs in question. It
was looking in directory : /usr/lib/x86_64-linux-gnu

I guess I'm missing a environment variable ...

As a fix, I've created symbolic links in that folder to all the libraries in
my hugin-build/hugin-2009.07.1-Linux/lib folder. Now I have a running
interface.

I'll be conducting several tests to see if everything works.


-- 
Sébastien

--~--~-~--~~~---~--~~
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: Mailing List(s)

[Bart van Andel]

> [...] I rather think that we will
> have one separated list for notifications (tracker and commits), and one
> separated list for talk (which can very well be hugin-ptx if the users
> tolerate more dev talk).

As a user with an interest in coding and algorithms, I'm pretty happy
with the way the hugin-ptx list is working right now, but the approach
mentioned above seems fair. Since I'm reading all the list messages
through the Google Groups interface [0], everything gets grouped
properly already, and a few extra messages to read or decline won't
hurt.

[0] http://groups.google.com/group/hugin-ptx/

--
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: Installer for SVN 4352 / 2009.2

[Oskar Sander]

Preliminary, it installs and works OK (at least not worse than 0.8) with a
couple of old projects of mine on my XP.

GLpreview shows some crazy triangles and stuff, that are not visible in the
standard preview and in final result. This is bug reported already, and no
need for further bugreport/trace info, right?

Cheers
/O

2009/9/9 Ad Huikeshoven 

> Hi,
>
> Yuval asked me to build an installer based on 2009.2 branch in stead of
> trunk. This morning I succeeded in packaging something. It should be up at
> http://hugin.huikeshoven.org/ now.
>
> Ad Huikeshoven
>
> >
>


-- 
/O

--~--~-~--~~~---~--~~
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: strangely calling antipano-sift-c

[Bart van Andel]

If a previous version of Hugin (on Windows) was installed with and
setup for autopano-sift-c (0.7.0 included this optionally if I
remember correctly), these settings are saved in the registry. Since
all Hugin versions use the same registry keys, newer versions may use
old settings if those aren't cleaned up. I guess this is what is
happening here.

--
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: Installer for SVN 4352 / 2009.2

[Seb Perez-D]

On Wed, Sep 9, 2009 at 11:45, Ad Huikeshoven wrote:
> Yuval asked me to build an installer based on 2009.2 branch in stead of
> trunk. This morning I succeeded in packaging something. It should be up at
> http://hugin.huikeshoven.org/ now.

What would be great is a version of the Installer that does not need
administrator rights. Since Hugin "just works" if you install it in a
folder, I don't think that would cause (much) problems.

The fact is that I only have Hugin 0.7 (SVN 3407) on this (locked) machine...

Cheers,

Seb

--~--~-~--~~~---~--~~
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] Installer for SVN 4352 / 2009.2

[Ad Huikeshoven]

Hi,

Yuval asked me to build an installer based on 2009.2 branch in stead of
trunk. This morning I succeeded in packaging something. It should be up at
http://hugin.huikeshoven.org/ now.

Ad Huikeshoven

--~--~-~--~~~---~--~~
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: Updated extended enfuse and enblend documentation

[michael crane]

2009/9/9 Harry van der Wolf :

> If you find some new, not so labour intensive route, from texi to wiki
> please let us know.

the newest texi2html seems to make perfect html in no time at all.
texi2html 1.82.
http://www.nongnu.org/texi2html/

The online converters to mediawiki that I tried fail with some
characters  missing sometimes and some of the anchor links do not
work.

http://toolserver.org/~diberri/cgi-bin/html2wiki/index.cgi

http://labs.seapine.com/htmltowiki.cgi

I think I can allow import html into my crispy new mikiwiki. I'll try
that and then see if I can export it.

regards

mick

--~--~-~--~~~---~--~~
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 installation issue

[Kornel Benko]

Am Wednesday 09 September 2009 schrieb sebastien delcoigne:
> I copy/pasted the command line directly from the tutorial :
> 
> cmake ../hugin -DENABLE_LAPACK=YES -DCPACK_BINARY_DEB:BOOL=ON
> -DCPACK_BINARY_NSIS:BOOL=OFF \
> -DCPACK_BINARY_RPM:BOOL=OFF -DCPACK_BINARY_STGZ:BOOL=OFF
> -DCPACK_BINARY_TBZ2:BOOL=OFF \
> -DCPACK_BINARY_TGZ:BOOL=OFF -DCPACK_BINARY_TZ:BOOL=OFF
> 
> I'll try it again. Do I need to remove the CMakeCache.txt file first ?

No, not needed. Is there (in the build-directory really no *.deb file?)

Try ldd on hugin executable and post the result.

Kornel
-- 
Kornel Benko
kornel.be...@berlin.de


signature.asc
Description: This is a digitally signed message part.

[hugin-ptx] Re: hugin installation issue

[sebastien delcoigne]

I copy/pasted the command line directly from the tutorial :

cmake ../hugin -DENABLE_LAPACK=YES -DCPACK_BINARY_DEB:BOOL=ON
-DCPACK_BINARY_NSIS:BOOL=OFF \
-DCPACK_BINARY_RPM:BOOL=OFF -DCPACK_BINARY_STGZ:BOOL=OFF
-DCPACK_BINARY_TBZ2:BOOL=OFF \
-DCPACK_BINARY_TGZ:BOOL=OFF -DCPACK_BINARY_TZ:BOOL=OFF

I'll try it again. Do I need to remove the CMakeCache.txt file first ?

On Wed, Sep 9, 2009 at 10:34 AM, Kornel Benko wrote:

> Am Wednesday 09 September 2009 schrieb sebastien.delcoigne:
> >
> > Hi all,
> >
> > After using the good ol' version 0.7 I've decided to have a look at
> > the newest features and began installing the trunk version from 2 days
> > ago. I have been following the tutorial at
> > http://wiki.panotools.org/Hugin_Compiling_ubuntu#Building_Hugin but I
> > am stuck at some point.
> >
> > In the hugin section, under build and install it is said to launch
> > cmake package command which is supposed to generate a deb package.
> > Instead I get a tar archive.
>
> You surelly forgot the parameter -DCPACK_BINARY_DEB:BOOL=ON for cmake
> (This is the only one with "ON")
>
> > It seems to contain all the necessary
> > elements but still I cannot launch hugin. I get an error saying the
> > computer does not find some libraries (libhugin something, I can post
> > the exact name if needed).
> >
> > I was wondering if I simply need to update (or create) an environment
> > variable or if I did something wrong somewhere.
> >
> > Any clues ?
>
>Kornel
> --
> Kornel Benko
> kornel.be...@berlin.de
>



-- 
Sébastien

--~--~-~--~~~---~--~~
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 installation issue

[Kornel Benko]

Am Wednesday 09 September 2009 schrieb sebastien.delcoigne:
> 
> Hi all,
> 
> After using the good ol' version 0.7 I've decided to have a look at
> the newest features and began installing the trunk version from 2 days
> ago. I have been following the tutorial at
> http://wiki.panotools.org/Hugin_Compiling_ubuntu#Building_Hugin but I
> am stuck at some point.
> 
> In the hugin section, under build and install it is said to launch
> cmake package command which is supposed to generate a deb package.
> Instead I get a tar archive.

You surelly forgot the parameter -DCPACK_BINARY_DEB:BOOL=ON for cmake
(This is the only one with "ON")

> It seems to contain all the necessary 
> elements but still I cannot launch hugin. I get an error saying the
> computer does not find some libraries (libhugin something, I can post
> the exact name if needed).
> 
> I was wondering if I simply need to update (or create) an environment
> variable or if I did something wrong somewhere.
> 
> Any clues ?

Kornel
-- 
Kornel Benko
kornel.be...@berlin.de


signature.asc
Description: This is a digitally signed message part.

[hugin-ptx] Re: Updated extended enfuse and enblend documentation

[Harry van der Wolf]

Hi Mick,

Thanks for your attempts.

In the previous round (February/March 2009) is have endlessly tossed around
with all kind of converters, also the one you are mentioning and also going
through all kind of intermediate formats. I have almost broken my system to
get the latest "bleading edge" svn/cvs versions of necessary tools but the
conversion from texi to wiki (whatever rout you choose) is very cumbersome
and very labour intensive. That's also the reason why I haven't started that
yet and have been searching for other conversion routes or extra plugi'n's
for the wiki to read/convert whatever intermediate format.
Until now: no results.
If you find some new, not so labour intensive route, from texi to wiki
please let us know.

I support both Christoph's point of view for having the latest up-to-date
versions with the source and Klaus' point of view where it comes to easy
access for a broad audience.

Harry

harry

2009/9/9 michael crane 

>
> texi2html was moaning about lines that contain @tie
>
> @tie{}C
>
> maybe it is something to do with that ?
>  mick
>
> >
>

--~--~-~--~~~---~--~~
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 installation issue

[sebastien.delcoigne]

A few more info just in case :
running ubuntu studio Hardy (e.g ubuntu 8.04) on an AMD64

On 9 sep, 10:26, "sebastien.delcoigne" 
wrote:
> Hi all,
>
> After using the good ol' version 0.7 I've decided to have a look at
> the newest features and began installing the trunk version from 2 days
> ago. I have been following the tutorial 
> athttp://wiki.panotools.org/Hugin_Compiling_ubuntu#Building_Huginbut I
> am stuck at some point.
>
> In the hugin section, under build and install it is said to launch
> cmake package command which is supposed to generate a deb package.
> Instead I get a tar archive. It seems to contain all the necessary
> elements but still I cannot launch hugin. I get an error saying the
> computer does not find some libraries (libhugin something, I can post
> the exact name if needed).
>
> I was wondering if I simply need to update (or create) an environment
> variable or if I did something wrong somewhere.
>
> Any clues ?
>
> Thanks for the help.
--~--~-~--~~~---~--~~
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 installation issue

[sebastien.delcoigne]

Hi all,

After using the good ol' version 0.7 I've decided to have a look at
the newest features and began installing the trunk version from 2 days
ago. I have been following the tutorial at
http://wiki.panotools.org/Hugin_Compiling_ubuntu#Building_Hugin but I
am stuck at some point.

In the hugin section, under build and install it is said to launch
cmake package command which is supposed to generate a deb package.
Instead I get a tar archive. It seems to contain all the necessary
elements but still I cannot launch hugin. I get an error saying the
computer does not find some libraries (libhugin something, I can post
the exact name if needed).

I was wondering if I simply need to update (or create) an environment
variable or if I did something wrong somewhere.

Any clues ?

Thanks for the help.
--~--~-~--~~~---~--~~
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 installation issue

[sebastien.delcoigne]

Hi all,

After using the good ol' version 0.7 I've decided to have a look at
the newest features and began install the trunk version (from 2 days
ago). I have been following the tutorial at
http://wiki.panotools.org/Hugin_Compiling_ubuntu#Building_Hugin but I
am stuck at some point.

In the hugin section, under build and install it is said to launch
cmake package command which is supposed to geenrate
--~--~-~--~~~---~--~~
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: strangely calling antipano-sift-c

[Seb Perez-D]

On Wed, Sep 9, 2009 at 08:48, Elvis wrote:
> And I check my hugin SVN 3478, there is no antipano-sift-c excutable,
>
> but there is a antipano excutable,
>
> I thought builded hugin should call something which was created inside
> the project, but not a ready-made one,
>
> and I found there seems to be  no source code of antipano-sift-c, even
> in SVN 4096

I assume you mean autopano-sift-c ;-)

Autopano-sift-c (APSC for short) is not included in the same part of
the SVN tree as Hugin, but it has its own special folder. You need to
download it and build it separately.

http://wiki.panotools.org/Hugin_SDK_%28MSVC_2008%29#autopano-sift-C

Cheers,

Seb

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---