I'm using Yocto 1.7.1 I'd like built programs to have the build path
striped down. The goal is if I'm looking at some programs log after cross
compiling I want this:
src/program.c:388
where I currently get this:
/usr/local/jenkins/workspace/project-build-manual/Project/build-project/tmp/work/arm
Thanks, I just found this post was addressed already ->
https://lists.yoctoproject.org/pipermail/poky/2015-August/010197.html
On Mon, Sep 12, 2016 at 1:16 PM, Burton, Ross wrote:
>
> On 12 September 2016 at 19:22, Matthew Stanger <
> matthew_stan...@trimble.com> wrote:
&g
Hi,
I'm running Yocto 1.7.1 and was wondering if there was a simple way to
roll/bump all package versions. For example in every .bb I want to bump PV
= $version higher. I'm trying to do this as we've designed our headless
system to update using opkg but now we are struggling to find a simple way
t
No Thanks I'm a rookie :)
On Mon, Mar 20, 2017 at 11:22 AM, Gary Thomas wrote:
> On 2017-03-20 16:52, Matthew Stanger wrote:
>
>> Hi,
>>
>> I'm running Yocto 1.7.1 and was wondering if there was a simple way to
>> roll/bump all package versions. For e
Hi,
I'm seeing the exact same bug as outlined here. It only happens when
the build server is unreachable:
http://lists.openembedded.org/pipermail/bitbake-devel/2015-April/005696.html
It crashes with the exact same error (self.state = 6) and bitbake
continues running in the background at 100% unti
I'm trying to figure out why when running devshell in Warrior CC/CFLAGS are
not the same as do_compile for a recipe. For example.
devshell printenv yields:
CC=aarch64-poky-linux-gcc -fuse-ld=bfd
-fmacro-prefix-map=/home/matt/rdk_warrior/build/tmp/work/7271-poky-linux/brcm/18.3+AUTOINC+0a6fb7430f-
d this would unset
CFLAGS and such but am not sure why the devshell should be different that
the environment at the first line of do_compile?
On Tue, Jun 18, 2019 at 10:08 AM Khem Raj wrote:
> On Mon, Jun 17, 2019 at 4:55 PM matthew stanger
> wrote:
> >
> > I'm trying t
>
> Is ./sources/poky/meta/recipes-core/systemd/systemd_234.bb the proper
> place to patch this service file?
You should really put this in a `.bbappend` instead and also that
`.bbappend` should be in your own meta-layer if possible. In case you want
to upgrade stuff in the future it makes lif