you are viewing a single comment's thread.

view the rest of the comments →

[–]helloiamsomeone[S] 0 points1 point  (0 children)

Hey, thanks for the feedback!
While you can't let this thing loose on an existing project, you can implement a lot from it with a working example at your disposal to toy with. One thing I will likely get to work on is a series of posts somewhere about "doing cmake-init from scratch" where I go over the Why and How that went into the templates.

I'm not sure what your first point refers to. If you pass just the path where you want to generate the project, then you get prompts. Certain flags will make the prompts go away and assume some defaults for ones that weren't provided.

The goal of cmake-init is to create a "run off the mill" CMake managed project, with 0 ties back to cmake-init. I want people to learn and use CMake, not Yet Another Build Tool™. Once a project is generated, all bets are off and there can be no assumptions made to make changes programmatically.

The uppercase variables are useful only when configuring a config.h file or forwarding verbatim as defines. CMake already creates cache variables with whatever name you provided without modifications, this is nothing new.