CMake build examples flag

[dutkalex]

Separate the building of the tests from the building of the examples.
For reference: cburstedde/p4est#316

[cburstedde]

Cool; I'm wondering what's up with the CI?

[cburstedde]

Would you know what we need the CMake version condition for?

[dutkalex]

Cool; I'm wondering what's up with the CI?

It doesn't seem related to the CMake change, since the autotools build also fails...

Would you know what we need the CMake version condition for?

No idea. It was there so I left it as is, but I really don't know what was the rationale behind

[cburstedde]

> Cool; I'm wondering what's up with the CI? It doesn't seem related to the CMake change, since the autotools build also fails...

So we should have a look at the current state of the CI on the develop branch of libsc? Maybe @mkirilin has an idea.

> Would you know what we need the CMake version condition for? No idea. It was there so I left it as is, but I really don't know what was the rationale behind

It would be interesting to check the CMake example build code, maybe we can remove it. @scivision may know what it is needed for?

[mkirilin]

The PR tries to merge into the master branch. The master is from March, 2024. Github updates provided OS and packages versions on regular basis. It might be a case, that some CI updates were merged into develop only (rather than master) to react on new OS / packages versions.

[dutkalex]

Spot-on @mkirilin. That was indeed the issue. Thanks for your help 😊

[cburstedde]

Thanks for figuring it out! We can follow up on the version tests separately.