base: add support for ADEiger module.

[gustavosr8]

Description

Add support for ADEiger module, in order to operate Pilatus4.

ZeroMQ library development package is required in the build stage of ADEiger module.

There are some unreleased features we would like to use, regarding Pilatus4 support, what makes necessary a checkout after initializing the submodule. The EDEIGER_VERSION points to the latest commit, but should point to R3-6 when the version were tagged.

Checklist

• Follow the commit format specified in CONTRIBUTING.md;
• Describe your user-facing changes in CHANGES.md, following the format
  established by previous entries.

[ericonr]

commit message:

base: add support for ADEiger module.

base: add ADEiger module.

ZeroMQ library development package is required in the build stage of
ADEiger module.

This module uses libzmq to interact with the detector data stream.

(this way you justify the presence of the -dev package and the runtime package in your runtime image)

There are some unreleased features we would like to use, regarding
Pilatus4 support, what makes necessary a checkout after initializing the
submodule. The EDEIGER_VERSION points to the latest commit, but should
point to R3-6 when the version were tagged.

Since Pilatus4 support hasn't been released yet and we are interested in using
it, we are using the latest commit from the master branch instead of a tagged
release.

[ericonr]

I think tagging a new release is pending on further driver changes, right? So we have to use a commit for now.

[gustavosr8]

I think tagging a new release is pending on further driver changes, right? So we have to use a commit for now.

Yeap, discussed here: areaDetector/ADEiger#70 (comment)

[ericonr]

Well, there is something for us to choose here. Does this need to be merged before the tag? We're perfectly capable of building the IOC image ourselves, and use it for commissioning tests in the beamline. In the meantime, we can try and move along the missing functionality, so we can have everything merged before the machine stop ends.

[gustavosr8]

Does this need to be merged before the tag?

Since we are talking about commissioning tests, there is no hurry on merging this, IMHO. (This is actually the reason for leaving this PR as draft on the first time)

But when comes the time to the official deploy for operation, if it hasn't been tagged yet, then we should use the untagged version.

[ericonr]

#25 130.0 /usr/bin/g++ -o test_lz4  -L/opt/epics/modules/areaDetector/ADEiger/lib/linux-x86_64 -Wl,-rpath,/opt/epics/modules/areaDetector/ADEiger/lib/linux-x86_64          -rdynamic -m64         test_lz4.o    -ldectrisCompression  -llz4 
#25 130.0 /usr/bin/ld: cannot find -llz4: No such file or directory

is using lz4 wrongly. I will create a PR for this...

[gustavosr8]

Just documenting, @ericonr's PR has been closed since Mark Rivers is addressing this differently in areaDetector/ADEiger#91. While it still unmerged, I think we should use the last stable commit, areaDetector/ADEiger@6ca17ce. What do you think?

[ericonr]

As discussed, we need areaDetector/ADEiger@083243f for the TIFF fixes. We'll patch test_lz4 for now.

[ericonr]

Please rebase properly onto main.

[ericonr]

nit:

I prefer [1] <link-content> directly, without the colon