Fixes build error:
| make: *** No rule to make target 'openembedded'. Stop.
Signed-off-by: Yi Zhao
---
.../recipes-openscap/scap-security-guide/scap-security-guide_0.1.33.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git
a/meta-security-compliance/recipes-openscap/scap-security-guide/s
On Wed, Mar 6, 2019 at 11:37 PM Mark Hatle wrote:
>
> On 3/5/19 10:44 PM, Alex Kiernan wrote:
> > On Tue, Mar 5, 2019 at 10:50 PM Richard Purdie
> > wrote:
> >>
> >> On Tue, 2019-03-05 at 16:05 +, Alejandro Del Castillo wrote:
> >>>
> >>> On 3/5/19 12:11 AM, ChenQi wrote:
> Hi All,
> >>>
On 3/5/19 10:44 PM, Alex Kiernan wrote:
> On Tue, Mar 5, 2019 at 10:50 PM Richard Purdie
> wrote:
>>
>> On Tue, 2019-03-05 at 16:05 +, Alejandro Del Castillo wrote:
>>>
>>> On 3/5/19 12:11 AM, ChenQi wrote:
Hi All,
Recently I'm dealing with issue from which some discussion raise
On 2019-03-06 14:26, Kaz Kylheku (poky) wrote:
So I'm guessing this should be
FILES_${PN}-core_remove =
No dice. FILES_${PN}-core_remove = "${libdir}/python-2.7/encodings" does
not register anywhere. In the "bitbake -e" output, no _remove event
appears for FILES_python-core, and the image
On Wed, 6 Mar 2019 at 22:27, Kaz Kylheku (poky)
<442-103-8...@kylheku.com> wrote:
> Ah, okay; this is because it's been split into various sub-packages. So
> we have to operate on "-core".
> The .json manifest brings these into the "core" package:
>
> "${libdir}/python2.7/encodings",
>
On 2019-03-06 12:29, Burton, Ross wrote:
On Wed, 6 Mar 2019 at 20:14, Kaz Kylheku (poky)
<442-103-8...@kylheku.com> wrote:
So, the issues are now is that
FILES_${PN}_remove = "${libdir}/python2.7/encodings"
in fact does not work, as I believed.
Have a look at python.bb. Specifically:
PACKA
On Wed, 6 Mar 2019 at 20:14, Kaz Kylheku (poky)
<442-103-8...@kylheku.com> wrote:
> So, the issues are now is that
>
> FILES_${PN}_remove = "${libdir}/python2.7/encodings"
>
> in fact does not work, as I believed.
Have a look at python.bb. Specifically:
PACKAGES_remove = "${PN}"
There is no PN
On 2019-03-06 10:23, Richard Purdie wrote:
On Tue, 2019-03-05 at 18:28 -0800, Kaz Kylheku (poky) wrote:
How do we get Yocto to react to FILES changes, short of blowing away
the entire build tree?
Maybe related to this change:
http://git.yoctoproject.org/cgit.cgi/poky/commit/bitbake/lib/bb/dat
My use case, as I've told to Scott, was building a bare metal firmware for
a cortex m0 with an external GCC toolchain. Although, the toolchain's
binaries are strippable, there are some other blob files that are needed
for the build, which are not.
Cheers,
Dimitris
Scott Rifenbark schrieb am Mi.,
Got it. Thanks Khem.
On Wed, Mar 6, 2019 at 10:22 AM Khem Raj wrote:
> On Wed, Mar 6, 2019 at 9:48 AM Scott Rifenbark
> wrote:
> >
> > I think we should probably at least document the variable in the YP
> Reference Manual's glossary. Correct?
> >
>
> yes and also mention that we only expect it
On Tue, 2019-03-05 at 18:28 -0800, Kaz Kylheku (poky) wrote:
> Hi,
>
> I'm working in a Yocto 2.5 environment.
>
> In my own layer, I added a bbappend targeting python which does this:
>
>FILES_${PN}_remove = "${libdir}/python2.7/encodings"
>
> Now this didn't take effect as I expected. I h
On Wed, Mar 6, 2019 at 9:48 AM Scott Rifenbark wrote:
>
> I think we should probably at least document the variable in the YP Reference
> Manual's glossary. Correct?
>
yes and also mention that we only expect it to be used in rare special
curcumstances, e,g, prebuilt binaries etc.
> Scott
>
>
I think we should probably at least document the variable in the YP
Reference Manual's glossary. Correct?
Scott
On Wed, Mar 6, 2019 at 9:24 AM Khem Raj wrote:
> On Wed, Mar 6, 2019 at 8:15 AM Scott Rifenbark
> wrote:
> >
> > Dimitris,
> >
> > Good find... I will see about documenting this.
>
On Wed, Mar 6, 2019 at 8:15 AM Scott Rifenbark wrote:
>
> Dimitris,
>
> Good find... I will see about documenting this.
>
Although its not encouranged to use it, its to be used as a last resort
we use it sparingly.
> Scott
>
> On Wed, Mar 6, 2019 at 8:12 AM Dimitris Tassopoulos wrote:
>>
>> Hi
From: Bruce Ashfield
The 5.0 kernel is available and 4.18 will soon be dropped,
so we updated the preferred version to 5.0.
Signed-off-by: Bruce Ashfield
---
meta-poky/conf/distro/poky.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-poky/conf/distro/poky.conf b/me
From: Kevin Hao
Signed-off-by: Kevin Hao
Signed-off-by: Bruce Ashfield
---
meta-yocto-bsp/conf/machine/beaglebone-yocto.conf | 2 +-
meta-yocto-bsp/conf/machine/edgerouter.conf | 2 +-
meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf | 2 +-
3 files changed, 3 insertions(+), 3 deletions
From: Kevin Hao
Boot test for all the boards.
Signed-off-by: Kevin Hao
Signed-off-by: Bruce Ashfield
---
.../linux/linux-yocto_5.0.bbappend| 24 +--
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.0.
From: Bruce Ashfield
Although the hardware reference boards are not using the 5.x
kernel yet, we generate a baseline bbappend for future work.
Signed-off-by: Bruce Ashfield
---
.../linux/linux-yocto_5.0.bbappend| 27 +++
1 file changed, 27 insertions(+)
create mode
From: Bruce Ashfield
This is a follow on to my oe-core series that introduces the 5.0
kernel. Once that is merged (and all outstanding issues resolved),
these can be applied to make the default 5.0 for poky and the
reference BSPs.
The removal of 4.18 from master will follow once everything is up
Dimitris,
Good find... I will see about documenting this.
Scott
On Wed, Mar 6, 2019 at 8:12 AM Dimitris Tassopoulos
wrote:
> Hi all,
>
> this is not a request for help.
>
> Today, I've found a very nice option which is not documented
> which is the INHIBIT_SYSROOT_STRIP and is used in the sysr
Hi all,
this is not a request for help.
Today, I've found a very nice option which is not documented
which is the INHIBIT_SYSROOT_STRIP and is used in the sysroot_strip()
inside the poky/meta/classes/staging.bbclass.
I had an issue with a recipe that had a few binaries that I wanted to add
to th
Yocto master has got a lot of fixing around gitsm fetcher
(particularly creation of symlinks seems to be gone), so if you could
try that and report, that would be appreciated.
Alex
On Wed, 6 Mar 2019 at 15:20, philippe gislard
wrote:
>
> Hello everyone,
>
> Our use case is the following:
> - We
The supported recommended workflow for this things is with devtool.
Please try especially 'devtool modify' and 'devtool upgrade'. The latter
will rebase patches for you, regardless of how they were made.
Alex
On Wed, 6 Mar 2019 at 15:18, Pandey, Kamal wrote:
> Hello,
>
> I am trying to modify
Hello everyone,
Our use case is the following:
- We are building firmwares using yocto on machines that have no internet access
- We have a mirror that we are feeding with tarballs generated by a
machine connected to internet
- We want to port our BSP to yocto thud
Until now (we used krogoth) our
Hello,
I am trying to modify the src code of a package named say x,
For this I type the command $bitbake x -c devshell.
This leads me to the git repo of the x package(if it is a git repo).
Now I do my changes, commit the changes, and create a patch out of it using git
format-patch.
Now I want this
25 matches
Mail list logo
