<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/bitbake/lib/bb/ui/crumbs/builder.py, branch krogoth</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=krogoth</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=krogoth'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2016-03-02T22:41:23+00:00</updated>
<entry>
<title>bitbake: hob: removal of hob ui and associated ui files</title>
<updated>2016-03-02T22:41:23+00:00</updated>
<author>
<name>bavery</name>
<email>brian.avery@intel.com</email>
</author>
<published>2016-02-29T18:26:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a9dc72f08bf5bdd898fba429729acee0e7305838'/>
<id>urn:sha1:a9dc72f08bf5bdd898fba429729acee0e7305838</id>
<content type='text'>
We've been gearing up the Toaster web UI to replace the Hob (GTK+ based) UI
for some time now; Hob has basically been on life support for the past few
releases. As of late last month in master, Toaster has the capability to
select the packages in an image, removing the last thing that Hob could do
that Toaster couldn't.

To recap, the reasons why Hob is being removed include:

- The code is tightly woven into BitBake, making it fragile. This means it
needs significant QA and maintenance on an ongoing basis.

- Some of the implementation is not ideal; we'll be able to remove some cruft
from BitBake and OE-Core at the same time.

- It's GTK+ 2 based, not the current GTK+ 3.

- Toaster is now a much more capable UI and is being actively maintained

The discussion about removing hob can be found at:
http://lists.openembedded.org/pipermail/openembedded-architecture/2016-February/000082.html

(Bitbake rev: be2cceea159c6ca9111eff3df87b98513eab6d72)

Signed-off-by: bavery &lt;brian.avery@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: Allow Hob to run images on a custom simulator, other than qemu</title>
<updated>2016-02-18T07:41:15+00:00</updated>
<author>
<name>Mirela Rabulea</name>
<email>mirela.rabulea@nxp.com</email>
</author>
<published>2016-01-19T14:31:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=5a87d8c477ea829012785f2b284307c56f42787c'/>
<id>urn:sha1:5a87d8c477ea829012785f2b284307c56f42787c</id>
<content type='text'>
The current behavior of Hob is that there is a "Run Image" button which becomes visible only for qemu images.

My suggested change is:
- if an image is selected and it is qemu-compatible, let the "Run image" button be named "Run qemu image"
- if an image is selected and it is not qemu-compatible, let the same button show up with the name "Run custom image", and besides that, an option shows-up to allow the selection of the custom script (by default it points out to runqemu script) to be used for launching this custom image

Note: in case there is more than one toggled image (qemu runnable or deployable), when the user clicks the "Run custom image" button, a dialog will be presented, allowing to choose between any of the existing images.

[YOCTO #8940]

(Bitbake rev: cc4cfc2370297b8feb2dc39d4262e73adf06c09a)

Signed-off-by: Mirela Rabulea &lt;mirela.rabulea@nxp.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake: Add explict getVar param for (non) expansion</title>
<updated>2015-06-23T10:57:53+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2015-06-18T14:14:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=69b69193411849de71cf7c81735c3239e28a2940'/>
<id>urn:sha1:69b69193411849de71cf7c81735c3239e28a2940</id>
<content type='text'>
Rather than just use d.getVar(X), use the more explict d.getVar(X, False)
since at some point in the future, having the default of expansion would
be nice. This is the first step towards that.

This patch was mostly made using the command:

sed -e 's:\(getVar([^,()]*\)\s*):\1, False):g' -i `grep -ril getVar *`

(Bitbake rev: 659ef95c9b8aced3c4ded81c48bcc0fbde4d429f)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: hob: add "recipes/images/" to BBFILES when Hob is launched</title>
<updated>2014-04-08T12:07:25+00:00</updated>
<author>
<name>Irina Patru</name>
<email>irina.patru@intel.com</email>
</author>
<published>2014-04-08T11:59:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=bbc9aafbbf902f036e5bb54b4fe17f46b3079700'/>
<id>urn:sha1:bbc9aafbbf902f036e5bb54b4fe17f46b3079700</id>
<content type='text'>
The path for "recipes/images/" was not added in BBFILES when Hob had
to search for an image recipe. Therefore, it could not find it and an
error occurred.
This path needs to be added when Hob is launched.

[HOB #6086]

(Bitbake rev: 35c67281775b08925957c32663d587d486944e0e)

Signed-off-by: Irina Patru &lt;irina.patru@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: hob: fix customization of empty image recipe</title>
<updated>2014-04-04T14:07:01+00:00</updated>
<author>
<name>Marius Avram</name>
<email>marius.avram@intel.com</email>
</author>
<published>2014-04-03T12:15:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=07231022e20e3e15f2c851617626b52e8de0843c'/>
<id>urn:sha1:07231022e20e3e15f2c851617626b52e8de0843c</id>
<content type='text'>
This fixes a problem which happened when you tried to build an
image by selecting 'Start with an empty image recipe' from the
Image configuration page of hob.

The reason on of the bug was that the name of the resulting image
was threated the same way as ordinary custom images, when in fact
they should use the default name: "hob-image", because they do not
derive from any other recipe.

[YOCTO #6102]

(Bitbake rev: fa4ea3b4b40e7e9e6767e0cd51c6701e0af07135)

Signed-off-by: Marius Avram &lt;marius.avram@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: hob: output filenames based on initial recipe name</title>
<updated>2014-03-24T17:54:46+00:00</updated>
<author>
<name>Marius Avram</name>
<email>marius.avram@intel.com</email>
</author>
<published>2014-03-18T12:17:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=299fbbf31aa99d360a7ca884d1f0e0dff24d8887'/>
<id>urn:sha1:299fbbf31aa99d360a7ca884d1f0e0dff24d8887</id>
<content type='text'>
If a recipe for an image was edited from the hob interface the name
of the files outputed in the &lt;build_dir&gt;/tmp/deploy/images/${MACHINE}/ and the
temporary recipes from &lt;build_dir&gt;/recipes/images/ contained only the
generic name "hob-image". From now on both the temporary recipes and
the output from the deploy/ directory will contain the name of the base
recipe appended by the "-edited" suffix, in the case when a base image recipe was
edited. The base recipe can be a standard recipe (e.g core-image-minimal) or
a custom created and saved by the user.

For example, if core-image-minimal is edited the deploy/ directory will contain
core-image-minimal-edited-20140318-140428-qemux86.ext3 and the recipes/images/
directory will contain the recipe core-image-minimal-edited-20140318-140428.bb.

[YOCTO #5002]

(Bitbake rev: f34575809677dc52e1071a3ae3daebe92819cec0)

Signed-off-by: Marius Avram &lt;marius.avram@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: hob: create a base hob image used to create custom images</title>
<updated>2014-02-28T14:48:40+00:00</updated>
<author>
<name>Cristiana Voicu</name>
<email>cristiana.voicu@intel.com</email>
</author>
<published>2014-02-25T13:30:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=ed19ed0db163acf9556048d01466b074403a0336'/>
<id>urn:sha1:ed19ed0db163acf9556048d01466b074403a0336</id>
<content type='text'>
In order to remove hob-image.bb from meta-hob, a hob-image.bb should
be created somewhere in the build directory. I've saved it in build/recipes/images
directory, and moved the templates to recipes/images/custom (here are those
templates saved by the user).
The image is created when hob starts. Also it appends to BBFILES the directory
where it is created.

Removed images directory from meta-hob.

[YOCTO #5118]
(Bitbake rev: 4587297b51b7ca71d314bdb2c06f2061e7d4aa7d)

Signed-off-by: Cristiana Voicu &lt;cristiana.voicu@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: hob: replace the use of hob-toolchain with populate_sdk task</title>
<updated>2014-02-25T08:06:11+00:00</updated>
<author>
<name>Cristiana Voicu</name>
<email>cristiana.voicu@intel.com</email>
</author>
<published>2014-02-25T07:15:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=72576e2d04dc8b43ae0d7f31cddd74318f52103e'/>
<id>urn:sha1:72576e2d04dc8b43ae0d7f31cddd74318f52103e</id>
<content type='text'>
Now bitbake has an API to run individual task for targets.
Hob can use this to build the sdk, instead of using the hob-
toolchain.

(Bitbake rev: 4a5009036e9cb38f6e0260a88278948931073bc6)

Signed-off-by: Cristiana Voicu &lt;cristiana.voicu@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: hob: No need for enable_proxy and same_proxy in conf file</title>
<updated>2014-01-28T00:52:57+00:00</updated>
<author>
<name>Irina Patru</name>
<email>irina.patru@intel.com</email>
</author>
<published>2014-01-23T09:49:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9a46332aa0a433f5713d750f225a0361879a5339'/>
<id>urn:sha1:9a46332aa0a433f5713d750f225a0361879a5339</id>
<content type='text'>
Hob doesn't read these variable from file and bitbake doesn't use them,
so they shouldn't be set in conf file.

(Bitbake rev: a8c9df86b96e27dc49028c2da42034d13988960c)

Signed-off-by: Irina Patru &lt;irina.patru@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: hob: Don't always save proxy values in conf file</title>
<updated>2014-01-28T00:52:57+00:00</updated>
<author>
<name>Irina Patru</name>
<email>irina.patru@intel.com</email>
</author>
<published>2014-01-23T09:49:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=914e50e5ea3c13e90dd2a8198fb6358715b976b4'/>
<id>urn:sha1:914e50e5ea3c13e90dd2a8198fb6358715b976b4</id>
<content type='text'>
If enable_proxy is not activated, Hob should not save the proxy values
in the conf file when user hits save button.

[ HOB #5308 ]

(Bitbake rev: fbe0851221ecfcefea5bdd4b629a05ed4f5ac189)

Signed-off-by: Irina Patru &lt;irina.patru@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
