build - CMake Roundtrip Workflow -

i understand cmake enables project built in variety of compiler/ide environments. have experienced myself , amazed when cmake produced working, buildable xcode project me open source project (cool!)

but don't understand how update cmake system after have made significant changes project cmake created you.

for example envisioning workflow in project should kept portable via cmake. create clone of github project, use cmake create xcode project, , go work implementing new feature or bug fix. perhaps these changes non-trivial , affect build.

after these changes complete want push code base github. happens now? must of cmake files updated hand reflect of work i've done? or there equally magical feature update cmake files changes implemented in xcode (or visual studio, or other supported ide/compiler combo)?

what general "roundtrip" workflow cmake , how efficient it?

the point change project changing cmake configuration files themselves. you'll find other tool manages cmake projects, make changes cmake files. in example mention, have check if xcode modifying cmake files.

you have commit necessary modifications cmake files, , build program (make, ninja, or other) run cmake every time cmake project files touched.

advanced note: if use command file globbing instructions list of sources files, might interested read getting cmake run before building after pulling git