Search results

# Lines containing feature-[foo] are removed at build time if the machine # doesn't have the feature "foo".

For example, if at some point between master and devel your recipe foo stopped building, then you could drive the bisection like this: $ git bisect run sh -c "cd build ; bitbake foo"

BAZ = "foo" FATAL: BAZ: Invalid boolean value 'foo'

Assuming you are calling your layer 'meta-foo', you could do the following: * create your meta-foo layer (see other docs for this)

* Please do NOT mix major releases (e.g. building a meta-foo bsp layer with edison 6.0 and meta-qt3 5.0.1 ).

# toasterui receives a TaskStarted event with name "foo" and file "/bar/bar/humbug"; it passes the event to buildinfohelper. ...t with the build record B; it also stores T under the key "/bar/bar/humbug:foo" in taskdata.

# "bin/foo/foo_products.json" : Product JSON file: "defect_tags" : "{\"key\":\"FOO\"}",

...bitbake tool. You can also add in extra layers, usually of the form "meta-foo" to provide machine support and additional functionality.

...that are pass the bitbake environment scrub would be useful. i.e. KBRANCH=foo bitbake -c configure linux-yocto. This goes along with the other BSP bootst ...ese would be of the form: git://somelocation/somerepo.git;name=ref1;branch=foo;name=ref2;branch=bar SRCREV_ref1 = "hash1" SRCREV_ref2 = "hash2" wh

...y are all already within the same intranet. Under this limitation, if user Foo needs their work fully separate from user Bar, they could just have separat

poky-{glibc,uclibc}.inc: Add libc-foo OVERRIDES