HDRMerge AppImage - first experiment

Do you also need the LibRAW demosaicing packs?

No, I don’t think so.

So here is a new version with LibRaw 0.17.2 (or at least it is supposed to… ;-)).

And I think that this is the main interest in appcimages: you can run a piece of software with all the most appropriate dependencies without installing anything…

Where is here?

Sorry, I was doing 10 things at the same time and forgot the link… :dizzy_face:

1 Like

I just tested the new appimage. It still uses an old libraw version here. You can test it using the files from Merging 3 brackets? - #4 by anubis and running hdrmerge -vv (two v, not 1 w). HDRMerge should report cblack: 2048 or 2049 in console output. The appimage still reports cblack: 0 which is the output when using an older libraw version.
I tested on a machine which has an old version of libraw btw.

The first good news is that the appimage does not crash… this evening I will look into the lib raw version issue, I’m pretty sure that the solution is rather simple.

1 Like

Here is a new version of the AppImage, this time correctly using LibRaw 0.17.2:

I also discovered a mistake in the HDRMerge sources: in two places, the LibRaw header is included like that:

#include <libraw/libraw.h>

However, the correct syntax should be

#include <libraw.h>

because the cmake configuration already sets

-I${prefix}/libraw

in the compiler options. As a consequence, the current way of including LibRaw always picks the system-wide header in

/usr/include/libraw/libraw.h

even when a custom version is being linked.

@heckflosse: to which github issue tracker should I file this bug?

Please file the bug here

@Carmelo_DrRaw Fixed, also added this

Very good!

Did you also test the appimage already?

This works on my Debian system where the GIMP AppImage does not. The Krita AppImage also works, for what it’s worth.

Yes, works fine on Mint 17.2. Thank you!

Should we put it on the “Community Software” page?

Sure. Why not?

Great to see this!

@Carmelo_DrRaw if @heckflosse agrees, I think it would be best if you used libraw from GitHub. Reason being is that the latest stable is old (as is the case with RawTherapee), while the latest release - 0.18-Beta3 - is much newer, but probably unavailable in most distros.

@Morgan_Hardwood I agree if you tested it. I didn’t :wink:

That was also my initial idea, but then I ran into some issues with the LibRaw build system from git: it only provides a configure.ac file, and running autoconf was giving me some fatal errors.

Before spending time to investigate the issue, I wanted to set-up the appimage to work with a custom LibRaw version, so I picked 0.17.2.

Now I will come back to the git version and try to solve the building issue…

Great, thank you. I’ll not be able to test the new appimage before saturay evening or sunday btw…

@heckflosse @Morgan_Hardwood New appimage version, this time with LibRaw from git: https://framadrop.org/r/UC-K6kzuRX#yuDB4eYjZZZCmEVcfJfV/I1hJyPhy+kWJ4FYUXa7JIU=

Building from git was actually almost trivial…

1 Like