Skip to content

monitor-manager: Don't include generated code in header file

Meson doesn't seem handle depending on generated headers, at least when those headers are pulled in indirectly via another header file.

Luckily, we don't actually need to include the generated D-Bus boiler plate in meta-monitor-manager-private.h, since the MetaMonitorManager type no longer is based on the D-Bus service skeleton.

So, by moving the inclusion of the generated D-Bus header file into meta-monitor-manager.c, we should hopefully get rid of the sporadic build issues.

Closes: #1682 (closed)

Merge request reports