ApplicationCore was hitting the limit...

* Create test case for testing multiple modules having the same.

* Use message IDs to support modules with similar names.

ToDo: Remove variable connections to CS like with MicroDAQ.

* Use automatic connection via CS. Rebuild hierarchy in Logging module.

* Put logging variables into a separate hierarchy level.

* Let user write to alias via CS. Keep last message in the PV.

Before the message was always cleared after writing it. Now a new log
level is used to indicate the situation that write was called on the
message PV without calling sendMessage - it happens if the owning module
calls writeAll(). Now the last message of each sender is availble in the
CS.

* Add test with modified hierarchy.

* Clang formaat applied.

* Hide internal PVs. Use different internal tag to work with regex.

update project template

Comment describes which clang-format version to use and how to get it.

Ignore files generated by CMake during configure

There are a couple of files in the CMakeFiles folder that will match the
search patterns. This is problematic during package build, since debian
builds in a subfolder of the source folder, so we hit those files and
tests fail

[project-template] add coding style checker

The VoidAccessor comes along with the convenience classes VoidInput and VoidOutput,
and the TestFacility function getVoid()

Update project template

Enable by adding
  include(cmake/enable_code_style_check.cmake)
to the project's CMakeLists.txt

update project template

This fixes together with another change in DeviceAccess the LNM
MathPlugin with push-type variables as parameters.

Ignore eclipse python project file.

Jens Georg authored 3 years ago and Martin Christoph Hierholzer committed 2 years ago

 - Remove Makefile.coverage.in
 - Drop BUILD_COVERAGE_ON_DEBUG for ENABLE_COVERAGE_REPORT (defaults to
    on if included)
 - Add clean-gcda target

Dietrich Rothe authored 3 years ago and Martin Christoph Hierholzer committed 2 years ago

this is required for dcmctrl7 config

Jens Georg authored 3 years ago and Martin Christoph Hierholzer committed 2 years ago

This fixes issues when using LaTeX in doxygen

Previous attempt to work around the tine linking issue did not work.

This is a work around for not finding libtinemt at runtime. The DOOCS serverlib is lacking the RPATH, hence its dependencies are not found. If clientlib is linked first, tine is already linked.

Search explicitly for libgul14 which is required by DOOCS libraries

Introduce StatusWithMessage and StatusWithMessageReader which handle this.
It is used in DeviceModule error reporting.
This is a preparation in order that we can report errors consistently to DOOCS, in DoocsAdapter

make StatusAggregator use StatusWithMessage

it should output always status code + string
on the input side, connects to either status or status + string
corresponding string input is found automatically
NOTE: DeviceModule API change, the status output variables are
renamed from (status, message) to (status, status_message)!

update testing of DeviceModule outputs

because of API change of DeviceModule  (renamed message ->
status_message)

fix crash and improve message and test

- fix crash due to incorrect handling of cast to Derived
- improve message output
- make existing tests pass
- add test for status message of StatusAggregator

move StatusWithMessageReaderBase and Status def to ControlSystemAdapter

since it is required from ApplicationCore as well as from the adapters