update project template

Provide a configure script which knows the version of config generator

* fix: Do not modify model while iterating in XML generator

* fix: Change XML generator for TriggerReceivers

Give it a chance to comply with the XSD we provide

* fix: Update XML output XSD for changed output

 - Add Void and Boolean
 - Add TriggerReciever
 - Make class optional

* chore: Update test for XML generator

Add a DeviceModule whose absence was causing the XML generator to fail unnoticed

feat(project-template): Find python modules (#44)

Add a simple cmake helper to find installed python modules. This is
mostly useful if the tests have some dependency on some python modules

feat(project-template): conf-gen: follow symlinks at builddir creation

Instead of copying a symlink file, resulting in a broken link, the
target file is copied instead, unless the target is in the same
directory, in which case the symlink is maintained.

If a device was only defined by CDD and the CDD contained some sort of
hierarchy separator, the unescaped CDD was causing an invalid variable
name.

Modifying the model while visiting is not allowed because the
modification invalidates the iterators used for visiting. This lead in
this case to a very subtle crash (segfault) only appearing under very
specific circumstances (only when running in ctest and only on some
Ubuntu 20.04 machines).

ProcessVariableProxy::removeNode() was effectively taking a reference to
a shared pointer as an argument and is removing the same (effective)
shared pointer from a list. This poses a problem if the reference passed
points to the list directly and is the last shared pointer to this
object so it gets freed, because removeNode() is accessing the object
after removing it from the list.

chore(project-template): remove workaround for doocstiminglib

Dietrich Rothe authored 1 year ago and Martin Christoph Hierholzer committed 1 year ago

Handle doocstiminglib like other doocs packages, since it now provides
a proper pkgconfig.

The VersionInfoProvider registers with the Application, so we can find
the (singleton-like) instance in the Application. If it is destroyed
for whatever reason, this instance pointer must be de-registered to
prevent use-after-free as well as allow the subsequent creation of
another VersionInfoProvider.

If the StatusAggregator would propagate the DataValidity of its inputs
normally, device errors (runtime exceptions) will normally be presented
as an invalid because values from the device will be aggregated  often
with the same StatusAggregator (if it is on the top level of the app).
This is clearly undesired.

The StatusAggregator did not pass on messages unless the
StatusWithMessage was from another StatusAggregator. StatusWithMessage
outputs from normal modules were treated like normal StatusOutputs
without message.

feat(project-template): add VersionInfo.h generation (#40)

vaeng authored 1 year ago and Martin Christoph Hierholzer committed 1 year ago

* The example app has been updated to show the implementation of the
new VersionInfoProvider module

fix(project-template): remove conflicting llwm-include-order