[yocto] [meta-mono][PATCH] mono-4.xx: compiling mono 4 with btls requires cmake

Alex Lennon ajlennon at dynamicdevices.co.uk
Fri Nov 3 04:48:30 PDT 2017



On 02/11/2017 15:59, Khem Raj wrote:
> On Thu, Nov 2, 2017 at 8:46 AM, Pascal Bach <pascal.bach at siemens.com> wrote:
>> On 27.10.2017 23:41, Khem Raj wrote:
>>> On Fri, Oct 27, 2017 at 3:51 AM, Pascal Bach <pascal.bach at siemens.com> wrote:
>>>> This was probably working before pyro and the recipes specific sysroots.
>>>>
>>>> Signed-off-by: Pascal Bach <pascal.bach at siemens.com>
>>>> ---
>>>>   recipes-mono/mono/mono-4.xx.inc | 2 +-
>>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/recipes-mono/mono/mono-4.xx.inc b/recipes-mono/mono/mono-4.xx.inc
>>>> index e06fac7..cf9170b 100644
>>>> --- a/recipes-mono/mono/mono-4.xx.inc
>>>> +++ b/recipes-mono/mono/mono-4.xx.inc
>>>> @@ -4,7 +4,7 @@ HOMEPAGE = "http://mono-project.com"
>>>>   BUGTRACKER = "http://bugzilla.xamarin.com/"
>>>>   SECTION = "devel"
>>>>
>>>> -DEPENDS = "zlib"
>>>> +DEPENDS = "zlib cmake-native"
>>>>
>>> perhaps this should inehrit cmake if its using cmake
>>> or explain how cmake is used where abstactions
>>> are not relevant
>> Using the cmake bbclass doesn't work as it is not really a CMake project.
>>
>> Mono requires cmake to build the bundled BoringSSL library. I didn't look why it works in detail but I currently assume that BoringSSL is standalone enough that no additional
>> CMake toolchain settings are required to make it work.
>>
> yeah that probably is a case of bundling which is on rise at app level
> these days,
>
>> One option would be to disable it with `--disable-btls` but I fear that would disable TLS1.2 support (http://www.mono-project.com/docs/about-mono/releases/4.8.0/#tls-12-support).
>> But I have no way of checking that.
>>
> interesting, do they support any other TLS implementations ?
>

It is disabled in 5.x builds by default as it breaks the build e.g.

http://git.yoctoproject.org/cgit/cgit.cgi/meta-mono/tree/recipes-mono/mono/mono-5.4.0.201.inc

It's probably time to look at a working build with it re-enabled. 
Patches welcomed...

(I did have a quick look at inheriting cmake but that breaks the build too)

Cheers,

Alex




More information about the yocto mailing list