Well the problem in 12762 is that cmake *hardcodes a list of valid
boost versions*, and I'm struggling to understand why this would seem
like a good idea.
Some thoughts:
1) We definitely need a selftest for cmake. We have a few build-stuff
test cases already (lzip, cpio, galculator in sdk and run
On 06/10/2018 12:25 AM, Alexander Kanavin wrote:
> 2018-06-09 23:00 GMT+03:00 Armin Kuster :
>> +DEPENDS = "boost"
>
>
>> +find_package(Boost 1.60 REQUIRED
>> +COMPONENTS
>> +unit_test_framework
>> +)
>
> Is it possible to use something else than boost here, if we want to
> test cmak
2018-06-09 23:00 GMT+03:00 Armin Kuster :
> +DEPENDS = "boost"
> +find_package(Boost 1.60 REQUIRED
> +COMPONENTS
> +unit_test_framework
> +)
Is it possible to use something else than boost here, if we want to
test cmake's ability to find compoments? So that the build time is as
qui
This came out of Yocto bug 12762. We need to ensure cmake will support
various packages in core as they update.
Test case provided by Dennis Menschel , thanks
Signed-off-by: Armin Kuster
---
.../recipes-test/cmake/cmake-boost-version-test.bb | 20 ++
.../recipes-test/cmake/files
