Using a chain of GDbus generation macros is unweildy

Bug #1671807 reported by Pete Woods
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cmake-extras (Ubuntu)
Fix Released
Medium
Pete Woods

Bug Description

THe convention in CMake for code generation is for macros to behave as follows:

set(MY_SOURCES foo.c)

generate_stuff(MY_SOURCES ........ ARGS)
generate_stuff(MY_SOURCES ........ OTHER ARGS)
generate_stuff(MY_SOURCES ........ MORE ARGS)

add_executable(hello ${MY_SOURCES})

i.e. each generator automatically appends to the MY_SOURCES variable.

See QDBus for comparison:

qt5_add_dbus_interface(
    MY_SOURCES
    "org.freedesktop.URfkill.xml"
    URfkillInterface
)

qt5_add_dbus_interface(
    MY_SOURCES
    "org.freedesktop.URfkill.Device.xml"
    URfkillDeviceInterface
)

Related branches

Pete Woods (pete-woods)
Changed in cmake-extras (Ubuntu):
assignee: nobody → Pete Woods (pete-woods)
status: New → In Progress
importance: Undecided → High
importance: High → Medium
Pete Woods (pete-woods)
Changed in cmake-extras (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.