Re: Marble versioning
Tobias Leupold <[email protected]> Mon, 26 Jul 2021 22:26:51 +0200
| Newsgroups | gmane.comp.kde.kimdaba |
|---|---|
| Message-ID | <36985960.J2Yia2DhmK@ginuog> |
> Ok, let's counter this with yet more ugly code, something along this
> line would work for some years:
>
> set(ALLVERS "24.0.0" "23.0.0" "22.0.0" "21.0.0" "0.28.0")
> foreach(V IN LISTS ALLVERS)
> find_package(Marble ${V})
> if (${Marble_VERSION} MATCHES "[02].*\..*") )
> break()
> endif()
> endforeach()
> find_package(Marble ${Marble_VERSION} REQUIRED)
>
> will probably find the newest package for some years to come.
>
> Harald.
You're right -- but if we do a version check like this, we can as well simply
check for no version at all, as we do now ;-)
Unless Marble changes it's versioning scheme, I think this will be the only
reasonable option ...