>>> >>> 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) > I did some more testing. And adding "cmake-native" still doesn't build btls. I guess it need cmake to figure that out. But this means it was never enabled in the first place.
So my proposal for the moment is to explicitly set "--disable-btls" for Mono 4 too, this way it builds and it is clear that it is disabled. If somebody figures out how to enable it again. I will send an updated Patch. Pascal -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
