From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id EA474E00E7A; Fri, 2 Sep 2016 02:44:29 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00,RDNS_NONE autolearn=no version=3.3.1 X-Spam-HAM-Report: * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.8 RDNS_NONE Delivered to internal network by a host with no rDNS Received: from blaine.gmane.org (unknown [195.159.176.226]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 6E095E00E41 for ; Fri, 2 Sep 2016 02:44:22 -0700 (PDT) Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1bfl1G-0000JC-EY for yocto@yoctoproject.org; Fri, 02 Sep 2016 11:44:18 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: yocto@yoctoproject.org From: Pietro Date: Fri, 02 Sep 2016 09:44:31 +0000 Message-ID: <87h99yab5s.fsf@posteo.net> References: <87poooc2ha.fsf@posteo.net> <87k2ewau7z.fsf@posteo.net> <87fupkarqt.fsf@posteo.net> <85bd928a2ecb47663d9a90ca24756f16@herrie.org> <87bn07bw9s.fsf@posteo.net> <874m5zbuwl.fsf@posteo.net> <5ab4fbf1a8106fa4a5d7db3b457db8fb@herrie.org> <87zinraduo.fsf@posteo.net> <2470b2c489daa8d6863159ea44d04367@herrie.org> <87shtjaaje.fsf@posteo.net> Mime-Version: 1.0 X-Complaints-To: usenet@blaine.gmane.org User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) Cancel-Lock: sha1:/baTHo8nncltg0Q1xEskQZNQHZE= Subject: Re: Yocto and Google protobuffer X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2016 09:44:30 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Maciej Borzęcki writes: > On Thu, Sep 1, 2016 at 5:45 PM, Pietro wrote: >> Herman van Hazendonk >> writes: >> >>> If it takes the wrong version, it could be your layers aren't in the >>> right order. That's the first thing to check. >>> >>> You might want to try to run bitbake with >>> >>> -f protobuf -c cleanall or -f protobuf-native -c cleanall >>> >>> This will remove all locally ;) >>> >>> Then rebuild it... I haven't played much with the -native bits, so not >>> sure how those work. >>> >> I needed to specify DEPENDS = "protobuf-native" to get it working, I >> would be really interested to understand exactly what that does, but I >> must admit to myself I can't understand everything in a single shot. > > Quoting my first email: >>> All you need to do, >>>is include meta-oe in your layers (bblayers.conf) and have >>> protobuf-native listed in DEPENDS inside your package recipe. > > DEPENDS lists build time dependencies, like libraries, tools etc. > protobuf-native, by convention, means that the package was built for > your build host. This enables you to run protoc during the build to > generate proper language bindings. > >> >> So never mind. >> >> I still have another question :-) >> >> I am about to create another recipe for the gprc library for C++, to >> build it on my local machine has been pretty simple: >> >> $ git clone -b $(curl -L http://grpc.io/release) >> https://github.com/grpc/grpc >> $ cd grpc >> $ git submodule update --init >> $ make >> $ [sudo] make install >> >> The recipe I have created so far would clone/checkout the source code >> from a GIT repo or something similar and then the build process could >> start straight away. >> >> In my case I have an additional step: >> >> git submodule update --init >> > > There's a submodule fetcher, when setting SRC_URI use `gitsm://` > instead of `git://` see > https://www.yoctoproject.org/docs/2.1/bitbake-user-manual/bitbake-user-manual.html#gitsm-fetcher > for details. > > Cheers, > -- > Maciej Borzecki > RnDity Thanks a lot. It looks like the project I am trying to clone does not follow the convention the gitsm module expects. ERROR: Function failed: Fetcher failure: Fetch command failed with exit code 1, output: cp: cannot stat '/.../build/downloads/git2/github.com.grpc.grpc/modules': No such file or directory Is there a way to get around it ? I have also noticed that the tag parameter does not work properly - it might be me making a mistake though. SRC_URI = "git://github.com/grpc/grpc;protocol=http;rev=3df9bdf88013e4c9cb5b5f092ac7cd1aad11fa96 Works fine, but: ERROR: Function failed: Fetcher failure for URL: 'git://github.com/grpc/grpc;protocol=http;tag=v1.0.0'. The command git -c core.fsyncobjectfiles=0 ls-remote http://github.com/grpc/grpc refs/heads/v1.0.0 refs/t ags/v1.0.0^{} gave empty output unexpectedly And indeed the command git -c core.fsyncobjectfiles=0 ls-remote http://github.com/grpc/grpc refs/heads/v1.0.0 refs/tags/v1.0.0^{} Does not result in any output while the command : git -c core.fsyncobjectfiles=0 ls-remote http://github.com/grpc/grpc refs/heads/v1.0.0 refs/tags/v1.0.0 Results in : 2a69139aa7f609e439c24a46754252a5f9d37500 refs/tags/v1.0.0 What's the use of '^{}' ?