Hello.
I have following recipe files and want to remove .patch added to SRC_URI at
ii).
i) _git.bb - specifies RC_URI revision by SRCREV parameter
ii) _%.bbappend - adds several .patch to SRC_URI
iii) _%.bbappend - my recipe
I want to make it (removal) conditional to SR
On 01/24/2017 06:37 AM, Takashi Matsuzawa wrote:
In other words, in my iii) recipe I could say SRC_URI_remove =
"file://.patch", but I want to make it only for specific SRCREV
revisions.
Or any other way of writing my iii) recipe for this?
I would remove ii) altogether in the local layer
Hello Paul,
you are brilliant:
I had errors with django 1.10 and uncommented:
from django.conf.global_settings import TEMPLATE_CONTEXT_PROCESSORS as TCP
TEMPLATE_CONTEXT_PROCESSORS = TCP + (
'django.core.context_processors.request',
'layerindex.context_processors.layerindex_context',
)
Sin
Add the SSHD_CONFIG variable description to the glossary. This variable is
introduced by the following patch series on OE-Core:
https://patchwork.openembedded.org/series/4904
David Vincent (1):
ref-manual: New SSHD_CONFIG variable description
documentation/ref-manual/ref-variables.xml | 21 ++
Add description for the SSHD_CONFIG variable which is used to select the
package to use as provider for sshd-config.
Signed-off-by: David Vincent
---
documentation/ref-manual/ref-variables.xml | 21 +
1 file changed, 21 insertions(+)
diff --git a/documentation/ref-manual/ref
Hi,
TL;DR after migrating from jethro to morty my out-of-tree modules do not
load.
Long version:
Im developing uio driver for a custom FPGA. The base is xilinx zu15 (note:
as the explanation will go on I *think* it will be clear that this is not
related to meta-xilinx).
It's basically a debug int
A release candidate build for yocto-2.3_M2.rc1 is now available at:
http://autobuilder.yoctoproject.org/pub/releases/yocto-2.3_M2.rc1
Please begin QA on this build as soon as possible.
Build hash information:
meta-qt4 : 2c7f8df9039be498f8a2232d1428adb7f4e5e800
meta-intel : 1d36b0c379d3
In order to support a use-case that embeds information about the Git
revision of Yocto itself that was used to make a build, I would like to run
some arbitrary Python code and dump the results (Git SHA1's, tag names,
etc) into a Bitbake variable.
The idea is that the variable would get consumed in
On Tue, Jan 24, 2017 at 9:55 AM, Matt Hoosier wrote:
> In order to support a use-case that embeds information about the Git
> revision of Yocto itself that was used to make a build, I would like to run
> some arbitrary Python code and dump the results (Git SHA1's, tag names, etc)
> into a Bitbake
Patch state can only be set/changed at patchwork web interface,
resulting in a poor user experience for project maintainers.
This change allows project maintainers to change a patch status
directly from an email message sent as a reply to the related mailing list
thread by including a the string "
Hi Jacob,
Sorry for the delay, I hadn't noticed the patches initially because
the tag was missing, then I was busy with other things. I'm taking a
look at them now.
On Thu, Jan 19, 2017 at 10:17 AM, Leon Woestenberg wrote:
> Hi Jacob,
>
> On Thu, Jan 19, 2017 at 11:09 AM, Jacob Chen wrote:
>>
>
ping
On 01/18/2017 04:31 PM, Jose Lamego wrote:
> From: Alex Franco
>
> When a recipe search returns only one result, clicking the single
> result at the results view is still required to view further
> recipe detail.
>
> This change automatically redirects to the recipe details view
> when the
ping
On 01/18/2017 04:31 PM, Jose Lamego wrote:
> From: Alex Franco
>
> Recipe search cannot be narrowed to a specific layer, producing
> unnecessary results.
>
> This change allows including a layers name when searching for recipes to
> narrow the yielded results by adding a layer name to the
From: Mirza Krak
Not applicaple on U-boot 2016.03 which is used in poky/morty.
This reverts commit 031e26954b95d49a66ea4677b9e867d08441f450.
[Issue #43]
Signed-off-by: Mirza Krak
---
.../0003-Include-lowlevel_init.o-for-rpi2.patch| 25 ++
recipes-bsp/u-boot/u-boot_%.b
From: Mirza Krak
Not applicable on U-boot 2016.03 which is used in poky/morty and causes an build
error when KERNEL_IMAGETYPE = "uImage".
This reverts commit 031e26954b95d49a66ea4677b9e867d08441f450.
[Issue #43]
Signed-off-by: Mirza Krak
---
Changes in V2:
- Fixed spelling and improved commi
Right, we have not tested the layer index code with Django > 1.8.x, I would
expect problems like this until we migrate (which probably won't be for a
while I suspect).
Cheers,
Paul
On Tuesday, 24 January 2017 2:57:46 PM NZDT Peter Tulpen wrote:
> Hello Paul,
> you are brilliant:
> I had errors
On 1/24/17 7:16 AM, Bogusz Brodziński wrote:
> Hi,
>
> TL;DR after migrating from jethro to morty my out-of-tree modules do not
> load.
>
> Long version:
> Im developing uio driver for a custom FPGA. The base is xilinx zu15
> (note: as the explanation will go on I *think* it will be clear that
From: Mirza Krak
U-boot has been updated to 2017.01 in poky/oe-core which contains these
patches.
Signed-off-by: Mirza Krak
---
...0001-arm-add-save_boot_params-for-ARM1176.patch | 56
...through-of-the-firmware-provided-FDT-blob.patch | 156 -
recipes-bsp/u-boot/
On Tue, 24 Jan 2017 19:32:04 +0100
Mirza Krak wrote:
> From: Mirza Krak
>
> U-boot has been updated to 2017.01 in poky/oe-core which contains
> these patches.
>
> Signed-off-by: Mirza Krak
I've been working on the exact same patch here, just hadn't had chance
to test it yet. Looks good to me
Hello Yocto.
Though it may feel to me matter of taste, is there suggestion on when which of
these to use when you need to define your customized feature.
DISTRO_FEATURES seems to be more relaxed, you can define things in your distro
conf.
IMAGE_FEATURE seems to be more strict, and you need to ad
For the last couple of days, I've been seeing my bitbake builds
just shutdown, without actually completing, like this:
Initialising tasks: 100%
|###| Time:
0:00:10
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR
On 2017-01-25 07:50, Gary Thomas wrote:
For the last couple of days, I've been seeing my bitbake builds
just shutdown, without actually completing, like this:
Initialising tasks: 100%
|###| Time:
0:00:10
NOTE: Executing SetScene T
22 matches
Mail list logo
