On Sun 07-Sep-2008 at 06:58 +0200, Stephan Hegel wrote:
>
>I've played around with panostart and would like to mention a few more issues
>beside the missing dependency of the Makefile itsself:
>
>1st. It prints out
>   Use of uninitialized value in subtraction (-) at /usr/bin/panostart line 41.
>when there are no exif data in the image.

Ok need to fix that, and make it so it looks at file dates if there 
is no EXIF date.

>2nd. Makefile:
>The dependency for target "images" shoud be, e.g. img_0014-img0020.tif. Note
>the tif extension. The same is true for the last target. Otherwise, after
>running make once and typing "make" again, it doesn't recognize that the
>output pano is up-to-date and starts running "nona" again.

This is a problem because different output types produce different 
filenames.  A 'Normal' panorama will generate img_0014-img0020.tif, 
but an 'Exposure blended' panorama will generate img_0014-img0020_fused.tif

panostart doesn't know which type of panorama is going to be 
created, so it currently specifies a phony target rather than the 
filename.

I think the solution is to create rules for all possible output 
filenames but copy the stack detection logic from match-n-shift to 
provide a default target.  This will break if you edit the .pto file 
and change the output between 'normal' and 'exposure blended'.

>3rd. Makefile
>The targets all, pto, mk and images should be declared phony, e.g. in the last
>line of the Makefile like this:
>   .PHONY: all pto mk images

Yes, was in my plan but I forgot ;-)

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

Reply via email to