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

[Elvis]

Dear sir

I thought I have set the correct path for
Boost_THREAD_LIBARY_DEBUG &
Boost_THREAD_LIBARY_RELEASE,

but error message shows:
MESSAGE(FATAL_ERROR "boost thread library not found. If it is
installed with a\nunrecognized suffix, specify it with -
DBOOST_LIBRARYDIR= and -DBOOST_INCLUDEDIR=")

The path should be something like C:\hugin-trunk\boost_1_39_0\stage
\lib


if I randomly set the path directly to one of the the library file,
like
C:\hugin-trunk\boost_1_39_0\stage\lib\libboost_thread-vc90-mt-
s-1_39.lib
C:\hugin-trunk\boost_1_39_0\stage\lib\libboost_thread-vc90-mt-s.lib
C:\hugin-trunk\boost_1_39_0\stage\lib\libboost_thread-vc90-mt-
sgd-1_39.lib
C:\hugin-trunk\boost_1_39_0\stage\lib\libboost_thread-vc90-mt-sgd.lib

then, Cmake can pass it (but i dont know if I am doing right)and show
next error message.

Cmake Error at CMakeModules/FindPackegeHandleStandardArgs.cmake:51
(MESSAGE):
Could not fine REQUIRED package wsWidgers
Call Stack (most recent call first):
C:Program Files/CMake 2.6/share/cmake-2.6/Modules/FindwxWidgets.cmake:
782 (FIND_Package_HANDLE_STANDARD_ARGS)
CMakeLists.txt:106 (FINDPACKAGE)

But the wxWidgets_LIB_DIR has been located previously by Cmake to C:
\hugin-trunk\wxWidgets-2.8.10/lib/vc_lib

I am confused, what should I do to complete CMAKE ?

Thank you so much.

Elvis

btw:
win32
hugin-rc revision: 2094
Cmake vision: 2.6.4


On 8月6日, 下午4時45分, Elvis  wrote:
> Thank you so much,
>
> Now I am trying this way, building Hugin with updated SDK.
>
> Elvis
>
> On 8月5日, 下午5時58分, Guido Kohlmeyer  wrote:
>
>
>
> > The SDK which I built and refering in my last post is not appropriate to
> > build enblend/enfuse. It contains a pre-build version from enblend
> > homepage. It was discussed to extend the SDK to even build
> > enblend/enfuse, but so far there is no such SDK version available which
> > fits all build use scenarios on Win platform.
>
> > Guido
>
> > > Dear Guido
>
> > > Thank you so much,
>
> > > I will run the process again with updated environment immediatelly.
>
> > > I have a question,
>
> > > Should I rebuild Enblend with updated SDK?
>
> > > or it doesn't manner that Enblend is built with elder SDK, and Hugin
> > > is builted with updated SDK ?
>
> > > I really appreciate your help.
>
> > > Best regards
>
> > > Elvis- 隱藏被引用文字 -
>
> > - 顯示被引用文字 -- 隱藏被引用文字 -
>
> - 顯示被引用文字 -
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---

[hugin-ptx] Re: NOT SOLVED: Re: Enfuse unpicks alignment - what's up?

[Doug]

Hi Joachim,
I responded to Gerry before seeing your post, so I've inlined my 
comments after following his suggestions.

J. Schneider wrote:
> Gerry Patterson schrieb:
>   
>> Hello Doug,
>> ... Perhaps the following sequence will work:
>>
>>1. load both images into hugin.
>>2. Under the lens tab ensure they have the same lens number assigned
>>   to both images.
>> 
> No, different lens numbers, because he accidentally changed the zoom. 
>   
That would make sense - I couldn't see how to change the lens number and 
they were already assigned to 0 and 1

> But I wonder if the exif info isn't already correctly used by hugin. If 
> so the images should already be assigned no. 0 and no. 1.
>   
>>3. Create a few control points manually (say 5 or 6).  Ensure they
>>   are spread out across the images
>>4. Under optimizer tab select "Positions and View (y,p,r,v)  The
>>   maximum error should very small.  As in less than 1.  ...
>> 
I set a half-dozen control points manually. After optimising, the 
maximum error was 0.06

> If handheld it might be greater but even a few pixels should often work 
> acceptably.
>
> Optimizing for v wouldn't give sensible results if both images share the 
> same lens number. If they don't you can check one of them to be 
> optimized and one to stay fixed.
> If exif values for focal length are used correctly by hugin, optimizing 
> for v would only correct for slight rounding errors in this transmitted 
> data or for movement of the camera back or forth between shots.
>   

The remapped images were very crude and blocky; but as far as I could 
tell by overlaying them in Gimp or enfusing them, they were reasonably 
well aligned.
> regards
> Joachim
>
>   
What's  the explanation?

Doug

--~--~-~--~~~---~--~~
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: Request: Absolute paths for project files in .pto.mk

[Yuval Levy]

Milo van der Linden wrote:
> I have added it to the tracker:
> 
> https://sourceforge.net/tracker/?func=detail&aid=2834409&group_id=77506&atid=550444

perfect, thanks, great contribution! can't promise anything, bit it is 
on *my* list of things I'd like to do.

I am currently at the research part, looking for a library that handles 
preferences (this problem must have been solved gazillions of times, 
there are so many softwares that save them).

I am slow because I don't have much time. I am currently analyzing 
.

If other people find "preferences libraries" or "best practices to store 
preferences" or other interesting links/tools, I'll be happy to read / 
analyze them.

The ideal candidate will:
1. be multi-platform
2. have functions to store and retrieve preferences in C/C++ and Perl. 
Other languages optional and very welcome

My plan is to find such a library, branch out from trunk, implement a 
proof of concept. If the proof of concept works, we'll have to consider 
when to add it to trunk to minimize integration pains with other ongoing 
development.

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: NOT SOLVED: Re: Enfuse unpicks alignment - what's up?

[J. Schneider]

Gerry Patterson schrieb:
> Hello Doug,
> ... Perhaps the following sequence will work:
> 
>1. load both images into hugin.
>2. Under the lens tab ensure they have the same lens number assigned
>   to both images.
No, different lens numbers, because he accidentally changed the zoom. 
But I wonder if the exif info isn't already correctly used by hugin. If 
so the images should already be assigned no. 0 and no. 1.
>3. Create a few control points manually (say 5 or 6).  Ensure they
>   are spread out across the images
>4. Under optimizer tab select "Positions and View (y,p,r,v)  The
>   maximum error should very small.  As in less than 1.  ...
If handheld it might be greater but even a few pixels should often work 
acceptably.

Optimizing for v wouldn't give sensible results if both images share the 
same lens number. If they don't you can check one of them to be 
optimized and one to stay fixed.
If exif values for focal length are used correctly by hugin, optimizing 
for v would only correct for slight rounding errors in this transmitted 
data or for movement of the camera back or forth between shots.

regards
Joachim

--~--~-~--~~~---~--~~
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: No Hugin 0.8 for Windows?

[Yuval Levy]

Test it, compare it to 0.7.0, and you will find out.
Yuv

Flo wrote:
> Cool, thanks!
> 
> So why don't they just put that one on the homepage?
> 
> 
> 
> On Aug 8, 11:15 pm, Harry van der Wolf  wrote:
>> Hi Flo,
>>
>> You can download hugin 0.8 windows versions from Allard's 
>> pages:http://allardkatan.net/misc/hugin/
>>
>> Harry
>>
>> 2009/8/8 Flo 
>>
>>
>>
>>> Hi everyone,
>>> I just wandet to make sure: Is there no official Windows version of
>>> Hugin 0.8 for me to just download and use?
>>> (The download-link on the homepage points to 0.7)
>>> If so, will there ever be one or is Windows just not officially
>>> supported?
>>> I'm one of those people who are just barely smart enough to use a
>>> computer (which is why I use Windows) but when it comes to programming
>>> and linux and stuff like that, I have no clue (I know, I tried...). So
>>> you shoudn't waste your time explaining me how to compile it (whatever
>>> that means) or whatever.
>>> Thank you,
>>> Flo.
> > 


--~--~-~--~~~---~--~~
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: NOT SOLVED: Re: Enfuse unpicks alignment - what's up?

[Doug]

Gerry Patterson wrote:
> On Sat, Aug 8, 2009 at 1:02 PM, Doug  > wrote:
>
> 
> >
> Evidently I spoke too soon.
> I assumed the problem arose from different magnificatiions and hadn't
> appreciated v should have corrected for that.
> I've also tried align-image-stack -m as suggested by Gerry. That gives
> an even worse result.
>
> Back to square one :-(
>
> Doug
>
>
> Hello Doug,
>
> Do you remember just how far apart in Ev the two images are (how many 
> stops different?).  I am wondering if there is just too much 
> difference that control points aren't getting generated properly  
> (Areas that are very light in one picture and very dark in the other, 
> makes finding control points difficult).  Perhaps the following 
> sequence will work:
>
>1. load both images into hugin.
>2. Under the lens tab ensure they have the same lens number
>   assigned to both images.
>3. Create a few control points manually (say 5 or 6).  Ensure they
>   are spread out across the images
>4. Under optimizer tab select "Positions and View (y,p,r,v)  The
>   maximum error should very small.  As in less than 1.  You can
>   check this after the dialog closes by pressing F3 and sorting by
>   distance
>5. Under stitcher select "remapped images"
>
> Now you can open the images and see how they overlay.  You should also 
> be able to pass them to enfuse as well.
>
> If you are comfortable with it, you can send me the images privately 
> and I can also try it from here.
>
> - Gerry
>
Thanks Gerry. I'll get back to you as soon as all the grandchildren have 
departed!
Doug

--~--~-~--~~~---~--~~
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: Request: Absolute paths for project files in .pto.mk

[Milo van der Linden]

Thanks Gerry and Yuval for the responses!

I have added it to the tracker:

https://sourceforge.net/tracker/?func=detail&aid=2834409&group_id=77506&atid=550444

And added your responses as comments.

For now I will distribute my project without the mk file!

Kind regards,

Milo


--~--~-~--~~~---~--~~
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] KImageFuser 0.3.0.1 - New release and KImageFuser now added to Hugin svn

[Harry van der Wolf]

Hi all,

(KImageFuser is a graphical interface for enfuse and align_image_stack for
Linux).

On request of Bruno Postle I added KImageFuser to the hugin svn as new
separate top-level "project" like autopano-sift-C and panoglview. You can
retrieve it with https://hugin.svn.sourceforge.net/svnroot/hugin/KImageFuser>. I did not
create a separate trunk and/or branches as KImageFuser is currently only one
script.

For the time being it is also available from my own webpages at <
http://panorama.dyndns.org/index.php?lang=en&subject=KImageFuser&texttag=KImagefuser>,
but that one might be stopped recently soon. I don't know yet.

The 0.3.0.1 is only a "cosmetic" update over the 0.3.0 to make the look &
feel more stable on multiple linux distro's.

Hoi,
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: No Hugin 0.8 for Windows?

[Flo]

Cool, thanks!

So why don't they just put that one on the homepage?



On Aug 8, 11:15 pm, Harry van der Wolf  wrote:
> Hi Flo,
>
> You can download hugin 0.8 windows versions from Allard's 
> pages:http://allardkatan.net/misc/hugin/
>
> Harry
>
> 2009/8/8 Flo 
>
>
>
> > Hi everyone,
>
> > I just wandet to make sure: Is there no official Windows version of
> > Hugin 0.8 for me to just download and use?
> > (The download-link on the homepage points to 0.7)
> > If so, will there ever be one or is Windows just not officially
> > supported?
>
> > I'm one of those people who are just barely smart enough to use a
> > computer (which is why I use Windows) but when it comes to programming
> > and linux and stuff like that, I have no clue (I know, I tried...). So
> > you shoudn't waste your time explaining me how to compile it (whatever
> > that means) or whatever.
>
> > Thank you,
> > Flo.
--~--~-~--~~~---~--~~
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: coding style

[Lukáš Jirkovský]

2009/8/8 Yuval Levy :
>
> Hi Lukáš
>
> Lukáš Jirkovský wrote:
>> I like more loose coding style. Spending a day learning what to do and
>> what not to do is IMO boring.
>
> I see where you are coming from, and me too I prefer loose. I don't feel
> like policing contributors. But then I see where I am coming from and I
> think I need and want guidance before I damage the project.
>
> I'm a C++ monkey. No formal training. Just an itch to scratch and I
> scratch so deep that I find myself in the source code. I usually go by
> example, so for the coding style I just looked at how the file was and
> adapted.
>
> This is OK when changing a couple of lines to fix a bug; or when working
> alone. But when contributing serious chunks of code or when working in a
> team it is not OK.
>
> Some nuances where not immediately clear on me and when I started moving
> from file to file and finding completely different conventions, it
> became difficult to read.
>
> Good style is important for readability. Consistent style is important
> for guidance for newbies. Both make the project more viable long term,
> and more scalable in terms of people working on it.
>
> So I came to the conclusion that I will document the coding style in
> much more detail than I thought (there are some really good
> feedbacks/additions here on the thread, keep them coming) and propose it
> for adoption.
>
> I don't think it will take one day to read/learn.

I understand this need and I've nothing against it. Moreover, when it
takes less than a day to learn it's OK ;-)

>
> I do acknowledge that it is slightly more difficult for individual
> contributors to adapt, especially if they already have strong opinions
> about how things should be; and if they are change-averse. Adaptability
> is a good skills to learn/have.
>
> I am still unsure about the 1TBS vs. Allman style. I read good arguments
> on both sides. I am currently a 1TBS user. Maybe I should stay so? or
> maybe I should adopt Allman? I don't know. I need guidance, but most of
> all the project needs consistency.

I'd select the one which is more widely used in current code. After a
quick look it seems to be neither 1TBS neither Allman style but
something more like BSD KNF [1]. Anyway, what about wait for a Pablo's
attitude, he has written most of the code.

Lukáš

>
> Yuv
>
> >
>

[1] http://en.wikipedia.org/wiki/Indent_style#BSD_KNF_style

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