TST: add test package depending on a cmake subproject

[dnicolodi]

No description provided.

[rgommers]

This is Draft until the upstream bugs are fixed, right?

[dnicolodi]

It depends on your definition of draft PR 🙂. The PR is complete, but there is a bug in Meson that makes merging it not productive. I keep this open just to remember ourselves of the bug: I don't know cmake at all and I don't have the spare cycles required to investigate this.

[rgommers]

👍🏼

In my book:

• draft = "no need to review it"
• non-draft & green = "ready for review & merge"

[dnicolodi]

This was supposed to be non-draft and red, thus also not ready for review, probably. But it is so old that the test results have been flushed out. Setting it as draft now.

[dnicolodi]

This test does not really test much on the meson-python side, but it was useful to identify the problem on the Meson side, therefore I'm thinking to merge it to avoid the support for CMake subprojects to regress in the future. @rgommers, what do you think?

[rgommers]

That seems like a good idea to me, covering this kind of thing with tests is helpful for meson-python users that rely on it.

Our CI doesn't check macOS + meson master, did you test that locally? If not I'll do that before merging.

[dnicolodi]

Our CI doesn't check macOS + meson master, did you test that locally?

Yes, I tested that locally. On macOS the test passes also with older versions on Meson. The Meson fix is necessary only on Linux. However, I did not think that verifying this in CI was necessary. We can do that, if you think it is useful.

[dnicolodi]

I extended the test to run on macOS too. Merging.