[oe] [meta-oe] WIP: cloud9: created
Cloud9 is a web-browser based IDE. This application should support multiple architectures as long as they have node.js and a build of node-o3-xml that is dropped into this system. Ideally, that library would be added separately as a system-dependent portion, because everything else should be ISA independent. Advice on cleaning up this recipe is welcome. I will continue to improve it as I understand how. It is rather useful as-is. --- meta-oe/recipes-devtools/cloud9/cloud9_0.5.1.bb | 28 +++ 1 files changed, 28 insertions(+), 0 deletions(-) create mode 100644 meta-oe/recipes-devtools/cloud9/cloud9_0.5.1.bb diff --git a/meta-oe/recipes-devtools/cloud9/cloud9_0.5.1.bb b/meta-oe/recipes-devtools/cloud9/cloud9_0.5.1.bb new file mode 100644 index 000..626332f --- /dev/null +++ b/meta-oe/recipes-devtools/cloud9/cloud9_0.5.1.bb @@ -0,0 +1,28 @@ +DESCRIPTION = Meet Cloud9, development-as-a-service for Javascripters and other developers +HOMEPAGE = http://c9.io; +RDEPENDS = nodejs + +SRC_URI = git://github.com/jadonk/cloud9.git;protocol=git \ + + +LICENSE = GPLv3 +LIC_FILES_CHKSUM = file://LICENSE;md5=4784c3bcff601fd8f9515f52a11e7018 + +SRCREV = 08bae1d1cc2ba9f7f883a25afd07f0339a82fa8b +S = ${WORKDIR}/git + +do_configure_prepend () { + git submodule update --init --recursive +} + +do_compile () { +} + +do_install () { + install -m 0755 -d ${D}/usr/share/cloud9 ${D}${bindir} + rsync -r --exclude=.* ${S}/* ${D}/usr/share/cloud9 + touch ${D}${bindir}/cloud9 + echo #!/bin/sh ${D}${bindir}/cloud9 + echo node /usr/share/cloud9/bin/cloud9.js -l 0.0.0.0 -w /home/root -p 3000 ${D}${bindir}/cloud9 + chmod 0755 ${D}${bindir}/cloud9 +} -- 1.7.4.1 ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] [meta-oe] WIP: cloud9: created
Dear Jason, Am Samstag, den 24.09.2011, 03:08 -0400 schrieb Jason Kridner: Cloud9 is a web-browser based IDE. This application should support multiple architectures as long as they have node.js and a build of node-o3-xml that is dropped into this system. Ideally, that library would be added separately as a system-dependent portion, because everything else should be ISA independent. Advice on cleaning up this recipe is welcome. what problems to do you see? I will continue to improve it as I understand how. It is rather useful as-is. --- meta-oe/recipes-devtools/cloud9/cloud9_0.5.1.bb | 28 +++ 1 files changed, 28 insertions(+), 0 deletions(-) create mode 100644 meta-oe/recipes-devtools/cloud9/cloud9_0.5.1.bb diff --git a/meta-oe/recipes-devtools/cloud9/cloud9_0.5.1.bb b/meta-oe/recipes-devtools/cloud9/cloud9_0.5.1.bb new file mode 100644 index 000..626332f --- /dev/null +++ b/meta-oe/recipes-devtools/cloud9/cloud9_0.5.1.bb @@ -0,0 +1,28 @@ +DESCRIPTION = Meet Cloud9, development-as-a-service for Javascripters and other developers +HOMEPAGE = http://c9.io; +RDEPENDS = nodejs This belongs further down too. + +SRC_URI = git://github.com/jadonk/cloud9.git;protocol=git \ + Please put that below the license stuff [1]. + +LICENSE = GPLv3 +LIC_FILES_CHKSUM = file://LICENSE;md5=4784c3bcff601fd8f9515f52a11e7018 + +SRCREV = 08bae1d1cc2ba9f7f883a25afd07f0339a82fa8b +S = ${WORKDIR}/git + +do_configure_prepend () { + git submodule update --init --recursive +} + +do_compile () { +} Maybe add comments why the above overrides are needed. + +do_install () { + install -m 0755 -d ${D}/usr/share/cloud9 ${D}${bindir} + rsync -r --exclude=.* ${S}/* ${D}/usr/share/cloud9 Should `rsync` be put in `DEPENDS`? + touch ${D}${bindir}/cloud9 + echo #!/bin/sh ${D}${bindir}/cloud9 + echo node /usr/share/cloud9/bin/cloud9.js -l 0.0.0.0 -w /home/root -p 3000 ${D}${bindir}/cloud9 + chmod 0755 ${D}${bindir}/cloud9 +} Thanks, Paul [1] http://openembedded.org/index.php?title=Styleguide signature.asc Description: This is a digitally signed message part ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] ti_cgt_c6000_6.1.17_setup_linux_x86.bin error while installing ti-codec-engine
On 2011-09-23 14:46, Michael Poole wrote: On Fri, Sep 23, 2011 at 6:47 AM, Gary Thomas wrote: Check to make sure that you don't have write permission to /opt If you have write permission in the directory /opt, the installer fails to put the tools where they belong in your OE build. Is it generally known that this limitation is due to a bug in ti-eula-unpack.inc? (Python's print automatically adds a newline, which the code's author apparently did not expect.) My local repo has these changes to allow in-tree installs by users with write access to /opt; please pardon Gmail's mangling of leading whitespace: I don't know if this is a generally known fact; it should be, I reported it to this list more than a year ago and was basically ignored [actually told I just shouldn't have write access to /opt so the issue was my own fault...] Does the unpack work with your patches if /opt is not writeable? diff --git a/recipes/powervr-drivers/libgles-omap3.inc b/recipes/powervr-driv index ab4b248..5acc4da 100644 --- a/recipes/powervr-drivers/libgles-omap3.inc +++ b/recipes/powervr-drivers/libgles-omap3.inc @@ -19,7 +19,8 @@ SRC_URI = http://software-dl.ti.com/dsps/dsps_public_sw/sd S = ${WORKDIR}/OMAP35x_Graphics_SDK_${SGXPV} # Logic to unpack installjammer file -TI_BIN_UNPK_CMDS=Y: qY:workdir:Y +TI_BIN_UNPK_CMDS=Y:workdir +TI_BIN_UNPK_WDEXT = /Graphics_SDK_${SGXPV} require ../ti/ti-eula-unpack.inc BINLOCATION ?= ${S}/gfx_rel diff --git a/recipes/powervr-drivers/omap3-sgx-modules_1.6.16.3977.bb b/recip index 216b3ae..be4b7a1 100644 --- a/recipes/powervr-drivers/omap3-sgx-modules_1.6.16.3977.bb +++ b/recipes/powervr-drivers/omap3-sgx-modules_1.6.16.3977.bb @@ -5,7 +5,8 @@ LICENSE = GPLv2 # http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/gfxsdk/ # see libgles-omap3.inc for detailed installation instructions -TI_BIN_UNPK_CMDS=Y: qY:workdir:Y +TI_BIN_UNPK_CMDS=Y:workdir: +TI_BIN_UNPK_WDEXT = /Graphics_SDK_${SGXPV} require ../ti/ti-eula-unpack.inc SGXPV = 4_03_00_02 diff --git a/recipes/ti/ti-eula-unpack.inc b/recipes/ti/ti-eula-unpack.inc index 3b79c24..82ea785 100644 --- a/recipes/ti/ti-eula-unpack.inc +++ b/recipes/ti/ti-eula-unpack.inc @@ -53,7 +53,7 @@ python ti_bin_do_unpack() { wdext = bb.data.getVar('TI_BIN_UNPK_WDEXT', localdata) wdext = bb.data.expand(wdext, localdata) cmd = workdir+wdext -printf, %s\n % cmd +printf, %s % cmd f.close() # Expand the tarball that was created if required ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Re: [oe] ti_cgt_c6000_6.1.17_setup_linux_x86.bin error while installing ti-codec-engine
Actually i copy them from /opt/ti manually and paste them where they must be.. And i can basically say: no it is not known and it is not easy problem to fix if you are beginner at both bitbake and openembedded. There was no-answer for this situation. but i added a reply to a forum which has the same problem with me and waiting for the reply.. On 2011-09-23 14:46, Michael Poole wrote: On Fri, Sep 23, 2011 at 6:47 AM, Gary Thomas wrote: Check to make sure that you don't have write permission to /opt If you have write permission in the directory /opt, the installer fails to put the tools where they belong in your OE build. Is it generally known that this limitation is due to a bug in ti-eula-unpack.inc? (Python's print automatically adds a newline, which the code's author apparently did not expect.) My local repo has these changes to allow in-tree installs by users with write access to /opt; please pardon Gmail's mangling of leading whitespace: I don't know if this is a generally known fact; it should be, I reported it to this list more than a year ago and was basically ignored [actually told I just shouldn't have write access to /opt so the issue was my own fault...] Does the unpack work with your patches if /opt is not writeable? diff --git a/recipes/powervr-drivers/libgles-omap3.inc b/recipes/powervr-driv index ab4b248..5acc4da 100644 --- a/recipes/powervr-drivers/libgles-omap3.inc +++ b/recipes/powervr-drivers/libgles-omap3.inc @@ -19,7 +19,8 @@ SRC_URI = http://software-dl.ti.com/dsps/dsps_public_sw/sd S = ${WORKDIR}/OMAP35x_Graphics_SDK_${SGXPV} # Logic to unpack installjammer file -TI_BIN_UNPK_CMDS=Y: qY:workdir:Y +TI_BIN_UNPK_CMDS=Y:workdir +TI_BIN_UNPK_WDEXT = /Graphics_SDK_${SGXPV} require ../ti/ti-eula-unpack.inc BINLOCATION ?= ${S}/gfx_rel diff --git a/recipes/powervr-drivers/omap3-sgx-modules_1.6.16.3977.bb b/recip index 216b3ae..be4b7a1 100644 --- a/recipes/powervr-drivers/omap3-sgx-modules_1.6.16.3977.bb +++ b/recipes/powervr-drivers/omap3-sgx-modules_1.6.16.3977.bb @@ -5,7 +5,8 @@ LICENSE = GPLv2 # http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/gfxsdk/ # see libgles-omap3.inc for detailed installation instructions -TI_BIN_UNPK_CMDS=Y: qY:workdir:Y +TI_BIN_UNPK_CMDS=Y:workdir: +TI_BIN_UNPK_WDEXT = /Graphics_SDK_${SGXPV} require ../ti/ti-eula-unpack.inc SGXPV = 4_03_00_02 diff --git a/recipes/ti/ti-eula-unpack.inc b/recipes/ti/ti-eula-unpack.inc index 3b79c24..82ea785 100644 --- a/recipes/ti/ti-eula-unpack.inc +++ b/recipes/ti/ti-eula-unpack.inc @@ -53,7 +53,7 @@ python ti_bin_do_unpack() { wdext = bb.data.getVar('TI_BIN_UNPK_WDEXT', localdata) wdext = bb.data.expand(wdext, localdata) cmd = workdir+wdext - printf, %s\n % cmd + printf, %s % cmd f.close() # Expand the tarball that was created if required ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel -- Gary Thomas | Consulting for the MLB Associates | Embedded world ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel