Problem building Enblend trunk

[Terry Duell]

Hello All,
I have just tried to do a test build of the current default Enblend 4.3, and have run
into a cmake error.

The error message is a follows...

-- Found Exiv2 release >= 0.12
-- Found Exiv2: /usr/lib64/libexiv2.so
-- Performing Test EXIV2_COMPILES_FLAG
-- Performing Test EXIV2_COMPILES_FLAG - Failed
CMake Error at CMakeModules/FindEXIV2.cmake:145 (MESSAGE):
Found exiv2 library, but this library is not recent enough to compile
enblend/enfuse.
Call Stack (most recent call first):
CMakeLists.txt:271 (FIND_PACKAGE)

I'm attempting to build on Fedora 35, using rpmbuild, and following the process I've
used for many moons, although it must be said that I don't do this as often as I used
to, may have missed something.
Anyone else have an issue with this, or have any advice?

Cheers,
--
Terry Duell <tdu...@iinet.net.au>

[David W. Jones]

Hmm, sounds like you might need to build a more recent version of exiv2
first, yes?

--
David W. Jones
gnome...@gmail.com
wandering the landscape of god
http://dancingtreefrog.com
My password is the last 8 digits of π.

[Terry Duell]

Hello David,

On Sat, 2022-03-12 at 13:31 -1000, David W. Jones wrote:
> On 3/12/22 12:31, Terry Duell wrote:
> > Hello All,
> > I have just tried to do a test build of the current default Enblend 4.3, and have
> > run
> > into a cmake error.
> >
> > The error message is a follows...
> >
> > -- Found Exiv2 release >= 0.12
> > -- Found Exiv2: /usr/lib64/libexiv2.so
> > -- Performing Test EXIV2_COMPILES_FLAG
> > -- Performing Test EXIV2_COMPILES_FLAG - Failed
> > CMake Error at CMakeModules/FindEXIV2.cmake:145 (MESSAGE):
> >    Found exiv2 library, but this library is not recent enough to compile
> >    enblend/enfuse.
> > Call Stack (most recent call first):
> >    CMakeLists.txt:271 (FIND_PACKAGE)
> >
> > I'm attempting to build on Fedora 35, using rpmbuild, and following the process
> > I've
> > used for many moons, although it must be said that I don't do this as often as I
> > used
> > to, may have missed something.
> > Anyone else have an issue with this, or have any advice?
>
> Hmm, sounds like you might need to build a more recent version of exiv2
> first, yes?

It would seem so, but curiously the config message prior to the error suggests that
Exiv2 >= 0.12 was found, and one would presume was an indication that was OK.
The current Exiv2 installed (Exiv2, Exiv2-devel, Exiv2-libs) on Fedora 35 is 0.27.5.

[David W. Jones]

Hmm, sorry, didn't notice that. Beyond me!

[T. Modes]

Hi Terry,

Tduell schrieb am Samstag, 12. März 2022 um 23:32:02 UTC+1:

Anyone else have an issue with this, or have any advice?

For the default branch you still need the exiv2 version from the repository (which has no official version number, so this can't be checked, 0.27. is not recent enough)

or to disable the metadata transfer ( -DENABLE_METADATA_TRANSFER=OFF)

But this is not new. I wrote this already to you https://groups.google.com/g/hugin-ptx/c/MOx1J8OXABU/m/cBd3ihaxAQAJ

Here nothing has changed.

Thomas

[Terry Duell]

Thanks Thomas.
Not sure what's gone astray here as builds have been OK over the past 2 years since
that advice.

[Terry Duell]

Hello Thomas,

On Sat, 2022-03-12 at 23:43 -0800, T. Modes wrote:
>

> But this is not new. I wrote this already to you
> https://groups.google.com/g/hugin-ptx/c/MOx1J8OXABU/m/cBd3ihaxAQAJ
> Here nothing has changed.
>

You prompted me to do some revision, as I had completely forgotten about that.
It looks like I built Exiv2 from the repository after your message referred to above,
and as a result subsequent builds of Enblend were trouble free.
It would seem that my local copy of that version of Exiv2 disappeared with an upgrade
of Fedora without me realising.
Now I know...but will I remember??

Thanks for your help.

[Terry Duell]

On Sat, 2022-03-12 at 23:43 -0800, T. Modes wrote:
> >

> For the default branch you still need the exiv2 version from the repository (which
> has no official version number, so this can't be checked, 0.27. is not recent
> enough)
> or to disable the metadata transfer ( -DENABLE_METADATA_TRANSFER=OFF)
> But this is not new. I wrote this already to you
> https://groups.google.com/g/hugin-ptx/c/MOx1J8OXABU/m/cBd3ihaxAQAJ
> Here nothing has changed.

Just a followup on this, which may be of interest to some.
I pulled exiv2 from the repository, which git described (git describe --tags) as
version 'nightly-34-g573c3c79'.
I set the version in the rpmbuild spec file as '0.27.99.0' following previous
practice by others, and attempted to build, but rpmbuild failed with a message to the
effect (I didn't record the exact detail) that rpmbuild detected that the version was
'1.0.0.9'. Setting the rpmbuild version to '1.0.0.9' built without error.
Unfortunately I can't install this version of exiv2 as it causes conflicts with a
couple of programs that were built with the current version (0.27) of exiv2.
The suggested alternate solution of -DENABLE_METADATA_TRANSFER=OFF looks the only
answer at the moment.

[Terry Duell]

On Wed, 2022-03-16 at 09:55 +1100, Terry Duell wrote:
>
> The suggested alternate solution of -DENABLE_METADATA_TRANSFER=OFF looks the only
> answer at the moment.
>

Now getting this error, and looking back into history, I saw that a few years ago.

error: ISO C++17 does not allow dynamic exception specifications
796 | throw(PreconditionViolation)

Does this mean that I also need vigra from git to build the current default enblend?