tl;dr, the below does not work for me: The resulting moc_<basename>.cpp files are generated in custom directories and automatically included in a generated <AUTOGEN_BUILD_DIR>/mocs_compilation.cpp file, *which is compiled as part of the target. (nope....)*
On Mon, Jan 28, 2019 at 10:06 PM Venedict Tchistopolskii <veny...@gmail.com> wrote: > The first CMake generation pass: Generates but no inclusion > > > > *Forcing a second pass makes it include the newly generated moc.* > It says *"AutoMoc: Generating 'XXXXX' because the MOC settings changed"* > > I'm not too clear on why this is happening, any ideas on how to fix it, or > force it to reload whatever 'moc settings' are changing? > > Possibly related: https://gitlab.kitware.com/cmake/cmake/issues/17456 > > e.g. mocs_compilation.cpp and include_XXXX folder -> Created but not added > until CMake re-run.... >
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
