I went a little deeper into this code and found that in tests/ you've added what looks like generated marshallers for glib callbacks. It might be better to autogenerate that a build time instead of shipping it in the source distribution since the *.list could change whenever we need a new marshaller. For example
Yo Dawg,
I went a little deeper into this code and found that in tests/ you've added what looks like generated marshallers for glib callbacks. It might be better to autogenerate that a build time instead of shipping it in the source distribution since the *.list could change whenever we need a new marshaller. For example
add_executable (test-signals ... ${CMAKE_ CURRENT_ BINARY_ DIR}/generated/ test_glib_ signals_ utils_marshal. cpp
...)
file (MAKE_DIRECTORY ${CMAKE_ CURRENT_ BUILD_DIR} /generated) CURRENT_ SOURCE_ DIR}/test_ glib_signals_ utils_marshal. list CURRENT_ BINARY_ DIR}/generated)
add_custom_command (TARGET test-signals PRE_BUILD
COMMAND glib-genmarshals ${CMAKE_
WORKING_DIRECTORY ${CMAKE_
That way we can create and perceive the marshallers at the same time, without the person doing the compiling ever knowing that!
(I can't comment on the nature of the code itself, knowing little about glib, however I do intend to run the tests and try it out)