Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 85455E00CE0; Thu, 1 Sep 2016 03:27:59 -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=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [149.210.149.69 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] X-Greylist: delayed 356 seconds by postgrey-1.32 at yocto-www; Thu, 01 Sep 2016 03:27:55 PDT Received: from outbound0.mail.transip.nl (outbound0.mail.transip.nl [149.210.149.69]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 15498E00CC3 for ; Thu, 1 Sep 2016 03:27:55 -0700 (PDT) Received: from submission6.mail.transip.nl (submission6.mail.transip.nl [149.210.149.10]) by outbound0.mail.transip.nl (Postfix) with ESMTP id 3sPywb4WrJzxgrR; Thu, 1 Sep 2016 12:21:51 +0200 (CEST) Received: from webmail.frontend (web0.mail.transip.nl [149.210.149.95]) by submission6.mail.transip.nl (Postfix) with ESMTPA id 3sPywg1fwhz12Ljb; Thu, 1 Sep 2016 12:21:54 +0200 (CEST) MIME-Version: 1.0 Date: Thu, 01 Sep 2016 12:21:54 +0200 From: Herman van Hazendonk To: Pietro Mail-Reply-To: yoctoproject.org@herrie.org In-Reply-To: <87fupkarqt.fsf@posteo.net> References: <87poooc2ha.fsf@posteo.net> <87k2ewau7z.fsf@posteo.net> <87fupkarqt.fsf@posteo.net> Message-ID: <85bd928a2ecb47663d9a90ca24756f16@herrie.org> X-Sender: me@herrie.org User-Agent: Webmail X-Scanned-By: ClueGetter at submission6.mail.transip.nl X-Report-Abuse-To: abuse@transip.nl Cc: yocto@yoctoproject.org Subject: Re: Yocto and Google protobuffer X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: yoctoproject.org@herrie.org List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2016 10:27:59 -0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Pietro, You can override the recipe by adding a recipe for version 3.0.0+ in your own layer and making sure your layer has a higher priority in bblayers.conf. See for example what we do in our project: https://github.com/webOS-ports/webos-ports-setup/blob/testing/conf/bblayers.conf openembedded-core provides ofono 1.1.7 for example with https://github.com/openembedded/openembedded-core/tree/krogoth/meta/recipes-connectivity/ofono However we want to use ANOTHER version of ofono (1.1.7 based, but from a different repo/project). So we have our own .bbappend at https://github.com/webOS-ports/meta-webos-ports/blob/krogoth/meta-luneos/recipes-connectivity/ofono/ofono_git.bbappend where we specify the different repo etc to use. This doesn't apply 1:1 in your case, but you could simply add a protobuf_3.0.0.bb in your own layer and it should build that instead. Just make sure you have your layer at a higher position compared to meta-openembedded in your bblayers.conf Herrie On 2016-09-01 11:34, Pietro wrote: > Maciej Borzęcki > writes: > >> On Thu, Sep 1, 2016 at 10:40 AM, Pietro >> wrote: >>> Maciej Borzęcki >>> writes: >>> >>>> On Wed, Aug 31, 2016 at 6:44 PM, Pietro >>>> wrote: >>>>> Hi all, >>>>> >>>>> I am new to the Yocto building system and I could be talking >>>>> nonsense. I >>>>> used to work with buildroot time ago and I remember there is an >>>>> area >>>>> where compiled software/packages/tools previously built are >>>>> "staged" and >>>>> used when building other packages. >>>>> >>>>> Is there something like that available with Yocto ? Specifically I >>>>> would >>>>> like to add a package which uses the Google Protocol Buffer, I do >>>>> not have >>>>> administrator rights on the machine and I can't install the >>>>> packages I >>>>> need system wise. >>>>> >>>>> Is it possible to add recipes and use them at building time without >>>>> including them in the image being generated ? >>>>> >>>>> A good example for that would be the protoc, the protocol buffer >>>>> description >>>>> file compiler. >>>>> >>>> >>>> There is a recipe for protobuf in meta-oe (2.6.1). 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. >>>> >>>> The protoc compiler will be available in the PATH when package is >>>> being built, so autotools checks like AC_CHECK_PROG/AC_PATH_PROG >>>> should be able to find it. >>>> >>>> Cheers, >>>> -- >>>> Maciej Borzecki >>>> RnDity >>> Thanks a lot. >>> >>> I have added the DEPENDS line and it indeed downloads and build the >>> some >>> protobuf related stuff, where did you get the dependency name from ? >>> I can't see the protobuf-native as a recipe in the meta-oe website : >>> >>> https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ >> >> It's just a mechanism that allows for building the native (i.e. for >> the host) packages, and these are autmatically named ${PN}-native. >> There should a BBCLASSEXTEND = "..native.." stanza inside the protobuf >> recipe that enables this feature. >> >>> >>> I have just realised that GRPC (http://www.grpc.io/) is needed for my >>> project, it is a library which uses the protobuffers, is there a >>> recipe/package which provides them around or do I need to create my >>> own >>> recipe ? >> >> You can try searching for a recipe at http://layers.openembedded.org >> If there's none, try to write your own. This might be a good changes >> to get yourself acquainted with `devtool` tool that will help you in >> the process. >> >>> >>> I would like to check the root filesystem being generated as part of >>> the >>> build process, where is it ? >>> >> >> ${TMPDIR}/_//../rootfs >> >> for instance, for my current build: >> >> tmp/work/vexpress_qemu-poky-linux-gnueabi/core-image-minimal/1.0-r0/rootfs >> >> -- >> Maciej Borzecki >> RnDity > > Thanks, much appreciated. > > Do you know where the software which is not included in the image - > such > us protoc - is it stored ? > > It turns out the recipe for the protobuffer uses version 2.6 while I > would need version 3.0.0 to be used, is there a way to partially > "override" a recipe ? > > http://cgit.openembedded.org/cgit.cgi/meta-openembedded/tree/meta-oe/recipes-devtools/protobuf/protobuf_2.6.1.bb?h=master > > Thanks a lot. > P.