ninja-native: add initial recipe, ninja 1.6.0
PATCH 1/1 ninja-native: add initial recipe, ninja 1.6.0
--- .../recipes-devtools/ninja/ninja-native_1.6.0.bb | 25 ++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 meta-oe/recipes-devtools/ninja/ninja-native_1.6.0.bb
meta-oe/recipes-devtools/ninja/ninja-native_1.6.0.bb new file +25 -0
@@ -0,0 +1,25 @@ +SUMMARY = "Ninja is a small build system with a focus on speed." +HOMEPAGE = "http://martine.github.com/ninja/" +LICENSE = "Apache-2.0" +LIC_FILES_CHKSUM = "file://COPYING;md5=a81586a64ad4e476c791cda7e2f2c52e" + +DEPENDS = "re2c-native" + +inherit native + +SRCREV="484c16336f19bd8970bb6e75322d61b92a229899" + +SRC_URI = "git://github.com/martine/ninja.git;branch=release" + +S="${WORKDIR}/git" + +do_configure[noexec] = "1" + +do_compile() { + python ${S}/configure.py --bootstrap +} + +do_install() { + install -d ${D}${bindir} + install -m 0755 ${S}/ninja ${D}${bindir}/ +}
Signature · 1 line
1.9.1
Quoted 38 lines · Andre McCurdy
Signed-off-by Andre McCurdy <[email protected]>--- .../recipes-devtools/ninja/ninja-native_1.6.0.bb | 25 ++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 meta-oe/recipes-devtools/ninja/ninja-native_1.6.0.bbmeta-oe/recipes-devtools/ninja/ninja-native_1.6.0.bb new file +25
-1@@ -0,0 +1,25 @@ +SUMMARY = "Ninja is a small build system with a focus on speed." +HOMEPAGE = "http://martine.github.com/ninja/" +LICENSE = "Apache-2.0" +LIC_FILES_CHKSUM = "file://COPYING;md5=a81586a64ad4e476c791cda7e2f2c52e" + +DEPENDS = "re2c-native" + +inherit native + +SRCREV="484c16336f19bd8970bb6e75322d61b92a229899" + +SRC_URI = "git://github.com/martine/ninja.git;branch=release" + +S="${WORKDIR}/git" + +do_configure[noexec] = "1" + +do_compile() { + python ${S}/configure.py --bootstrap +} + +do_install() { + install -d ${D}${bindir} + install -m 0755 ${S}/ninja ${D}${bindir}/ +} --
Quoted 2 lines
1.9.1
Yes ninja-native needs a more central place. Currently we have it (at least - I checked my environment only) in
meta-qt5
meta-browser
meta-tizen
Once applied: Would you send patches to the other layers?
Andreas
Quoted 44 lines · Andreas Müller
Quoted 38 lines · Andre McCurdy
Signed-off-by Andre McCurdy <[email protected]>--- .../recipes-devtools/ninja/ninja-native_1.6.0.bb | 25 ++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 meta-oe/recipes-devtools/ninja/ninja-native_1.6.0.bbmeta-oe/recipes-devtools/ninja/ninja-native_1.6.0.bb new file +25
-1@@ -0,0 +1,25 @@ +SUMMARY = "Ninja is a small build system with a focus on speed." +HOMEPAGE = "http://martine.github.com/ninja/" +LICENSE = "Apache-2.0" +LIC_FILES_CHKSUM = "file://COPYING;md5=a81586a64ad4e476c791cda7e2f2c52e" + +DEPENDS = "re2c-native" + +inherit native + +SRCREV="484c16336f19bd8970bb6e75322d61b92a229899" + +SRC_URI = "git://github.com/martine/ninja.git;branch=release" + +S="${WORKDIR}/git" + +do_configure[noexec] = "1" + +do_compile() { + python ${S}/configure.py --bootstrap +} + +do_install() { + install -d ${D}${bindir} + install -m 0755 ${S}/ninja ${D}${bindir}/ +} --Quoted 2 lines
1.9.1
Yes ninja-native needs a more central place. Currently we have it (at least - I checked my environment only) in
Quoted 5 lines
meta-qt5
meta-browser
meta-tizenOnce applied: Would you send patches to the other layers?
Those layers all currently use older versions of ninja.
Since I can't easily test all the packages in these layers, it's probably best if the respective layer maintainers take care of removing their own ninja-native recipes at their own pace (ie once they've tested against ninja 1.6.0 in meta-oe and confirmed that everything works as expected).
Quoted 6 lines
Andreas
--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Quoted 55 lines · Andre McCurdy
Quoted 44 lines · Andreas Müller
Quoted 38 lines · Andre McCurdy
Signed-off-by Andre McCurdy <[email protected]>---
.../recipes-devtools/ninja/ninja-native_1.6.0.bb | 25 ++++++++++++++++++++++1 file changed, 25 insertions(+)create mode 100644 meta-oe/recipes-devtools/ninja/ninja-native_1.6.0.bb
meta-oe/recipes-devtools/ninja/ninja-native_1.6.0.bb new file +25
-1@@ -0,0 +1,25 @@ +SUMMARY = "Ninja is a small build system with a focus on speed." +HOMEPAGE = "http://martine.github.com/ninja/" +LICENSE = "Apache-2.0" +LIC_FILES_CHKSUM = "file://COPYING;md5=a81586a64ad4e476c791cda7e2f2c52e" + +DEPENDS = "re2c-native" + +inherit native + +SRCREV="484c16336f19bd8970bb6e75322d61b92a229899" + +SRC_URI = "git://github.com/martine/ninja.git;branch=release" + +S="${WORKDIR}/git" + +do_configure[noexec] = "1" + +do_compile() { + python ${S}/configure.py --bootstrap +} + +do_install() { + install -d ${D}${bindir} + install -m 0755 ${S}/ninja ${D}${bindir}/ +} --Quoted 2 lines
1.9.1
Yes ninja-native needs a more central place. Currently we have it (at least - I checked my environment only) in
Quoted 5 lines
meta-qt5
meta-browser
meta-tizenOnce applied: Would you send patches to the other layers?
Quoted 7 lines
Those layers all currently use older versions of ninja.
Since I can't easily test all the packages in these layers, it's probably best if the respective layer maintainers take care of removing their own ninja-native recipes at their own pace (ie once they've tested against ninja 1.6.0 in meta-oe and confirmed that everything works as expected).
While thats right, you can help sending same patch to the layers and help them testing part can be left to them. Somehow the layer maintainers should know about this whether its sending a patch or filing a bug doesn't matter.