Re: [yocto] [PATCH 1/1][Image Creator] Remove unused target tree data for Hob
Op 21 jul. 2011, om 07:50 heeft Ke Liping het volgende geschreven:
> From: Liping Ke
>
> Since Hob only needes package dependency information, we can
> create a new version of package information retrieving methods,
> remove task dependency information, so that we can greatly
> reduce data loading time for Hob
Does this fix the bug where DEPENDS are leaking into the RDEPENDS list? If you
select something like systemd the gui will list 'gtk' as a runtime dep for the
image, while it's only a transitive buildtime one.
>
> Signed-off-by: Liping Ke
> ---
> bitbake/lib/bb/cooker.py | 96 +-
> 1 files changed, 77 insertions(+), 19 deletions(-)
>
> diff --git a/bitbake/lib/bb/cooker.py b/bitbake/lib/bb/cooker.py
> index 8badd2d..26ed2ae 100644
> --- a/bitbake/lib/bb/cooker.py
> +++ b/bitbake/lib/bb/cooker.py
> @@ -296,13 +296,12 @@ class BBCooker:
> if data.getVarFlag( e, 'python', envdata ):
> logger.plain("\npython %s () {\n%s}\n", e, data.getVar(e,
> envdata, 1))
>
> -def prepareTreeData(self, pkgs_to_build, task):
> +def prepareTreeData(self, pkgs_to_build, task, runqueue=True):
> """
> Prepare a runqueue and taskdata object for iteration over
> pkgs_to_build
> """
> # Need files parsed
> self.updateCache()
> -
> # If we are told to do the None task then query the default task
> if (task == None):
> task = self.configuration.cmd
> @@ -322,12 +321,22 @@ class BBCooker:
> runlist.append([k, "do_%s" % task])
> taskdata.add_unresolved(localdata, self.status)
>
> -rq = bb.runqueue.RunQueue(self, self.configuration.data,
> self.status, taskdata, runlist)
> -rq.rqdata.prepare()
> -
> -return taskdata, rq
> -
> -def generateDepTreeData(self, pkgs_to_build, task, more_meta=False):
> +# For some users, take Hob as example, we only need less dependency
> data
> +# mark this kind of user as "less_meta" data requesterG
> +if (runqueue):
> +rq = bb.runqueue.RunQueue(self, self.configuration.data,
> self.status, taskdata, runlist)
> +rq.rqdata.prepare()
> +return taskdata, rq
> +else:
> +tasks_fnid = []
> +if len(taskdata.tasks_name) == 0:
> +# Nothing to do
> +return
> +for task in xrange(len(taskdata.tasks_name)):
> +tasks_fnid.append(taskdata.tasks_fnid[task])
> +return taskdata, tasks_fnid
> +
> +def generateTaskDepTreeData(self, pkgs_to_build, task):
> """
> Create a dependency tree of pkgs_to_build, returning the data.
> When more_meta is set to True include summary, license and group
> @@ -351,18 +360,10 @@ class BBCooker:
> fn = taskdata.fn_index[fnid]
> pn = self.status.pkg_fn[fn]
> version = "%s:%s-%s" % self.status.pkg_pepvpr[fn]
> -if more_meta:
> -summary = self.status.summary[fn]
> -lic = self.status.license[fn]
> -section = self.status.section[fn]
> if pn not in depend_tree["pn"]:
> depend_tree["pn"][pn] = {}
> depend_tree["pn"][pn]["filename"] = fn
> depend_tree["pn"][pn]["version"] = version
> -if more_meta:
> -depend_tree["pn"][pn]["summary"] = summary
> -depend_tree["pn"][pn]["license"] = lic
> -depend_tree["pn"][pn]["section"] = section
> for dep in rq.rqdata.runq_depends[task]:
> depfn = taskdata.fn_index[rq.rqdata.runq_fnid[dep]]
> deppn = self.status.pkg_fn[depfn]
> @@ -407,12 +408,69 @@ class BBCooker:
> return depend_tree
>
>
> +def generatePkgDepTreeData(self, pkgs_to_build, task):
> +"""
> +Create a dependency tree of pkgs_to_build, returning the data.
> +When more_meta is set to True include summary, license and group
> +information in the returned tree.
> +"""
> +taskdata, tasks_fnid = self.prepareTreeData(pkgs_to_build, task,
> False)
> +
> +seen_fnids = []
> +depend_tree = {}
> +depend_tree["depends"] = {}
> +depend_tree["pn"] = {}
> +depend_tree["rdepends-pn"] = {}
> +depend_tree["packages"] = {}
> +depend_tree["rdepends-pkg"] = {}
> +
> +for task in xrange(len(tasks_fnid)):
> +fnid = tasks_fnid[task]
> +fn = taskdata.fn_index[fnid]
> +pn = self.status.pkg_fn[fn]
> +version = "%s:%s-%s" % self.status.pkg_pepvpr[fn]
> +summary = self.status.summary[fn]
> +lic = self.status.license[fn]
> +section = self.status.section[fn]
> +if pn not in depend_tree["pn"]:
> +depend_tree["pn"][pn] = {}
[yocto] statue of multilib?
Richard, I'm working on getting a ppc64 build going and looking close to having that done. I was wondering what the state of multilib support was as I'd really like to have that functional for the ppc64 system. Think this will also be useful to flush out any multilib issues by having another arch (beyond x86/x86_64) that we try multilib out on thanks - k ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] best cfg for building all of yocto?
On 07/20/2011 10:10 PM, Kumar Gala wrote: For a new bsp/target what's the best config choice to try and build all of yocto? Is it core-image-sato? - k bitbake world should build all of the available packages that aren't explicitly excluded due to machine incompatibilities. It doesn't generate a final image though, just all of the output packages. core-image-lsb builds a significantly larger set of packages than -sato if you want a reference image that includes more packages. Scott -- Scott Garman Embedded Linux Engineer - Yocto Project Intel Open Source Technology Center ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] .gitignore: Update build ignores to have wildcard
ignore not just build/* but any build*/* cases. Signed-off-by: Kumar Gala --- .gitignore | 12 ++-- 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/.gitignore b/.gitignore index b13086d..d44e729 100644 --- a/.gitignore +++ b/.gitignore @@ -1,11 +1,11 @@ *.pyc *.pyo -build/conf/local.conf -build/conf/bblayers.conf -build/downloads -build/tmp/ -build/sstate-cache -build/pyshtables.py +build*/conf/local.conf +build*/conf/bblayers.conf +build*/downloads +build*/tmp/ +build*/sstate-cache +build*/pyshtables.py pstage/ scripts/oe-git-proxy-socks sources/ -- 1.7.3.4 ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] best cfg for building all of yocto?
On Thu, Jul 21, 2011 at 8:29 AM, Scott Garman wrote: > bitbake world should build all of the available packages that aren't > explicitly excluded due to machine incompatibilities. It doesn't generate a > final image though, just all of the output packages. Is there an easy way to remove a specific package from being built with running bitbake world? There are unmet dependencies: NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES 'libmad' ERROR: Required build target 'libomxil' has no buildable providers. Missing or unbuildable dependency chain was: ['libomxil', 'libmad'] -M ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] best cfg for building all of yocto?
On Thu, 21 Jul 2011, McClintock Matthew-B29882 wrote: > On Thu, Jul 21, 2011 at 8:29 AM, Scott Garman > wrote: > > bitbake world should build all of the available packages that aren't > > explicitly excluded due to machine incompatibilities. It doesn't generate a > > final image though, just all of the output packages. > > Is there an easy way to remove a specific package from being built > with running bitbake world? There are unmet dependencies: > > NOTE: Resolving any missing task queue dependencies > ERROR: Nothing PROVIDES 'libmad' > ERROR: Required build target 'libomxil' has no buildable providers. > Missing or unbuildable dependency chain was: ['libomxil', 'libmad'] i saw that a couple days ago but i figured someone else would pick up on it in short order. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] best cfg for building all of yocto?
On Thu, 2011-07-21 at 16:32 +, McClintock Matthew-B29882 wrote: > On Thu, Jul 21, 2011 at 8:29 AM, Scott Garman > wrote: > > bitbake world should build all of the available packages that aren't > > explicitly excluded due to machine incompatibilities. It doesn't generate a > > final image though, just all of the output packages. > > Is there an easy way to remove a specific package from being built > with running bitbake world? There are unmet dependencies: > > NOTE: Resolving any missing task queue dependencies > ERROR: Nothing PROVIDES 'libmad' > ERROR: Required build target 'libomxil' has no buildable providers. > Missing or unbuildable dependency chain was: ['libomxil', 'libmad'] EXCLUDE_FROM_WORLD_pn-libmad = "1" should remove libmad from world builds. Cheers, Richard ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] best cfg for building all of yocto?
On 07/21/2011 09:32 AM, McClintock Matthew-B29882 wrote: On Thu, Jul 21, 2011 at 8:29 AM, Scott Garman wrote: bitbake world should build all of the available packages that aren't explicitly excluded due to machine incompatibilities. It doesn't generate a final image though, just all of the output packages. Is there an easy way to remove a specific package from being built with running bitbake world? There are unmet dependencies: NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES 'libmad' ERROR: Required build target 'libomxil' has no buildable providers. Missing or unbuildable dependency chain was: ['libomxil', 'libmad'] This happens because conf/distro/include/default-distrovars.inc excludes some recipes which are known to use commercial licenses: COMMERCIAL_LICENSE ?= "lame gst-fluendo-mp3 libmad mpeg2dec ffmpeg qmmp" If you'd like to build these recipes, set COMMERCIAL_LICENSE = "" in your local.conf. Scott -- Scott Garman Embedded Linux Engineer - Yocto Project Intel Open Source Technology Center ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] best cfg for building all of yocto?
On Thu, 21 Jul 2011, Scott Garman wrote: > On 07/21/2011 09:32 AM, McClintock Matthew-B29882 wrote: > > On Thu, Jul 21, 2011 at 8:29 AM, Scott Garman > > wrote: > > > bitbake world should build all of the available packages that aren't > > > explicitly excluded due to machine incompatibilities. It doesn't generate > > > a > > > final image though, just all of the output packages. > > > > Is there an easy way to remove a specific package from being built > > with running bitbake world? There are unmet dependencies: > > > > NOTE: Resolving any missing task queue dependencies > > ERROR: Nothing PROVIDES 'libmad' > > ERROR: Required build target 'libomxil' has no buildable providers. > > Missing or unbuildable dependency chain was: ['libomxil', 'libmad'] > > This happens because conf/distro/include/default-distrovars.inc excludes some > recipes which are known to use commercial licenses: > > COMMERCIAL_LICENSE ?= "lame gst-fluendo-mp3 libmad mpeg2dec ffmpeg qmmp" > > If you'd like to build these recipes, set COMMERCIAL_LICENSE = "" in your > local.conf. related to richard's earlier post about how to exclude packages, shouldn't the initial settings be consistent, then? either a default yocto setup should include commercial licenses, or exclude them (and their packages) entirely. it seems that running a simple "bitbake world" shouldn't just fail. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] best cfg for building all of yocto?
On 07/21/2011 10:08 AM, Robert P. J. Day wrote: On Thu, 21 Jul 2011, Scott Garman wrote: On 07/21/2011 09:32 AM, McClintock Matthew-B29882 wrote: On Thu, Jul 21, 2011 at 8:29 AM, Scott Garman wrote: bitbake world should build all of the available packages that aren't explicitly excluded due to machine incompatibilities. It doesn't generate a final image though, just all of the output packages. Is there an easy way to remove a specific package from being built with running bitbake world? There are unmet dependencies: NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES 'libmad' ERROR: Required build target 'libomxil' has no buildable providers. Missing or unbuildable dependency chain was: ['libomxil', 'libmad'] This happens because conf/distro/include/default-distrovars.inc excludes some recipes which are known to use commercial licenses: COMMERCIAL_LICENSE ?= "lame gst-fluendo-mp3 libmad mpeg2dec ffmpeg qmmp" If you'd like to build these recipes, set COMMERCIAL_LICENSE = "" in your local.conf. related to richard's earlier post about how to exclude packages, shouldn't the initial settings be consistent, then? either a default yocto setup should include commercial licenses, or exclude them (and their packages) entirely. it seems that running a simple "bitbake world" shouldn't just fail. I agree with Robert. I have filed bug #1262 to track this issue. Scott -- Scott Garman Embedded Linux Engineer - Yocto Project Intel Open Source Technology Center ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [bitbake-devel] [PATCH 1/1][Image Creator] Remove unused target tree data for Hob
On Thu, 2011-07-21 at 11:04 +0200, Koen Kooi wrote: > Op 21 jul. 2011, om 07:50 heeft Ke Liping het volgende geschreven: > > > From: Liping Ke > > > > Since Hob only needes package dependency information, we can > > create a new version of package information retrieving methods, > > remove task dependency information, so that we can greatly > > reduce data loading time for Hob > > > Does this fix the bug where DEPENDS are leaking into the RDEPENDS list? > If you select something like systemd the gui will list 'gtk' as a > runtime dep for the image, while it's only a transitive buildtime one. > It does not, 1263 filed. http://bugzilla.pokylinux.org/show_bug.cgi?id=1263 Regards, Joshua -- Joshua Lock Yocto Project "Johannes Factotum" Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] best cfg for building all of yocto?
Op 21 jul. 2011, om 18:43 heeft Scott Garman het volgende geschreven: > On 07/21/2011 09:32 AM, McClintock Matthew-B29882 wrote: >> On Thu, Jul 21, 2011 at 8:29 AM, Scott Garman >> wrote: >>> bitbake world should build all of the available packages that aren't >>> explicitly excluded due to machine incompatibilities. It doesn't generate a >>> final image though, just all of the output packages. >> >> Is there an easy way to remove a specific package from being built >> with running bitbake world? There are unmet dependencies: >> >> NOTE: Resolving any missing task queue dependencies >> ERROR: Nothing PROVIDES 'libmad' >> ERROR: Required build target 'libomxil' has no buildable providers. >> Missing or unbuildable dependency chain was: ['libomxil', 'libmad'] > > This happens because conf/distro/include/default-distrovars.inc excludes some > recipes which are known to use commercial licenses: > > COMMERCIAL_LICENSE ?= "lame gst-fluendo-mp3 libmad mpeg2dec ffmpeg qmmp" COMMERCIAL_LICENSE is a mis-nomber for a lot of them, NEED_TO_GIVE_MONEY_TO_MPEGLA is closer to the truth. What I'm trying to say is that the recipes in question don't have a commercial license, but can be subject to royalties in some cases. It could be that your silicon vendor already pays the royalty for you for each chip they sell, so it is helpfull to dig into this before tweaking COMMERCIAL_LICENSE. ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 0/2][Image Creator] Hob Cache for speed up switching
On Thu, 2011-07-21 at 13:39 +0800, Ke, Liping wrote: > Hi, Josh > > Yes, definitely this patch's importance is much less than the previous one. > But if more users are using hob, the cache would be very useful. > Because when using UI, users tend to switch between all combination of menu > frequently. > Even with the improved the speed, we still need around 7s. It would be nice > if he switches back the UI is loaded immediately without waiting time. > > Yes. Definitely we need to make sure the hash key was correct. > Currently I am not sure which elements should be the final correct one (the > UI might changes in the future). > So my suggestion is that: we hold the patch. In the near future, when Hob is > very mature and nice, we can decide the combination key. > Then we rebase the patch and resend the patch. How do you think about it? I agree on reviewing the status later. Thanks, Joshua -- Joshua Lock Yocto Project "Johannes Factotum" Intel Open Source Technology Centre ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] building crownbay images
On Tue, 2011-07-19 at 03:15 -0700, Andre Haupt wrote: > Hi all, > > I am new to Yocto and to Distro work in general. > > I want to use Yocto on the Kontron nanoETXexpressTT boards. > (http://de.kontron.com/products/computeronmodules/com+express/com+express+ultra/nanoetxexpresstt.html) > > These boards are based on the Intel Atom E6xx and the EG20T platform > controller hub, so i think it is a good idea to start with the crownbay > BSP. > > What would be the best, known to work, way to produce crownbay-noemgd images > for poky bernard? > Should i use git? Which branches should i use (the docs are contraditing > at least in parts)? > Hi Andre, Sorry for not replying earlier - was (and still am) out on vacation. In the Downloads | BSP section on the Yocto site, there's a 'transcript from git checkout to meta-intel BSP' link that you should be able to use to get started building meta-intel images using git, including crownbay. You'll have to adapt it slightly for crownbay-noemgd e.g. use 'crownbay-noemgd' machine name instead of the 'fishriver' that the example uses, change directory names for your system, etc. Also, if you follow the 'Board Support Package (BSP) Downloads' link on the same page, to the 'Intel Atom Processor E660 with Intel Platform Controller Hub EG20T Development Kit', Version 5.0 Bernard, to the 'Building the Meta-crownbay BSP Layer' section, you can find instructions on building the 'crownbay-noemgd' BSP from the poky-bernard-5.0 tarballs and the crownbay-noemgd-bernard-5.0 tarball. These are also contained in README file in the BSP download. You should be able to use either method to get a crownbay-noemgd image for bernard, depending only on your preference. If there are contradictions in the documentation, or if you can think of a better way to make this info accessible to new users, please let me know the specifics and we can fix the website and/or documentation... > I read somewhere, that i should install Yocto to /usr/local/src/yocto. > Is this really necessary? > No, this isn't necessary - it just happens to be where I did the build for the example. You can use any location you want for the BSP build directory. Hope that helps, Tom > Thanks for any hints. > > regards, > > Andre > > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto bug traige call for action: Please Verify Resolved bugs in bugzilla
Hi All, In today's bug triage meeting, we noticed there're total 564 bugs that are in "Resolved" status. The process is once a bug is in Resolved status, the original reporter of the bug should verify the resolution, either a valid fix or acceptable reason and mark the bug as "Verified". So please take a look at Yocto bugzilla (http://bugzilla.pokylinux.org/buglist.cgi?query_format=advanced&bug_status=RESOLVED) and verify those bugs that you've reported and now is marked as Resolved. Thanks, Jessica ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
