[oe] [meta-oe][PATCH] ninja-native: add initial recipe, ninja 1.6.0

[Khem Raj]

> On Oct 30, 2015, at 4:41 PM, Andre McCurdy <armccurdy at gmail.com> wrote:
> 
> On Fri, Oct 30, 2015 at 12:31 PM, Andreas Müller
> <schnitzeltony at googlemail.com> wrote:
>> On Fri, Oct 30, 2015 at 8:19 PM, Andre McCurdy <armccurdy at gmail.com> wrote:
>>> Signed-off-by: Andre McCurdy <armccurdy at gmail.com>
>>> ---
>>> .../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
>>> 
>>> diff --git a/meta-oe/recipes-devtools/ninja/ninja-native_1.6.0.bb b/meta-oe/recipes-devtools/ninja/ninja-native_1.6.0.bb
>>> new file mode 100644
>>> index 0000000..c00710a
>>> --- /dev/null
>>> +++ b/meta-oe/recipes-devtools/ninja/ninja-native_1.6.0.bb
>>> @@ -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}/
>>> +}
>>> --
>>> 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?
> 
> 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20151030/1e007933/attachment-0002.sig>