Re: [yocto] Anyone done a VAR-SOM-SOLO run-up?
OK thanks. I've found the serial port now (not the 9 pin D type as expected but a header) for the console and confirmed that a DTB file is totally missing from the build! Avagudweegend On 17 July 2015 at 02:27, Leonardo Sandoval < leonardo.sandoval.gonza...@linux.intel.com> wrote: > Robin, > you may have better luck if you send your question to the meta-freescale > mailing list. > > Leo > > On 07/15/2015 08:38 PM, Robin Gilks wrote: > >> Greetings all >> >> I'm having problems with the run-up of a Dizzy build on a VAR-SOM-SOLO. >> The >> same image is OK with a quad core variant, its just the single core fails >> so probably a DTB problem. >> >> I can't find any info on getting into u-boot - not even which serial port >> is used - so I can start debugging this. >> >> Has anyone on the list experience of this SOM and its associated >> VAR-MX6CustomBoard development/breakout board? >> >> Thanks >> >> >> >> -- *Robin Gilks* Development Delta Strike Success through Delta Strike phone:+64 3 982 9892 skype: robindeltastrike web: www.deltastrike.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 02/11] dbus-sharp-glib: use mono.bbclass
Signed-off-by: Richard Tollerton --- recipes-mono/dbus-sharp-glib/dbus-sharp-glib.inc | 13 ++--- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/recipes-mono/dbus-sharp-glib/dbus-sharp-glib.inc b/recipes-mono/dbus-sharp-glib/dbus-sharp-glib.inc index 2028609..8be7a65 100644 --- a/recipes-mono/dbus-sharp-glib/dbus-sharp-glib.inc +++ b/recipes-mono/dbus-sharp-glib/dbus-sharp-glib.inc @@ -1,11 +1,12 @@ SUMMARY = "C# implementation of D-Bus GlibC integration module" DESCRIPTION = "This is a fork of ndesk-dbus-glib, which provides GLib main loop integration for Managed D-Bus." SECTION = "devel/mono" -DEPENDS = "mono dbus-sharp" +DEPENDS = "dbus-sharp" LICENSE = "MIT" LIC_FILES_CHKSUM = "files://COPYING;md5=ea73672fbe49f67f1c1b44a7e763dab4" inherit autotools +inherit mono def dbus_sharp_glib_download_version(d): pvsplit = d.getVar('PV', True).split('.') @@ -19,16 +20,6 @@ S = "${WORKDIR}/${PN}-${SDIRVER}" FILESPATH =. "${FILE_DIRNAME}/${PN}-${PV}:" -FILES_${PN} += " \ - ${libdir}/mono/dbus-sharp-glib-2.0/dbus-sharp-glib.dll \ - ${libdir}/mono/gac/dbus-sharp-glib/*/*.config \ - ${libdir}/mono/gac/dbus-sharp-glib/*/*dll \ -" - -FILES_${PN}-dbg += " \ - ${libdir}/mono/gac/dbus-sharp-glib/*/*.mdb \ -" - do_configure_prepend() { export DBUS_SHARP_LIBS="/r:${STAGING_LIBDIR}/mono/dbus-sharp-2.0/dbus-sharp.dll" } -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 09/11] gtk-sharp.inc: use mono.bbclass and make some FILES fixes
/usr/lib/gtk-sharp-2.0 and /usr/share/gapi-2.0 are (AFAIK) only used for building, and so belong in gtk-sharp-dev. All other relevant FILES entries have been rolled into mono.bbclass. Signed-off-by: Richard Tollerton --- recipes-mono/gtk-sharp/gtk-sharp.inc | 23 --- 1 file changed, 4 insertions(+), 19 deletions(-) diff --git a/recipes-mono/gtk-sharp/gtk-sharp.inc b/recipes-mono/gtk-sharp/gtk-sharp.inc index 45d12b2..e466a8b 100644 --- a/recipes-mono/gtk-sharp/gtk-sharp.inc +++ b/recipes-mono/gtk-sharp/gtk-sharp.inc @@ -2,11 +2,11 @@ SUMMARY = "GUI toolkit for Mono" DESCRIPTION = "GTK+ bindings for Mono" SECTION = "devel/mono" BUGTRACKER = "http://bugzilla.xamarin.com"; -RDEPENDS_${PN} = "mono" LICENSE = "LGPL-2.1" RDEPENDS_${PN}-dev += "perl" inherit autotools +inherit mono # For some reason the URL template changes from version to version, # therefore use some variables for the directory and extension @@ -21,22 +21,7 @@ def gtk_sharp_download_version(d): FILESPATH =. "${FILE_DIRNAME}/gtk-sharp-${PV}:" -FILES_${PN} = "\ - ${bindir}/* \ - ${libdir}/* \ +FILES_${PN}-dev += "\ + ${libdir}/${PN}*/* \ + ${datadir}/* \ " - -FILES_${PN}-dbg = "\ -${libdir}/.debug \ -${datadir}/* \ -/usr/src/* \ -" - -FILES_${PN}-doc = "\ -${libdir}/monodoc/* \ -" - -FILES_${PN}-dev = "\ -${libdir}/pkgconfig \ -" - -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 08/11] mono-basic-4.xx.inc: use mono.bbclass
*.Pdb and *.Mdb files were not found in the install so they are not added to FILES. Signed-off-by: Richard Tollerton --- recipes-mono/mono-basic/mono-basic-4.xx.inc | 13 + 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/recipes-mono/mono-basic/mono-basic-4.xx.inc b/recipes-mono/mono-basic/mono-basic-4.xx.inc index 8b0a11e..cac0fb1 100644 --- a/recipes-mono/mono-basic/mono-basic-4.xx.inc +++ b/recipes-mono/mono-basic/mono-basic-4.xx.inc @@ -6,21 +6,10 @@ LICENSE = "LGPLv2" LIC_FILES_CHKSUM = "file://LICENSE;md5=d8c5dc22eb6f25667cf8d96f603635e7" inherit autotools +inherit mono SRC_URI = "https://github.com/mono/mono-basic/archive/${PV}.tar.gz"; -FILES_${PN} += " \ - ${libdir}/mono/*/* \ - ${libdir}/mono/gac/*/*/*.dll \ -" - -FILES_${PN}-dbg += " \ - ${libdir}/mono/*/*.mdb \ - ${libdir}/mono/*/*.Pdb \ - ${libdir}/mono/*/*.Mdb \ - ${libdir}/mono/*/*/*/*.mdb \ -" - do_compile_prepend() { sed -e "s|\$(prefix)|${STAGING_DIR_NATIVE}/usr|" -i build/profiles/net_4_0.make sed -e "s|\$(prefix)|${STAGING_DIR_NATIVE}/usr|" -i build/profiles/net_4_5.make -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 10/11] gtk-sharp-native: remove mono-native dependency
mono.bbclass already adds it so it's unnecessary here. Signed-off-by: Richard Tollerton --- recipes-mono/gtk-sharp/gtk-sharp-native_2.12.21.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-mono/gtk-sharp/gtk-sharp-native_2.12.21.bb b/recipes-mono/gtk-sharp/gtk-sharp-native_2.12.21.bb index 76eb770..6396b42 100644 --- a/recipes-mono/gtk-sharp/gtk-sharp-native_2.12.21.bb +++ b/recipes-mono/gtk-sharp/gtk-sharp-native_2.12.21.bb @@ -2,7 +2,7 @@ require gtk-sharp.inc inherit pkgconfig native -DEPENDS = "mono-native gtk+-native atk-native pango-native cairo-native glib-2.0-native libglade-native " +DEPENDS += " gtk+-native atk-native pango-native cairo-native glib-2.0-native libglade-native " LIC_FILES_CHKSUM = "files://COPYING;md5=f14599a2f089f6ff8c97e2baa4e3d575" -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 05/11] mono-addins: use mono.bbclass
Signed-off-by: Richard Tollerton --- recipes-mono/mono-addins/mono-addins.inc | 14 ++ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/recipes-mono/mono-addins/mono-addins.inc b/recipes-mono/mono-addins/mono-addins.inc index 767ad78..5549fb9 100644 --- a/recipes-mono/mono-addins/mono-addins.inc +++ b/recipes-mono/mono-addins/mono-addins.inc @@ -6,7 +6,7 @@ SECTION = "mono/applications" PRIORITY = "optional" LICENSE = "MIT" LIC_FILES_CHKSUM = "file://COPYING;md5=4e024d772d8266e3ff9747185842ca82" -DEPENDS = "mono gtk-sharp" +DEPENDS = "gtk-sharp" SRCREV = "64a45d96f39d4714ec85adf0fe04b68ec7273ae1" SRCBRANCH = "master" @@ -16,14 +16,4 @@ SRC_URI = "git://github.com/mono/mono-addins.git;branch=${SRCBRANCH}" S = "${WORKDIR}/git" inherit autotools pkgconfig - -FILES_${PN} += " \ - ${libdir}/mono/gac/* \ - ${libdir}/mono/gac/*/*/*.dll \ - ${libdir}/mono/gac/*/*/*.config \ - ${libdir}/mono/${PN}/* \ -" - -FILES_${PN}-dbg += " \ - ${libdir}/mono/gac/*/*/*.mdb \ -" +inherit mono -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 07/11] mono-xsp: use mono.bbclass
Signed-off-by: Richard Tollerton --- recipes-mono/mono-xsp/mono-xsp-3.x.inc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/recipes-mono/mono-xsp/mono-xsp-3.x.inc b/recipes-mono/mono-xsp/mono-xsp-3.x.inc index bee35ea..dac2b1a 100644 --- a/recipes-mono/mono-xsp/mono-xsp-3.x.inc +++ b/recipes-mono/mono-xsp/mono-xsp-3.x.inc @@ -1,11 +1,10 @@ DESCRIPTION = "Standalone web server written in C# that can be used to run ASP.NET applications" SECTION = "devel/mono" -DEPENDS = "mono" -RDEPENDS_${PN} = "mono" LICENSE = "MIT" LIC_FILES_CHKSUM = "file://COPYING;md5=9e1603e27acd337015fdfa7f7ff936c7" inherit autotools-brokensep +inherit mono SRC_URI = "https://github.com/mono/xsp/archive/${PV}.tar.gz"; -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 11/11] gtk-sharp: remove mono-native dependency
mono.bbclass already adds it so it's unnecessary here. Signed-off-by: Richard Tollerton --- recipes-mono/gtk-sharp/gtk-sharp_2.12.21.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-mono/gtk-sharp/gtk-sharp_2.12.21.bb b/recipes-mono/gtk-sharp/gtk-sharp_2.12.21.bb index 563da51..c72b0bb 100644 --- a/recipes-mono/gtk-sharp/gtk-sharp_2.12.21.bb +++ b/recipes-mono/gtk-sharp/gtk-sharp_2.12.21.bb @@ -2,7 +2,7 @@ require gtk-sharp.inc inherit pkgconfig -DEPENDS = "mono gtk+ atk pango cairo glib-2.0 libglade " +DEPENDS += " gtk+ atk pango cairo glib-2.0 libglade" LIC_FILES_CHKSUM = "files://COPYING;md5=f14599a2f089f6ff8c97e2baa4e3d575" -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 01/11] mono.bbclass: add
The DEPENDS_*, RDEPENDS_*, and FILES_* settings between C# packages share a lot in common. We can refactor these bits into their own bbclass: - DEPEND on mono-native because we need it to compile stuff - DEPEND on mono to have the native sysroot available - RDEPEND on mono to make sure we can run the package - ${PN} contains dlls, exes, and config bits thereof - ${PN}-dbg contains mono debug (mdb) files - ${PN}-dev contains: - build response (rsp) files - machine-readable assembly documentation (xml) - xbuild-related files - ${PN}-doc contains monodoc output Some C# packages build native code, though, so don't set PACKAGE_ARCH="all". Signed-off-by: Richard Tollerton --- classes/mono.bbclass | 32 1 file changed, 32 insertions(+) create mode 100644 classes/mono.bbclass diff --git a/classes/mono.bbclass b/classes/mono.bbclass new file mode 100644 index 000..315ee82 --- /dev/null +++ b/classes/mono.bbclass @@ -0,0 +1,32 @@ +# Class for building C# packages. If your package is all-managed, add +# PACKAGE_ARCH="all" + +DEPENDS += "mono-native mono" +RDEPENDS_${PN} += "mono" + +FILES_${PN} += "\ + ${libdir}/mono/*/*.exe \ + ${libdir}/mono/*/*.dll \ + ${libdir}/mono/*/*.config \ + ${libdir}/mono/gac/*/*/*.dll \ + ${libdir}/mono/gac/*/*/*.*.config \ +" + +FILES_${PN}-dbg += "\ + ${libdir}/mono/*/*.mdb \ + ${libdir}/mono/gac/*/*/*.mdb \ +" + +FILES_${PN}-dev += "\ + ${libdir}/mono/*/*.rsp \ + ${libdir}/mono/*/*.xml \ + ${libdir}/mono/gac/*/*/*.xml \ + ${libdir}/mono/xbuild/* \ + ${libdir}/mono/xbuild-frameworks/* \ + ${libdir}/mono/Microsoft* \ + ${libdir}/mono/*/*.Targets \ +" + +FILES_${PN}-doc += "\ + ${libdir}/monodoc/* \ +" -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 04/11] fsharp.inc: use mono.bbclass
Signed-off-by: Richard Tollerton --- recipes-mono/fsharp/fsharp.inc | 19 +-- 1 file changed, 1 insertion(+), 18 deletions(-) diff --git a/recipes-mono/fsharp/fsharp.inc b/recipes-mono/fsharp/fsharp.inc index 25c41b6..f5bdcc1 100644 --- a/recipes-mono/fsharp/fsharp.inc +++ b/recipes-mono/fsharp/fsharp.inc @@ -1,36 +1,19 @@ SUMMARY = "F# programming language" DESCRIPTION = "F# is a strongly-typed, functional-first programming language for writing simple code to solve complex problems." SECTION = "devel/mono" -DEPENDS = "mono" LICENSE = "Apache-2.0" LIC_FILES_CHKSUM = "files://LICENSE;md5=512efb9375da0bd2fee9e2b9352c08af" inherit autotools-brokensep +inherit mono # For some reason the URL template changes from version to version, # therefore use some variables for the directory and extension SRC_URI = "https://github.com/fsharp/fsharp/archive/${PV}.tar.gz"; FILES_${PN} += "\ - ${libdir}/mono/*/*.exe \ - ${libdir}/mono/*/*.dll \ - ${libdir}/mono/*/*.config \ ${libdir}/mono/*/*.optdata \ ${libdir}/mono/*/*.sigdata \ - ${libdir}/mono/gac/*/*/*.config \ ${libdir}/mono/gac/*/*/*.optdata \ ${libdir}/mono/gac/*/*/*.sigdata \ " - -FILES_${PN}-dbg += "\ - ${libdir}/mono/gac/*/*/*.mdb \ -" - -FILES_${PN}-dev = "\ - ${libdir}/mono/xbuild/* \ - ${libdir}/mono/xbuild-frameworks/* \ - ${libdir}/mono/Microsoft* \ - ${libdir}/mono/*/*.Targets \ - ${libdir}/mono/*/*.xml \ - ${libdir}/mono/gac/*/*/*.xml \ -" -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 00/11] Refactor common mono build bits into mono.bbclass
Building CLI packages involves lots of boilerplate recipe settings, particularly involving FILES and DEPENDS. This is a first attempt at refactoring these settings into a single bbclass that can be inherited by all CLI packages that do not require unusual build settings. I attempted to refactor every recipe in the layer with these exceptions: - cefglue, because it doesn't actually install anything (!) - monotools-server, because I haven't been able to build it successfully - mono-upnp and taglib-sharp because I don't use them The following changes since commit 136ed556de19bd497279d6c3ae8704551fb1ec4d: mono-xsp-3.x.inc: use autogen.sh (2015-07-16 18:56:23 +0100) are available in the git repository at: git://github.com/rtollert/meta-mono dev/rtollert/v4/bbclass https://github.com/rtollert/meta-mono/tree/dev/rtollert/v4/bbclass Richard Tollerton (11): mono.bbclass: add dbus-sharp-glib: use mono.bbclass dbus-sharp: use mono.bbclass fsharp.inc: use mono.bbclass mono-addins: use mono.bbclass mono-helloworld: use mono.bbclass mono-xsp: use mono.bbclass mono-basic-4.xx.inc: use mono.bbclass gtk-sharp.inc: use mono.bbclass and make some FILES fixes gtk-sharp-native: remove mono-native dependency gtk-sharp: remove mono-native dependency classes/mono.bbclass | 32 ++ recipes-mono/dbus-sharp-glib/dbus-sharp-glib.inc | 13 ++--- recipes-mono/dbus-sharp/dbus-sharp.inc | 13 + recipes-mono/fsharp/fsharp.inc | 19 + recipes-mono/gtk-sharp/gtk-sharp-native_2.12.21.bb | 2 +- recipes-mono/gtk-sharp/gtk-sharp.inc | 23 +++- recipes-mono/gtk-sharp/gtk-sharp_2.12.21.bb| 2 +- recipes-mono/mono-addins/mono-addins.inc | 14 ++ recipes-mono/mono-basic/mono-basic-4.xx.inc| 13 + recipes-mono/mono-helloworld/mono-helloworld.inc | 4 +-- recipes-mono/mono-xsp/mono-xsp-3.x.inc | 3 +- 11 files changed, 47 insertions(+), 91 deletions(-) create mode 100644 classes/mono.bbclass -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 06/11] mono-helloworld: use mono.bbclass
Signed-off-by: Richard Tollerton --- recipes-mono/mono-helloworld/mono-helloworld.inc | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/recipes-mono/mono-helloworld/mono-helloworld.inc b/recipes-mono/mono-helloworld/mono-helloworld.inc index 8fa046f..d63ca8c 100644 --- a/recipes-mono/mono-helloworld/mono-helloworld.inc +++ b/recipes-mono/mono-helloworld/mono-helloworld.inc @@ -6,16 +6,14 @@ SECTION = "mono/applications" PRIORITY = "optional" LICENSE = "GPLv3" LIC_FILES_CHKSUM = "file://LICENSE;md5=783b7e40cdfb4a1344d15b1f7081af66" -DEPENDS = "mono" SRC_URI = "https://github.com/DynamicDevices/mono-helloworld/archive/v${PV}.tar.gz"; inherit autotools +inherit mono FILES_${PN} = "${libdir}/helloworld/helloworld.exe \ ${bindir}/helloworld \ ${libdir}/helloworld/helloworldform.exe \ ${bindir}/helloworldform \ " - -RDEPENDS_${PN} += "mono" -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 03/11] dbus-sharp: use mono.bbclass
Signed-off-by: Richard Tollerton --- recipes-mono/dbus-sharp/dbus-sharp.inc | 13 + 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/recipes-mono/dbus-sharp/dbus-sharp.inc b/recipes-mono/dbus-sharp/dbus-sharp.inc index 243b489..a458082 100644 --- a/recipes-mono/dbus-sharp/dbus-sharp.inc +++ b/recipes-mono/dbus-sharp/dbus-sharp.inc @@ -1,11 +1,11 @@ SUMMARY = "C# implementation of D-Bus" DESCRIPTION = "An inter-process communication framework that lets applications interface with the system event bus as well as allowing them to talk to one another in a peer-to-peer configuration." SECTION = "devel/mono" -DEPENDS = "mono" LICENSE = "MIT" LIC_FILES_CHKSUM = "files://COPYING;md5=09d60852216ea29fdba9ea146513336c" inherit autotools +inherit mono def dbus_sharp_download_version(d): pvsplit = d.getVar('PV', True).split('.') @@ -18,14 +18,3 @@ SRC_URI = "https://github.com/mono/dbus-sharp/archive/v${SDIRVER}.tar.gz"; S = "${WORKDIR}/${PN}-${SDIRVER}" FILESPATH =. "${FILE_DIRNAME}/${PN}-${PV}:" - -FILES_${PN} += " \ - ${libdir}/mono/dbus-sharp-2.0/* \ - ${libdir}/mono/gac/dbus-sharp/*/*.dll \ - ${libdir}/mono/gac/dbus-sharp/*/*.config \ -" - -FILES_${PN}-dbg += " \ - ${libdir}/mono/gac/dbus-sharp/*/*.mdb \ -" - -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-mono] [PATCH 4/4] mono-xsp-3.x.inc: use autogen.sh
Alex J Lennon writes: > Many thanks for the updates, fixes, and cleanups Richard. Your > patch-sets for mono-xsp, fsharp, mono-basic are applied. > > In future can you remove any trailing newlines from your patches > please? You're welcome! Yes, I will get those removed in future pull requests. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-mono] [PATCH 4/4] mono-xsp-3.x.inc: use autogen.sh
On 16/07/2015 18:22, Richard Tollerton wrote: > The following build failure was observed: > > | Makefile.am:7: error: BUILD_DOCS does not appear in AM_CONDITIONAL > > This occurs because aclocal must be called with "-I build/m4/shamrock -I > build/m4/shave", as is done in autogen.sh. > > I tried adding those includes to EXTRA_AUTORECONF or acpaths. That seems > to only partially solve the problem, as MONO_MODULE remains undefined > and unsubstituted in configure, leading to: > > | xsp-3.0.11/configure: line 2651: syntax error near unexpected token > `MONO_MODULE,' > > This might have something to do with the `automake --gnu` option in > autogen.sh. I don't know for certain > > In any case, merely calling autogen.sh does work. This patch implements > that, using autotools.bbclass:oe_runconf() as a template. > > Signed-off-by: Richard Tollerton > --- > recipes-mono/mono-xsp/mono-xsp-3.x.inc | 11 +++ > 1 file changed, 11 insertions(+) > > diff --git a/recipes-mono/mono-xsp/mono-xsp-3.x.inc > b/recipes-mono/mono-xsp/mono-xsp-3.x.inc > index ffe0a28..77af516 100644 > --- a/recipes-mono/mono-xsp/mono-xsp-3.x.inc > +++ b/recipes-mono/mono-xsp/mono-xsp-3.x.inc > @@ -9,6 +9,17 @@ inherit autotools-brokensep > > SRC_URI = "https://github.com/mono/xsp/archive/${PV}.tar.gz"; > > +do_configure () { > +set +e > +${CACHED_CONFIGUREVARS} ${S}/autogen.sh --verbose ${CONFIGUREOPTS} > ${EXTRA_OECONF} > +if [ "$?" != "0" ]; then > + echo "Configure failed. The contents of all config.log files follows to > aid debugging" > + find ${S} -name config.log -print -exec cat {} \; > + bbfatal "oe_runconf failed" > +fi > +set -e > +} > + > S = "${WORKDIR}/xsp-${PV}" > > PACKAGES += "${PN}-test \ Many thanks for the updates, fixes, and cleanups Richard. Your patch-sets for mono-xsp, fsharp, mono-basic are applied. In future can you remove any trailing newlines from your patches please? Thanks, Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH] firmware.inc: fetch from SVN instead of Git
Hi all, > > > > So there is no support for depth clones until 2.5.0? I didn't really > > understand. > > Well, shallow clones are supported but only for branch tips, which is > not what we need. This feature for shallow cloning a specific revision > is available only in git 2.5.0+. Also, this feature needs a server-side > configuration option to be enabled, in order to work properly. > > Regards, > Nikolay > I'd argue that this whole issue with the whole meta-raspberrypi firmware.inc download is more than just slow, inconvenient download. I've left builds running all night (8+ hours on a 30Mib/s residential link) that just hang on this, usually timing out. I initially thought it was just me, but am hearing others confirm this as well. As such, I just wanted to continue this conversation. It sounds like git fetch's --depth is the best option on the table, but has the issues Nikolay has described. What are your thoughts on the following? (1) We create a git-native and build a version that supports this the fetch depth? I suspect this could be made to work, but haven't dug into what dependencies git may have and how that would play out on various LTS distros. My knee-jerk is that has too high of a risk/benefit ration, given that we're talking about 1 repo. (2) We update the git fetcher to check the git version and support a depth= option if the git version is sufficient. If it is not, we spit out a warning and fall back to the current behavior. Neither (1) nor (2) address Nikolay's point that --depth requires server-side support. However, I'd argue this is something you'd be testing and verifying when writing the recipe. Is this a reasonable assertion? How likely is it that a server supporting this would suddenly be re-configured? (3) We request that the upstream maintainer of meta-raspberrypi use the GitHub Release feature [a] to post a tarball of a known checksum at somewhat regular intervals. I'm told by a few package maintainers that while the tarballs that it generates for specific changesets are subject to change, that the tarballs it autogenerates when using its Releases feature do not. However, I have not confirmed this. If this is false, then one can upload a tarball with known checksums to the release as an attachment; I would be *shocked* if they touch your attachments. While (3) is a nice "not our problem" solution, I think (2) might have some benefits for other recipes later. Any other ideas? Best regards, Jon [a] https://help.github.com/articles/creating-releases/ -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 4/4] mono-xsp-3.x.inc: use autogen.sh
The following build failure was observed: | Makefile.am:7: error: BUILD_DOCS does not appear in AM_CONDITIONAL This occurs because aclocal must be called with "-I build/m4/shamrock -I build/m4/shave", as is done in autogen.sh. I tried adding those includes to EXTRA_AUTORECONF or acpaths. That seems to only partially solve the problem, as MONO_MODULE remains undefined and unsubstituted in configure, leading to: | xsp-3.0.11/configure: line 2651: syntax error near unexpected token `MONO_MODULE,' This might have something to do with the `automake --gnu` option in autogen.sh. I don't know for certain In any case, merely calling autogen.sh does work. This patch implements that, using autotools.bbclass:oe_runconf() as a template. Signed-off-by: Richard Tollerton --- recipes-mono/mono-xsp/mono-xsp-3.x.inc | 11 +++ 1 file changed, 11 insertions(+) diff --git a/recipes-mono/mono-xsp/mono-xsp-3.x.inc b/recipes-mono/mono-xsp/mono-xsp-3.x.inc index ffe0a28..77af516 100644 --- a/recipes-mono/mono-xsp/mono-xsp-3.x.inc +++ b/recipes-mono/mono-xsp/mono-xsp-3.x.inc @@ -9,6 +9,17 @@ inherit autotools-brokensep SRC_URI = "https://github.com/mono/xsp/archive/${PV}.tar.gz"; +do_configure () { +set +e +${CACHED_CONFIGUREVARS} ${S}/autogen.sh --verbose ${CONFIGUREOPTS} ${EXTRA_OECONF} +if [ "$?" != "0" ]; then + echo "Configure failed. The contents of all config.log files follows to aid debugging" + find ${S} -name config.log -print -exec cat {} \; + bbfatal "oe_runconf failed" +fi +set -e +} + S = "${WORKDIR}/xsp-${PV}" PACKAGES += "${PN}-test \ -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 3/4] mono-xsp_3.0.11.bb: add
Signed-off-by: Richard Tollerton --- recipes-mono/mono-xsp/mono-xsp_3.0.11.bb | 5 + 1 file changed, 5 insertions(+) create mode 100644 recipes-mono/mono-xsp/mono-xsp_3.0.11.bb diff --git a/recipes-mono/mono-xsp/mono-xsp_3.0.11.bb b/recipes-mono/mono-xsp/mono-xsp_3.0.11.bb new file mode 100644 index 000..196ca32 --- /dev/null +++ b/recipes-mono/mono-xsp/mono-xsp_3.0.11.bb @@ -0,0 +1,5 @@ +require mono-xsp-3.x.inc + +SRC_URI[md5sum] = "6a694d5e87ebe57e532ec80a16b6966d" +SRC_URI[sha256sum] = "290e302a03396c5cff7eb53dae008e9f79dd00aca15ad1e62865907220483baa" + -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 2/4] mono-xsp-3.x.inc: updating SRC_URI and LIC_FILES_CHKSUM
Signed-off-by: Richard Tollerton --- recipes-mono/mono-xsp/mono-xsp-3.x.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/recipes-mono/mono-xsp/mono-xsp-3.x.inc b/recipes-mono/mono-xsp/mono-xsp-3.x.inc index add1199..ffe0a28 100644 --- a/recipes-mono/mono-xsp/mono-xsp-3.x.inc +++ b/recipes-mono/mono-xsp/mono-xsp-3.x.inc @@ -3,11 +3,11 @@ SECTION = "devel/mono" DEPENDS = "mono" RDEPENDS_${PN} = "mono" LICENSE = "MIT" -LIC_FILES_CHKSUM = "file://COPYING;md5=84b17f6d63c3c28399d0f3786831d40c" +LIC_FILES_CHKSUM = "file://COPYING;md5=9e1603e27acd337015fdfa7f7ff936c7" inherit autotools-brokensep -SRC_URI = "http://download.mono-project.com/sources/xsp/xsp-${PV}.tar.bz2"; +SRC_URI = "https://github.com/mono/xsp/archive/${PV}.tar.gz"; S = "${WORKDIR}/xsp-${PV}" -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 1/4] mono-xsp-3.x.inc: copy from mono-xsp.inc
Signed-off-by: Richard Tollerton --- recipes-mono/mono-xsp/mono-xsp-3.x.inc | 33 + 1 file changed, 33 insertions(+) create mode 100644 recipes-mono/mono-xsp/mono-xsp-3.x.inc diff --git a/recipes-mono/mono-xsp/mono-xsp-3.x.inc b/recipes-mono/mono-xsp/mono-xsp-3.x.inc new file mode 100644 index 000..add1199 --- /dev/null +++ b/recipes-mono/mono-xsp/mono-xsp-3.x.inc @@ -0,0 +1,33 @@ +DESCRIPTION = "Standalone web server written in C# that can be used to run ASP.NET applications" +SECTION = "devel/mono" +DEPENDS = "mono" +RDEPENDS_${PN} = "mono" +LICENSE = "MIT" +LIC_FILES_CHKSUM = "file://COPYING;md5=84b17f6d63c3c28399d0f3786831d40c" + +inherit autotools-brokensep + +SRC_URI = "http://download.mono-project.com/sources/xsp/xsp-${PV}.tar.bz2"; + +S = "${WORKDIR}/xsp-${PV}" + +PACKAGES += "${PN}-test \ + ${PN}-unittest \ +" + +FILES_${PN}-test = "${libdir}/xsp/test/*" + +FILES_${PN}-unittest = "${libdir}/xsp/unittests/*" + +FILES_${PN}-doc += "${libdir}/monodoc/*" + +# AJL - For now we are going to parcel up the different XSP hosting (mod_mono, fastcgi, xsp) together. More granular packages in future +FILES_${PN} = "${bindir}/* \ + ${libdir}/mono/* \ + ${libdir}/xsp/2.0/* \ + ${libdir}/xsp/4.0/* \ +" + +# We seem to run into problems with make parallelisation building mono-xsp, so disable it for now +PARALLEL_MAKE = "" + -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 0/4] mono-xsp: upgrade and fix build
I ran into some fairly bad build issues when trying to build mono-xsp that appear to be worked around by using mono-xsp's autogen.sh instead of letting autotools.bbclass attempt to call everything itself. I then took the opportunity to upgrade the package to 3.0. I haven't actually tested these changes -- I was under the mistaken impression that monotools-server was necessary for remote debugging to work with mono4, and figured that I might as well not let these changes go to waste, even though I will probably not use them. The following changes since commit 8c613bf3d82dd5edb58472e5b016d86a1a9e4a63: README: Add contributors section (2015-07-16 10:17:06 +0100) are available in the git repository at: git://github.com/rtollert/meta-mono dev/rtollert/v3/mono-xsp https://github.com/rtollert/meta-mono/tree/dev/rtollert/v3/mono-xsp Richard Tollerton (4): mono-xsp-3.x.inc: copy from mono-xsp.inc mono-xsp-3.x.inc: updating SRC_URI and LIC_FILES_CHKSUM mono-xsp_3.0.11.bb: add mono-xsp-3.x.inc: use autogen.sh recipes-mono/mono-xsp/mono-xsp-3.x.inc | 44 recipes-mono/mono-xsp/mono-xsp_3.0.11.bb | 5 2 files changed, 49 insertions(+) create mode 100644 recipes-mono/mono-xsp/mono-xsp-3.x.inc create mode 100644 recipes-mono/mono-xsp/mono-xsp_3.0.11.bb -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 1/3] fsharp_3.1.2.4.bb: add
There are several build issues in 3.1.1.1 that appear to be fixed in 3.1.2.4, so rather than try to fix the old version, add the new one. Signed-off-by: Richard Tollerton --- recipes-mono/fsharp/fsharp_3.1.2.4.bb | 7 +++ 1 file changed, 7 insertions(+) create mode 100644 recipes-mono/fsharp/fsharp_3.1.2.4.bb diff --git a/recipes-mono/fsharp/fsharp_3.1.2.4.bb b/recipes-mono/fsharp/fsharp_3.1.2.4.bb new file mode 100644 index 000..6e21d72 --- /dev/null +++ b/recipes-mono/fsharp/fsharp_3.1.2.4.bb @@ -0,0 +1,7 @@ +require fsharp.inc + +inherit pkgconfig + +SRC_URI[md5sum] = "6b86979034d15efb1d5e167129ae7a9e" +SRC_URI[sha256sum] = "cf3b5ea00fd13b9d35f5a4ffec6fbd8cecc2c4039d09a79fb0e3f7fa48da9429" + -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 3/3] fsharp.inc: refactor FILES_*
fsharp was failing the 'debug-deps' QA test, i.e. fsharp depended on fsharp-dbg because fsharp's file list included files that properly belong to fsharp-dbg. Fix this by being more explicit about the types of files that ship in fsharp vs fsharp-dbg. Generalize file patterns as appropriate to make file lists more concise and robust; i.e. replace mono/4.0/*, mono/2.0/* with mono/*/*. Move .xml (machine-readable assembly docs), .rsp, .Targets, etc. into fsharp-dev. Signed-off-by: Richard Tollerton --- recipes-mono/fsharp/fsharp.inc | 52 +- 1 file changed, 16 insertions(+), 36 deletions(-) diff --git a/recipes-mono/fsharp/fsharp.inc b/recipes-mono/fsharp/fsharp.inc index acb17ce..25c41b6 100644 --- a/recipes-mono/fsharp/fsharp.inc +++ b/recipes-mono/fsharp/fsharp.inc @@ -12,45 +12,25 @@ inherit autotools-brokensep SRC_URI = "https://github.com/fsharp/fsharp/archive/${PV}.tar.gz"; FILES_${PN} += "\ - ${libdir}/mono/* \ - ${libdir}/mono/4.0/* \ - ${libdir}/mono/2.0/* \ - ${libdir}/mono/xbuild/Microsoft/VisualStudio/* \ - ${libdir}/mono/Microsoft F#/v4.0/* \ - ${libdir}/mono/Microsoft SDKs/F#/3.0/* \ - ${libdir}/mono/Microsoft SDKs/F#/3.1/* \ - ${libdir}/mono/gac/* \ - ${libdir}/mono/gac/*/* \ - ${libdir}/mono/gac/*/*/* \ - ${libdir}/mono/monotouch/* \ - ${libdir}/mono/monodroid/* \ + ${libdir}/mono/*/*.exe \ + ${libdir}/mono/*/*.dll \ + ${libdir}/mono/*/*.config \ + ${libdir}/mono/*/*.optdata \ + ${libdir}/mono/*/*.sigdata \ + ${libdir}/mono/gac/*/*/*.config \ + ${libdir}/mono/gac/*/*/*.optdata \ + ${libdir}/mono/gac/*/*/*.sigdata \ " FILES_${PN}-dbg += "\ - ${libdir}/mono/*.mdb \ - ${libdir}/mono/4.0/*.mdb \ - ${libdir}/mono/4.0/*.optdata \ - ${libdir}/mono/4.0/*.sigdatadata \ - ${libdir}/mono/2.0/*.mdb \ - ${libdir}/mono/2.0/*.optdata \ - ${libdir}/mono/2.0/*.sigdata \ - ${libdir}/mono/xbuild/Microsoft/VisualStudio/*.mdb \ - ${libdir}/mono/Microsoft F#/v4.0/*.mdb \ - ${libdir}/mono/Microsoft SDKs/F#/3.0/*.mdb \ - ${libdir}/mono/Microsoft SDKs/F#/3.1/*.mdb \ - ${libdir}/mono/gac/*.mdb \ - ${libdir}/mono/gac/*/*.mdb \ ${libdir}/mono/gac/*/*/*.mdb \ - ${libdir}/mono/gac/*/*/*.xml \ - ${libdir}/mono/gac/*/*/*.optdata \ - ${libdir}/mono/gac/*/*/*.sigdata \ - ${libdir}/mono/monotouch/*.mdb \ - ${libdir}/mono/monotouch/*.xml \ - ${libdir}/mono/monotouch/*.sigdata \ - ${libdir}/mono/monotouch/*.optdata \ - ${libdir}/mono/monodroid/*.mdb \ - ${libdir}/mono/monodroid/*.xml \ - ${libdir}/mono/monodroid/*.optdata \ - ${libdir}/mono/monodroid/*.sigdata \ " +FILES_${PN}-dev = "\ + ${libdir}/mono/xbuild/* \ + ${libdir}/mono/xbuild-frameworks/* \ + ${libdir}/mono/Microsoft* \ + ${libdir}/mono/*/*.Targets \ + ${libdir}/mono/*/*.xml \ + ${libdir}/mono/gac/*/*/*.xml \ +" -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 2/3] fsharp: disable build separation
The fsharp build isn't compatible with separate build dirs. [fsharp #438] -- https://github.com/fsharp/fsharp/issues/438 Signed-off-by: Richard Tollerton --- recipes-mono/fsharp/fsharp.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-mono/fsharp/fsharp.inc b/recipes-mono/fsharp/fsharp.inc index d217ec5..acb17ce 100644 --- a/recipes-mono/fsharp/fsharp.inc +++ b/recipes-mono/fsharp/fsharp.inc @@ -5,7 +5,7 @@ DEPENDS = "mono" LICENSE = "Apache-2.0" LIC_FILES_CHKSUM = "files://LICENSE;md5=512efb9375da0bd2fee9e2b9352c08af" -inherit autotools +inherit autotools-brokensep # For some reason the URL template changes from version to version, # therefore use some variables for the directory and extension -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 0/3] fsharp: build fixes and refactors
I ran into some build issues with fsharp (mono4 related IIRC) that were resolved by upgrading it. I also noticed that the build needs autotools-brokensep so I added that too. There was also a QA failure (debug-deps). Given that opportunity, I also refactored the FILES_* settings. The following changes since commit 8c613bf3d82dd5edb58472e5b016d86a1a9e4a63: README: Add contributors section (2015-07-16 10:17:06 +0100) are available in the git repository at: git://github.com/rtollert/meta-mono dev/rtollert/v3/fsharp https://github.com/rtollert/meta-mono/tree/dev/rtollert/v3/fsharp Richard Tollerton (3): fsharp_3.1.2.4.bb: add fsharp: disable build separation fsharp.inc: refactor FILES_* recipes-mono/fsharp/fsharp.inc| 54 +++ recipes-mono/fsharp/fsharp_3.1.2.4.bb | 7 + 2 files changed, 24 insertions(+), 37 deletions(-) create mode 100644 recipes-mono/fsharp/fsharp_3.1.2.4.bb -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 1/2] mono-basic-4.xx.inc: copy from mono-basic.inc
Signed-off-by: Richard Tollerton --- recipes-mono/mono-basic/mono-basic-4.xx.inc | 33 + 1 file changed, 33 insertions(+) create mode 100644 recipes-mono/mono-basic/mono-basic-4.xx.inc diff --git a/recipes-mono/mono-basic/mono-basic-4.xx.inc b/recipes-mono/mono-basic/mono-basic-4.xx.inc new file mode 100644 index 000..ad26924 --- /dev/null +++ b/recipes-mono/mono-basic/mono-basic-4.xx.inc @@ -0,0 +1,33 @@ +DESCRIPTION = "Visual Basic.NET support in Mono" +SECTION = "devel/mono" +DEPENDS = "mono" +RDEPENDS_${PN} = "mono" +LICENSE = "LGPLv2" +LIC_FILES_CHKSUM = "file://LICENSE;md5=d8c5dc22eb6f25667cf8d96f603635e7" + +inherit autotools + +SRC_URI = "http://download.mono-project.com/sources/mono-basic/mono-basic-${PV}.tar.bz2"; + +FILES_${PN} += " \ + ${libdir}/mono/*/* \ + ${libdir}/mono/gac/*/*/*.dll \ +" + +FILES_${PN}-dbg += " \ + ${libdir}/mono/*/*.mdb \ + ${libdir}/mono/*/*.Pdb \ + ${libdir}/mono/*/*.Mdb \ + ${libdir}/mono/*/*/*/*.mdb \ +" + +do_compile_prepend() { + sed -e "s|\$(prefix)|${STAGING_DIR_NATIVE}/usr|" -i build/profiles/net_2_0.make + sed -e "s|\$(prefix)|${STAGING_DIR_NATIVE}/usr|" -i build/profiles/net_4_0.make +} + +do_install_append() { + install -d "${D}${libdir}/mono/4.5" + ln -sf ${libdir}/mono/4.0/Microsoft.VisualBasic.dll ${D}${libdir}/mono/4.5/Microsoft.VisualBasic.dll +} + -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 2/2] mono-basic: add version 4.0
Signed-off-by: Richard Tollerton --- recipes-mono/mono-basic/mono-basic-4.xx.inc | 4 ++-- recipes-mono/mono-basic/mono-basic_4.0.bb | 5 + 2 files changed, 7 insertions(+), 2 deletions(-) create mode 100644 recipes-mono/mono-basic/mono-basic_4.0.bb diff --git a/recipes-mono/mono-basic/mono-basic-4.xx.inc b/recipes-mono/mono-basic/mono-basic-4.xx.inc index ad26924..1eec933 100644 --- a/recipes-mono/mono-basic/mono-basic-4.xx.inc +++ b/recipes-mono/mono-basic/mono-basic-4.xx.inc @@ -7,7 +7,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=d8c5dc22eb6f25667cf8d96f603635e7" inherit autotools -SRC_URI = "http://download.mono-project.com/sources/mono-basic/mono-basic-${PV}.tar.bz2"; +SRC_URI = "https://github.com/mono/mono-basic/archive/${PV}.tar.gz"; FILES_${PN} += " \ ${libdir}/mono/*/* \ @@ -22,8 +22,8 @@ FILES_${PN}-dbg += " \ " do_compile_prepend() { - sed -e "s|\$(prefix)|${STAGING_DIR_NATIVE}/usr|" -i build/profiles/net_2_0.make sed -e "s|\$(prefix)|${STAGING_DIR_NATIVE}/usr|" -i build/profiles/net_4_0.make + sed -e "s|\$(prefix)|${STAGING_DIR_NATIVE}/usr|" -i build/profiles/net_4_5.make } do_install_append() { diff --git a/recipes-mono/mono-basic/mono-basic_4.0.bb b/recipes-mono/mono-basic/mono-basic_4.0.bb new file mode 100644 index 000..af674cd --- /dev/null +++ b/recipes-mono/mono-basic/mono-basic_4.0.bb @@ -0,0 +1,5 @@ +require mono-basic-4.xx.inc + +SRC_URI[md5sum] = "c0783a53234ba878a103fcbc2f10630d" +SRC_URI[sha256sum] = "1760936b2b4d780fb69ccf230280216836d28a2c49d08f483afe2c3192d8359d" + -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mono] [PATCH 0/2] upgrade mono-basic to 4.0
I don't use mono-basic and haven't tested it -- I just noticed there was a newer version. This is the first of three patchsets for mono packages, to prepare for two additional patchsets I will submit on top of these three: 1. Refactoring common mono recipe variables into a bbclass 2. Setting PACKAGE_ARCH=all on packages with all-managed code The following changes since commit 8c613bf3d82dd5edb58472e5b016d86a1a9e4a63: README: Add contributors section (2015-07-16 10:17:06 +0100) are available in the git repository at: git://github.com/rtollert/meta-mono dev/rtollert/v3/mono-basic https://github.com/rtollert/meta-mono/tree/dev/rtollert/v3/mono-basic Richard Tollerton (2): mono-basic-4.xx.inc: copy from mono-basic.inc mono-basic: add version 4.0 recipes-mono/mono-basic/mono-basic-4.xx.inc | 33 + recipes-mono/mono-basic/mono-basic_4.0.bb | 5 + 2 files changed, 38 insertions(+) create mode 100644 recipes-mono/mono-basic/mono-basic-4.xx.inc create mode 100644 recipes-mono/mono-basic/mono-basic_4.0.bb -- 2.4.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] meta-toolchain uclibc issue
Hello All, I'm trying to build a cross compiler toolchain for PowerPC (mpc8544). I'm able to successfully bitbake the meta-toolchain target for glibc, when I check inside the sysroot directory of the sdk, I find the following directories: ppce500v2-poky-linux-gnuspe x86_64-pokysdk-linux The directory ppce500v2-poky-linux-gnuspe, contains root filesystem for target (ppc500v2). The directory x86_64-pokysdk-linux, contains the cross development tools, for my host, particularly gcc (powerpc-poky-linux-gnuspe-gcc) If I execute: powerpc-poky-linux-gnuspe-gcc -v the target is set to: powerpc-poky-linux which I interpret to mean a powerpc based target with glibc&linux I want to build a uclibc toolchain: to this I understand you need to add the following line to my local.conf: TCLIBC = "uclibc" After doing so, I am again able successfully build the target meta-toolchain. Again if I look inside the sysroot directory two directories have been created: ppce500v2-poky-linux-uclibcspe x86_64-pokysdk-linux ppce500v2-poky-linux-uclibcspe, this time the root filesystem is based on uclibc and this is refelected in the name. x86_64-pokysdk-linux, again a directory to hold the host tools has been created. The gcc tools are located in under directory ./usr/bin/powerpc-poky-linux-gnuspe as before, If I execute: powerpc-poky-linux-gnuspe-gcc -v the target is set to: powerpc-poky-linux However given that I've selected uclibc, I was expecting the gcc tools to be located under a directory: ./usr/bin/powerpc-poky-linux-uclibcspe to reflect the fact that the tools are targeting uclibc. If I look inside the environment script created by the meta-toolchain target it shares this expectation as is reflected by the extract for CC envvar: export CC="powerpc-poky-linux-uclibcspe-gcc -m32 -mcpu=8548 -mabi=spe -mspe -mfloat-gprs=double --sysroot=$SDKTARGETSYSROOT" If I search the files created by the target meta-toolchain, it has actually created an apprpriate gcc located deeply nested under the work diretcory, a gcc toolset of the correct form has been created, namely: powerpc-poky-linux-uclibcspe-g++ Just to confirm when I run with the -v option it shows its target as: powerpc-poky-linux-uclibcspe Can someone clarify what's happening here?!? 1. Are my expectations correct? 2. If so, why is the correct toolchain created, but not put in the correct place by the populate-sdk target? Thanks in advance for any help you can provide! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Read-only file system with persistent storage
Hi Gary, I'm interested in that too. In my case I want to have a reset-to-factory-defaults-button on my device. The idea was use an readonly filesystem and, on top of it, a read-write filesystem. All modifications goes to top-half, once the RTFD button is pressed the top-half is formated and the system goes back to its instalattion. I have no ideia about support for that on Yocto, I know of OverlayFS existence only. I think its possible but I don't know really how to do it, also never tried. I'm just fearing that dealing with OverlayFS on rootfs could be a headache. Anyway, take a look on this: https://www.kernel.org/doc/Documentation/filesystems/overlayfs.txt Best regards - dhs 2015-07-16 8:36 GMT-03:00 Gary Thomas : > I'd like to set up a system with a read-only root file system > along with some persistent read-write storage. What are the > [best] options in Poky/Yocto for this? Is there any support > for some type of overlay file system? > > Thanks for any ideas/pointers > > -- > > Gary Thomas | Consulting for the > MLB Associates |Embedded world > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- *"Do or do not. There is no try"* *Yoda Master* -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Read-only file system with persistent storage
I'd like to set up a system with a read-only root file system along with some persistent read-write storage. What are the [best] options in Poky/Yocto for this? Is there any support for some type of overlay file system? Thanks for any ideas/pointers -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [yocto-docs][PATCH] ref-manual: fix example of setting root password using extrausers
We need to use usermod here not useradd. Signed-off-by: Paul Eggleton --- documentation/ref-manual/ref-classes.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml index d482ca0..253079d 100644 --- a/documentation/ref-manual/ref-classes.xml +++ b/documentation/ref-manual/ref-classes.xml @@ -860,7 +860,7 @@ inherit extrausers EXTRA_USERS_PARAMS = "\ - useradd -P 1876*18 root; \ + usermod -P 1876*18 root; \ " -- 2.1.0 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-mono] [PATCH 0/1] mono: use PARALLEL_MAKEINST="" instead of PARALLEL_MAKE=""
On 16/07/2015 02:25, Richard Tollerton wrote: > Hi, last week I sent out a patch to disable parallel builds in mono; in > hindsight I should have used PARALLEL_MAKEINST instead of PARALLEL_MAKE. Patch > follows. > > This is one of several topic branches I've hacked together over the last > couple > of weeks; you can see the rest at https://github.com/rtollert/meta-mono. I'll > be meting them out over the next several days. > > > The following changes since commit 9f63cbaaa859f9ae55288de06c1c0eb0e6992f53: > > mono-4.xx.inc: disable parallel make (2015-07-08 11:46:11 +0100) > > are available in the git repository at: > > git://github.com/rtollert/meta-mono dev/rtollert/v2/parallel > https://github.com/rtollert/meta-mono/tree/dev/rtollert/v2/parallel > > Richard Tollerton (1): > mono-4.xx.inc: use PARALLEL_MAKEINST="" instead of PARALLEL_MAKE="" > > recipes-mono/mono/mono-4.xx.inc | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Merged, thanks Richard -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-mono] [PATCH 0/3] DEPENDS/RDEPENDS fixes
On 16/07/2015 02:29, Richard Tollerton wrote: > These are fixes for build/runtime issues due to insufficient dependency > specifications. The libgdiplus patches fix observed build failures; the > gtk-sharp-dev patch is untested but pretty obvious. > > > The following changes since commit 9f63cbaaa859f9ae55288de06c1c0eb0e6992f53: > > mono-4.xx.inc: disable parallel make (2015-07-08 11:46:11 +0100) > > are available in the git repository at: > > git://github.com/rtollert/meta-mono dev/rtollert/v2/depends > https://github.com/rtollert/meta-mono/tree/dev/rtollert/v2/depends > > Richard Tollerton (3): > libgdiplus-native: depend explicitly on giflib-native > gtk-sharp-dev: add perl dependency > libgdiplus: add jpeg, tiff, giflib, libexif dependencies > > recipes-mono/gtk-sharp/gtk-sharp.inc| 1 + > recipes-mono/libgdiplus/libgdiplus-native_2.10.8.bb | 2 +- > recipes-mono/libgdiplus/libgdiplus_2.10.8.bb| 2 +- > 3 files changed, 3 insertions(+), 2 deletions(-) > Merged, thanks Richard -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] using gdb with externalsrc
On Wednesday 15 July 2015 19:54:08 Khem Raj wrote: > On Wed, Jul 15, 2015 at 2:52 PM, Dave Kimble wrote: > > Yes, I'm able to debug the externalsrc component. I can see variables, set > > breakpoints, step/next through the code etc. (so the symbols are valid). > > And local changes to the externalsrc component are reflected when I > > debug. > > > > But I can't list the externalsrc component source code from within gdb (or > > find it anywhere in the image). The source for all of the other components > > is in the image (and I can list it in gdb). When I try to list the code > > for > > the externalsrc component, gdb prints this error message: > > "[path on my build machine]/sourceFile.c: No such file or directory." > > is this path pointing to S which is externalsrc path or to B which is > under build TMPDIR > and secondly, can you see compiler flags used during build for externalsrc ? This sounds suspiciously like this bug that coincidentally I just filed yesterday: https://bugzilla.yoctoproject.org/show_bug.cgi?id=8015 As far as I can tell it has something to do with the source not being in the path we're passing to debugedit, but I'm not immediately sure how to fix it. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Is there a fetcher for (dare I say it?) TFS (arrrrgh, I said it...) out there somewhere, or do I have to roll my own?
Hi Paul, List rodger that, thanks! Looks like it's time to embiggen my python nature... A quick skim through the sources suggests (to me, at least) that the p4 command-set looks similar enough to TEE's to make it a reasonable starting point for a TFS fetcher. Would anyone with wider experience of the various (supported) SCCS care to correct my naïve impression? Greets, -- jim -Ursprüngliche Nachricht- Von: Paul Eggleton [mailto:paul.eggle...@linux.intel.com] Gesendet: Mittwoch, 15. Juli 2015 12:56 An: Spriggs, Jim Cc: yocto@yoctoproject.org Betreff: Re: [yocto] Is there a fetcher for (dare I say it?) TFS (agh, I said it...) out there somewhere, or do I have to roll my own? On Wednesday 15 July 2015 10:23:09 Paul Eggleton wrote: > Hi Jim, > > On Wednesday 15 July 2015 09:06:19 Spriggs, Jim wrote: > > [ before anyone tells me to wash my mouth with soap: I actually have > > to live with this junk on a daily basis, so cut me some slack > > already :-\ ] > Been there! (Not with TFS, but VSS in a previous job...) > > > I'm running the dizzy version of bb on my build-server, and > > currently actively *push* stuff to it from the TFS-server. > > > > Obviously, I'd much rather have the build-server *pull* from the > > TFS-server, probably using the TEE CLC. > > > > I realize that there's never likely to be any "official" support for > > TFS, and I'll probably have to roll my own fetcher. > > FWIW, and I hope Richard doesn't hit me, I think we would accept a > fetcher implementation into BitBake rather than having to have it > floating around somewhere externally - you can see we've done that for > other proprietary version control systems. The challenge with these > fetchers though is that nobody who regularly maintains BitBake is able > to test them, so we are almost completely reliant on folks in the > community such as yourself to do that testing for us after it gets > merged (and not send us patches that break it, because we probably won't be > able to verify that they don't). > > > The current Bitbake User Manual seems only to describe the standard > > fetchers, so if anyone could point me at a clue or two about how to > > write and integrate a custom fetcher, I'd be very grateful indeed. > > I don't think we have anything in the way of documentation on writing > your own fetcher - the only documentation is the code. That said, > using the existing fetchers as examples it should be fairly > straightforward I would hope. Hmm, the bit I neglected to state explicitly - I'm not aware of anyone having previously implemented a TFS fetcher, but hopefully if such a person exists they will speak up here ;) Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre RAYLASE AG Argelsrieder Feld 2+4 82234 Wessling Germany Tel.: +49-(0)8153/88 98-0 Fax: +49-(0)8153/88 98-10 http://www.raylase.de District Court Munich, HRB 131450 Board: Peter von Jan (CEO) Supervisory Board: Dr. Ulrich Lohmann (Chairman) Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto