Hugin 2018.0 rc2 released

[T. Modes]

Hi all,

because of a found bug we are releasing release candidate 2 of Hugin 2018.0.

Source tarball can be downloaded
at sourceforge: https://sourceforge.net/projects/hugin/files/hugin/hugin-2018.0/hugin-2018.0rc2.tar.bz2/download
or at launchpad: https://launchpad.net/hugin/2018.0/2018.0rc2/+download/hugin-2018.0rc2.tar.bz2

Verify its checksums:
md5:91cb2c31409c9ef02fc86e17ec2fa068  hugin-2018.0rc2.tar.bz2

sha1:

bf62cc597015f8fcbddb52590fe3f8eac497449f  hugin-2018.0rc2.tar.bz2

This is a source code release.
Users communities produce executables for their respective platforms. Please announce them here.

(The rc2 corresponds to changeset 5abfb4de7961 in our repository, which is also tagged as 2018.0rc2).

Changes since 2018.0 rc1

* Fixes crash when closing Hugin with open help window (Mac).

* Check window help position before opening (to prevent help window opening outside of desktop area).

* Fixes a warning in lens_calibration_gui

Changes since 2017.0

The version 2018.0 is mainly a bug fix release and introduce some minor new features.
* Several improvements for optimizer tabs:
   **mark deselected images
   ** allow changing optimizer variables for all selected images at once
   ** option to ignore line cp

* hugin_stacker: New tool to stack overlapping images with several averaging modes (e.g. mean, median).

* Hugin: Added option to disable auto-rotation of images in control point and mask editor.
* Nona, verdandi and hugin_stacker can now write BigTIFF images (for files >4 GB). The output of BigTIFF has to manually activated on the command line. It is not set automatically. (For a complete panorama in BigTIFF you will probably also need enblend/enfuse from repository. The last released version of enblend does not yet support writing BigTIFF files.)

* Added expression parser to GUI: This allows to manipulate several image variables at once. (This is the same as running pto_var --set from the command line.) This can be used e.g. to prealign the images in a given setup and then run cpfind --prealigned to search control points only in overlapping images.
* Add user-defined assistant and expose it in the GUI. It allows to set up different assistant strategies without the need to recompiling. Provide also some examples (scanned images, multi-row panoramas with orphaned images, single-shot panorama cameras).

Upgrading from previous versions of Hugin should be seamless. If you do have problems with old settings, these can be reset in the Preferences window by clicking 'Load defaults'.

The release notes can be found at http://hugin.sourceforge.net/releases/2018.0.0/en.shtml

Please test and report bug/issues to mailing list or bug tracker https://bugs.launchpad.net/hugin

Know issue

Hugin does not run native on Wayland because of a bug in the underlying wxWidgets library.

The source code contains a workaround which forces the usage of the XWayland emulation layer. This workaround has be activated during compiling by adding -DUSE_GDKBACKEND_X11=on to the CMake command line.

[T. Modes]

For Windows user: an installer package for Windows 64 bit can be downloaded from
https://sourceforge.net/projects/hugin/files/hugin/hugin-2018.0/Hugin-2018.0rc2-win64.msi/download

MD5 checksum is
bef26239f194bd2225e7e0865bbfe47b  Hugin-2018.0rc2-win64.msi

[Niklas Mischkulnig]

The executables for macOS (10.9 and newer) are available for download from sourceforge:

https://sourceforge.net/projects/hugin/files/hugin/hugin-2018.0/Hugin-2018.0.0-rc2.dmg/download

sha1: 1410138b91b25c9a6290536eaef330a07a912099  Hugin-2018.0.0-rc2.dmg

[Bruno Postle]

On Sat 27-Jan-2018 at 00:03 -0800, Thomas Modes wrote:
>
>because of a found bug we are releasing release candidate 2 of Hugin
>2018.0.

As usual, Fedora packages can be found in 'copr': https://copr.fedorainfracloud.org/coprs/bpostle/panorama/

--
Bruno

[Greg 'groggy' Lehey]

On Saturday, 27 January 2018 at 0:03:44 -0800, T. Modes wrote:
> Hi all,
>
> because of a found bug we are releasing release candidate 2 of Hugin
> 2018.0.

The bug with "in-source builds are not allowed" is still there. Apart
from that it builds under FreeBSD. It would be nice to finally get
this fixed.

Greg
--
Sent from my desktop computer.
Finger groo...@gmail.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

[T. Modes]

Am Sonntag, 28. Januar 2018 00:32:28 UTC+1 schrieb Groogle:

On Saturday, 27 January 2018 at  0:03:44 -0800, T. Modes wrote:
> Hi all,
>
> because of a found bug we are releasing release candidate 2 of Hugin
> 2018.0.

The bug with "in-source builds are not allowed" is still there.  

This is not a bug (and you are the only one constantly complaining).
It is a design decision and will not change.

You can build in the source folder, but not in the root folder. Simply create a folder where all the generated files are stored.

In the source dir
mkdir build
cd build
cmake ..
(as described in INSTALL_cmake)

[Greg 'groggy' Lehey]

On Sunday, 28 January 2018 at 1:38:08 -0800, T. Modes wrote:
> Am Sonntag, 28. Januar 2018 00:32:28 UTC+1 schrieb Groogle:
>>
>> On Saturday, 27 January 2018 at 0:03:44 -0800, T. Modes wrote:
>>> Hi all,
>>>
>>> because of a found bug we are releasing release candidate 2 of Hugin
>>> 2018.0.
>>
>> The bug with "in-source builds are not allowed" is still there.
>
> This is not a bug (and you are the only one constantly complaining).

One is enough.

> It is a design decision and will not change.

I disagree. At the very least, it is a conscious decision to make
Hugin less portable. From memory it was because one part of the
documentation builds differently from the rest, and if it is built in
the source directory, it will fail the second time. The rest of the
documentation builds correctly, so there's clearly a solution. But
you decided "don't do that, then", rather than fix the bug. Before
this, things worked with no problem.

> You can build in the source folder, but not in the root
> folder. Simply create a folder where all the generated files are
> stored.

I thought you might mean directory when you say folder, but clearly
we're not talking about the root directory here.

> In the source dir
> mkdir build
> cd build
> cmake ..
> (as described in INSTALL_cmake)

This is not the way the FreeBSD Ports Collection works. Summarizing
(this is not what you actually do),

cd /usr/ports/graphics/hugin
mkdir -p work/hugin-2018.0.0
cd work/hugin-2018.0.0
tar xvf /usr/ports/distfiles/hugin-2018.0rc2.tar.bz2
cmake
make

This is a design decision. It works for 25,000 ports, and it will not
change for one package that doesn't want to build in its own tree.

I can work around this bug by patching the files. From
/usr/ports/graphics/hugin/files/patch-CMakeLists.txt:


--- CMakeLists.txt~ 2016-01-24 20:16:54.000000000 +1100
+++ CMakeLists.txt 2016-02-29 14:04:08.376365000 +1100
@@ -2,11 +2,6 @@
# require at least cmake 2.8
cmake_minimum_required(VERSION 2.8.12 FATAL_ERROR )

-# prevent in-tree building
-if("${CMAKE_SOURCE_DIR}" STREQUAL "${CMAKE_BINARY_DIR}")
- message(FATAL_ERROR "In-source builds are not allowed.")
-endif()
-
if(COMMAND cmake_policy)
cmake_policy(SET CMP0003 NEW)
endif(COMMAND cmake_policy)

But that's tacky. There are two obvious ways to handle the problem:

1 (preferred): Fix the build issue. If you have lost track of it, I
can dig it out.
2 (tacky): Put a conditional round the commands in CMakeLists.txt to
not make the check when built with FreeBSD.

[T. Modes]

Am Montag, 29. Januar 2018 02:15:22 UTC+1 schrieb Groogle:

It works for 25,000 ports, and it will not
change for one package that doesn't want to build in its own tree.

It works as out of source build for more than 200,000 packages (Ubuntu, Fedora,  Debian, ...).
And there at least 2 more bigger packages I know (e.g. OpenCV, LLVM) which prohibit in source build the same way as Hugin.