Closed jcfreeman2 closed 3 years ago
Thanks @jcfreeman2. The fix also adds the model file to the dependency list. But, I'm not sure if this is good or bad as in this particular example, the model is provided by moo itself and not by the project source. As long as render-deps
and eventual render
is all with the same moo
I think there will not be any weirdness.
Thanks for the speedy resolution @brettviren. Adding the model file to the dependency list strikes me as the right call.
One thing I'm noticing is that when
moo render-deps
gets called within daq-cmake 'smoo_render
function to make a list of dependencies for a generated header in a*.d
file, not all the dependencies are listed. We can look at such a file by setting up a work area and building opmonlib and appfwk (where appfwk uses a template file opmonlib provides):The resulting
build/appfwk/codegen/include/appfwk/queueinfo/InfoStructs.hpp.d
looks like the following (I've inserted newlines for ease-of-reading):It makes sense that
info_hpp_macros.j2
is listed, but I'd also have expected theInfoStructs.hpp.j2
which imports it to have been included.You can also replicate this by directly running moo, of course: