Re: [yocto] How to use JRE (Java Runtime) in Yocto Projects
Hello all, I did some things like this wiki. I added the meta-java layer but the only important diference is that I'm using meta poky (/poky/meta) and no meta oe-core (/oe-core/meta). https://github.com/woglinde/meta-java/wiki The fisrt probleme tha I have is that the package LLVM show me some errors. here is what I have: raul@phi04:/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$ bitbake openjdk-6 WARNING: Host distribution "Ubuntu 12.04.1 LTS" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. NOTE: Error expanding variable populate_packages | ETA: 00:00:38 NOTE: Error during finalise of /home/prjs/newcom0001/workspace/philinux/meta-java/recipes-core/llvm/ llvm2.8_2.8.bb ERROR: Unable to parse /home/prjs/newcom0001/workspace/philinux/meta-java/recipes-core/llvm/ llvm2.8_2.8.bb ERROR: Command execution failed: Traceback (most recent call last): File "/home/prjs/poky/bitbake/lib/bb/command.py", line 84, in runAsyncCommand self.cooker.updateCache() File "/home/prjs/poky/bitbake/lib/bb/cooker.py", line 1202, in updateCache if not self.parser.parse_next(): File "/home/prjs/poky/bitbake/lib/bb/cooker.py", line 1669, in parse_next self.virtuals += len(result) UnboundLocalError: local variable 'result' referenced before assignment Summary: There was 1 WARNING message shown. Summary: There were 2 ERROR messages shown, returning a non-zero exit code. raul@phi04:/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$ Thanks ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to use JRE (Java Runtime) in Yocto Projects
On Wednesday 19 December 2012 08:25:00 Raul Rosetto Munoz wrote: > Hello all, > I did some things like this wiki. > > I added the meta-java layer but the only important diference is that I'm > using meta poky (/poky/meta) and no meta oe-core (/oe-core/meta). > > https://github.com/woglinde/meta-java/wiki > > The fisrt probleme tha I have is that the package LLVM show me some errors. > > here is what I have: > > raul@phi04:/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$ > bitbake openjdk-6 > WARNING: Host distribution "Ubuntu 12.04.1 LTS" has not been validated with > this version of the build system; you may possibly experience unexpected > failures. It is recommended that you use a tested distribution. > NOTE: Error expanding variable populate_packages > > | ETA: 00:00:38 > > NOTE: Error during finalise of > /home/prjs/newcom0001/workspace/philinux/meta-java/recipes-core/llvm/ > llvm2.8_2.8.bb > ERROR: Unable to parse > /home/prjs/newcom0001/workspace/philinux/meta-java/recipes-core/llvm/ > llvm2.8_2.8.bb > ERROR: Command execution failed: Traceback (most recent call last): > File "/home/prjs/poky/bitbake/lib/bb/command.py", line 84, in > runAsyncCommand > self.cooker.updateCache() > File "/home/prjs/poky/bitbake/lib/bb/cooker.py", line 1202, in updateCache > if not self.parser.parse_next(): > File "/home/prjs/poky/bitbake/lib/bb/cooker.py", line 1669, in parse_next > self.virtuals += len(result) > UnboundLocalError: local variable 'result' referenced before assignment > > > Summary: There was 1 WARNING message shown. > Summary: There were 2 ERROR messages shown, returning a non-zero exit code. > raul@phi04:/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$ Which version of the build system are you using? Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to use JRE (Java Runtime) in Yocto Projects
raul@phi04:/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$ bitbake --version BitBake Build Tool Core version 1.15.2, bitbake version 1.15.2 2012/12/19 Paul Eggleton > On Wednesday 19 December 2012 08:25:00 Raul Rosetto Munoz wrote: > > Hello all, > > I did some things like this wiki. > > > > I added the meta-java layer but the only important diference is that I'm > > using meta poky (/poky/meta) and no meta oe-core (/oe-core/meta). > > > > https://github.com/woglinde/meta-java/wiki > > > > The fisrt probleme tha I have is that the package LLVM show me some > errors. > > > > here is what I have: > > > > raul@phi04 > :/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$ > > bitbake openjdk-6 > > WARNING: Host distribution "Ubuntu 12.04.1 LTS" has not been validated > with > > this version of the build system; you may possibly experience unexpected > > failures. It is recommended that you use a tested distribution. > > NOTE: Error expanding variable populate_packages > > > > | ETA: > 00:00:38 > > > > NOTE: Error during finalise of > > /home/prjs/newcom0001/workspace/philinux/meta-java/recipes-core/llvm/ > > llvm2.8_2.8.bb > > ERROR: Unable to parse > > /home/prjs/newcom0001/workspace/philinux/meta-java/recipes-core/llvm/ > > llvm2.8_2.8.bb > > ERROR: Command execution failed: Traceback (most recent call last): > > File "/home/prjs/poky/bitbake/lib/bb/command.py", line 84, in > > runAsyncCommand > > self.cooker.updateCache() > > File "/home/prjs/poky/bitbake/lib/bb/cooker.py", line 1202, in > updateCache > > if not self.parser.parse_next(): > > File "/home/prjs/poky/bitbake/lib/bb/cooker.py", line 1669, in > parse_next > > self.virtuals += len(result) > > UnboundLocalError: local variable 'result' referenced before assignment > > > > > > Summary: There was 1 WARNING message shown. > > Summary: There were 2 ERROR messages shown, returning a non-zero exit > code. > > raul@phi04 > :/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$ > > Which version of the build system are you using? > > Cheers, > Paul > > -- > > Paul Eggleton > Intel Open Source Technology Centre > -- *Raul Rosetto Muñoz* ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to use JRE (Java Runtime) in Yocto Projects
raul@phi04:/home/prjs/poky$ git branch * local/origin/denzil 2012/12/19 Raul Rosetto Munoz > raul@phi04:/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$ > bitbake --version > BitBake Build Tool Core version 1.15.2, bitbake version 1.15.2 > > > > 2012/12/19 Paul Eggleton > >> On Wednesday 19 December 2012 08:25:00 Raul Rosetto Munoz wrote: >> > Hello all, >> > I did some things like this wiki. >> > >> > I added the meta-java layer but the only important diference is that I'm >> > using meta poky (/poky/meta) and no meta oe-core (/oe-core/meta). >> > >> > https://github.com/woglinde/meta-java/wiki >> > >> > The fisrt probleme tha I have is that the package LLVM show me some >> errors. >> > >> > here is what I have: >> > >> > raul@phi04 >> :/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$ >> > bitbake openjdk-6 >> > WARNING: Host distribution "Ubuntu 12.04.1 LTS" has not been validated >> with >> > this version of the build system; you may possibly experience unexpected >> > failures. It is recommended that you use a tested distribution. >> > NOTE: Error expanding variable populate_packages >> > >> > | ETA: >> 00:00:38 >> > >> > NOTE: Error during finalise of >> > /home/prjs/newcom0001/workspace/philinux/meta-java/recipes-core/llvm/ >> > llvm2.8_2.8.bb >> > ERROR: Unable to parse >> > /home/prjs/newcom0001/workspace/philinux/meta-java/recipes-core/llvm/ >> > llvm2.8_2.8.bb >> > ERROR: Command execution failed: Traceback (most recent call last): >> > File "/home/prjs/poky/bitbake/lib/bb/command.py", line 84, in >> > runAsyncCommand >> > self.cooker.updateCache() >> > File "/home/prjs/poky/bitbake/lib/bb/cooker.py", line 1202, in >> updateCache >> > if not self.parser.parse_next(): >> > File "/home/prjs/poky/bitbake/lib/bb/cooker.py", line 1669, in >> parse_next >> > self.virtuals += len(result) >> > UnboundLocalError: local variable 'result' referenced before assignment >> > >> > >> > Summary: There was 1 WARNING message shown. >> > Summary: There were 2 ERROR messages shown, returning a non-zero exit >> code. >> > raul@phi04 >> :/home/prjs/newcom0001/workspace/philinux/philinux-imx28-newcom$ >> >> Which version of the build system are you using? >> >> Cheers, >> Paul >> >> -- >> >> Paul Eggleton >> Intel Open Source Technology Centre >> > > > > -- > *Raul Rosetto Muñoz* > -- *Raul Rosetto Muñoz* ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to use JRE (Java Runtime) in Yocto Projects
On Wednesday 19 December 2012 15:31:42 Raul Rosetto Munoz wrote: > raul@phi04:/home/prjs/poky$ git branch > * local/origin/denzil There doesn't seem to be a denzil branch for meta-java and it's likely the error you're receiving is because the master branch of meta-java is incompatible with the denzil release. I would suggest updating to the danny release, or alternatively you'll need to modify meta-java to be compatible with denzil (i.e. you'll have to match indenting in python functions such as populate_packages_prepend). Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Git tag systematics ?
Dear Elizabeth,
In message
you wrote:
>
> > However, there is no such release tag as "danny-8.0".
>
> You are correct. That was an oversight on my part. I've corrected it.
Thanks.
Is there some formal procedure in place how git release tags are
assigned, and when?
> > What is the system in this numbering / tagging?
>
> Milestones: 1.x_My.rcz
> Major releases: 1.x and they should also get the name-x.y.z tag
Thanks again - but is there any documetn somehere on the web pages or
in the wiki that actually says what the name of the next release will
be, and which branch it is being worked on?
> > Releated: is there any document which explains the branch names being
> > used for development. for example, how can I find out ("officially")
> > what the branch name for Yocto 1.4 will be / is ?
>
> When Richard tells me :)
We have a "1.4_M1.final" tag in the "1.4_M1" branch, and I see similar
"1.x_My" branches for the other releases. When will some "name-..."
branch become visible?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de
Lots of people drink from the wrong bottle sometimes.
-- Edith Keeler, "The City on the Edge of Forever",
stardate unknown
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Weekly build availability.
The weekly build will be available in a few hours at: http://autobuilder.yoctoproject.org/pub/nightly/20121219-5 One known issue is that the eclipse plugin needs to be built alone and moved manually. I'll do this when it is finished building. This is due to some autobuilder issues I'll be fixing tonight. I *will* be producing weekly builds over the holidays in case we have anyone who wants them. -b -- Elizabeth Flanagan Yocto Project Build and Release ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 2/5] yocto-layer: new script
On 12/17/2012 09:51 AM, tom.zanu...@intel.com wrote:
> From: Tom Zanussi
>
> Implementation of the 'yocto-layer' command-line tool, for creating
> generic layers and listing their input properties.
No specific comments below, looks good.
Would the final version also include a removal of similar code from
yocto-bsp, such that yocto-bsp would call yocto-layer? I'm thinking
about reducing code duplication. I guess not as this is mostly just
argument parsing and all the logic is already abstracted into bsp.engine?
Thanks,
Darren
>
> Signed-off-by: Tom Zanussi
> ---
> scripts/yocto-layer | 142
>
> 1 file changed, 142 insertions(+)
> create mode 100755 scripts/yocto-layer
>
> diff --git a/scripts/yocto-layer b/scripts/yocto-layer
> new file mode 100755
> index 000..f759275
> --- /dev/null
> +++ b/scripts/yocto-layer
> @@ -0,0 +1,142 @@
> +#!/usr/bin/env python
> +# ex:ts=4:sw=4:sts=4:et
> +# -*- tab-width: 4; c-basic-offset: 4; indent-tabs-mode: nil -*-
> +#
> +# Copyright (c) 2012, Intel Corporation.
> +# All rights reserved.
> +#
> +# This program is free software; you can redistribute it and/or modify
> +# it under the terms of the GNU General Public License version 2 as
> +# published by the Free Software Foundation.
> +#
> +# This program is distributed in the hope that it will be useful,
> +# but WITHOUT ANY WARRANTY; without even the implied warranty of
> +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> +# GNU General Public License for more details.
> +#
> +# You should have received a copy of the GNU General Public License along
> +# with this program; if not, write to the Free Software Foundation, Inc.,
> +# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
> +#
> +# DESCRIPTION
> +# 'yocto-layer' is the Yocto Tool that helps users create a new Yocto
> +# layer. Invoking it without any arguments will display help screens
> +# for the 'yocto-layer' command and list the available 'yocto-layer'
> +# subcommands. Invoking a subcommand without any arguments will
> +# likewise display help screens for the specified subcommand. Please
> +# use that interface for detailed help.
> +#
> +# AUTHORS
> +# Tom Zanussi
> +#
> +
> +__version__ = "0.1.0"
> +
> +import os
> +import sys
> +import optparse
> +import logging
> +
> +scripts_path = os.path.abspath(os.path.dirname(os.path.abspath(sys.argv[0])))
> +lib_path = scripts_path + '/lib'
> +sys.path = sys.path + [lib_path]
> +
> +from bsp.help import *
> +from bsp.engine import *
> +
> +
> +def yocto_layer_create_subcommand(args, usage_str):
> +"""
> +Command-line handling for layer creation. The real work is done by
> +bsp.engine.yocto_layer_create()
> +"""
> +parser = optparse.OptionParser(usage = usage_str)
> +
> +parser.add_option("-o", "--outdir", dest = "outdir", action = "store",
> + help = "name of layer dir to create")
> +parser.add_option("-i", "--infile", dest = "properties_file", action =
> "store",
> + help = "name of file containing the values for layer
> input properties as a JSON file")
> +parser.add_option("-c", "--codedump", dest = "codedump", action =
> "store_true",
> + default = False, help = "dump the generated code to
> layergen.out")
> +(options, args) = parser.parse_args(args)
> +
> +if len(args) != 1:
> +logging.error("Wrong number of arguments, exiting\n")
> +parser.print_help()
> +sys.exit(1)
> +
> +layer_name = args[0]
> +
> +if options.outdir:
> +layer_output_dir = options.outdir
> +else:
> +layer_output_dir = "meta-" + layer_name
> +
> +yocto_layer_create(layer_name, scripts_path, layer_output_dir,
> options.codedump, options.properties_file)
> +
> +
> +def yocto_layer_list_subcommand(args, usage_str):
> +"""
> +Command-line handling for listing available layer properties and
> +values. The real work is done by bsp.engine.yocto_layer_list()
> +"""
> +parser = optparse.OptionParser(usage = usage_str)
> +
> +parser.add_option("-o", "--outfile", action = "store", dest =
> "properties_file",
> + help = "dump the possible values for layer properties
> to a JSON file")
> +
> +(options, args) = parser.parse_args(args)
> +
> +if not yocto_layer_list(args, scripts_path, options.properties_file):
> +logging.error("Bad list arguments, exiting\n")
> +parser.print_help()
> +sys.exit(1)
> +
> +
> +subcommands = {
> +"create": [yocto_layer_create_subcommand,
> + yocto_layer_create_usage,
> + yocto_layer_create_help],
> +"list": [yocto_layer_list_subcommand,
> + yocto_layer_list_usage,
> + yocto_layer_list_help],
> +}
> +
> +
> +def start_logging(loglevel):
> +logging.basicConfig(filname = 'yocto-layer.log', filemode = 'w',
> level=loglevel)
Re: [yocto] [PATCH 0/5] RFC: new 'yocto-layer' tool for creating generic Yocto layers
On 12/17/2012 09:51 AM, tom.zanu...@intel.com wrote: > From: Tom Zanussi > > Since I've been doing kind of similar work lately for the 'custom kernel' > support for yocto-bsp and have gotten several requests lately (mainly > from Darren in support of the new kernel documentation) for something > like this, I decided to just go ahead and try to quickly implement a > general-purpose layer-generation tool based on the BSP-generation code > used in the yocto-bsp tool. > > There's actually an enhancement request bug for this already in the > Yocto bugzilla, but it doesn't contain many details: > > Bug 3094 - Add a layer generation tool: > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=3094 > > So anyway, this is my initial take on what that bug means. It's an RFC for > a couple reasons, first that I'd like to get comments on whether this is > actually what's needed for a 'layer generation tool', and second, because I > still need to do some cleanup of the refactored code, but don't want to > waste much time on it if it's not really what's needed. > > Below are a couple examples of how it's used - you really have to try it > yourself to see what's generated - I don't want to post tarballs or such on > the list and it's simple to generate and look at the layers. > > The first case is just a very simple layer with a layer.conf and README - > basically the simplest layer you can create, and which exists mainly because > even that is easy to get wrong. As with the yocto-bsp tool, the script > queries the user for a couple items, here we just take the defaults, which > are a priority of 6 for the layer and no other components such as example > recipes: > > [trz@empanada build]$ yocto-layer create simplestlayer > Please enter the layer priority you'd like to use for the layer: [default: 6] > Would you like to have an example recipe created? (y/n) [default: n] > Would you like to have an example bbappend file created? (y/n) [default: n] Can these options be specified on the cli? It would be nice for documentation to not have to list all the questions to describe how to accomplish a specific task such as this. e.g. [trz@empanada build]$ yocto-layer create simplestlayer -p 6 --no-recipe --no-bbappend Or possibly having defaults to those questions accepted by default unless [-i|--interactive] is specified? empanada :-) Mm > New layer created in meta-simplestlayer. > > Don't forget to add it to your BBLAYERS (for details see > meta-simplestlayer\README). > > [trz@empanada build]$ find . > . > ./meta-simplestlayer > ./meta-simplestlayer/conf > ./meta-simplestlayer/conf/layer.conf > ./meta-simplestlayer/README > ./meta-simplestlayer/COPYING.MIT > It might make sense to create a recipes/ directory as well, just to support convention. > > In the second case, we tell the tool that we do want an example .bb and and > an example .bbappend. We're queried for the recipe name that we want our > recipe to have, and for the .bbappend, the name of the base recipe and its > version. Below you can see the files it generates - please look at the files > themselves to see the contents. For the recipe example, it generates a recipe > based on the example in the Yocto manual, and my own helloworld.c code > (untested so far which is also why this is an RFC). For the .bbappend > example, > it just creates an empty .patch file with some instructions on what to do to > modify the parent recipe with a patch: > > [trz@empanada build]$ yocto-layer create mylayer > Please enter the layer priority you'd like to use for the layer: [default: 6] > Would you like to have an example recipe created? (y/n) [default: n] y > Please enter the name you'd like to use for your example recipe: [default: > example] flork > Would you like to have an example bbappend file created? (y/n) [default: n] y > Please enter the name you'd like to use for your bbappend file: [default: > example] chork > Please enter the version number you'd like to use for your bbappend file > (this should match the recipe you're appending to): [default: 0.1] 0.22.3 Wow, that's quite a bit more than I was asking for... I can imagine that some folks my find that useful. > > New layer created in meta-mylayer. > > Don't forget to add it to your BBLAYERS (for details see meta-mylayer\README). > > [trz@empanada build]$ find . > . > ./meta-mylayer > ./meta-mylayer/recipes-example > ./meta-mylayer/recipes-example/example > ./meta-mylayer/recipes-example/example/flork-0.1 > ./meta-mylayer/recipes-example/example/flork-0.1/helloworld.c > ./meta-mylayer/recipes-example/example/flork-0.1/example.patch > ./meta-mylayer/recipes-example/example/flork_0.1.bb > ./meta-mylayer/conf > ./meta-mylayer/conf/layer.conf > ./meta-mylayer/recipes-example-bbappend > ./meta-mylayer/recipes-example-bbappend/example-bbappend > ./meta-mylayer/recipes-example-bbappend/example-bbappend/chork-0.22.3 > ./meta-mylayer/recipes-example-bbappend/example-bbappend/chork-0.2
Re: [yocto] [PATCH 4/5] yocto-layer: add 'layer' template data
On 12/17/2012 09:51 AM, tom.zanu...@intel.com wrote:
> From: Tom Zanussi
>
> Add a 'layer' target containing all the data that will be used to
> generate a generic yocto layer.
>
> Signed-off-by: Tom Zanussi
> ---
Great stuff Tom, only one nit below:
> new file mode 100644
> index 000..90ce90e
> --- /dev/null
> +++ "b/scripts/lib/bsp/substrate/target/arch/layer/{{ if
> create_example_recipe == \"y\": }}
> recipes-example/example/{{=example_recipe_name}}-0.1/helloworld.c"
> @@ -0,0 +1,6 @@
> +#include
> +
> +int main(int argc, char **argv)
> +{
> +printf("Hello World!\n");
If you specify a return type of int, you should be returning one:
return 0;
:-)
> +}
Looks good otherwise.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 5/5] scripts/lib/bsp/engine.py: refactor bsp-creation code
On 12/17/2012 09:51 AM, tom.zanu...@intel.com wrote: > From: Tom Zanussi > > This does a bit of refactoring of the bsp-generation code to make it > generically reusable for generating non-bsp layers. > > The first user remains the existing yocto-bsp tool; these changes > allow a second user, the new yocto-layer tool, to use the same code. Aha, this is what I was looking for earlier - sorry my email search pattern dropped this patch initially. Just a cursory review, but looks good to me. -- Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Where does the bitbake get the variable "TOPDIR"
At 2012-12-19 00:35:13,"Eren Türkay" wrote:
>On Tue, Dec 18, 2012 at 08:28:32PM +0800, Biao wrote:
>> >http://hambedded.org/blog/2012/11/24/from-bitbake-hello-world-to-an-image/
>> I will try to give some feedback after finishing the reading.
>> But for now, there are some silly questions:
>> 1. There is a base_do_fetch() {}, I did not find the explanation of the
>> keyword of 'base' in the manual, do i miss something?
>
>I don't know the internals of bitbake on that level but as far as I
>understand, bitbake uses the name of the bbclass file as a prefix in the
>function names for the sake of abstraction. So, as in autotools.bbclass,
>the tasks defined in base.bbclass gets prefixes with "base_" keyword.
>Probably, it's related with mapping the function names when 'inherit'
>keyword is used.
I agree it seems a prefix is mandatory when working with EXPORT_FUNCTIONS.
>
>I'm not clear on this topic either. A hand from an experienced bitbake
>guru would be really helpful here. The type of abstraction in bitbake
>should be explained in detail as well as how EXPORT_FUNCTION works.
>
>Any volunteers?
>
>> 2. There is 'bb.note' and 'bbnote' in the code example, is it a type-mistake
>> or something else?
>
>No, this is not a mistake. You can use python as well as shell functions
>in bitbake recipes and classes. See 'python' keyword in function
>definitons where bb.note is used. That's why python function "bb.note()"
>is used to print log information. Without python keyword, the bitbake
>function is treated as shell.
>
Ok, so the bb.note is a python provided functions, which is missing from the
docs.
>Regards,
>Eren
>
>--
>. 73! DE TA1AET
> http://linkedin.com/in/erenturkay
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Canceled: Yocto Project Technical Team Meeting - Cancelled this week due to holidays
BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:Pacific Standard Time BEGIN:STANDARD DTSTART:16010101T02 TZOFFSETFROM:-0700 TZOFFSETTO:-0800 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02 TZOFFSETFROM:-0800 TZOFFSETTO:-0700 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT ORGANIZER;CN="Liu, Song":MAILTO:song@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Anders Da rander':MAILTO:and...@chargestorm.se ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Barros Pen a, Belen":MAILTO:belen.barros.p...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Bodke, Kis hore K":MAILTO:kishore.k.bo...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Bruce Ash field':MAILTO:bruce.ashfi...@windriver.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Daniel Ca uchy':MAILTO:dcau...@mvista.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'deVries, Alex'":MAILTO:alex.devr...@windriver.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Dixon, Br ad'":MAILTO:brad_di...@mentor.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Dmytriyenk o, Denys":MAILTO:de...@ti.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Erway, Tra cey M":MAILTO:tracey.m.er...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Flanagan, Elizabeth":MAILTO:elizabeth.flana...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Hart, Darr en":MAILTO:darren.h...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Hatle, Ma rk'":MAILTO:mark.ha...@windriver.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Jeremy Pu hlman':MAILTO:jpuhl...@gmail.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Kridner, J ason":MAILTO:j...@ti.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Lieu.Ta@w indriver.com':MAILTO:'lieu...@windriver.com' ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Lock, Josh ua":MAILTO:joshua.l...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'McCombe, Kevin'":MAILTO:kevin.mcco...@windriver.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Moeller, T horsten":MAILTO:thorsten.moel...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Sanjay Ra ina':MAILTO:sra...@mvista.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Osier-mixo n, Jeffrey":MAILTO:jeffrey.osier-mi...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Polk, Jef frey'":MAILTO:jeff.p...@windriver.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Purdie, Ri chard":MAILTO:richard.pur...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Ranslam, Rob'":MAILTO:rob.rans...@windriver.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Saxena, Ra hul":MAILTO:rahul.sax...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Stewart, D avid C":MAILTO:david.c.stew...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Wold, Saul" :MAILTO:saul.w...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Zanussi, T om":MAILTO:tom.zanu...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Zhang, Jes sica":MAILTO:jessica.zh...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Rifenbark, Scott M":MAILTO:scott.m.rifenb...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Hudson, S ean'":MAILTO:sean_hud...@mentor.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Serban, La urentiu":MAILTO:laurentiu.ser...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Petrisor, Ileana":MAILTO:ileana.petri...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Damian, Al exandru":MAILTO:alexandru.dam...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Burton, Ro ss":MAILTO:ross.bur...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Mueller, R obert":MAILTO:robert.muel...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Arce Moren o, Abraham":MAILTO:abraham.arce.mor...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ravi Vomp olu':MAILTO:ravi.vomp...@mathworks.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Sadiq, Ir fan'":MAILTO:irfan_sa...@mentor.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Santana Lo pez, Mario A":MAILTO:mario.a.sant
[yocto] An added task is not run by bitbake, why is that ?
Hi All,
An added task is not run by bitbake, why is that ?
The meta-test layer setup is ok, you can forget this.
After i issue bitbake dummy, i found that it runs succeed with the tasks in
base.bbclass, but my dummy1 is not run, why is that?
meta-test/dummy/dummy.0.0.bb
DESCRIPTION = "A simply dummy package"
do_dummy0 () {
bbnote "Doing Dummy0."
}
do_dummy1 () {
bbnote "Doing Dummy1."
}
do_dummy2 () {
bbnote "Doing Dummy2."
}
addtask dummy1 before do_dummy2 after do_dummy0
Thanks,
Biao___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
