Multiple versions of CPM? about cpm.cmake

[TheLartians]

Hey, thanks for the question, this is a common use case.

CPM always sticks with the first version imported, but emits a warning if a (semantic) newer version is requested. You can see the logic here. In your examples:

What happens if project A uses project B?

The Project uses CPM 0.27.5, but a warning is emitted that B requires the more recent 1.01.0

What happens if project B uses project A?

The Project uses CPM 1.01.0

What happens if project B uses project C?

The Project uses CPM 1.01.0

What happens if project C uses project B?

The Project uses CPM 0.10.0, but a warning is emitted that B requires the more recent 1.01.0

Gotcha that makes sense.

Is something like this worth adding to the wiki/readme?

Or is this just expected cmake behavior? Because I believe vanilla FetchContent uses the same logic you described.

[TheLartians]

It's already kind-of mentioned in the: readme Dependencies using CPM will automatically use the updated script of the outermost project., but if you feel this isn't clear enough feel free to add it to the wiki. :)

Yeah as soon as I said it, I started looking at the readme... and sure enough it was there. Sorry that's a bad habit of mine.

I think it's clear in the README.md, just that the readme is huge and my eyes tend to glaze when the readme is too large. It may be worth moving more stuff into the wiki. But that's just my opinion.

[TheLartians]

I think most of us have that habit. 😄

I agree that the README has gotten rather huge and we can probably outsource move some to the wiki. Thanks for noting it, once I have some spare time I'll see if I can slim things down.