Re: [hugin-ptx] Hugin 2022.0 beta 1 released

[Kornel Benko]

Am Mon, 28 Nov 2022 08:42:06 -0800 (PST)
schrieb "T. Modes" :

> Hi Harry,
> 
> hvd...@gmail.com schrieb am Sonntag, 27. November 2022 um 16:43:40 UTC+1:
> 
> > Thanks.
> >
> > There is no equivalent Dutch verb for ΅focus-stacking", so I "blended" as 
> > good as possible two languages.
> > (Hugin is for blending, isn't it ;) )
> >
> 
> thanks for the fix. I also fix the german translation in the same way ;-)
> 
> @Kornel
> Thanks for your translations. But your last changes to the Slovak  
> translation contain a fatal error: 
> sk.po 
> sk.po:3549: number of format specifications in 'msgid' and 'msgstr' does 
> not match
> msgfmt: found 1 fatal error
> 1713 translated messages.
> 
> Thomas
> 

Thanks Thomas. Is that the only error? How have you checked?
Neither linguist nor lokalize showed any error, so it slipped through.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20221129083517.0378361b%40admin1-desktop.


pgpQBWg2eGauH.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Calculate Optimal Size Shifting Control Point Distance

[Kornel Benko]

Am Thu, 13 Oct 2022 19:01:53 +0100
schrieb Bruno Postle :

> The control point error is reported in terms of pixels in the output
> panorama. So if 'calculate optimal size' changed your 3000x1500 panorama
> into a 3x15000 panorama then all the control point distances will be
> ten times bigger. The output will look the same but with higher resolution.
> 
> You have a single row of images, so the canvas size (in pixels) of your
> panorama should be about the same height as your input images. Rather than
> clicking on 'calculate optimal size' (which isn't working for you), I would
> directly enter a canvas size that is a bit more reasonable.
> 
> I suspect the problem is that very wide rectilinear panoramas are not ideal
> for this automatic calculation.
> 

Would be nice to have an option to see the distances proportional to the angle.
 Something like (angle * 1000 / PI)

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20221015175425.1f8a324a%40admin1-desktop.


pgpitJjw3es4H.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Trying to compile Hugin: what is this MSGFMT error?

[Kornel Benko]

Am Thu, 6 Oct 2022 07:33:15 -0700 (PDT)
schrieb "johnfi...@gmail.com" :

> 
> 
> On Thursday, October 6, 2022 at 7:38:43 AM UTC-4 kornel wrote:
> 
> >  why don't you use 'make package'? That way. you should get a file like 
> > hugin-2021.1.0.8500-Linux.deb, which may be installed with 
> > # sudo dpkg -i hugin-2021.1.0.8500-Linux.deb 
> >
> > I have no guess why the OP chose not to do that.  But I always choose not 
> to do that because I want to build and test my own binaries separate and 
> not interfering with downloading and testing the distribution's binaries.
> 
> Feel free to teach me something about the process that I am 
> misunderstanding (I'm an expert C++ programmer, stumbling around in the 
> dark on many of the build vs. distribution topics), but so far as I have 
> discovered, building all the way to an installable package makes it harder 
> to do an isolated test of your new binaries.
> 

Why is it harder? There is only one step extra involved.
You have
 $ make all
 $ sudo make install
while with package you use
 $ make package
which includes 'make all', and
 $ dpkg -i 
which makes the install

There is no difference for testing IMO.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20221006165806.0ff29076%40admin1-desktop.


pgp83E5q20yw4.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Trying to compile Hugin: what is this MSGFMT error?

[Kornel Benko]

Am Wed, 5 Oct 2022 17:25:43 -1000
schrieb "David W. Jones" :

> On 10/5/22 02:02, Kornel Benko wrote:
> > Am Tue, 4 Oct 2022 21:54:17 -1000
> > schrieb "David W. Jones" :
> >   
> >> On 10/4/22 20:40, Gunter Königsmann wrote:  
> >>> Either you haven't gettext installed  
> >>
> >> I have gettext 0.21-4 installed.
> >>  
> >>> or your cake is too old to know about it.  
> >>
> >> Cake? You mean cmake? cmake is v3.18.4.
> >>
> >> This is on Debian 11. It's been almost a year since the last time I
> >> compiled Hugin. I successfully compiled Hugin 2021 to a /usr/local
> >> installation 1 January 2022.
> >>
> >> Ideas?
> >>  
> > 
> > It is part of hugin sources. Don't know, why cmake is not finding it.
> > 
> > Look foe 'CMakeModules/FindMSGFMT.cmake' in your cloned hugin.
> > 
> > Kornel  
> 
> I find that one in the cloned hugin tree. Cmake is still not finding 
> MSGFMT, although that is installed.
> 
> Here's what cmake tells me:
> 
> CMake Error at celeste/CMakeLists.txt:71 (set_target_properties):
>set_target_properties called with incorrect number of arguments.
> 
> CMake Error at translations/CMakeLists.txt:7 (find_package):
>By not providing "FindMSGFMT.cmake" in CMAKE_MODULE_PATH this project has
>asked CMake to find a package configuration file provided by 
> "MSGFMT", but
>CMake did not find one.
> 
>Could not find a package configuration file provided by "MSGFMT" with any
>of the following names:
> 
>  MSGFMTConfig.cmake
>  msgfmt-config.cmake
> 
>Add the installation prefix of "MSGFMT" to CMAKE_PREFIX_PATH or set
>"MSGFMT_DIR" to a directory containing one of the above files.  If 
> "MSGFMT"
>provides a separate development package or SDK, be sure it has been
>installed.
> 
> Gettext and msgfmt are installed here.
> 
> Anyway, here's what finally worked:
> 
> 1. Run "cmake .." in the build directory. That put the missing MSGFMT 
> .cmake files in a subfolder under the build directory.
> 
> 2. Run "make".
> 
> 3. Run "sudo make install".
> 
> That gave me a Hugin reporting itself as "Version: Pre-Release 
> 2021.1.0.33b93e37f209". Is that correct?
> 

Looks so, but why don't you use 'make package'? That way. you should get a file 
like
hugin-2021.1.0.8500-Linux.deb, which may be installed with
 # sudo dpkg -i hugin-2021.1.0.8500-Linux.deb

To enable package creation, you may need to configure withthe parameter
CPACK_BINARY_DEB:BOOL=ON, e.g.
 $ cmake -DCPACK_BINARY_DEB:BOOL=ON ...

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20221006133836.7db70ff2%40admin1-desktop.


pgp_QM676Nh7i.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Trying to compile Hugin: what is this MSGFMT error?

[Kornel Benko]

Am Tue, 4 Oct 2022 21:54:17 -1000
schrieb "David W. Jones" :

> On 10/4/22 20:40, Gunter Königsmann wrote:
> > Either you haven't gettext installed   
> 
> I have gettext 0.21-4 installed.
> 
> > or your cake is too old to know about it.  
> 
> Cake? You mean cmake? cmake is v3.18.4.
> 
> This is on Debian 11. It's been almost a year since the last time I 
> compiled Hugin. I successfully compiled Hugin 2021 to a /usr/local 
> installation 1 January 2022.
> 
> Ideas?
> 

It is part of hugin sources. Don't know, why cmake is not finding it.

Look foe 'CMakeModules/FindMSGFMT.cmake' in your cloned hugin.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20221005140233.67c017ac%40admin1-desktop.


pgpcFXr_Z5fe8.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] hugin++, creating package

[Kornel Benko]

Am Sun, 22 May 2022 09:01:15 -0400
schrieb John Fine :

> On Sun, May 22, 2022 at 3:59 AM Kornel Benko  wrote:
> 
> >
> > compiling hugin++ and creating a package, I regularly get the message
> > ...
> > CPack Warning: Adding file to tar:
> > #top level
> > directory:
> > /BUILD/BUILDMint18/BuildHugin_plus/_CPack_Packages/Linux/DEB/hugin-2021.1.0.8534-Linux
> > #missing file: /usr2/src/hugin/huginplusplus-hugin++/Debian/shlibs.local
> >
> 
> I hope someone helps you soon.  But in case no one does, I did not want you
> to think your post was ignored.
> 
> I'm the only Hugin++ developer using Linux, so any quick help would need to
> come from someone working on hugin, rather than on hugin++
> 
> I haven't even tried building a package for hugin++ yet.  I need to learn
> about that, but haven't had time.  I have only built hugin++ executables to
> use and test myself.  I use Fedora and haven't even booted my Ubuntu system
> in months (and the package building is very different between the two).  I
> know near zero about cmake.
> 
> I feel like I ought to take responsibility for the problem you found and
> eventually will if no one else does.  But for all the above reasons, it
> will be a fairly long time before I am able to do so.

It is not your fault. In fact, the same warning is when creating package for 
hugin.

The reason for this is the line in CMakeLists.txt
SET(CPACK_DEBIAN_PACKAGE_CONTROL_EXTRA
"${CMAKE_CURRENT_SOURCE_DIR}/Debian/postinst"
"${CMAKE_CURRENT_SOURCE_DIR}/Debian/shlibs.local")

but the repository does not contain the file shlibs.local.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20220522161944.7e2ec0af%40admin1-desktop.


pgpGunsToTH0M.pgp
Description: Digitale Signatur von OpenPGP

[hugin-ptx] hugin++, creating package

[Kornel Benko]

Hi,
compiling hugin++ and creating a package, I regularly get the message
...
CPack Warning: Adding file to tar:
#top level
directory: 
/BUILD/BUILDMint18/BuildHugin_plus/_CPack_Packages/Linux/DEB/hugin-2021.1.0.8534-Linux
#missing file: /usr2/src/hugin/huginplusplus-hugin++/Debian/shlibs.local


The mentioned directory contains only the 'postinst' file.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20220522095906.7c5bc9f7%40admin1-desktop.


pgpLbv7pScyV8.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Re: Compile error while building hugin++

[Kornel Benko]

Am Tue, 19 Apr 2022 04:52:00 -0700 (PDT)
schrieb "johnfi...@gmail.com" :

> When building hugin++ you need to use FastPTOptimizer instead of libpano13.
> https://sourceforge.net/projects/fastptoptimizer/
> 
> Your error message doesn't match the error I got when I used the original 
> libpano13 for hugin++, but your error is the kind of error I would expect 
> for that, so I think that is your problem.

Yes, that was the problem.

> If that is not correct, tell me and I will look into it further.

No other problems, thanks.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20220419143457.11a4c4c0%40admin1-desktop.


pgpc1KNdljPLI.pgp
Description: Digitale Signatur von OpenPGP

[hugin-ptx] Compile error while building hugin++

[Kornel Benko]

Hi, I tried to build hugin++ from the repo at
http://hg.code.sf.net/p/huginplusplus/hugin++, but failed.
The cmake call was error-free (though with some warnings).

The following make ended with:

[  2%] Building CXX object
src/hugin_base/CMakeFiles/huginbase.dir/algorithms/nona/NonaFileStitcher.cpp.o
cd /home/kornel/src/hugin_base && /usr/lib/ccache/c++ -DGLEW_STATIC -DHUGIN_HSI
-Dhuginbase_EXPORTS -I/home/kornel/src
-I/usr2/src/hugin/huginplusplus-hugin++/src/hugin_base
-I/usr2/src/hugin/huginplusplus-hugin++/src/celeste -I/home/kornel/src/celeste
-I/usr2/src/hugin/huginplusplus-hugin++/src -I/usr/include/OpenEXR
-I/usr/include/python3.6m -O3 -DNDEBUG -fPIC -fopenmp -pthread -std=gnu++11 -MD 
-MT
src/hugin_base/CMakeFiles/huginbase.dir/algorithms/nona/NonaFileStitcher.cpp.o 
-MF
CMakeFiles/huginbase.dir/algorithms/nona/NonaFileStitcher.cpp.o.d -o
CMakeFiles/huginbase.dir/algorithms/nona/NonaFileStitcher.cpp.o
-c 
/usr2/src/hugin/huginplusplus-hugin++/src/hugin_base/algorithms/nona/NonaFileStitcher.cpp
In file included
from 
/usr2/src/hugin/huginplusplus-hugin++/src/hugin_base/nona/RemappedPanoImage.h:43,
from /usr2/src/hugin/huginplusplus-hugin++/src/hugin_base/nona/Stitcher.h:53,
from 
/usr2/src/hugin/huginplusplus-hugin++/src/hugin_base/algorithms/nona/NonaFileStitcher.cpp:33:
 
/usr2/src/hugin/huginplusplus-hugin++/src/hugin_base/panotools/PanoToolsInterface.h:278:69:
error: ‘AlignInfoExt’ does not name a type; did you mean ‘AlignInfo’? IMPEX 
CPVector
GetAlignInfoCtrlPointsExt(const AlignInfo& gl, const AlignInfoExt& gl_ext); 
^~~~
AlignInfo src/hugin_base/CMakeFiles/huginbase.dir/build.make:78: recipe for 
target
'src/hugin_base/CMakeFiles/huginbase.dir/algorithms/nona/NonaFileStitcher.cpp.o'
 failed
make[2]: ***
[src/hugin_base/CMakeFiles/huginbase.dir/algorithms/nona/NonaFileStitcher.cpp.o]
 Error 1
make[2]: Verzeichnis „/home/kornel“ wird verlassen CMakeFiles/Makefile2:756: 
recipe for
target 'src/hugin_base/CMakeFiles/huginbase.dir/all' failed make[1]: ***
[src/hugin_base/CMakeFiles/huginbase.dir/all] Error 2
..
I could not find anything in the web about "AlignInfo", so I had to stop here.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20220418170758.33c3f274%40admin1-desktop.


pgpAs4f0XVpM0.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] libpano13-2.9.21 release candidate rc1

[Kornel Benko]

Ping ...

Am Sun, 24 Oct 2021 15:48:47 +0200
schrieb Kornel Benko :

> Am Sat, 16 Oct 2021 13:09:50 +0100
> schrieb Bruno Postle :
> 
> > libpano13 is the PanoTools library for panoramic imaging.
> > 
> > A libpano13-2.9.21 rc1 tarball has been uploaded to sourceforge, this is
> > a release candidate for testing that may become the final release:
> > 
> > https://sourceforge.net/projects/panotools/files/libpano13/libpano13-2.9.21/
> > 
> > This release should be binary compatible with previous versions - This means
> > that prebuilt Hugin executables should just work with this libpano13.
> > 
> > There have been some changes since 2.9.20:  
> ...
> 
> I am getting too many warning messages of for '-Wformat-overflow'.
> See attached (727 lines => 57 warnings, 31 from the 57 are uniq)
> 
>   Kornel
> 

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20211102113654.149934dc%40admin1-desktop.


pgp7jw7VYoAhQ.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] libpano13-2.9.21 release candidate rc1

[Kornel Benko]

Am Sat, 16 Oct 2021 13:09:50 +0100
schrieb Bruno Postle :

> libpano13 is the PanoTools library for panoramic imaging.
> 
> A libpano13-2.9.21 rc1 tarball has been uploaded to sourceforge, this is
> a release candidate for testing that may become the final release:
> 
> https://sourceforge.net/projects/panotools/files/libpano13/libpano13-2.9.21/
> 
> This release should be binary compatible with previous versions - This means
> that prebuilt Hugin executables should just work with this libpano13.
> 
> There have been some changes since 2.9.20:
...

I am getting too many warning messages of for '-Wformat-overflow'.
See attached (727 lines => 57 warnings, 31 from the 57 are uniq)

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20211024154847.51755c15%40admin1-desktop.


warn
Description: Binary data


pgpAp84742x3s.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Re: Hugin 2021.0 beta 1

[Kornel Benko]

Am Wed, 20 Oct 2021 17:53:24 +0800
schrieb RizThon :

> > abort: push creates new remote head 78598c26c57c!
> 
> I guess it means some changes are on the server but not on your local
> repository, and you have to pull and merge before pushing your changes.
> 

Thanks, hopefully it is merged and pushed.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20211020121950.06bd3f8b%40admin1-desktop.


pgpXFekjO5AQ9.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Hugin++ : fast geometrical optimization and other features

[Kornel Benko]

Am Sat, 14 Aug 2021 15:24:29 +
schrieb "'ChameleonScales' via hugin and other free panoramic software"
:

> line 112 in ./CMakeLists.txt (the one at the root), freshly downloaded from
> https://sourceforge.net/projects/huginplusplus/ :
> 
> > include( vcpkg/scripts/buildsystems/vcpkg.cmake )  
> 
> We're talking about vcpkg, right?
> 

Probably my fail. I am using hugin, not huginplusplus.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210814180957.635c1cca%40admin1-desktop.


pgpuqVaAGJHdO.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Hugin++ : fast geometrical optimization and other features

[Kornel Benko]

Am Sat, 14 Aug 2021 14:47:03 +
schrieb "'ChameleonScales' via hugin and other free panoramic software"
:

> I may be on to something:
> if I move the vcpkg build out of the hugin++ source directory, then wxWidgets 
> is found:
> 
> Found wxWidgets:
> -L/usr/lib/x86_64-linux-gnu;-pthread;;;-lwx_baseu-3.0;-lwx_gtk2u_core-3.0;-lwx_gtk2u_aui-3.0;-lwx_gtk2u_xrc-3.0;-lwx_gtk2u_html-3.0;-lwx_baseu_xml-3.0;-lwx_gtk2u_adv-3.0;-lwx_gtk2u_gl-3.0;-lwx_baseu_net-3.0;-lwx_gtk2u_qa-3.0
> (found version "3.0.4")
> 
> but vcpkg is obviously not found :
> 
> CMake Error at CMakeLists.txt:112 (include):
>   include could not find load file:
> vcpkg/scripts/buildsystems/vcpkg.cmake

There is no such entry at any CMakeLists.txt in the source.
So it could be your change?

> And if vcpkg is in the hugin++ source dir, the opposite happens (see output 
> of my
> previous message).
> 
> I guess I have to install vcpkg on the system, which is what I'm looking for 
> right now.
> 

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210814171021.08deaafe%40admin1-desktop.


pgpulFCi3OY3i.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Hugin++ : fast geometrical optimization and other features

[Kornel Benko]

Am Fri, 13 Aug 2021 21:45:07 +
schrieb "'ChameleonScales' via hugin and other free panoramic software"
:

> Thanks for your help.
> I could get rid of the rev.txt error by following your instructions as well 
> as the
> wxWidgets error by installing the following packages:
> 
> - libwxbase3.0-dev
> - libwxgtk3.0-dev
> - libwxgtk3.0-gtk3-dev
> 
> (not sure I need all of them though).
> 
> Then to get rid of this error:
> include could not find load file:
> vcpkg/scripts/buildsystems/vcpkg.cmake
> I [built vcpkg](https://vcpkg.io/en/getting-started.html?platform=linux) into 
> hugin++'s
> source directory.
> 
> However I'm stuck at this error which seems to be the last one:
> CMake Error at vcpkg/scripts/buildsystems/vcpkg.cmake:784 (_find_package):
> 
> Could not find a package configuration file provided by "OpenEXR" with any
> 
> of the following names:
> 
> OpenEXRConfig.cmake
> 
> openexr-config.cmake

The package 'extra-cmake-modules' provides FindOpenEXR.cmake, which should be 
enough.

> Add the installation prefix of "OpenEXR" to CMAKE_PREFIX_PATH or set
> 
> "OpenEXR_DIR" to a directory containing one of the above files. If
> 
> "OpenEXR" provides a separate development package or SDK, be sure it has
> 
> been installed.
> I looked for any -dev version related to openexr, mainly an openexr-dev but 
> all I could
> find is libopenexr-dev and it didn't help.
> 

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210814085013.4b8a1975%40admin1-desktop.


pgpdOlPNdhnsX.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Re: Multiblend 2.0 RC1 - better blending and 300x* faster than Enblend

[Kornel Benko]

Am Sun, 08 Aug 2021 00:01:58 +
schrieb "'ChameleonScales' via hugin and other free panoramic software"
:

> Hi everyone,
> I'd like to give multiblend 2.0 rc3 a try but the given build command for 
> Linux gives
> this error : multiblend.cpp:31:10: fatal error: tiffio.h: No such file or 
> directory
> and indeed there is no such file.
> What now ?
> 

On debian it is part of 'libtiff5-dev' package.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210808101438.34aa866c%40admin1-desktop.


pgpD3hr6yuK2O.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Re: lux - FOSS multiplatform image and panorama viewer

[Kornel Benko]

Am Sat, 5 Jun 2021 10:36:55 +0200
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:
...
> @Kornel: Is there a way to provide 'linux bundles' which include all 
> shared libraries, as I make them for the Windows stickware version? Can 
> CMake output flatpak or a similar format which works on more distros?

Too dangerous, even if that were possible.
But I can provide a debian package (based on ubuntu 19) if needed.
 $ dpkg -s lux
Package: lux
Status: install ok installed
Priority: optional
Section: universe/graphics
Installed-Size: 12741
Maintainer: Kay F. Jahnke 
Architecture: amd64
Version: 1.0.9-0git
Depends: libc6 (>= 2.15), libgcc1 (>= 1:3.0), libsfml-graphics2.4, 
libsfml-system2.4 (>=
2.4.2+dfsg-4~), libsfml-window2.4 (>= 2.4.1~), libstdc++6 (>= 6)
Description: lux - a free open source image and panorama viewer
 .
 lux can show -normal- images, panoramas in various formats
 and PTO files made with software like hugin. It can also do
 simple stitching and blending jobs. You can find documentation
 at the bitbucket site: https://bitbucket.org/kfj/pv


 $ ldd `which lux` | egrep 'libexiv|libgcc|libstdc|libvigra'
libvigraimpex.so.11 => /usr/local/lib/libvigraimpex.so.11 
(0x7ff05ae5d000)
libexiv2.so.27 => /usr/lib/libexiv2.so.27 (0x7ff05a21)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7ff059c68000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7ff0596b2000)

I suppose that libvigraimpex.so.11 may make problems though.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210605114315.061ff6ba%40admin1-desktop.


pgpGkuKZiZ44p.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Tue, 18 May 2021 11:01:22 +0200
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> I made another addition to the feature set, which will go into 1.0.9: 
> Display of metadata in the status line, now that lux has one. This is a 
> two-step process: First you may introduce up to ten exif tags you'd like 
> to be read from the current input with this syntax:
> 
>--metadata_query=
> 
> Adds a metadata query key to the list of queried metadata for the status
> line. This is a vector field, so you can pass this option several times,
> but currently the number of queried metadata keys is limited to ten
> (0-9). And it's optional.
> 
> An example: pass --metadata_query=Exif.Photo.DateTimeOriginal to obtain
> the original date and time. If the specified key has no value assigned 
> to it, it will be displayed as '---'.
> 
> For now, queries are for Exif tags only, and only for those understood 
> by libexiv2, as listed in https://www.exiv2.org/tags.html
> The conversion to the displayed string is left to libexiv2's toString() 
> function and can't be influenced via lux.
> 
>--metadata_format=
> 
> Format string for metadata display in the status line. This is new and
> still experimental. Pass a format string where %n will be replaced by
> the current filename, and %0 to %9 will be replaced by the value gleaned
> from querying they corresponding metadata_query entry (see above).
> %h yields the image's hfov, %p it's projection and %P the viewer's
> target projection.
> 
> If you omit the format string, metadata specified with
> '--metadata_query=...' will still be displayed: the value will be 
> prefixed by the key and a colon, and all specified keys will be 
> displayed in numerical order.
> 
> For now, this is only in master and you'll have to build yourself.
> 
> Kay
> 

The last commit is from 'Sun May 16', so these changes seem not be pushed yet?

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210518111549.46407764%40admin1-desktop.


pgpKqyYkg6_kF.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Sat, 24 Apr 2021 08:47:47 +0200
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> Am 23.04.21 um 16:29 schrieb 'Kay F. Jahnke' via hugin and other free 
> panoramic software:
> 
>  >> @Kornel: Can't we include find_package statements ...
>  >> to make cmake find the required libraries automatically?  
> 
> Now the penny drops. It's not that find_package actually *fetches* the 
> libraries, it only figures out where they have been put on the system. 
> As a debian user, where getting a bunch of libraries is as simple as 
> apt-get ..., I had asumed that CMake would do that for me. So what I had 
> in mind was something like FetchContent, but that doesn't seem to be 
> good for loading libraries. Any ideas?
> 
> Kay
> 

For such an action we would need to have superuser privileges.
And cmake does not provide anything in the direction of loading libraries
platform-independently.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210424101507.28c423ea%40admin1-desktop.


pgpbZQlZMKDHb.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Fri, 23 Apr 2021 14:49:49 +0200
schrieb Kornel Benko :

> Am Fri, 23 Apr 2021 11:59:36 +0200
> schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
> :
> 
> > @Kornel: Can't we include find_package statements in the CMakeLists.txt 
> > to make cmake find the required libraries automatically? I noticed there 
> > is only a find_package for libexiv2 so far. Maybe you have the code for 
> > the other libraries needed by lux in another project already?
> > 
> > Kay
> >   
> 
> Sure we can. And we do already (CmakeLists.txt:206) for
>   Vc vigraimpex sfml-window sfml-graphics sfml-system exiv2
> Have I missed something?
> 
>   Kornel

How about the attached?

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210423154446.40df9e37%40admin1-desktop.
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 2921f52..851ebc9 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -201,11 +201,17 @@ add_executable(${_pv} ${pv_sources})
 # Check if needed libraries available. Vc is a build time dependency only,
 # it provides a library (libVc.a) which has to be linked in. The other libs
 # are both build-time and run-time dependencies.
 
 set(LibFound ON)
-foreach(_l Vc vigraimpex sfml-window sfml-graphics sfml-system exiv2)
+set(reguired_libraries Vc vigraimpex sfml-window sfml-graphics sfml-system exiv2)
+if (WIN32 OR MSYS)
+  list(APPEND reguired_libraries Ole32 Comdlg32)
+else()
+  list(APPEND reguired_libraries pthread)
+endif()
+foreach(_l ${reguired_libraries})
 	string(TOUPPER ${_l} _UpcaseLib)
 	string(REGEX REPLACE "-" "_" _UpcaseLib ${_UpcaseLib})
 	set(libname "${_UpcaseLib}_LIBRARY")
 	find_library(${libname} NAMES ${_l})
 	if(${${libname}} MATCHES "_LIBRARY-NOTFOUND")
@@ -218,16 +224,10 @@ endforeach()
 
 if (NOT LibFound)
 	message(FATAL_ERROR "Missing needed libraries ... aborting cmake configuration")
 endif()
 
-if (WIN32 OR MSYS)
-  target_link_libraries(${_pv} ${USE_LEAK_SANITIZER} Ole32 Comdlg32)
-else()
-  target_link_libraries(${_pv} ${USE_LEAK_SANITIZER} pthread)
-endif()
-
 if (APPLE)
 set(CMAKE_MODULE_PATH ${CMAKE_SOURCE_DIR}/CMakeModules )
 find_package(EXIV2 REQUIRED)
 include_directories(${EXIV2_INCLUDE_DIR})
 endif (APPLE)


pgp3UYmjQkklu.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Fri, 23 Apr 2021 11:59:36 +0200
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> @Kornel: Can't we include find_package statements in the CMakeLists.txt 
> to make cmake find the required libraries automatically? I noticed there 
> is only a find_package for libexiv2 so far. Maybe you have the code for 
> the other libraries needed by lux in another project already?
> 
> Kay
> 

Sure we can. And we do already (CmakeLists.txt:206) for
Vc vigraimpex sfml-window sfml-graphics sfml-system exiv2
Have I missed something?

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210423144949.01620f74%40admin1-desktop.


pgpPP45GvSxGs.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Sun, 11 Apr 2021 18:41:57 +0200
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> @Kornel: I did quite a few changes in the CMakeLists.txt, introducing 
> one new feature and tweaking the compiler options. Can you have a look 
> and see if I made any obvious mistakes? You know my CMake isn't so good...

I would set 'USE_LEAK_SANITIZER' explicitly also if not using LEAK_SANITIZER
e.g.
if(LEAK_SANITIZER)
  set(USE_LEAK_SANITIZER "-g -fsanitize=leak")
else()
  set(USE_LEAK_SANITIZER )
endif()

Otherwise I did not see any obvious errors. (maybe in text: Wehn --> When)
To make it 'LEAK_SANITIZER' obvious in the cmake-gui I would use command 
'option'

option(LEAK_SANITIZER "When setting LEAK_SANITIZER=ON, the build will 
use clang's
   leak sanitizer, see https://clang.llvm.org/docs/LeakSanitizer.html"; 
OFF)

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210411192753.17c8c7d0%40admin1-desktop.


pgpXOs7D_XCyd.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Mon, 5 Apr 2021 16:29:26 +0200
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> Am 05.04.21 um 12:17 schrieb Kornel Benko:
> > Am Mon, 5 Apr 2021 11:54:59 +0200
> > schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
> > :
> >   
> >> lux version 1.0.8 released!
> >>  
> > 
> > Missing tag for 1.08.
> > 
> >   $ git describe --match 1.0.7 --tags
> > 1.0.7-69-g5a096a0
> > 
> > vs
> >   $ git describe --match 1.0.8 --tags
> > fatal: No names found, cannot describe anything.
> > Exit 128  
> 
> My mistake - forgot the git push --tags.
> 
> Kay
> 

OK, now the patch to handle the case that we are just at the start of the 
searched tag.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210406200546.5b9bdc0a%40admin1-desktop.
diff --git a/CMakeLists.txt b/CMakeLists.txt
index bc12562..0361f6c 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -193,10 +193,12 @@ if(LUX_GITVERSION)
 ERROR_VARIABLE tmp_GIT_ERROR
 OUTPUT_STRIP_TRAILING_WHITESPACE)
   if (tmp_GIT_RESULT EQUAL 0)
 if (tmp_LUX_PACKAGE_RELEASE MATCHES "^${pv_major}.${pv_minor}.${pv_patch}-\([0-9]+\)")
   set(LUX_PACKAGE_RELEASE ${CMAKE_MATCH_1})
+elseif(tmp_LUX_PACKAGE_RELEASE MATCHES "^${pv_major}.${pv_minor}.${pv_patch}")
+  set(LUX_PACKAGE_RELEASE 0)
 endif()
   endif()
   message(STATUS "LUX_PACKAGE_RELEASE = ${LUX_PACKAGE_RELEASE}")
 endif()
 


pgpvnsYgFgseX.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Mon, 5 Apr 2021 11:54:59 +0200
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> lux version 1.0.8 released!
> 

Missing tag for 1.08.

 $ git describe --match 1.0.7 --tags
1.0.7-69-g5a096a0

vs
 $ git describe --match 1.0.8 --tags
fatal: No names found, cannot describe anything.
Exit 128


Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210405121702.2e38ba75%40admin1-desktop.


pgpqXXLyv3SzO.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Wed, 31 Mar 2021 10:16:40 +0200
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> @Kornel: I checked the code looking at the desktop size, and I think I 
> made a mistake processing it. I changed it so that it should now indeed 
> take the desktop height as the relevant datum. Can you please check on 
> your ultra-wide setup? The GUI stripe should now only cover half your 
> desktop's width.
> 

Yes, it does now. Thanks.

[snip]

> All changes were pushed just now, please check it out and enjoy! I think 
> that the set of features I'd like to see in 1.0.8 are now all present, 
> I'll do a bit more testing and tweaking and then I think it's time for 
> the next level :D
> 
> It would be nice if you lot could also do a bit of testing on your end!
> 
> Kay
> 

Works nice here :)

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/2021033211.43cf5b9d%40admin1-desktop.


pgpfsQhoYnJWc.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Tue, 30 Mar 2021 19:46:03 +0200
schrieb Kornel Benko :

> Am Tue, 30 Mar 2021 18:50:38 +0200
> schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
> :
> 
> > Am 30.03.21 um 13:03 schrieb Kornel Benko:
> >   
> > > Could you please post
> > > 1.) The error messages you get if compiling with cmake configuration
> > > 2.) compile (and link) commands if compiling with make config  
> > 
> > Yes, sorry I didn't get around to it yet, I was busy with other stuff. 
> > The problem is with linking - the compile runs through fine, but then 
> > the linking stage fails. I attach a complete session log, from setting 
> > up the build directory until the failure.
> > 
> > I'm not sure if I'm doing everything right, I just tried to do the same 
> > sequence I use on Linux, assuming that msys2 works in a similar fashion. 
> > It may well be that the msys2 build on w10 is not a well-trodden path, 
> > but I don't have MSVC here.
> > 
> > Please let me know if you need more information or want me to try out 
> > stuff on windows.
> > 
> > Kay
> > 
> >   
> 
> Short googling ... Citing a result:
>   You need to link ole32.dll ("-lole32"). In order to link to that, you 
> need to
> have the import library for it (ole32.lib) installed, and in your search 
> paths. I
>   assume you might need to have the Windows SDK installed for that.
> 
> Maybe the attached helps.
> 
>   Kornel
> 

Or even better
if(WIN32)
target_link_libraries(${_pv} ole32)
endif()

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210330201240.564d0d68%40admin1-desktop.


pgpzmF9Qoz0Fy.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Tue, 30 Mar 2021 18:50:38 +0200
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> Am 30.03.21 um 13:03 schrieb Kornel Benko:
> 
> > Could you please post
> > 1.) The error messages you get if compiling with cmake configuration
> > 2.) compile (and link) commands if compiling with make config
> 
> Yes, sorry I didn't get around to it yet, I was busy with other stuff. 
> The problem is with linking - the compile runs through fine, but then 
> the linking stage fails. I attach a complete session log, from setting 
> up the build directory until the failure.
> 
> I'm not sure if I'm doing everything right, I just tried to do the same 
> sequence I use on Linux, assuming that msys2 works in a similar fashion. 
> It may well be that the msys2 build on w10 is not a well-trodden path, 
> but I don't have MSVC here.
> 
> Please let me know if you need more information or want me to try out 
> stuff on windows.
> 
> Kay
> 
> 

Short googling ... Citing a result:
You need to link ole32.dll ("-lole32"). In order to link to that, you 
need to have
the import library for it (ole32.lib) installed, and in your search 
paths. I
assume you might need to have the Windows SDK installed for that.

Maybe the attached helps.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210330194603.42cbbc21%40admin1-desktop.
diff --git a/CMakeLists.txt b/CMakeLists.txt
index db60db7..b264921 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -126,10 +126,13 @@ set_source_files_properties(${CMAKE_BINARY_DIR}/pv_cmb_avx512f.cc PROPERTIES COM
 set_source_files_properties(file_dialog.cc PROPERTIES COMPILE_FLAGS "-DUSE_TINYFILEDIALOGS")
 set_source_files_properties(pv_no_rendering.cc PROPERTIES COMPILE_FLAGS "-Ofast -std=c++11")
 set_source_files_properties(pv_initialize.cc PROPERTIES COMPILE_FLAGS "-Ofast -std=c++11")
 
 add_executable(${_pv} ${pv_sources})
+if(WIN32)
+  target_link_libraries(${_pv} -lole32.dll)
+endif()
 
 # Check if needed libraries available. Vc is a build time dependency only,
 # it provides a library (libVc.a) which has to be linked in. The other libs
 # are both build-time and run-time dependencies.
 


pgpcZO5HJWlG8.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Tue, 30 Mar 2021 12:45:34 +0200
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> Am 30.03.21 um 09:24 schrieb 'Kay F. Jahnke' via hugin and other free 
> panoramic software:
> > Am 29.03.21 um 23:51 schrieb smib:  
> >> Hi Kay,
> >> Are you planning to provide another windows build?  At the moment I am 
> >> having problems building but this is due to my lack of knowledge  
> 
> I merged master into msys2 and tried a build on w10. I did not manage 
> with cmake, but the 'plain old makefile' worked for me. I made a bundle 
> - this is a development snapshot, so don't be surprised if it's not 
> stable or bits are missing, but the latest features are in it and I did 
> a brief test. You can find it here:
> 
> https://www.magentacloud.de/lnk/5CiIh4ZO
> 
> Password: hugin-ptx
> 
> Kay
> 

Could you please post
1.) The error messages you get if compiling with cmake configuration
2.) compile (and link) commands if compiling with make config
?

We could then try to add the appropriate compile-flags in cmake.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210330130354.32a29915%40admin1-desktop.


pgpohGLzxM68t.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Mon, 22 Mar 2021 09:08:48 +0100
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> Am 21.03.21 um 22:08 schrieb Kornel Benko:
> > 
> > Still black result-picture BTW.  
> 
> Can you be more specific? like what panorama (maybe send the PTO), what 
> parameters, alpha channel images or not? I don't get the 'black output' 
> anymore since 4de331e.
> 
> Kay
> 

I was soo sure I had recompiled. (but forgot to install!).

Works.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210322101331.388a3f1c%40admin1-desktop.


pgpLp2NCuUst2.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Sun, 21 Mar 2021 18:30:27 +0100
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> @Harry, @Kornel
> 
> Yuv has pointed out that I did not have the issue tracker active on the 
> bitbucket repo. Again, my fault. If you like we can move technical 
> discussions to the issue tracker, which is a more structured approach as 
> well. I set it up so you don't need a bitbucket account for the issue 
> tracker. Then we can stop cluttering hugin-ptx with lux technical details.

OK.

> Kay
> 

Still black result-picture BTW.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210321220852.76bee918%40admin1-desktop.


pgp0Z23i2ZiQf.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Sun, 21 Mar 2021 13:05:47 +0100
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> The snapshot button is for the live view and snapshots the live view.
> To stitch, use the 'P' key (not Shift+P).
> 

The pto displays OK.
Pressing 'p', I get black image as a result.
 $ ls -l pict0876-9.pto.pv.1.pano.jpg
-rw-rw-r-- 1 kornel kornel73375 Mär 21 13:24 
pict0876-9.pto.pv.1.pano.jpg

 $ file pict0876-9.pto.pv.1.pano.jpg
pict0876-9.pto.pv.1.pano.jpg: JPEG image data, JFIF
standard 1.01, aspect ratio, density 1x1, segment length 16, Exif 
Standard:
[TIFF image data, little-endian, direntries=1], baseline, precision 8, 
3072x864,
frames 3

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210321133124.3b4d79f4%40admin1-desktop.


pgprr4ioDtatg.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Sat, 20 Mar 2021 12:11:17 +0100
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> Am 19.03.21 um 19:11 schrieb Harry van der Wolf:
> > 
> > Although it is only a "git checkout mac", I also prefer one branch. The 
> > power of cmake is that you can combine it. This will allow users to make 
> > packages for the environment.  
> 
> Okay, if you're both against the mac branch, I'm not too attached to it. 
> I've merged it back into master, so now the 'scripts' folder from the 
> mac branch is in master. I'll delete the mac branch eventually.
> 
> The latest push adds experimental code for 'quorate blending', see the 
> comments in pv_rendering.cc for now.
> 
> Kay
> 

Thanks.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210320132404.4bf93b7a%40admin1-desktop.


pgpUirNMKMv93.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Fri, 19 Mar 2021 18:53:14 +0100
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> Am 19.03.21 um 18:18 schrieb Kornel Benko:
> >>> Why still the need for mac-branch?  
> >>  
> > So the mac branch contains linux + mac already.
> > Is there -any- difference in the source (.cc, .h CMake) affecting linux?
> > If not, then I see no problem.  
> 
> Look at the 'scripts' folder in the mac branch for mac-specific code.

Sorry, but how does it disturb the linux-part?

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210319190832.4d13c057%40admin1-desktop.


pgpiuYmn1GuTj.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Fri, 19 Mar 2021 17:52:47 +0100
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> Am 19.03.21 um 12:55 schrieb Kornel Benko:
> > Am Fri, 19 Mar 2021 12:41:32 +0100
> > schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
> > :
> >   
> >> Am 18.03.21 um 21:21 schrieb Harry van der Wolf:  
> >>>
> >>> On MacOS I also build with cmake (cmake .. -D
> >>> CMAKE_INSTALL_PREFIX=/opt/local).
> >>> But it still builds pv instead of lux.
> >>>  
> >> ...
> >>
> >> @Harry: I just merged master to all other branches and pushed them to
> >> the repo because I think the code is good. If you like you can try build
> >> on the mac now with the updated CMakeLists.txt.
> >>
> >> I'll still do some tweaking and tinkering and I just had an idea how I
> >> can attempt to do automatic deghosting, which I want to investigate - if
> >> that works out, it could already go into the next version as an
> >> experimental new feature.
> >>
> >> Kay
> >>  
> > 
> > Why still the need for mac-branch?  
> 
> I like having separate branches for the different platforms. I don't 
> know much about the mac stuff, but to cover all mac packaging by 'ifdef 
> apple' statements in the cmake code is, I think, not a good idea.
> 
> Merging to these branches is not a big deal - it is usually enough to 
> issue two lines:
> 
> git checkout mac (optional if you're already on the mac branch)
> git merge master

So the mac branch contains linux + mac already.
Is there -any- difference in the source (.cc, .h CMake) affecting linux?
If not, then I see no problem.

> The same is true for the other branches, and the windows branch, with 
> it's code to produce stickware bundles, is quite different from master, 
> and the mac branch also has specialized bundle-building code which is 
> needed nowhere else. All that's needed is being aware of the different 
> branches, and the fact that I don't automatically merge every commit 
> instantly.
> 
> Development, for the time being, is happening on linux: I haven't heard 
> from a single mac user

Harry is one ...

> or windows user who would be interested, nor of 
> any who have downloaded and tried the bundles we've produced. I think 
> it's perfectly good enough to merge master and make bundles when there's 
> a new release out, just in case there's a user somewhere.
> 
> So that's my opinion just now - doesn't mean it has to stay like that 
> forever. But I prefer a clear focus on getting the code to run well on 
> linux, and let it trickle down to other platforms as needed, without 
> putting much work into it. With my windows branch, this has worked fine 
> for quite some time now (ca. 40 releases).
> 
> Kay

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210319181849.4431804d%40admin1-desktop.


pgpXxHqZYKhr8.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Fri, 19 Mar 2021 12:41:32 +0100
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> Am 18.03.21 um 21:21 schrieb Harry van der Wolf:
> > 
> > On MacOS I also build with cmake (cmake .. -D 
> > CMAKE_INSTALL_PREFIX=/opt/local).
> > But it still builds pv instead of lux.
> >   
> ...
> 
> @Harry: I just merged master to all other branches and pushed them to 
> the repo because I think the code is good. If you like you can try build 
> on the mac now with the updated CMakeLists.txt.
> 
> I'll still do some tweaking and tinkering and I just had an idea how I 
> can attempt to do automatic deghosting, which I want to investigate - if 
> that works out, it could already go into the next version as an 
> experimental new feature.
> 
> Kay
> 

Why still the need for mac-branch?

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210319125510.17f4379b%40admin1-desktop.


pgpt0ajuPe3LY.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Thu, 18 Mar 2021 21:21:14 +0100
schrieb Harry van der Wolf :

> I can't find the question backs, but you asked me about the speed after
> your improvements.
> 
> The current version is about 10-15% faster.
> 
> I built with cmake on linux and get a binary lux. sudo make install
> installs the font and font readme in /usr/local/share/lux/fonts where lux
> can find it.
> 
> On MacOS I also build with cmake (cmake .. -D
> CMAKE_INSTALL_PREFIX=/opt/local).
> But it still builds pv instead of lux.
> 
> sudo make install does install pv in /opt/local/bin
> It installs the font in /opt/local/share/pv/fonts, but it does not install
> the font readme on mac.
> pv can find the font on mac.
> I will have to look what I need to specify as install prefix to make pv
> find the font in the bundle, or that the bundle requires an extra setting
> for bundle builds.
> 
> Harry
> 

Maybe old CMakeLists.txt?

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210318213247.786fd764%40admin1-desktop.


pgpBQk6zNE8B2.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Thu, 18 Mar 2021 16:50:19 +0100
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> @Kornel: If I update pv_combine.cc in the root directory, then issue 
> 'make' in the build directory, the update goes unnoticed. I can touch 
> the generated per-isa variants (pv_combine_avx.cc etc.) which triggers a 
> recompile, but I think this should happen automatically. Can you maybe 
> fix that? It should just be a matter of telling cmake about the 
> unexpected dependencies.
> 
> Kay
> 

My fail.
use
foreach(_f pv_fallback pv_avx pv_avx2  pv_avx512f)
add_custom_command(
COMMAND $(CMAKE_COMMAND) -E copy_if_different
ARGS ${CMAKE_CURRENT_SOURCE_DIR}/pv_rendering.cc
${CMAKE_BINARY_DIR}/${_f}.cc OUTPUT ${CMAKE_BINARY_DIR}/${_f}.cc
DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/pv_rendering.cc
)
endforeach()
foreach(_f pv_cmb_fallback pv_cmb_avx pv_cmb_avx2 pv_cmb_avx512f)
add_custom_command(
COMMAND $(CMAKE_COMMAND) -E copy_if_different
ARGS ${CMAKE_CURRENT_SOURCE_DIR}/pv_combine.cc
${CMAKE_BINARY_DIR}/${_f}.cc OUTPUT ${CMAKE_BINARY_DIR}/${_f}.cc
DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/pv_combine.cc
)
endforeach()

(See 'DEPENDS', hope this is better)

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210318181505.431d0fab%40admin1-desktop.


pgpx_zZ5Bsaom.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Thu, 18 Mar 2021 11:46:22 +0100
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> Am 18.03.21 um 11:34 schrieb Kornel Benko:
> > Am Thu, 18 Mar 2021 11:01:31 +0100
> > schrieb Kornel Benko :
> >   
> >>> Please explain. What do you mean by 'use'? Is PV_FONTDATADIR an
> >>> environment variable? Or something CMake will patch in the source?
> >>>
> >>> Kay
> >>>  
> >>
> >> Compilation is called as
> >>clang++ ... -DPV_FONTDATADIR="/usr/local/share/lux/fonts" ...
> >> so that in the source you can use
> >>#if defined(PV_FONTDATADIR)
> >>... do something
> >>#endif  
> 
> Got it. applied. We had crossed mails, please check if my edit suits you.
> 
> >>Kornel  
> > 
> > An alternative is the following
> > Create a template pv_config.h.cmake (attached)
> > add to CMakeLists.txt the commands to create pv_config.h (in the build dir)
> > patch attached
> > 
> > use
> > #include "pv_config.h"  
> 
> I opted against this for now and I'm going with the PV_FONTDATADIR read 
> directly.
> 
> Kay
> 

OK. Mark that using defines in a config file may be preferred because the
compile-command-line is shorter.
BTW, it works.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210318115601.5d982dfa%40admin1-desktop.


pgpT7yPCOfipC.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Thu, 18 Mar 2021 11:01:31 +0100
schrieb Kornel Benko :

> > Please explain. What do you mean by 'use'? Is PV_FONTDATADIR an 
> > environment variable? Or something CMake will patch in the source?
> > 
> > Kay
> >   
> 
> Compilation is called as
>   clang++ ... -DPV_FONTDATADIR="/usr/local/share/lux/fonts" ...
> so that in the source you can use
>   #if defined(PV_FONTDATADIR)
>   ... do something
>   #endif
> 
>   Kornel

An alternative is the following
Create a template pv_config.h.cmake (attached)
add to CMakeLists.txt the commands to create pv_config.h (in the build dir)
patch attached

use
#include "pv_config.h"
where needed.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210318113410.3ec493c6%40admin1-desktop.
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 7bf029f..cf91656 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -159,13 +159,15 @@ install(TARGETS ${_pv} DESTINATION bin)
 if(UNIX)
 	set(DataDir "${CMAKE_INSTALL_PREFIX}/share/${_pv}/")
 elseif(WIN32)
 	set(DataDir "${CMAKE_INSTALL_PREFIX}/Resources/")
 elseif(APPLE)
-	set(DataDir "${CMAKE_INSTALL_PREFIX}/${_pv}.app/Contents/Resources")
+	set(DataDir "${CMAKE_INSTALL_PREFIX}/${_pv}.app/Contents/Resources/")
 endif()
-add_definitions(" -DPV_FONTDATADIR=${DataDir}/fonts")
+#add_definitions(" -DPV_FONTDATADIR=\"${DataDir}fonts\"")
+set(PV_FONTDATADIR "${DataDir}fonts")
+configure_file("${CMAKE_CURRENT_SOURCE_DIR}/pv_config.h.cmake" "${CMAKE_CURRENT_BINARY_DIR}/pv_config.h" @ONLY)
 
 install(FILES Sansation_Regular.ttf Sansation_1.31_ReadMe.txt DESTINATION
  "${DataDir}/fonts")
 
 set(CPACK_PACKAGE_INSTALL_DIRECTORY ${CMAKE_INSTALL_PREFIX})
#ifndef _PV_CONFIG_H
#define _PV_CONFIG_H

#define PV_FONTDATADIR "@PV_FONTDATADIR@"

#endif


pgpG34kcJzLxq.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Thu, 18 Mar 2021 10:52:54 +0100
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> Am 18.03.21 um 10:45 schrieb Kornel Benko:
> > Am Thu, 18 Mar 2021 09:56:00 +0100
> > schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
> > :
> >   
> >> Am 17.03.21 um 19:11 schrieb Kornel Benko:  
> >>> Am Wed, 17 Mar 2021 17:52:10 +0100
> >>> schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"  
> >>  
> >>>> @Kornel: Maybe cmake can produce something like a pv_config.h header
> >>>> which has such platform-specific information? That should not be too
> >>>> hard - and it might be nice to maybe have a bit more platform-specific
> >>>> info at hand, like the user's home directory, to put stuff in which
> >>>> persists from session to session, and the location of the binary...
> >>>>
> >>>> I wouldn't be surprised if cmake does that all the time - I'm just not
> >>>> very good at it.
> >>>> 
> >>>
> >>> I can do that. I have to know the variable-names and their value.
> >>> And of course the desired name of the header file.  
> >>
> >> Sorry, @Kornel, I think this was yet another one of my quick shots. I
> >> have doubts now after sleeping over it. If you were to generate a C++
> >> header file which is compiled into the program, the resulting binary
> >> contains a hard-coded path - even if this is only the third option if
> >> the other two options fail. Can we be sure that such a binary will not
> >> be produced/used on another platform/distro where it's bound to fail?  
> > 
> > Sure we can. Because the installed ttf is exactly there, where it is 
> > expected.
> > In CMakeLists we specify the destination. You have to use 'PV_FONTDATADIR' 
> > in
> > pv_no_rendering.cc to find the font.  
> 
> Please explain. What do you mean by 'use'? Is PV_FONTDATADIR an 
> environment variable? Or something CMake will patch in the source?
> 
> Kay
> 

Compilation is called as
clang++ ... -DPV_FONTDATADIR="/usr/local/share/lux/fonts" ...
so that in the source you can use
#if defined(PV_FONTDATADIR)
... do something
#endif

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210318110131.3d00621f%40admin1-desktop.


pgpQWG3b6c0z0.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Thu, 18 Mar 2021 09:56:00 +0100
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> Am 17.03.21 um 19:11 schrieb Kornel Benko:
> > Am Wed, 17 Mar 2021 17:52:10 +0100
> > schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"  
> 
> >> @Kornel: Maybe cmake can produce something like a pv_config.h header
> >> which has such platform-specific information? That should not be too
> >> hard - and it might be nice to maybe have a bit more platform-specific
> >> info at hand, like the user's home directory, to put stuff in which
> >> persists from session to session, and the location of the binary...
> >>
> >> I wouldn't be surprised if cmake does that all the time - I'm just not
> >> very good at it.
> >>  
> > 
> > I can do that. I have to know the variable-names and their value.
> > And of course the desired name of the header file.  
> 
> Sorry, @Kornel, I think this was yet another one of my quick shots. I 
> have doubts now after sleeping over it. If you were to generate a C++ 
> header file which is compiled into the program, the resulting binary 
> contains a hard-coded path - even if this is only the third option if 
> the other two options fail. Can we be sure that such a binary will not 
> be produced/used on another platform/distro where it's bound to fail?

Sure we can. Because the installed ttf is exactly there, where it is expected.
In CMakeLists we specify the destination. You have to use 'PV_FONTDATADIR' in
pv_no_rendering.cc to find the font.

> I've thought about this some more, and I think the ideal solution would 
> be to have an agent which resides on a machine and can produce 
> system-specific information. What I'd like is something which is not 
> part of the program, but local to the machine, yet can be accessed in a 
> platform-independent way. How about environment variables? As far as I 
> know they are available on every platform and they are accessible from 
> C++ via a standard header. To get the information into the program, they 
> are definitely a viable path. What do you think?

This agent would also have the same problem, so I am not optimistic.

> If we were to go with this idea, the question is, how can we *set* the 
> environment variables in a platform-specific way, i.e. set an 
> environment variable LUX_GUI_FONT to 
> /usr/local/share/lux/Sansation_Regular.ttf on ubuntu? We can't use cmake 
> directly, because it won't be available on the user's machine, so there 
> must be an indirect way. If the installation process could set the 
> required variables persistently, builders could modify that step to fit 
> their needs, and the binary would remain platform-independent. I 
> wouldn't be surprised if cmake's package-building code would have 
> built-in support to set environment variables, but I couldn't find it 
> when I looked just now. One problem with session-wide environment 
> variables is that they won't be available until the user has logged in 
> again (speaking about linux here, if we were to modify e.g. ~/.profile)

No need, since the executable knows the position.

> Another way to have the right environment variable would be to launch 
> lux via a helper script, which I like anyway because it's a good way for 
> experienced users to configure the launch. The script can export the 
> environment variable, then launch lux. I think I'd favor this option.

Sure, that is how I am using it, but is not ideal IMO.

> I have added code to pv_no_rendering.cc to try and glean the value of an 
> environment variable LUX_GUI_PATH, if neither the GUI font from the 
> command line (if any) nor in the pwd (if any) can be loaded. It's the 
> 'last resort'. With this option in the code, we can experiment if this 
> idea is a viable path.

I have seen it already. Again, why not use PV_FONTDATADIR?

> @Bruno: what do you think of this idea?
> 
> Kay
> 

The patch in CMakeLists.txt should take care of blanks in path to the ttf file.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210318104512.614fc960%40admin1-desktop.
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 7bf029f..3542fce 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -159,13 +159,13 @@ i

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Wed, 17 Mar 2021 17:52:10 +0100
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> Am 17.03.21 um 12:29 schrieb Bruno Postle:
> > On Wed 17-Mar-2021 at 11:12 +0100, Hugin ptx wrote:  
> >> I'd like to tackle the find-the-font issue. CMake installs the font to 
> >> a platform-specific location. The easiest way to deal with that is to 
> >> simply hard-code this location in the C++ code and have it differ 
> >> between the branches, so in the master branch I've modified the code 
> >> pv_no_rendering.cc accordingly. It now does this:
> >>
> >> - if the user has passed a font on the CL, that takes preference.
> >>
> >> - next, lux will check the pwd. if the font isn't there
> >>
> >> - lux will try and access the target-specific location, assuming it 
> >> has been installed on the local machine  
> > 
> > You have hard-coded /usr/local in this check:
> > 
> >  ?? "/usr/local/share/lux/Sansation_Regular.ttf"
> > 
> > Whereas (for example in Linux distribution package), this would be:
> > 
> >  ?? "/usr/share/lux/Sansation_Regular.ttf"  
> 
> Thanks for pointing this out - I did fear it wasn't as easy as my quick 
> shot :(
> 
> > CMAKE_INSTALL_PREFIX defaults to "/usr/local", but can be set to 
> > whatever location the builder likes (for rpm I'm setting it to "/usr"). 
> > Can you use this definition in a macro to compile-in the installed 
> > location of the font?  
> 
> Good question.
> 
> @Kornel: Maybe cmake can produce something like a pv_config.h header 
> which has such platform-specific information? That should not be too 
> hard - and it might be nice to maybe have a bit more platform-specific 
> info at hand, like the user's home directory, to put stuff in which 
> persists from session to session, and the location of the binary...
> 
> I wouldn't be surprised if cmake does that all the time - I'm just not 
> very good at it.
> 
> Kay
> 

I can do that. I have to know the variable-names and their value.
And of course the desired name of the header file.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210317191148.6bd1facf%40admin1-desktop.


pgpUPBu0luofO.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Wed, 17 Mar 2021 11:12:56 +0100
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> I'd like to tackle the find-the-font issue. CMake installs the font to a 
> platform-specific location. The easiest way to deal with that is to 
> simply hard-code this location in the C++ code and have it differ 
> between the branches, so in the master branch I've modified the code 
> pv_no_rendering.cc accordingly. It now does this:
> 
> - if the user has passed a font on the CL, that takes preference.
> 
> - next, lux will check the pwd. if the font isn't there
> 
> - lux will try and access the target-specific location, assuming it has 
> been installed on the local machine
> 
> - if that fails, lux will exit
> 
> I've groomed the CMakeLists.txt a bit and also added code to copy the 
> Font's README to the font path, as required by the font's license.

You may have used
if(UNIX)
set(DataDir "${CMAKE_INSTALL_PREFIX}/share/${_pv}/")
elseif(WIN32)
set(DataDir "${CMAKE_INSTALL_PREFIX}/Resources/")
elseif(APPLE)
set(DataDir "${CMAKE_INSTALL_PREFIX}/${_pv}.app/Contents/Resources")
endif()
add_definitions(" -DPV_FONTDATADIR=${DataDir}/fonts")


and later
 install(FILES Sansation_Regular.ttf Sansation_1.31_ReadMe.txt DESTINATION
 "${DataDir}/fonts")

> For now I've only changed the master branch to this behaviour, so you 
> can try it out. Let me know what you think. If this works satisfactorily 
> on linux, I'll change the other branches accordingly.
> 
> @Harry: can you please tell me what path the font is installed to on the 
> mac, so I can adapt the mac branch?
> 
> I did a trial 'sudo make install' on my machine and it works fine. I 
> don't like having platform-specific code, but for this single issue I 
> can just about live with it ;)
> 
> The last push to master also should have resolved an issue with 
> stitching images with alpha channel, so 'manual deghosting' by erasing 
> unwanted bits from partials where other partials have content to 'fill 
> the gap' should now work as expected for stitches - exposure fusions and 
> faux brackets weren't affected.
> 
> I'll carry on grooming and refactoring for a while, and I may be able to 
> save some more memory. With the last commit, I already introduced new 
> code which only uses single-float masks, where pv had used RGB data for 
> convenience's sake. This should already have produced the bulk of memory 
> savings I think possible.
> 
> @Harry: please check memory use again, let me know how far I got memory 
> consumption down, and if the lowering of the number of threads with 
> --snapshot_threads now works for you.
> 
> Kay
> 

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210317120149.1727ef4b%40admin1-desktop.


pgpDN0W8s6WtL.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Tue, 16 Mar 2021 19:19:02 +0100
schrieb Harry van der Wolf :

> Question of compilation of pv/lux.
> 
> Whether you use cmake or simply the makefile based make, compilation takes
> quite some time.
> When using "make -j 4" to use 4 cores for compilation instead of 1, the
> compilation is much faster.
> Of course not every software is suitable to do this. At least not (quite)
> some years ago (I was Apple maintainer for avidemux which did not support
> it) and I really don't know if that has changed in general.
> Can I use multiple cores to compile pv/lux?
> I did a compilation this evening and so far I did not find issues.
> 
> Harry
> 

No problems here Harry. I always use 'make -j16'.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210316192524.07b49de5%40admin1-desktop.


pgpSUNDAurppi.pgp
Description: Digitale Signatur von OpenPGP

[hugin-ptx] Re: pv: Amend 0913a185

[Kornel Benko]

Am Sun, 14 Mar 2021 09:33:11 +0100
schrieb Kornel Benko :

> Omit also the last single-quote from brief_description.txt.
> 
> Omits the output 'at it's bitbucket site:'
> 
>   Kornel

Kay?

Ping

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210315120424.72daa731%40admin1-desktop.


pgpFzj9qr9aNq.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] pv: debian packaging

[Kornel Benko]

Am Sun, 14 Mar 2021 10:24:30 +0100
schrieb Kornel Benko :

> If creating a debian package, the section defaults to "devel" if not 
> otherwise set.
> Changing it to "graphics", which is more appropriate.
> 
>   Kornel
> 

Kay?

Ping

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210315120343.2a831147%40admin1-desktop.


pgpLni5dPXJPU.pgp
Description: Digitale Signatur von OpenPGP

[hugin-ptx] pv: debian packaging

[Kornel Benko]

If creating a debian package, the section defaults to "devel" if not otherwise 
set.
Changing it to "graphics", which is more appropriate.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210314102430.1cd3d7ad%40admin1-desktop.
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 3409575..29a5ca8 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -171,10 +171,12 @@ file(READ LICENSE CPACK_PACKAGE_LICENSE)
 
 # insert description
 
 set(CPACK_PACKAGE_DESCRIPTION_FILE "${CMAKE_SOURCE_DIR}/brief_description.txt")
 
+set(CPACK_DEBIAN_PACKAGE_SECTION "graphics")
+
 # is 'VENDOR' the right term here? This is FOSS
 
 set(CPACK_PACKAGE_VENDOR "Kay F. Jahnke")
 
 set(CPACK_STRIP_FILES 1)


pgpl22wv4O1hl.pgp
Description: Digitale Signatur von OpenPGP

[hugin-ptx] pv: Amend 0913a185

[Kornel Benko]

Omit also the last single-quote from brief_description.txt.

Omits the output 'at it's bitbucket site:'

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210314093311.228f7ef7%40admin1-desktop.
diff --git a/brief_description.txt b/brief_description.txt
index 97fd5ce..0768d10 100644
--- a/brief_description.txt
+++ b/brief_description.txt
@@ -1,8 +1,6 @@
 pv - a free open source image and panorama viewer
 
 pv can show -normal- images, panoramas in various formats
 and PTO files made with software like hugin. It can also do
 simple stitching and blending jobs. You can find documentation
-at it's bitbucket site:
-
-https://bitbucket.org/kfj/pv
+at the bitbucket site: https://bitbucket.org/kfj/pv


pgpcEsCEmPpOg.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Sat, 13 Mar 2021 22:16:59 +0100
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> Kornel, I applied both your patches to master.
> 
> Kay
> 

Thanks Kay.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210313222457.30356fff%40admin1-desktop.


pgpPy1sUZhuOU.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Sat, 13 Mar 2021 21:47:26 +0100
schrieb Kornel Benko :

> Am Sat, 13 Mar 2021 21:44:23 +0100
> schrieb Kornel Benko :
> 
> > Am Sat, 13 Mar 2021 21:33:18 +0100
> > schrieb Kornel Benko :
> >   
> > > Am Sat, 13 Mar 2021 19:12:32 +0100
> > > schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
> > > :
> > > 
> > > > > ...
> > > >   
> > > > >>> So I should actually create 2 patches.
> > > > >>> I simply acted too quickly and combined the two.
> > > > 
> > > > I sucked in the patch best I could and pushed --all, have a look if 
> > > > you're both happy with the state of master and mac branches in the repo 
> > > > now. and let's do single-file patches from now on, save me headaches...
> > > > 
> > > > Kay
> > > >   
> > >   
> 

Try to omit in-source build.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/2021031316.26c5a850%40admin1-desktop.
diff --git a/CMakeLists.txt b/CMakeLists.txt
index d9bbefe..780c20d 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -33,10 +33,18 @@
 # mkdir build
 # cd build
 # cmake ..
 # make
 
+get_filename_component(_varsource "${CMAKE_SOURCE_DIR}" REALPATH)
+get_filename_component(_varbinary "${CMAKE_BINARY_DIR}" REALPATH)
+
+# prevent in-tree building
+if("${_varsource}" STREQUAL "${_varbinary}")
+	message(FATAL_ERROR "In-source builds are not allowed")
+endif()
+
 set(ENV{CXX} clang++)
 set(ENV{CC} clang)
 
 set(_pv pv)	# Project name
 project (${_pv})
@@ -157,11 +165,11 @@ endif()
 set(CPACK_PACKAGE_INSTALL_DIRECTORY ${CMAKE_INSTALL_PREFIX})
 set(CPACK_SET_DESTDIR "ON")
 
 # TODO: insert license
 
-file(READ LICENSE CPACK_RPM_PACKAGE_LICENSE)
+file(READ LICENSE CPACK_PACKAGE_LICENSE)
 
 # TODO: insert description
 # how about:
 
 set(CPACK_PACKAGE_DESCRIPTION_FILE "${CMAKE_SOURCE_DIR}/brief_description.txt")


pgpAaSIbDw3eK.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Sat, 13 Mar 2021 21:44:23 +0100
schrieb Kornel Benko :

> Am Sat, 13 Mar 2021 21:33:18 +0100
> schrieb Kornel Benko :
> 
> > Am Sat, 13 Mar 2021 19:12:32 +0100
> > schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
> > :
> >   
> > > > ...  
> > > 
> > > >>> So I should actually create 2 patches.
> > > >>> I simply acted too quickly and combined the two.  
> > > 
> > > I sucked in the patch best I could and pushed --all, have a look if 
> > > you're both happy with the state of master and mac branches in the repo 
> > > now. and let's do single-file patches from now on, save me headaches...
> > > 
> > > Kay
> > > 
> > 

Change variable name CPACK_RPM_PACKAGE_LICENSE to more general 
CPACK_PACKAGE_LICENSE.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210313214726.66ac56f2%40admin1-desktop.
diff --git a/CMakeLists.txt b/CMakeLists.txt
index d9bbefe..a56fc7d 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -157,11 +157,11 @@ endif()
 set(CPACK_PACKAGE_INSTALL_DIRECTORY ${CMAKE_INSTALL_PREFIX})
 set(CPACK_SET_DESTDIR "ON")
 
 # TODO: insert license
 
-file(READ LICENSE CPACK_RPM_PACKAGE_LICENSE)
+file(READ LICENSE CPACK_PACKAGE_LICENSE)
 
 # TODO: insert description
 # how about:
 
 set(CPACK_PACKAGE_DESCRIPTION_FILE "${CMAKE_SOURCE_DIR}/brief_description.txt")


pgpsP5uNO25Ac.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Sat, 13 Mar 2021 21:33:18 +0100
schrieb Kornel Benko :

> Am Sat, 13 Mar 2021 19:12:32 +0100
> schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
> :
> 
> > > ...
> >   
> > >>> So I should actually create 2 patches.
> > >>> I simply acted too quickly and combined the two.
> > 
> > I sucked in the patch best I could and pushed --all, have a look if 
> > you're both happy with the state of master and mac branches in the repo 
> > now. and let's do single-file patches from now on, save me headaches...
> > 
> > Kay
> >   
> 
> Missing changes to LICENSE file.
> 
> Substitute all double-quotes with single-quotes to fit in the cpack-variable
> CPACK_RPM_PACKAGE_LICENSE.
> 
>   Kornel

Changing the single-quote in brief_description.txt to dash.
The output of 'dpkg -s pv' is better readable.
Compare
pv can show -normal- images, panoramas in various formats
with
pv can show 'normal' images, panoramas in various formats

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210313214423.1260a7a4%40admin1-desktop.
diff --git a/brief_description.txt b/brief_description.txt
index ba0e2ec..97fd5ce 100644
--- a/brief_description.txt
+++ b/brief_description.txt
@@ -1,8 +1,8 @@
 pv - a free open source image and panorama viewer
 
-pv can show 'normal' images, panoramas in various formats
+pv can show -normal- images, panoramas in various formats
 and PTO files made with software like hugin. It can also do
 simple stitching and blending jobs. You can find documentation
 at it's bitbucket site:
 
 https://bitbucket.org/kfj/pv


pgp8FqZV7dvgH.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Sat, 13 Mar 2021 19:12:32 +0100
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> > ...  
> 
> >>> So I should actually create 2 patches.
> >>> I simply acted too quickly and combined the two.  
> 
> I sucked in the patch best I could and pushed --all, have a look if 
> you're both happy with the state of master and mac branches in the repo 
> now. and let's do single-file patches from now on, save me headaches...
> 
> Kay
> 

Missing changes to LICENSE file.

Substitute all double-quotes with single-quotes to fit in the cpack-variable
CPACK_RPM_PACKAGE_LICENSE.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210313213318.23e11001%40admin1-desktop.
diff --git a/LICENSE b/LICENSE
index 94a9ed0..7b4cbfa 100644
--- a/LICENSE
+++ b/LICENSE
@@ -70,70 +70,70 @@ modification follow.
 
TERMS AND CONDITIONS
 
   0. Definitions.
 
-  "This License" refers to version 3 of the GNU General Public License.
+  'This License' refers to version 3 of the GNU General Public License.
 
-  "Copyright" also means copyright-like laws that apply to other kinds of
+  'Copyright' also means copyright-like laws that apply to other kinds of
 works, such as semiconductor masks.
 
-  "The Program" refers to any copyrightable work licensed under this
-License.  Each licensee is addressed as "you".  "Licensees" and
-"recipients" may be individuals or organizations.
+  'The Program' refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as 'you'.  'Licensees' and
+'recipients' may be individuals or organizations.
 
-  To "modify" a work means to copy from or adapt all or part of the work
+  To 'modify' a work means to copy from or adapt all or part of the work
 in a fashion requiring copyright permission, other than the making of an
-exact copy.  The resulting work is called a "modified version" of the
-earlier work or a work "based on" the earlier work.
+exact copy.  The resulting work is called a 'modified version' of the
+earlier work or a work 'based on' the earlier work.
 
-  A "covered work" means either the unmodified Program or a work based
+  A 'covered work' means either the unmodified Program or a work based
 on the Program.
 
-  To "propagate" a work means to do anything with it that, without
+  To 'propagate' a work means to do anything with it that, without
 permission, would make you directly or secondarily liable for
 infringement under applicable copyright law, except executing it on a
 computer or modifying a private copy.  Propagation includes copying,
 distribution (with or without modification), making available to the
 public, and in some countries other activities as well.
 
-  To "convey" a work means any kind of propagation that enables other
+  To 'convey' a work means any kind of propagation that enables other
 parties to make or receive copies.  Mere interaction with a user through
 a computer network, with no transfer of a copy, is not conveying.
 
-  An interactive user interface displays "Appropriate Legal Notices"
+  An interactive user interface displays 'Appropriate Legal Notices'
 to the extent that it includes a convenient and prominently visible
 feature that (1) displays an appropriate copyright notice, and (2)
 tells the user that there is no warranty for the work (except to the
 extent that warranties are provided), that licensees may convey the
 work under this License, and how to view a copy of this License.  If
 the interface presents a list of user commands or options, such as a
 menu, a prominent item in the list meets this criterion.
 
   1. Source Code.
 
-  The "source code" for a work means the preferred form of the work
-for making modifications to it.  "Object code" means any non-source
+  The 'source code' for a work means the preferred form of the work
+for making modifications to it.  'Object code' means any non-source
 form of a work.
 
-  A "Standard Interface" means an interface that either is an official
+  A 'Standard Interface' means an interface that either is an official
 standard defined by a recognized standards body, or, in the case of
 interfaces specified for a particular programming language, one that
 is widely used among developers working in that language.
 
-  The "System Libraries" of an executable work include anything, other
+  The 'System Libraries' of an executable work include anything, other
 than the work as a whole, that (a) is included in the normal form of
 packaging a Major Component, but which is not part of that Major
 Component, and (b) serves only to enable use of the 

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Sat, 13 Mar 2021 17:51:26 +0100
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> Sorry, @Harry, I accidentally answered to you only, here's to the list:
> 
> Am 13.03.21 um 16:06 schrieb Harry van der Wolf:
> 
> > The linux version is the master branch.
> > Mac works on the origin/mac branch.  
> 
> @ Harry, Kornel
> 
> Yeah, I figured the mac-only stuff would best be placed in the mac 
> branch, because it means nothing to the other branches, whereas the 
> CMakeLists.txt is multi-platform, so I put it in master.
> 
> Kornel proposed to keep the build files updated by doing ordinary
> diff -u diffs against single files, which I would find easier than 
> patches against the whole repo or branches of it - so far the number of 
> files affected is quite low. I only touched the CMakeLists.txt yesterday 
> to put in the copyright header and some initial comments and I don't 
> expect to have too much to contribute to it, so we shouldn't run into 
> messy conflicts.
> 
> Is that okay with you guys?

Yes from my side.

> > So I should actually create 2 patches.
> > I simply acted too quickly and combined the two.
> > 
> > So actually the first patch should go on the mac branch, and I should 
> > make a second patch for the master branch.
> > Or better: Change the makefile in the master branch so that it checks 
> > whether it runs on Apple, gnu linux or win32/win64, and then remove the 
> > mac branch.  
> 
> So... which is what and what should I put in the repo now??
> 
> > And in the CMakeLists.txt file we should have at line 38 something like
> > # prevent in-tree building
> > if("${CMAKE_SOURCE_DIR}" STREQUAL "${CMAKE_BINARY_DIR}")
> >  ?? ?? message(FATAL_ERROR "In-source builds are not allowed.")
> > endif()  
> 
> You might as well simply trust the user. Most people who've come so far 
> as doing their own builds should know that in-tree builds aren't cool. I 
> think it's best to keep it simple, no need to regulate everything. Just 
> my personal opinion...

I don't trust. The messy things start if one tries to use cmake _and_ 
automake-build in
source. Better to omit the mess, less things that may go wrong.

> Kay

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210313181837.6c32831c%40admin1-desktop.


pgpxzcccreDEl.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Sat, 13 Mar 2021 16:06:58 +0100
schrieb Harry van der Wolf :

> I'm sorry.
> The linux version is the master branch.
> Mac works on the origin/mac branch.
> 
> So I should actually create 2 patches.
> I simply acted too quickly and combined the two.
> 
> So actually the first patch should go on the mac branch, and I should make
> a second patch for the master branch.
> Or better: Change the makefile in the master branch so that it checks
> whether it runs on Apple, gnu linux or win32/win64, and then remove the mac
> branch.
> 
> And in the CMakeLists.txt file we should have at line 38 something like
> # prevent in-tree building
> if("${CMAKE_SOURCE_DIR}" STREQUAL "${CMAKE_BINARY_DIR}")
> message(FATAL_ERROR "In-source builds are not allowed.")
> endif()
> 

Good hint. I never liked the in-source builds anyway.

> Best,
> Harry
> 
> 
> 
> Harry
> 
Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210313161521.3b392e0f%40admin1-desktop.


pgpV206BHgFDR.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv

[Kornel Benko]

Am Sat, 13 Mar 2021 15:11:23 +0100
schrieb Harry van der Wolf :

> Sorry,
> 
> I made the patch on my Mac and forgot about the changes for Linux 18.04
> 
> See attached patch 2 including the changes of the previous patch as well.
> Do not apply the previous "mac_exiv2_bundle.patch", but only this
> "mac_exiv2_bundle_2.patch"
> 

We have to wait for Kay anyway. He is ATM the only on I know of who can commit.

Applying the patch locally I got errors.

patching file CMakeLists.txt
patching file CMakeModules/FindEXIV2.cmake
can't find file to patch at input line 163
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--
|diff --git a/scripts/make_bundle.sh b/scripts/make_bundle.sh
|index 16f73d8..40cd80c 100755
|--- a/scripts/make_bundle.sh
|+++ b/scripts/make_bundle.sh
--
File to patch:

.
Here, the scripts directory does (of course) not exist.

Apart from that, pv is still compilable. Thanks for the patch.
(Ask Kay to include your scripts dir)

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210313153053.14e1dfd3%40admin1-desktop.


pgpp76xXMWjid.pgp
Description: Digitale Signatur von OpenPGP

[hugin-ptx] pv:LICENSE

[Kornel Benko]

Since we use the file 'LICENSE' as content of the cpack variable
CPACK_RPM_PACKAGE_LICENSE,
we have a problem.
The definition looks like
set(CPACK_RPM_PACKAGE_LICENSE "  ")
but the content contains character ", so we get parse errors.
Replacing all " with ' in LICENSE cures the problem for me.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210313112742.57125048%40admin1-desktop.


pgpvIB1ynODAt.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Image Stitching and Exposure Fusion with pv-feedback

[Kornel Benko]

Am Wed, 3 Mar 2021 10:32:40 +0100
schrieb "'Kay F. Jahnke' via hugin and other free panoramic software"
:

> If my code turns out to be good, I'd be happy to see it used by others. 
> I just don't want to go fiddling with other people's software to force 
> my new stuff in. Integration into extant software is better done by the 
> original authors, who know their way around their code. As far as pv and 
> it's new components are concerned, I want to stay upstream and focus on 
> innovation.

Hi Kay,
just to make some feedback about using pv.
Compiles fine (source from the repo), happy to use it.
I have to specify the font though to run pv.
Works fine on .pto files.
Thanks for the nice tool.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20210308130044.06af39f6%40admin1-desktop.


pgp8NauUfVj2L.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Re: [PATCH] Install MIME type icon into the hicolor theme

[Kornel Benko]

Am Sun, 24 May 2020 04:36:27 -0700 (PDT)
schrieb "T. Modes" :

> Hi Chris,
> 
> Am Donnerstag, 7. Mai 2020 20:13:23 UTC+2 schrieb Chris Mayo:
> >
> > Most Hugin icons are installed into the hicolor theme but the MIME type 
> > icon is still going into the defunct gnome theme.
> > The attached patch changes that and removes the gnome-mime- prefix from 
> > the icon filename.
> >
> 
> Thanks for the patch.
> But before applying I would like to hear from somebody else that it works 
> also for him.
> 
> So a questions to other Linux user: can you confirm that the patch works 
> also for you? Or does it break on other distros?
> 
> Thomas
> 


I use 'mate', which is built over gnome. No problems with the patch.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20200524141140.1e8d527c%40admin1-desktop.


pgpdxGF8yZGQR.pgp
Description: Digitale Signatur von OpenPGP

[hugin-ptx] Cmake-warning

[Kornel Benko]

With cmake 3.16, I get the following warning:

CMake Warning (dev) at /usr/share/cmake-3.16/Modules/FindOpenGL.cmake:275 
(message):
  Policy CMP0072 is not set: FindOpenGL prefers GLVND by default when
  available.  Run "cmake --help-policy CMP0072" for policy details.  Use the
  cmake_policy command to set the policy and suppress this warning.

  FindOpenGL found both a legacy GL library:

OPENGL_gl_LIBRARY: /usr/lib/x86_64-linux-gnu/libGL.so

  and GLVND libraries for OpenGL and GLX:

OPENGL_opengl_LIBRARY: /usr/lib/x86_64-linux-gnu/libOpenGL.so
OPENGL_glx_LIBRARY: /usr/lib/x86_64-linux-gnu/libGLX.so

  OpenGL_GL_PREFERENCE has not been set to "GLVND" or "LEGACY", so for
  compatibility with CMake 3.10 and below the legacy GL library will be used.
Call Stack (most recent call first):
  CMakeLists.txt:227 (FIND_PACKAGE)
This warning is for project developers.  Use -Wno-dev to suppress it.
..

What about the attached patch?
The resulting hugin executable works fine here.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20200120214822.184feec4%40admin1-desktop.
diff -r 2749e5583624 CMakeLists.txt
--- a/CMakeLists.txt	Mon Jan 20 18:53:04 2020 +0100
+++ b/CMakeLists.txt	Mon Jan 20 21:44:36 2020 +0100
@@ -9,6 +9,9 @@
 
 if(COMMAND cmake_policy)
   cmake_policy(SET CMP0003 NEW)
+  if (POLICY CMP0072)
+cmake_policy(SET CMP0072 NEW)
+  endif()
 endif(COMMAND cmake_policy)
 
 if(APPLE)


pgpJeTgLSK7ry.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Re: Warnings while compiling hugin

[Kornel Benko]

Am Mon, 20 Jan 2020 11:41:13 -0800 (PST)
schrieb "T. Modes" :

> 
> 
> Am Montag, 20. Januar 2020 20:05:36 UTC+1 schrieb kornel:
> >
> > Thanks, but the buffer size is 10. How can 16 digits fit there? 
> > You meant 6 digits probably? 
> >
> 
> No, I meant 16. The warning was in line 525:
> std::sprintf(fmt,"%%.%df",digits);
> Here only the format string is build. So for 16 digits fmt becomes "%.16f". 
> This is shorter than the 10 bytes of fmt.
> (The warning above the overflow would result when digits>=100, because 
> then fmt would become "%.100f" which will not fit into char fmt[10].)
> 
> The actual conversion of the double to string is done in line 530ff:
> #ifdef _MSC_VER
> _snprintf (c, 1023, fmt, d);
> #else
> snprintf (c, 1023, fmt, d);
> #endif
> Here we have a buffer with length 1024.
> 

Thanks Thomas, makes sense.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20200120213900.2750d0e3%40admin1-desktop.


pgpwyT0KEBRJH.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Re: Warnings while compiling hugin

[Kornel Benko]

Am Mon, 20 Jan 2020 10:01:01 -0800 (PST)
schrieb "T. Modes" :

> 
> 
> Am Montag, 20. Januar 2020 13:02:59 UTC+1 schrieb kornel:
> >
> > Hi, 
> > apart from getting some 'deprecated' messages while compiling hugin, 
> > there are also these possibly dangerous messages. 
> >
> 
> The overflow can only happen if sometime wants a number with more then 
> 99 digits after the period. Hugin is using the function with maximal 6 
> digits. So this overflow is very theoretic/is very unlikely.
> Nevertheless I added an additional check to prevent the usage of so much 
> digits.
> 

Thanks, but the buffer size is 10. How can 16 digits fit there?
You meant 6 digits probably?

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20200120200533.0d1c9bd3%40admin1-desktop.


pgpMsNjSjq_cG.pgp
Description: Digitale Signatur von OpenPGP

[hugin-ptx] Warnings while compiling hugin

[Kornel Benko]

Hi,
apart from getting some 'deprecated' messages while compiling hugin,
there are also these possibly dangerous messages.

...
/usr/src/hugin/hugin_hg/src/hugin_base/hugin_utils/utils.cpp: In function
‘std::__cxx11::string hugin_utils::doubleToString(double,
int)’: /usr/src/hugin/hugin_hg/src/hugin_base/hugin_utils/utils.cpp:225:26: 
warning: ‘%d’
directive writing between 1 and 10 bytes into a region of size 8 
[-Wformat-overflow=]
std::sprintf(fmt,"%%.%df",digits);
^~~~ /usr/src/hugin/hugin_hg/src/hugin_base/hugin_utils/utils.cpp:225:26: 
note:
directive argument in the range [0, 2147483647] In file included
from /usr/include/stdio.h:862, from /usr/include/c++/8/cstdio:42,
from /usr/include/c++/8/ext/string_conversions.h:43,
from /usr/include/c++/8/bits/basic_string.h:6400, from 
/usr/include/c++/8/string:52,
 from 
/usr/src/hugin/hugin_hg/src/hugin_base/hugin_utils/utils.h:30,
 from 
/usr/src/hugin/hugin_hg/src/hugin_base/hugin_utils/utils.cpp:25:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:33:34: note: 
‘__builtin___sprintf_chk’ output
between 5 and 14 bytes into a destination of size 10 return 
__builtin___sprintf_chk (__s,
__USE_FORTIFY_LEVEL - 1, ^~
   __bos (__s), __fmt, __va_arg_pack ());
   ~
...

Easy to correct.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20200120130255.037e2c78%40admin1-desktop.
diff -r b3c64862bbfc src/hugin_base/hugin_utils/utils.cpp
--- a/src/hugin_base/hugin_utils/utils.cpp	Sun Jan 19 16:04:22 2020 +0100
+++ b/src/hugin_base/hugin_utils/utils.cpp	Mon Jan 20 13:02:00 2020 +0100
@@ -218,7 +218,7 @@
 
 std::string doubleToString(double d, int digits)
 {
-char fmt[10];
+char fmt[20];
 if (digits < 0) {
 strcpy(fmt,"%f");
 } else {


pgpFVeiMVX08H.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Compiling enblend with gnu g++

[Kornel Benko]

Am Fri, 22 Nov 2019 06:42:24 +0100
schrieb Gunter Königsmann :

> I believe if you add -std=c++1z  to the compiler flags it works.
> 
> Kind regards,
> 
> Gunter.

Unfortunately this does not help. The resulting error is the same as with 
-std=c++17.

> Am 22. November 2019 00:57:58 MEZ schrieb Kornel Benko 
> :
> >Hi,
> >the recent version of enblend sources (from repo) is
> >not compilable with the gnu compiler.
> >
> >Using it I get
> >In file included from /usr/src/enblend/enblend-code/src/enblend.cc:85:
> >/usr/src/enblend/enblend-code/src/optional_transitional.hpp:40:51:
> >error: 'experimental'
> >in namespace 'std' does not name a type 40 | template 
> >using optional
> >= ::std::experimental::optional; |
> >^~~~
> >/usr/src/enblend/enblend-code/src/optional_transitional.hpp:41:11:
> >error:
> >'experimental' has not been declared 41 | using
> >experimental::nullopt;
> >  |   ^~~~
> >/usr/src/enblend/enblend-code/src/enblend.cc:118:6: error: 'optional'
> >in namespace 'std'
> >does not name a template type 118 | std::optional
> >OutputMaskFileName;
> >  |  ^~~~
> >/usr/src/enblend/enblend-code/src/enblend.cc:118:1: note:
> >'std::optional' is only
> >available from C++17 onwards
> >...
> >
> >Patching the CMakeLists.txt to use the required --std=c++17, the error
> >compiling src/enblend.cc is:
> >In file included from /usr/include/vigra/stdconvolution.hxx:43,
> > from /usr/include/vigra/convolution.hxx:41,
> >  from /usr/src/enblend/enblend-code/src/openmp_vigra.h:32,
> > from /usr/src/enblend/enblend-code/src/enblend.h:41,
> > from /usr/src/enblend/enblend-code/src/enblend.cc:197:
> >/usr/include/vigra/separableconvolution.hxx:1413:13: error: ISO C++17
> >does not allow
> >dynamic exception specifications 1413 |
> >throw(PreconditionViolation)
> >  | ^
> >.
> >
> >This is the same with the recent g++9.2 compiler.
> >
> > Kornel
> >

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20191122113615.2e9a019c%40admin1-desktop.


pgpbv5ppuzAqC.pgp
Description: Digitale Signatur von OpenPGP

[hugin-ptx] Compiling enblend with gnu g++

[Kornel Benko]

Hi,
the recent version of enblend sources (from repo) is
not compilable with the gnu compiler.

Using it I get
In file included from /usr/src/enblend/enblend-code/src/enblend.cc:85:
/usr/src/enblend/enblend-code/src/optional_transitional.hpp:40:51: error: 
'experimental'
in namespace 'std' does not name a type 40 | template  using 
optional
= ::std::experimental::optional; |
^~~~ /usr/src/enblend/enblend-code/src/optional_transitional.hpp:41:11: 
error:
'experimental' has not been declared 41 | using experimental::nullopt;
  |   ^~~~
/usr/src/enblend/enblend-code/src/enblend.cc:118:6: error: 'optional' in 
namespace 'std'
does not name a template type 118 | std::optional 
OutputMaskFileName;
  |  ^~~~
/usr/src/enblend/enblend-code/src/enblend.cc:118:1: note: 'std::optional' is 
only
available from C++17 onwards
...

Patching the CMakeLists.txt to use the required --std=c++17, the error
compiling src/enblend.cc is:
In file included from /usr/include/vigra/stdconvolution.hxx:43,
 from /usr/include/vigra/convolution.hxx:41,
 from /usr/src/enblend/enblend-code/src/openmp_vigra.h:32,
 from /usr/src/enblend/enblend-code/src/enblend.h:41,
 from /usr/src/enblend/enblend-code/src/enblend.cc:197:
/usr/include/vigra/separableconvolution.hxx:1413:13: error: ISO C++17 does not 
allow
dynamic exception specifications 1413 | throw(PreconditionViolation)
  | ^
.

This is the same with the recent g++9.2 compiler.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20191122005758.60f2c8a6%40admin1-desktop.


pgpX_nUyavDvC.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Problem building Enblend

[Kornel Benko]

Am Sun, 3 Nov 2019 06:05:30 -0800 (PST)
schrieb "T. Modes" :

> Hi Terry,
> 
> Am Freitag, 1. November 2019 22:23:03 UTC+1 schrieb Tduell:
> >
> > Looks like exiv2 0.27.2 has caused the problems here. 
> >  
> 
> After the latest changes you need exiv2 from the repository/master branch. 
> 0.27.x is too old.
> Or disable metadata transfer.

The repo-version shows as 0.27.99.0. Compiled, installed.
Try to compile enblend with '-DENABLE_METADATA_TRANSFER:BOOL=ON'.
Works.

Thanks Thomas.

> Thomas
> 

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20191103175203.2069851b%40admin1-desktop.


pgpsPkyAUIkEK.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Problem building Enblend

[Kornel Benko]

Am Fri, 01 Nov 2019 15:45:27 +1100
schrieb "Terry Duell" :

> Hello Luís,
> 
> On Fri, 01 Nov 2019 14:14:44 +1100, Luís Henrique Camargo Quiroz  
>  wrote:
> 
> >   Hi Terry,
> >
> >   I have built mine on a fresh Debian testing without problems, about a
> > week ago.
> >  
> 
> That's interesting.
> Chris added some changes to the default branch about 10 days ago, which  
> related to exiv2, and it's probably those that are causing grief on my  
> system.
> Fedora 30 is using exiv2 0.27.2.
> Not sure if it's relevant or not, but which version of exiv2 are you  
> using, and did your recent build use rev. 1526 or later?
> 
> Cheers,

Hello Terry,
I had no problems with exiv2 0.25.3.
To be sure, I started with "make clean" to compile the c++ sources.
Only creation of the tex-docs had some errors (current updated TL19)

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20191101114043.74cc191f%40admin1-desktop.


pgpnkWSbS_9lN.pgp
Description: Digitale Signatur von OpenPGP

Re: [hugin-ptx] Imaging stacking without transparency

[Kornel Benko]

Am Montag, 7. Mai 2018 11:07:56 CEST schrieb Roberto Pinto 
:
> Hi Gunter! I'm trying to stack only 2 pics at first. I created a mask 
> around the boy in the second pic type "Inclusion region", and I exported 
> this mask. In the first pic I imported the previous mask and typed it 
> "exclusion region", but, unfortunately the final pic does not display the 2 
> boys.
> Do you have any idea about what I'm doing wrong?
> Regards, Roberto

Instead of excluding some parts, you may want to include parts you want to have.
You don't need to exclude a region which is already included in other image.

> Em domingo, 6 de maio de 2018 19:19:55 UTC-3, Roberto Pinto escreveu:
> >
> > Hi Gunter! Do you gui Hugin or command line?
> > Regards, Roberto
> >
> > Em domingo, 6 de maio de 2018 14:35:31 UTC-3, Gunter Königsmann escreveu:
> >>
> >> 1.) In each picture you add a mask for the places you don't want to 
> >> include from this picture.
> >> 2.) You mark all pictures, tell hugin to add control points
> >> 3.) You tell hugin to align the pictures
> >> 4.) Let hugin stitch the pictures.
> >> Done.
> >>
> >> I always use the advanced interface for my work.
> >>
> >> Kind regards,
> >>
> >>   Gunter.
> >>
> >> Roberto Pinto  schrieb am So., 6. Mai 2018, 17:23:
> >>
> >>> Hi, I'd like to know if it is possible to use Hugin to develop a picture 
> >>> like the one attached. I'd like to stack many pics without transparency. 
> >>> Regards, Roberto.
> >>>

Kornel


-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/3264531.ci05lJM9Xe%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Re: Hugin 2017.0 beta 1 release

[Kornel Benko]

Am Dienstag, 16. Mai 2017 um 09:27:29, schrieb T. Modes 
> 
> Am Dienstag, 16. Mai 2017 18:19:13 UTC+2 schrieb kornel:
> >
> > It is not compilable because of 
> >
> 
> Should be fixed.
> 
> Thomas
> 

It is.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/8746338.YYxbceifgN%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Re: Hugin 2017.0 beta 1 release

[Kornel Benko]

Am Dienstag, 16. Mai 2017 um 08:38:17, schrieb Niklas Mischkulnig 

> It should be fixed, please try out this new version:
> 
> https://sourceforge.net/projects/hugin/files/hugin/hugin-2017.0/Hugin-2017.0.0-beta1-r1.dmg/download
> 
> 
> Niklas

It is not compilable because of
cd /BUILD/BUILDMint17/BuildHugin_hg/src/translations && /usr/bin/msgfmt -o 
/BUILD/BUILDMint17/BuildHugin_hg/src/translations/pt_BR.gmo 
/BUILD/BUILDMint17/BuildHugin_hg/src/translations/pt_BR.po
/BUILD/BUILDMint17/BuildHugin_hg/src/translations/pt_BR.po:7476: 'msgid' and 
'msgstr' entries do not both end with '\n'
/usr/bin/msgfmt: found 1 fatal error
make[2]: *** [src/translations/pt_BR.gmo] Error 1
make[2]: *** Deleting file `src/translations/pt_BR.gmo'
make[2]: Leaving directory `/BUILD/BUILDMint17/BuildHugin_hg'
make[1]: *** [src/translations/CMakeFiles/translations.dir/all] Error 2
make[1]: Leaving directory `/BUILD/BUILDMint17/BuildHugin_hg'
make: *** [all] Error 2

The patch is easy though.

#diff -r 462085503da3 src/translations/pt_BR.po
--- a/src/translations/pt_BR.po Tue May 16 10:12:02 2017 -0300
+++ b/src/translations/pt_BR.po Tue May 16 18:12:27 2017 +0200
@@ -7162,7 +7162,7 @@
 "intermediate images."
 msgstr ""
 "O seguinte arquivo de argumentos será usado para copiar etiquetas da "
-"primeira imagem para todas as imagens intermediárias.\n"
+"primeira imagem para todas as imagens intermediárias."
 
 #: hugin1/hugin/xrc/pref_dialog.xrc:971
 msgid "Intermediate ExifTool argfile:"

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/5798308.vRNKq4yn71%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Re: Enblend: Compilation problem with gcc 4.8

[Kornel Benko]

Am Freitag, 25. November 2016 um 04:45:38, schrieb cspiel 
> On Friday, 25 November 2016 11:00:22 UTC+1, kornel wrote:
> 
> > Does it mean, I have a too old c++ compiler? (g++ (Ubuntu 
> > 4.8.4-2ubuntu1~14.04.3) 4.8.4) 
> >
> 
> Yes.
> 
> Currently, g++-4.9.2 is the minimum requirement for the tip
> of the Enblend/Enfuse development branch.
> 
> /cls
> 

Thanks for the info. Seems, I am out of the game :(

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/640.5DEyVmoWDI%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Enblend: Compilation problem with gcc 4.8

[Kornel Benko]

Am Freitag, 25. November 2016 um 12:21:07, schrieb Stefan Peter 

> Hi Kornel
> 
> Am 25.11.2016 um 11:00 schrieb Kornel Benko:
> > Compiling enblend, I get this error:
> > 
> > /usr/src/enblend/enblend-code/src/metadata.cc: In function ‘void 
> > metadata::augment(Exiv2::Image*)’:
> > /usr/src/enblend/enblend-code/src/metadata.cc:92:71: error: invalid 
> > initialization of non-const reference of type ‘Exiv2::ExifData&’ from an 
> > rvalue of type ‘’
> >  Exiv2::ExifData& output_exif {some_output_metadata->exifData()};
> 
> With which enblend source?

Source directly from trunk. (changeset 1489:5f0e75fac301)

> I do nightly builds of master for ubuntu with
> g++ (Debian 4.9.2-10) 4.9.2
> and have not seen this error.
>
> The last successful build was 2016-10-10.

Hm, the last change to metadata.cc is from oct 18 2016. The relevant
line is already there since oct 11 (changeset 1481:dce1a6baf8bd)

> However, due to dependency problems, I can build for xenial and yakkety
> only.
> 
> 
> With kind regards
> 
> Stefan Peter
> 

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/7834927.WmeMAxzb2g%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

[hugin-ptx] Enblend: Compilation problem with gcc 4.8

[Kornel Benko]

Compiling enblend, I get this error:

/usr/src/enblend/enblend-code/src/metadata.cc: In function ‘void 
metadata::augment(Exiv2::Image*)’:
/usr/src/enblend/enblend-code/src/metadata.cc:92:71: error: invalid 
initialization of non-const reference of type ‘Exiv2::ExifData&’ from an rvalue 
of type ‘’
 Exiv2::ExifData& output_exif {some_output_metadata->exifData()};

Does it mean, I have a too old c++ compiler? (g++ (Ubuntu 
4.8.4-2ubuntu1~14.04.3) 4.8.4)

Compiling with version 6.2 is OK, but then I cannot link. Too many undefined 
references.

Even recompiling vigra, exiv2 and boost with g++6.2 does not help in the end.
(In this case not even hugin is created)

All tries are with clean build directories.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/6824433.MxY6X1fE52%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Re: Every year the same cramp? Set @api-max in hugin's plugin scripts.

[Kornel Benko]

Am Samstag, 17. September 2016 um 07:29:42, schrieb T. Modes 

> 
> Am Mittwoch, 14. September 2016 17:43:45 UTC+2 schrieb kornel:
> >
> > I only test/use woa,  it works. 
> >
> 
> Then it is reasonable to update for api-max for woa only. When the other 
> scripts are untested, they remain at the current state until someone test 
> them.
> 
> > Also why skipping several versions? 
> >
> > What do you mean? 
> >
> 
> Current version of default branch is 2016.3. But you updated @api-max to 
> 2017.1 (what when in 2017.0 a api breacking change appear?)
> 
> I updated woa.

Thanks.

> PS: Cite: This itches ...
> woa had an api-max from 2015.1. So this was not pressing. Nobody complained 
> in the last 2 years... (nothing with "every year")
> 

OK, OK. I changed it locally also at that time but did not complain :(

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/2987774.cdPWAeWuml%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Re: Every year the same cramp? Set @api-max in hugin's plugin scripts.

[Kornel Benko]

Am Dienstag, 13. September 2016 um 09:17:06, schrieb T. Modes 

> 
> Am Mittwoch, 10. August 2016 19:55:06 UTC+2 schrieb kornel:
> >
> > This itches ... 
> >
> > See attached, master branch. 
> >
> 
> All scripts tested?

I only test/use woa,  it works.

> Does all still work? Or only updated the api-max?

Only updated api-max.

> Also why skipping several versions?

What do you mean?

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/4510981.ggLLpLAVaj%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

[hugin-ptx] Every year the same cramp? Set @api-max in hugin's plugin scripts.

[Kornel Benko]

This itches ...

See attached, master branch.

Kornel

signature.asc
Description: This is a digitally signed message part.
diff -r 959e1e604745 src/hugin_script_interface/plugins/crop_cp.py
--- a/src/hugin_script_interface/plugins/crop_cp.py	Thu Jul 21 17:13:06 2016 +0200
+++ b/src/hugin_script_interface/plugins/crop_cp.py	Wed Aug 10 19:51:03 2016 +0200
@@ -24,7 +24,7 @@
 # @category Control Points
 # @name Crop Control Points
 # @api-min  2011.1
-# @api-max  2015.1
+# @api-max  2017.1
 
 # crop_cps will function as a hugin plugin and as a standalone
 # Python script. It can also serve as a template for a slightly
diff -r 959e1e604745 src/hugin_script_interface/plugins/shooting_pattern.py
--- a/src/hugin_script_interface/plugins/shooting_pattern.py	Thu Jul 21 17:13:06 2016 +0200
+++ b/src/hugin_script_interface/plugins/shooting_pattern.py	Wed Aug 10 19:51:03 2016 +0200
@@ -41,7 +41,7 @@
 # @name 6-1-1 Shooting Pattern
 # @description apply a shooting pattern (6 around, 1 up 1 down)
 # @sys win nix mac
-# @api-max 2016.1
+# @api-max 2017.1
 # @api-min 2011.1
 
 # the position routine will apply yaw, pitch to an image
diff -r 959e1e604745 src/hugin_script_interface/plugins/top_five.py
--- a/src/hugin_script_interface/plugins/top_five.py	Thu Jul 21 17:13:06 2016 +0200
+++ b/src/hugin_script_interface/plugins/top_five.py	Wed Aug 10 19:51:03 2016 +0200
@@ -5,7 +5,7 @@
 # @category Control Points
 # @name keep 5 CPs per image pair
 # @api-min  2011.1
-# @api-max  2016.1
+# @api-max  2017.1
 
 #top_five.py - keep the five best CPs for each image pair
 
diff -r 959e1e604745 src/hugin_script_interface/plugins/woa.py
--- a/src/hugin_script_interface/plugins/woa.py	Thu Jul 21 17:13:06 2016 +0200
+++ b/src/hugin_script_interface/plugins/woa.py	Wed Aug 10 19:51:03 2016 +0200
@@ -25,7 +25,7 @@
 # @category Control Points
 # @name Warped Overlap Analysis
 # @api-min  2014.0
-# @api-max  2015.1
+# @api-max  2017.1
 
 # note that if you want to read the script, it's written bottom-up, so the
 # higher-level routines are towards the end.

[hugin-ptx] Creating docs for enblend

[Kornel Benko]

We use doc/createdvi.cmake.in as template for a script to create some dvi 
documents.
For this to work we have to set the environment TEXINPUTS.
For linux, the setting is done at line createdvi.cmake.in:11
set(ENV{TEXINPUTS} ".:@HEVEA_LIB_DIR@:${INPUT_DIR}//:")
That works, but unfortunatelly 3 lines bellow we overwrite it with
set($ENV{TEXINPUTS} ${INPUT_DIR})

This is wrong (because of missing trailing '//:').
Commenting this line the docs are created.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/1941812.04HasussxW%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] enblend / cmake

[Kornel Benko]

Am Mittwoch, 18. November 2015 um 23:44:24, schrieb Wirz 
> Hi,
> 
> I'm currently having trouble to build the 'package' target of enblend
> when I use cmake (files enblend.1 and enfuse.1 not found).  (My system
> is Debian 8 with CMake 3.0.2.)
> 
> For me the attached patch solves the problem.  However, I don't know
> enough CMake to say for sure that this isn't my local problem only.
> 
> cheers, lukas
> 
This is clearly not intended. The install here should install a manual,
not an executable binary.

The problem seems to be, that you did not create the manuals.

Did you configure with '-DDOC=ON'?

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/5615228.bpx54szrHy%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Re: Mercurial access for commiting translation

[Kornel Benko]

Am Donnerstag, 22. Oktober 2015 um 10:39:31, schrieb T. Modes 

> 
> Am Donnerstag, 22. Oktober 2015 09:34:54 UTC+2 schrieb Dusan Kazik:
> >
> > Hello.
> > Please can you give me access to mercurial?
> > I want to help translate Hugin to slovak language.
> > My SourceForge account: "prescott66"   E-Mail: "presc...@gmail.com 
> > "
> >
> >
> > Please attach your po file to our bug tracker: 
> https://bugs.launchpad.net/hugin/
> If we know you better (when you contributed) you can get mercurial access. 
> But this is the first contact with you. So please use the tracker in the 
> case.
> 
> PS: The Slovak translation has currently only 1 untranslated string:
> 
> sk.po 
> 1528 translated messages, 1 fuzzy translation.
> 

And ATM also the last message should be translated.
Dušan, you can contact me also directly, I would be happy to have a 
co-translator.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/1472368.ErhxKPxgeu%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Anyone built Enblend-4.1.4?

[Kornel Benko]

Am Samstag, 3. Oktober 2015 um 00:49:47, schrieb T. Modes 
> Hi Kornel,
> 
> Am Freitag, 2. Oktober 2015 09:25:23 UTC+2 schrieb kornel:
> >
> > Am Freitag, 2. Oktober 2015 um 16:31:11, schrieb Terry Duell <
> > tdu...@iinet.net.au > 
> > > Hello All, 
> > > I'm having problems here attempting to build Enblend-4.1.4 on Fedora 22. 
> >
> > On ubuntu, I had to load one extra perl package 'libreadonly-perl'. 
> > This was with cmake build. 
> >
> 
> you mix things up. Terry is refering to 4.1.4.
> The readonly perl module is only needed for the default branch, but not for 
> 4.1.4
> 

Hm, yes. Sorry.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/2609644.120apvnqmo%40amd64.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Anyone built Enblend-4.1.4?

[Kornel Benko]

Am Freitag, 2. Oktober 2015 um 19:59:37, schrieb Terry Duell 

> Hello Kornel,
> 
> On Fri, 02 Oct 2015 17:25:06 +1000, Kornel Benko   
> wrote:
> 
> 
> >
> > On ubuntu, I had to load one extra perl package 'libreadonly-perl'.
> > This was with cmake build.
> >
> 
> Thanks.
> I'll install that...I think it's perl-Readonly on Fedora.
> 
> Cheers,


We need something like
 
https://github.com/rpavlik/cmake-modules/blob/master/FindPerlModules.cmake
for our documentations. It is not included in cmake modules yet.

Search for used modules in the doc directory gives
# egrep -w '^use' config2tex docstrings updated-on cleantex *.pm |  tr 
-d ';' | gawk '{print $2}'|sort|uniq
Carp
constant
English
File::Basename
File::stat
FindBin
Getopt::Long
IO::File
IO::Handle
lib
OpenFile
POSIX
Quote
Readonly
strict
TexAux
warnings
.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/5390633.dzMIdv8gQC%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Anyone built Enblend-4.1.4?

[Kornel Benko]

Am Freitag, 2. Oktober 2015 um 16:31:11, schrieb Terry Duell 

> Hello All,
> I'm having problems here attempting to build Enblend-4.1.4 on Fedora 22.
> I have tried the cmake and the autotools approach, neither work for me,  
> but I have probably have missed something.
> I get messages related to gnuplot, essentially saying that no terminal has  
> been set for gnuplot and no output will be produced. Man pages and info  
> files, enblend and enfuse binaries are produced but no docs.
> If I use autotools, it reports that a number of cmake manual options have  
> not been used, can't say I have seen that sort of message previously, but  
> domestic blindness epidemics often rage through here.
> 
> 
> Cheers,

On ubuntu, I had to load one extra perl package 'libreadonly-perl'.
This was with cmake build.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/2817743.6MP9PEmtOv%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] hugin-2014.0 make fails on opensuse 12.2 when linking to boost

[Kornel Benko]

Am Mittwoch, 5. August 2015 um 02:09:26, schrieb Roger 
> Hi, I'm trying to build hugin-2014.0 on opensuse 12.2 64 bit. The
> cmake completes without errors, but the make aborts when linking to
> boost:
> 
> ...
> Linking CXX executable celeste_standalone

[snip]

> ../hugin_base/libhuginbase.so.0.0: undefined reference to 
> `boost::signals::detail::named_slot_map::begin()'
> ../hugin_base/libhuginbase.so.0.0: undefined reference to 
> `boost::signals::trackable::~trackable()'

[snip]

> /usr/lib64/libboost_signals.so.1.49.0

[snip]

> Does hugin-2014 need further boost libraries?, or a more recent boost?

Probably more recent boost.

Here the installed boost is 1.54. Looking for the references in the libs reveals
# nm /usr/lib/x86_64-linux-gnu/libboost_signals.a | egrep ' T ' | egrep 
named_slot_map| grep begin
 T _ZN5boost7signals6detail14named_slot_map5beginEv

# nm /usr/lib/x86_64-linux-gnu/libboost_signals.a | egrep ' T ' | egrep 
trackable
0060 T 
_ZNK5boost7signals9trackable16signal_connectedENS0_10connectionERNS0_6detail12bound_objectE
 T _ZN5boost7signals9trackableD1Ev
 T _ZN5boost7signals9trackableD2Ev
0040 T 
_ZN5boost7signals9trackable19signal_disconnectedEPvS2_

> Roger
> 

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/1492751.iKxoBTHC8k%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Save Enfuse output files at a certain ( maybe better a predefined ) path

[Kornel Benko]

Am Donnerstag, 2. Juli 2015 um 10:45:03, schrieb Digicrea 

> Hello Kornel,
> I accidentally created this issue twice - but i will follow this one 
> further.
> My command line was just an example - i just wanted to say, whatever i try, 
> always the same result.
> As you wrote "Probably  "--output=c:\pictures\fuse\results\some_name.tif"" 
> yes, i tried that, but that does not work.
> Enfuse always saves in the same place : the folder where my enfuse and my 
> batch file is
> and the output file name is also always the same : a.tif
> So, i have different batch files, with different commands for Enfuse -> 
> they all work fine, but i cannot redirect the place of output, nor the 
> filename.
> I hope its more clear now.
> Regards
> Marc.
> 

Hm, it works here. But I must confess, I don't have windows OS.
Looks like the offending char may be ':', so I would try to
not use the drive spec.
If that works, this is an error in enfuse (and probably enblend).

Kornel

> Op donderdag 2 juli 2015 17:55:52 UTC+2 schreef kornel:
> >
> > Am Donnerstag, 2. Juli 2015 um 08:16:38, schrieb Digicrea <
> > pentaxia...@gmail.com > 
> > > Hello, 
> > > I have placed this first on sourceforge Enblend, but i was send here for 
> > my 
> > > problem. 
> > > So, I have following problem : 
> > > I want to save the image output from enfuse at a certain path. 
> > > Its no problem to tell Enfuse where to find the input images, but 
> > pointing 
> > > the output to somewhere fails. 
> > > The enfuse help file tells me to use -o or --output, but that didnt work 
> > in 
> > > any way. 
> > > I tried ( simple example ) 
> > > enfuse c:\pictures\fuse*.tif enfuse_additional_parameters= --wExposure=1 
> > > --wSaturation=0.1 --wContrast=1 --levels=auto 
> > > --output=c:\pictures\fuse\results\*.tif 
> >
> >
> > What do you mean with "--output=c:\pictures\fuse\results\*.tif"? 
> > Probably  "--output=c:\pictures\fuse\results\some_name.tif" 
> >
> > > So, in this example, i want to save the output in 
> > c:\pictures\fuse\results\ 
> > > Can anyone tell me what to use to direct the output ? 
> > > 
> > > some extra information : 
> > > I run the above command line from a batch file in windows seven. 
> > > the batch file ( and i have more then one ) all work fine - i get an 
> > > output, but always in the same folder as Enfuse, and the output is 
> > always 
> > > a.tif - whatever i try 
> > > Many thanks ! 
> > > Regards 
> > > Marc 
> > > 
> >
> > Kornel
> 
> 

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/4354438.Llxfn6EuXJ%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Save Enfuse output files at a certain ( maybe better a predefined ) path

[Kornel Benko]

Am Donnerstag, 2. Juli 2015 um 08:16:38, schrieb Digicrea 

> Hello,
> I have placed this first on sourceforge Enblend, but i was send here for my 
> problem.
> So, I have following problem :
> I want to save the image output from enfuse at a certain path.
> Its no problem to tell Enfuse where to find the input images, but pointing 
> the output to somewhere fails.
> The enfuse help file tells me to use -o or --output, but that didnt work in 
> any way.
> I tried ( simple example )
> enfuse c:\pictures\fuse*.tif enfuse_additional_parameters= --wExposure=1 
> --wSaturation=0.1 --wContrast=1 --levels=auto 
> --output=c:\pictures\fuse\results\*.tif


What do you mean with "--output=c:\pictures\fuse\results\*.tif"?
Probably  "--output=c:\pictures\fuse\results\some_name.tif"

> So, in this example, i want to save the output in c:\pictures\fuse\results\ 
> Can anyone tell me what to use to direct the output ?
> 
> some extra information :
> I run the above command line from a batch file in windows seven.
> the batch file ( and i have more then one ) all work fine - i get an 
> output, but always in the same folder as Enfuse, and the output is always 
> a.tif - whatever i try
> Many thanks !
> Regards
> Marc
> 

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/1579474.4fGbjFSGqG%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Re: Nona GPU not working anymore

[Kornel Benko]

Am Donnerstag, 28. Mai 2015 um 10:21:55, schrieb T. Modes 
> 
> Am Donnerstag, 28. Mai 2015 15:55:59 UTC+2 schrieb kornel:
> >
> >
> > Ubuntu 14.04, 64 bit, default branch. 
> > Graphic card: NVIDIA, Geforce GTX 750, OpenGL/ES-Version 4.5.0 NVIDIA 
> > 346.47 
> >
> > The last versions of nona seem to be not working anymore. 
> > There is no crash and no error message. Nona simply hangs. 
> >
> > Using without '-g' parameter works. 
> > I suspect the 
> > changeset:   6978:0beb67edf587 
> > parent:  6976:e4c461b28afc 
> >
> 
> Suspect or tested that not another changeset is the culprit?
> (I tested this code with 2 different graphic cards on my side and also 
> Terry did a test on Linux and on all systems this changeset worked on all 
> our tested systems.)
> 
> The order for testing would be:
> 0beb67edf587
> db1a6c64cf17
> a6ad9e9ec0d2
> 35c1d9d96f3d5
>  
> until you get the hang.
> 
> When it hangs, does it print something or remain the console empty?
> When the console shows something, than the debug output of "nona -g -d .." 
> would be helpful and also the output of glewinfo.
> 
> It was not nice with the popup window, but at least it worked. 
> >
> 
> With this attitude we can leave the code as it is and don't need to do 
> anything more.

Sure.

> There are more reports about bugs/crashes in nona-gpu. There are less 
> reports about nona-gpu working.
> 

I start with current nona:
#nona -g -d -o xa dsc_4210-1.pto
nona: using graphics card: NVIDIA Corporation GeForce GTX 750 
Ti/PCIe/SSE2
destStart=[62, 1141]
destEnd=[4878, 4441]
destSize=[(4816, 3300)]
srcSize=[(4928, 3264)]
srcBuffer=0x7f82a18c0010
srcAlphaBuffer=0
destBuffer=0x7f829eb47010
destAlphaBuffer=0x7f829dc1e010
destGLInternalFormat=GL_RGBA8
destGLFormat=GL_RGB
destGLType=GL_UNSIGNED_BYTE
srcGLInternalFormat=GL_RGBA8
srcGLFormat=GL_RGB
srcGLType=GL_UNSIGNED_BYTE
srcAlphaGLType=GL_BYTE
destAlphaGLType=GL_UNSIGNED_BYTE

warparound=0
needsAtanWorkaround=0
maxTextureSize=16384
Here it hangs. Ctrl-C stops the process.

Test with  0beb67edf587: works
db1a6c64cf17: works
a6ad9e9ec0d2: hang

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/1685270.gQCzMPhBhY%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

[hugin-ptx] Nona GPU not working anymore

[Kornel Benko]

Ubuntu 14.04, 64 bit, default branch.
Graphic card: NVIDIA, Geforce GTX 750, OpenGL/ES-Version 4.5.0 NVIDIA 346.47

The last versions of nona seem to be not working anymore.
There is no crash and no error message. Nona simply hangs.

Using without '-g' parameter works.
I suspect the
changeset:   6978:0beb67edf587
parent:  6976:e4c461b28afc
user:tmodes
date:Wed May 27 17:48:45 2015 +0200
files:   CMakeLists.txt CMakeModules/win_bundle.cmake README 
src/hugin1/hugin/CMakeLists.txt src/hugin1/hugin/GLRenderer.cpp
src/hugin_base/CMakeLists.txt src/hugin_base/hugin_utils/utils.cpp 
src/hugin_base/vigra_ext/ImageTransformsGPU.cpp  src/tools/CMakeLists.txt
description:
Use own code for initialization of GLContext (Windows and Linux)

This should prevent a popup window, as opened by freeglut.
This removes the dependencies on glut/freeglut.
On MacOS there is still glut/freeglut used.

It was not nice with the popup window, but at least it worked.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/2224964.HmbnnpHVdz%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Re: Hugin 2015.0 beta 1

[Kornel Benko]

Am Montag, 27. April 2015 um 21:25:50, schrieb smib 
> > at line 59 (before IF(${VIGRA_VERSION} VERSION_EQUAL …) and report the 
> > output of CMake.
> >
> > Thomas
> >
> 
> Hi Thomas
> 
> I used cmake 3.0.0 but have now updated to 3.2.2. 
>  configVersion.hxx includes the correct define (ie ver 1.10.0).
> 
> Adding the extra line to findVIGRA.cmake as requested gives the following 
> output (note I also simplified some of the directory names and renamed the 
> debug library name) :
> 
> Found OPENEXR: 
> 
> Found VIGRA: 
> optimized;E:/Photographic/Huginbase/vigra/vigraimpex.lib;debug;E:/Photographic/Huginbase/vigra/lib/vigraimpexd.lib
> 
> CMake Error at CMakeModules/FindVIGRA.cmake:57 (FILE):
> file STRINGS given unknown argument "("
> Call Stack (most recent call first):
> CMakeLists.txt:230 (FIND_PACKAGE)
> 
> VIGRA version: ##
> 

I think, you must have removed line 58.
The lines should be:
...
STRING(REGEX REPLACE ".*#define +VIGRA_VERSION +\"([.0-9]+).*" "\\1" 
VIGRA_VERSION "${VIGRA_VERSION_HXX}")
MESSAGE(STATUS "VIGRA version: #${VIGRA_VERSION}#")
IF(${VIGRA_VERSION} VERSION_EQUAL VIGRA_FIND_VERSION OR 
${VIGRA_VERSION} VERSION_GREATER VIGRA_FIND_VERSION)
...

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/1581889.7jtejkX95H%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

[hugin-ptx] WOA not working -- again

[Kornel Benko]

First of all, I am a fan of Warped Overload Analysis.
Unfortunately calling it as plugin I get only a dialog weth the exit number 
'-21', which I cannot interpret.
Probably again some change in the API :( . I am using ubuntu 12.04, and from 
the README_woa.txt
it should work for ubuntu 11.4.

The command line script plugins/woa.py works though, but ends with exit != 0, 
so that it cannot
be directly used as a control point detector.

For now I created a small wrapper in perl and use woa that way. For me it's OK.

Can someone confirm non-working woa plugin?

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/1816948.EHkdQTGCBG%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Photometric Optimization Doesn't Function in 2014.0.0

[Kornel Benko]

Am Dienstag, 24. März 2015 um 14:39:18, schrieb T. Modes 
> 
> Am Dienstag, 24. März 2015 22:20:53 UTC+1 schrieb kornel:
> >
> > The error now is: 
> >
> 
> There is still USE_BOOST active. Fixed also this bug.
> With this bug there I may ask how you could test the boost variant 
> (USE_BOOST=TRUE) as written your mails.
> 

Yes, and somehow my build tree was tainted. Recompiled with fresh build, it 
looks good now.
Thanks,
Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/1626949.qUVZXZvCSY%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Photometric Optimization Doesn't Function in 2014.0.0

[Kornel Benko]

Am Dienstag, 24. März 2015 um 22:12:52, schrieb Kornel Benko 

> Am Dienstag, 24. März 2015 um 13:55:17, schrieb T. Modes 
> > Hi Kornel,
> > 
> > Am Dienstag, 24. März 2015 21:10:03 UTC+1 schrieb kornel:
> > >
> > > > Have you tried with USE_BOOST? (Checked hugin_config.h?) 
> > >
> > > Yes, see some lines above where I mentioned it. 
> > >
> > > > Could you provide the test project? I don't see the issue with my 
> > > projects. 
> > > > 
> > > > Thomas 
> > >
> > > Yes, I can. But only outside this list, the pictures are too big. 
> > >
> > 
> > I got the images, thanks. I committed a fix. It should be work again.
> 
> It changed. It is not much better though.
> 
> > But I don't know why the boost option does not work, because in this case 
> > the effective code did not change in the mentioned changeset.
> 
> 
> > Thomas
> > 
> > PS: One comment to your project. Using a different lens for each image 
> > results in many variables to optimize. So each image has its own vignetting 
> > parameters and its own response curve. This is very fragile for optimize. 
> > It's better to use only one lens. Then all images share the same vignetting 
> > parameters and the same response curve.
> 
> (Sometimes, if the camera itself corrects images, it is better to use 
> different lenses.)
> 
> Even if using only 1 lens, the optimized panorama is also with this new 
> change not good.
> 
> I always have to deselect vignetting optimization to get some reasonable 
> output.
> 
>   Kornel

Sorry, I overseen, that the compilation goes wrong and therefore use old hugin.

The error now is:
cd /usr/BUILD/BuildHugin_hg/src/hugin1/hugin && /usr/bin/c++   -DHUGIN_HSI 
-DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ -pthread -O3 -DNDEBUG 
-I/usr/BUILD/BuildHugin_hg/src -I/usr/src/hugin/hugin_hg/src/hugin_base 
-I/usr/src/hugin/hugin_hg/src/celeste -I/usr/BUILD/BuildHugin_hg/src/celeste 
-I/usr/src/hugin/hugin_hg/src -I/usr/include/x86_64-linux-gnu 
-I/usr/include/OpenEXR -I/usr/local/include -I/usr/include/python2.7 -isystem 
/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0 -isystem 
/usr/include/wx-3.0 -I/usr/src/hugin/hugin_hg/src/hugin1-fopenmp -o 
CMakeFiles/hugin.dir/TextureManager.cpp.o -c 
/usr/src/hugin/hugin_hg/src/hugin1/hugin/TextureManager.cpp

In file included from /usr/include/exiv2/metadatum.hpp:39:0,
 from /usr/include/exiv2/exif.hpp:34,
 from /usr/include/exiv2/bmpimage.hpp:34,
 from /usr/include/exiv2/exiv2.hpp:35,
 from 
/usr/src/hugin/hugin_hg/src/hugin1/hugin/TextureManager.cpp:67:
/usr/include/exiv2/value.hpp:984:25: note: attribute for ‘struct 
Exiv2::DateValue::Date’ must follow the ‘struct’ keyword
 EXIV2API struct Date
 ^
/usr/src/hugin/hugin_hg/src/hugin1/hugin/TextureManager.cpp: In member function 
‘void TextureManager::CheckUpdate()’:
/usr/src/hugin/hugin_hg/src/hugin1/hugin/TextureManager.cpp:431:31: error: 
‘make_shared’ is not a member of ‘sharedPtrNamespace’
   
sharedPtrNamespace::make_shared(view_state, tex_width_p, 
tex_height_p)
   ^
/usr/src/hugin/hugin_hg/src/hugin1/hugin/TextureManager.cpp:428:34: error: 
expected primary-expression before ‘(’ token
  (TextureKey(img_p, &photometric_correct),
  ^
/usr/src/hugin/hugin_hg/src/hugin1/hugin/TextureManager.cpp:431:31: error: 
‘make_shared’ is not a member of ‘sharedPtrNamespace’
   
sharedPtrNamespace::make_shared(view_state, tex_width_p, 
tex_height_p)
   ^
/usr/src/hugin/hugin_hg/src/hugin1/hugin/TextureManager.cpp:431:74: error: 
expected primary-expression before ‘>’ token
   
sharedPtrNamespace::make_shared(view_state, tex_width_p, 
tex_height_p)
  ^

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/237875255.NvlIS6lDKm%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Photometric Optimization Doesn't Function in 2014.0.0

[Kornel Benko]

Am Dienstag, 24. März 2015 um 13:55:17, schrieb T. Modes 
> Hi Kornel,
> 
> Am Dienstag, 24. März 2015 21:10:03 UTC+1 schrieb kornel:
> >
> > > Have you tried with USE_BOOST? (Checked hugin_config.h?) 
> >
> > Yes, see some lines above where I mentioned it. 
> >
> > > Could you provide the test project? I don't see the issue with my 
> > projects. 
> > > 
> > > Thomas 
> >
> > Yes, I can. But only outside this list, the pictures are too big. 
> >
> 
> I got the images, thanks. I committed a fix. It should be work again.

It changed. It is not much better though.

> But I don't know why the boost option does not work, because in this case 
> the effective code did not change in the mentioned changeset.


> Thomas
> 
> PS: One comment to your project. Using a different lens for each image 
> results in many variables to optimize. So each image has its own vignetting 
> parameters and its own response curve. This is very fragile for optimize. 
> It's better to use only one lens. Then all images share the same vignetting 
> parameters and the same response curve.

(Sometimes, if the camera itself corrects images, it is better to use different 
lenses.)

Even if using only 1 lens, the optimized panorama is also with this new change 
not good.

I always have to deselect vignetting optimization to get some reasonable output.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/2004975.oUnDYC4U2R%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Photometric Optimization Doesn't Function in 2014.0.0

[Kornel Benko]

Am Dienstag, 24. März 2015 um 12:19:33, schrieb T. Modes 
> 
> Am Dienstag, 24. März 2015 20:06:39 UTC+1 schrieb kornel:
> >
> > > No need for hg blame. Try 
> > > # hg log 
> > > and search for 6818 
> > > ==> tmodes: Use C++11  when possible 
> > > 
> >
> 
> That was not mentioned in the initial posts. They referred to 2013.0 and 
> 2014.0 and not to current trunk.
> See please be more precise and not so diffuse comments.

Yes, sorry. There were private mails with Terry.

> And before someone asks: I saw the diffs depending on '#ifdef HAVE_CXX11', 
> > and 
> > that it should use boost as before, if using -DUSE_BOOST=ON in 
> > configuration. 
> >
> 
> from CMakeLists.txt 
> 
> IF(USE_BOOST)
>   UNSET(USE_CXX11_THREAD)
>   UNSET(HAVE_CXX11)
> ..
> 
> 
> > Version 6817 is OK, 6818 is not OK. 
> >
> 
> Which compiler?

gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) 

> Have you tried with USE_BOOST? (Checked hugin_config.h?)

Yes, see some lines above where I mentioned it.

> Could you provide the test project? I don't see the issue with my projects.
> 
> Thomas

Yes, I can. But only outside this list, the pictures are too big.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/36598832.oFUNAOOjCT%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Photometric Optimization Doesn't Function in 2014.0.0

[Kornel Benko]

Am Dienstag, 24. März 2015 um 20:00:24, schrieb Kornel Benko 

> Am Dienstag, 24. März 2015 um 11:07:41, schrieb T. Modes 
> > 
> > Am Montag, 23. März 2015 23:09:31 UTC+1 schrieb Tduell:
> > >
> > > > 
> > > > Terry, I have a small (5 pictures) panorama, for which you could try 
> > > > the 
> > >   
> > > > photometric optimization. 
> > > > The outcome is .. terrifying .. 
> > > > 
> > >
> > > For the record, I also get a 'terrifying' result from photometric   
> > > optimisation of Kornel's project with my Fedora build of hugin-2014.1.0.  
> > >  
> > > The project can be recovered by resetting camera response. 
> > > I also rebuilt hugin-2013.0.0 (from a Fedora src.rpm) and this version   
> > > gets the photometric optimisation of Kornel's project correct without any 
> > >   
> > > intervention. 
> > >
> > 
> > Strange. There is - as far as I remember - no significant change to the 
> > photometric optimizer code between 2013.0 and 2014.0.
> > So I have no idea what's going wrong, and I have not observed the bug 
> > myself.
> > 
> > So you have a test project which fails reproducible and 2 changesets - one 
> > working and one not.
> > This is a good starting point for hg blame to find the culprit.
> 
> No need for hg blame. Try
>   # hg log
> and search for 6818
>   ==> tmodes: Use C++11  when possible
> 
> To see the diff:
>   # hg diff -c 6818
> 
> > Thomas
> > 

And before someone asks: I saw the diffs depending on '#ifdef HAVE_CXX11', and
that it should use boost as before, if using -DUSE_BOOST=ON in configuration.

But, it does not help.

Version 6817 is OK, 6818 is not OK.

Kornel
 

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/2675952.TdrlKcIs11%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Photometric Optimization Doesn't Function in 2014.0.0

[Kornel Benko]

Am Dienstag, 24. März 2015 um 11:07:41, schrieb T. Modes 
> 
> Am Montag, 23. März 2015 23:09:31 UTC+1 schrieb Tduell:
> >
> > > 
> > > Terry, I have a small (5 pictures) panorama, for which you could try the 
> >   
> > > photometric optimization. 
> > > The outcome is .. terrifying .. 
> > > 
> >
> > For the record, I also get a 'terrifying' result from photometric   
> > optimisation of Kornel's project with my Fedora build of hugin-2014.1.0.   
> > The project can be recovered by resetting camera response. 
> > I also rebuilt hugin-2013.0.0 (from a Fedora src.rpm) and this version   
> > gets the photometric optimisation of Kornel's project correct without any 
> >   
> > intervention. 
> >
> 
> Strange. There is - as far as I remember - no significant change to the 
> photometric optimizer code between 2013.0 and 2014.0.
> So I have no idea what's going wrong, and I have not observed the bug 
> myself.
> 
> So you have a test project which fails reproducible and 2 changesets - one 
> working and one not.
> This is a good starting point for hg blame to find the culprit.

No need for hg blame. Try
# hg log
and search for 6818
==> tmodes: Use C++11  when possible

To see the diff:
# hg diff -c 6818

> Thomas
> 
Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/1589052.a3WqYzhr6e%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Photometric Optimization Doesn't Function in 2014.0.0

[Kornel Benko]

Am Montag, 23. März 2015 um 08:45:08, schrieb Terry Duell 
> Hello Kornel,
> 
> On Mon, 23 Mar 2015 05:47:28 +1100, Kornel Benko   
> wrote:
> 
> > Am Sonntag, 22. März 2015 um 08:50:58, schrieb Terry Duell  
> > 
> 
> [snip]
> 
> >
> >> It all appears to be working as it should here with a build of the  
> >> current repo source on Linux.
> >>
> 
> >
> > Terry, I have a small (5 pictures) panorama, for which you could try the  
> > photometric optimization.
> > The outcome is .. terrifying ..
> >
> 
> OK. Put the images and the .pto on Dropbox or similar, or directly email a  
> zip, and I'll test.
> Second thoughts, Dropbox would also allow others to test which might be  
> useful if we have varying results from different builds of hugin.
> 
> Cheers,


Sent privately.

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/2393682.C6mjuYHMZ8%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Photometric Optimization Doesn't Function in 2014.0.0

[Kornel Benko]

Am Sonntag, 22. März 2015 um 08:50:58, schrieb Terry Duell 
> Hello Alex,
> 
> On Sun, 22 Mar 2015 05:13:16 +1100, Alex Blanck  wrote:
> 
> > I'm having an odd problem in the precompiled version of Hugin for OSX
> > (version 2014.0.0)

I too in the actual version.

> > After aligning the panorama from the photos tab, everything looks good in
> > the preview except for obvious vingetting at the borders between frames.  
> > I then attempt to optimize the photometric parameters by choosing low  
> > dynamic range and then clicking "Compute" in the photos tab. The  
> > calculation
> > appears to run (perhaps a bit too quickly) and then I get a dialog  
> > telling me that photometric optimization is finished. However, after  
> > clicking yes
> > there is no difference in the previews.

I cannot see this. Instead the 'optimized' panorama is crappy.

> > Additionally, if I change the photometric dropdown to "custom parameters"
> > to reveal the exposure tab, I can see that none of the vingetting or
> > exposure values have been changed (exposure is still based off of exif  
> > and vingetting is 0).

Seen it too, some days ago. But not with current hugin.

> > Has anyone else had a similar experience? I downgraded to the 2013  
> > version and the photometric optimization seemed to work correctly.
> >

That is my impression too.

> It all appears to be working as it should here with a build of the current  
> repo source on Linux.
> 
> Cheers,

Terry, I have a small (5 pictures) panorama, for which you could try the 
photometric optimization.
The outcome is .. terrifying ..

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/1800578.XyFI6O5PLg%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Re: Localisation with debian provided wx3.0 packages

[Kornel Benko]

Am Freitag, 20. März 2015 um 09:08:02, schrieb T. Modes 
> Hi Kornel,
> 
> Am Donnerstag, 19. März 2015 20:47:07 UTC+1 schrieb kornel:
> >
> > > Have you checked this variable? 
> > > What value is set to INSTALL_LOCALE_DIR in hugin_config.h? 
> >
> > It was empty. And you are right. If set, it searches there from start on 
> > now. 
> >
> > So, why don't we set this variable automatically? 
> >
> 
> I don't know. The line in the source code is there for a long time. But it 
> seems it was not needed for wxWidgets 2.8. So it makes problems with 
> wxWidgets 3.x.
>  
> 
> > Like: 
> > set(INSTALL_LOCALE_DIR ${CMAKE_INSTALL_PREFIX}/${LOCALEDIR}) 
> > before calling 
> > configure_file(src/hugin_config.h.in.cmake 
> > ${CMAKE_BINARY_DIR}/src/hugin_config.h) 
> >
> > I committed that change. Hopefully that fixes the issue and does not 
> introduce other problems. Please test.

Already tested. Works for me (with both wx 2.8 and 3.0).
Not needed on wx2.8, but also not disturbing.

> Thanks
> 
> Thomas

Thanks

Kornel



-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/2202258.EYgXkPX3Gv%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Re: Localisation with debian provided wx3.0 packages

[Kornel Benko]

Am Donnerstag, 19. März 2015 um 11:42:55, schrieb T. Modes 
> 
> Am Donnerstag, 19. März 2015 19:19:25 UTC+1 schrieb kornel:
> >
> > > Otherwise have a look at the variable INSTALL_LOCALE_DIR. 
> > > It is used by the code like 
> > >locale.AddCatalogLookupPathPrefix(wxT(INSTALL_LOCALE_DIR)); 
> > > but not correctly set in CMake. 
> > > The variable is defined in hugin_config.h.in.cmake 
> > > #define INSTALL_LOCALE_DIR "${INSTALL_LOCALE_DIR}" 
> > > 
> > > Maybe playing with this variable can help. 
> >
> > Unfortunately this seems not the problem, Hugin _correctly_ places 
> > 'hugin.mo'.

As expected, no problems with wx2.8.

> > It is only, that wx3.0 does search in 
> > 1.) /usr/share/locale 
> > 2.) /usr/local/share/hugin, but this is wrong. 
> > It should be /usr/local/share/locale. 
> > 
> Have you checked this variable? 
> What value is set to INSTALL_LOCALE_DIR in hugin_config.h?

It was empty. And you are right. If set, it searches there from start on now.

So, why don't we set this variable automatically?
Like:
set(INSTALL_LOCALE_DIR ${CMAKE_INSTALL_PREFIX}/${LOCALEDIR})
before calling
configure_file(src/hugin_config.h.in.cmake 
${CMAKE_BINARY_DIR}/src/hugin_config.h)


> Thomas

Kornel
> 

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/3489454.IeCIb24O4h%40amd64.
For more options, visit https://groups.google.com/d/optout.


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

Re: [hugin-ptx] Re: Localisation with debian provided wx3.0 packages

[Kornel Benko]

Am Donnerstag, 19. März 2015 um 10:19:04, schrieb T. Modes 
> Hi Kornel,
> 
> Am Donnerstag, 19. März 2015 16:08:25 UTC+1 schrieb kornel:
> >
> > Easy to change the CMakeLists.txt 
> >
> 
> Does it also works with wx2.8 after applying your patch?

I expect, it will not work with the patch. (I was not proposing to adopt the 
patch)

> Otherwise have a look at the variable INSTALL_LOCALE_DIR.
> It is used by the code like
>locale.AddCatalogLookupPathPrefix(wxT(INSTALL_LOCALE_DIR));
> but not correctly set in CMake.
> The variable is defined in hugin_config.h.in.cmake
> #define INSTALL_LOCALE_DIR "${INSTALL_LOCALE_DIR}"
> 
> Maybe playing with this variable can help.

Unfortunately this seems not the problem, Hugin _correctly_ places 'hugin.mo'.
It is only, that wx3.0 does search in
1.) /usr/share/locale
2.) /usr/local/share/hugin, but this is wrong.
It should be /usr/local/share/locale.

In the mean time I am installing into /usr (instead of /usr/local). This works 
without changes in source.

> Thomas

Kornel

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/2036322.sLOakhH5Q7%40amd64.
For more options, visit https://groups.google.com/d/optout.


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