mono-4.xx: compiling mono 4 with btls requires cmake
PATCH 1/1 mono-4.xx: compiling mono 4 with btls requires cmake
This was probably working before pyro and the recipes specific sysroots.
--- recipes-mono/mono/mono-4.xx.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
recipes-mono/mono/mono-4.xx.inc +1 -1
@@ -4,7 +4,7 @@ HOMEPAGE = "http://mono-project.com" BUGTRACKER = "http://bugzilla.xamarin.com/" SECTION = "devel" -DEPENDS = "zlib" +DEPENDS = "zlib cmake-native" SRC_URI = "http://download.mono-project.com/sources/mono/mono-${PV}.tar.bz2 \ file://dllmap-config.in.diff \
Signature · 1 line
2.1.4
Quoted 12 lines · Pascal Bach
This was probably working before pyro and the recipes specific sysroots.
Signed-off-by Pascal Bach <[email protected]>--- recipes-mono/mono/mono-4.xx.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)recipes-mono/mono/mono-4.xx.inc +0
-0
recipes-mono/mono/mono-4.xx.inc HOMEPAGE = "http://mono-project.com" · line 8
Quoted 6 lines
recipes-mono/mono/mono-4.xx.inc +1
-1@@ -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
Quoted 10 lines
recipes-mono/mono/mono-4.xx.inc +0
-1SRC_URI = "http://download.mono-project.com/sources/mono/mono-${PV}.tar.bz2 \ file://dllmap-config.in.diff \ --2.1.4
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Quoted 16 lines · Khem Raj
Quoted 15 lines · Pascal Bach
This was probably working before pyro and the recipes specific sysroots.
Signed-off-by Pascal Bach <[email protected]>--- recipes-mono/mono/mono-4.xx.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)recipes-mono/mono/mono-4.xx.inc +0
-0@@ -4,7 +4,7 @@ HOMEPAGE = "http://mono-project.com" BUGTRACKER = "http://bugzilla.xamarin.com/" SECTION = "devel"
Quoted 6 lines
recipes-mono/mono/mono-4.xx.inc HOMEPAGE = "http://mono-project.com" · line 8
Quoted 3 lines
recipes-mono/mono/mono-4.xx.inc +1
-1-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.
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.
Pascal
Quoted 11 lines
Quoted 11 lines
recipes-mono/mono/mono-4.xx.inc +0
-1SRC_URI = "http://download.mono-project.com/sources/mono/mono-${PV}.tar.bz2 \ file://dllmap-config.in.diff \ --2.1.4
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Quoted 24 lines · Pascal Bach
Quoted 16 lines · Khem Raj
Quoted 15 lines · Pascal Bach
This was probably working before pyro and the recipes specific sysroots.
Signed-off-by Pascal Bach <[email protected]>--- recipes-mono/mono/mono-4.xx.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)recipes-mono/mono/mono-4.xx.inc +0
-0@@ -4,7 +4,7 @@ HOMEPAGE = "http://mono-project.com" BUGTRACKER = "http://bugzilla.xamarin.com/" SECTION = "devel"Quoted 6 lines
recipes-mono/mono/mono-4.xx.inc HOMEPAGE = "http://mono-project.com" · line 8
Quoted 3 lines
recipes-mono/mono/mono-4.xx.inc +1
-1-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
Quoted 5 lines
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,
Quoted 3 lines
One option would be to disable it with
--disable-btlsbut 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 ?
Quoted 15 lines
Pascal
Quoted 11 lines
Quoted 11 lines
recipes-mono/mono/mono-4.xx.inc +0
-1SRC_URI = "http://download.mono-project.com/sources/mono/mono-${PV}.tar.bz2 \ file://dllmap-config.in.diff \ --2.1.4
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Quoted 29 lines · Khem Raj
Quoted 23 lines · Pascal Bach
Quoted 16 lines · Khem Raj
Quoted 15 lines · Pascal Bach
This was probably working before pyro and the recipes specific sysroots.
Signed-off-by Pascal Bach <[email protected]>--- recipes-mono/mono/mono-4.xx.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)recipes-mono/mono/mono-4.xx.inc +0
-0@@ -4,7 +4,7 @@ HOMEPAGE = "http://mono-project.com" BUGTRACKER = "http://bugzilla.xamarin.com/" SECTION = "devel"Quoted 6 lines
recipes-mono/mono/mono-4.xx.inc HOMEPAGE = "http://mono-project.com" · line 8
Quoted 3 lines
recipes-mono/mono/mono-4.xx.inc +1
-1-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
Quoted 5 lines
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.
Quoted 8 lines
yeah that probably is a case of bundling which is on rise at app level these days,
Quoted 3 lines
One option would be to disable it with
--disable-btlsbut 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
Quoted 13 lines
Quoted 4 lines
Quoted 4 lines
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.
Quoted 8 lines
yeah that probably is a case of bundling which is on rise at app level these days,
Quoted 3 lines
One option would be to disable it with
--disable-btlsbut 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 ?
Quoted 8 lines
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
Quoted 21 lines · Pascal Bach
Quoted 13 lines
Quoted 5 lines
Quoted 5 lines
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.
Quoted 8 lines
yeah that probably is a case of bundling which is on rise at app level these days,
Quoted 3 lines
One option would be to disable it with
--disable-btlsbut 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 ?
Quoted 8 lines
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)
Quoted 9 lines
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
Pascal,
For now I've put a couple of commits into master which re-enable BTLS for 5.8.022 and 5.4.0.201. Both of these seem to build with your cmake dependency added.
After listening to the team at #OEDEM I've been working to add basic Image Test support to core-image-mono and to get the Yocto Auto Builder going so I can automate some testing of the yocto release vs mono version vs mono features matrix
That's finally coming together at which point I'm hoping to genericise a bit more.
There are currently just three basic run time tests which previous to the image test support I've been performing manually
ref: http://git.yoctoproject.org/cgit/cgit.cgi/meta-mono/tree/lib/oeqa/runtime/cases/mono.py
If you have suggestions/patches for an image test for TLS (or indeed any other tests) they'll be gratefully received.
At some point I want to extend this with ptest support for running the Mono test suite on the target { qemu / real hardware etc }
ref: http://www.mono-project.com/community/contributing/test-suite/
Cheers,
Alex
Quoted 19 lines · Pascal Bach
Quoted 19 lines
Quoted 6 lines
Quoted 6 lines
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.
Quoted 8 lines
yeah that probably is a case of bundling which is on rise at app level these days,
Quoted 3 lines
One option would be to disable it with
--disable-btlsbut 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
Quoted 7 lines
Quoted 4 lines
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.
that seems reasonable
Quoted 5 lines
If somebody figures out how to enable it again. I will send an updated Patch.
Pascal