What is the name of the library target created, etc.

[dabrahams]

The documentation says almost nothing about how the system interacts with CMake. How am I supposed to use the library created by this thing from another project, to say nothing of the other targets? I don't even know their names. I'm sure this is just the tip of the iceberg in terms of missing information.

[PeriBooty]

I agree the documentation on what's generated behind the scenes is sparse, but to assist with your question, the utility will generate a target with the same name as placed in project.

E.g. if you have a project(MyCoolTool) then run cpp_library_setup, it will create a target called MyCoolTool.

The utility will additionally create an alias target based on the NAMESPACE option, for example:

... # skipping boilerplate
project(MyCoolTool)
... # skipping boilerplate

cpp_library_setup(
  NAMESPACE Cool
  ...
)

This will generate both a MyCoolTool target, and a Cool::MyCoolTool target, which aliases MyCoolTool.

---

As an added caveat, if your project started with the namespace followed by a dash, that would be stripped from the alias target, so one last example:

... # skip skip
project(Cool-MyCoolTool)
... # skip skip skip

cpp_library_setup(
  NAMESPACE Cool
  ...
)

This would generate Cool-MyCoolTool and Cool::MyCoolTool.

---

Here's the links to the files that handle this if you're interested:

• https://github.com/stlab/cpp-library/blob/main/cmake/cpp-library-setup.cmake#L27 (Actually has the add_library calls)
• https://github.com/stlab/cpp-library/blob/main/cpp-library.cmake#L174 (where that internal function is called in relation to cpp_library_setup)

[dabrahams]

Thanks, but I don't want the information or the links to the files in an issue; I want the documentation fixed. I'm probably never even going to use this project; I wrote it for the benefit of @sean-parent so he would know what was needed before it can be used by someone who isn't its author.

[sean-parent]

See #8 (Thanks @PeriBooty).

[sean-parent]

Complete overhaul of documentation in #9