If a name isn't provided, try to infer it from the git repo

[iboB]

Two reasons behind this PR

More compact CPMAddPackage calls

CPMAddPackage(
  GITHUB_REPOSITORY catchorg/Catch2
  VERSION 2.5.0
)

Less room for error in pasting CPMAddPackage calls

To me, and I suspect to many other users most packages look like this:

CPMAddPackage(
  NAME PackageName
  GITHUB_REPOSITORY user/PackageName
  VERSION x.y.z
)

When adding a new package, this gets pasted around and two identical occurrences of "PackageName" need to be replaced. If we follow the DRY principle, this repetition should be avoided and in the case of git repositories this is easy.

The old behavior still works for backwards compatibility and for the rare cases where the package name and the repo name aren't the same.

[TheLartians]

Thanks for the PR, I think this is a great idea to shorten the syntax and avoid repetition!

[TheLartians]

Also feel free to update the main example in the readme to show off the shorter syntax! :-)

[iboB]

Check. Suggested changes were added.

[TheLartians]

Awesome, thanks for the changes!

[TheLartians]

Feature released in v0.30.0! 🎉

[gudnimg]

@TheLartians
Hi, I'm glad to see all the improvements... I have one idea to improve the README:

This is what it looks like right now:

ExternalProject works similarly as FetchContent, however waits with adding dependencies until build time. This has a quite a few disadvantages, especially as it makes using custom toolchains / cross-compiling very difficult and can lead to problems with nested dependencies.

I think it makes sense to highlight the keywords ExternalProject and FetchContent like this: ExternalProject FetchContent or even link the words to the CMake documentation.

Idea 1

ExternalProject works similarly as FetchContent, however waits with adding dependencies until build time. This has a quite a few disadvantages, especially as it makes using custom toolchains / cross-compiling very difficult and can lead to problems with nested dependencies.

---

I just learned right now as I wrote this that you can create a link for coded words with

• `keyword ` (keyword) :D)

Or like this:

Idea 2

ExternalProject works similarly as FetchContent however waits with adding dependencies until build time. This has a quite a few disadvantages, especially as it makes using custom toolchains / cross-compiling very difficult and can lead to problems with nested dependencies.

Edit: It's like this: [`ExternalProject`](https://cmake.org/cmake/help/latest/module/ExternalProject.html)

[TheLartians]

@GunZi200 thanks for the suggestions! I think there are definitely some improvements that can be made to the readme. As the section you're referring to is written for users who already know both commands I think the link isn't necessary but highlighting the code does make sense. If you want, feel free to open a PR and we can discuss further changes there.