On Wed, Jul 11, 2018 at 9:28 AM Simon Chamlian wrote:
>
> I am getting the following error using devtool:
>
> $ devtool add help
> ERROR: Layer directory '/home/jay/sources/poky/meta' does not exist! Please
> check BBLAYERS in /home/jay/build/conf/bblayers.conf
>
> $ whereis devtool
> devtool:
I am getting the following error using devtool:
$ devtool add help
ERROR: Layer directory '/home/jay/sources/poky/meta' does not exist! Please
check BBLAYERS in /home/jay/build/conf/bblayers.conf
$ whereis devtool
devtool: /opt/PHYTEC_BSPs/yocto_imx7/sources/poky/scripts/devtool
The paths are
On 07/10/2018 02:18 PM, Paul Eggleton wrote:
On Tuesday, 10 July 2018 3:32:56 AM CEST ChenQi wrote:
I usually use the following steps when I need to modify source for some
purpose.
1. bitbake A (or at least bitbake A -c configure)
*2. cd tmp/work/x/A/**
**3. make the modification*
4.
On Tuesday, 10 July 2018 3:32:56 AM CEST ChenQi wrote:
> I usually use the following steps when I need to modify source for some
> purpose.
>
> 1. bitbake A (or at least bitbake A -c configure)
> *2. cd tmp/work/x/A/**
> **3. make the modification*
> 4. bitbake A -c compile -f
> 5. bitbake A
On Fri, Jul 6, 2018 at 8:20 AM Simon Chamlian wrote:
>
> Hi,
>
> Is there a way to keep the source code of a package to be able to modify it
> and then compile?
>
> For example, with LTIB ( Linux Target Image Builder ), it was possible with a
> command to extract the source code from a package,
Hi Simon,
I usually use the following steps when I need to modify source for some
purpose.
1. bitbake A (or at least bitbake A -c configure)
*2. cd tmp/work/x/A/**
**3. make the modification*
4. bitbake A -c compile -f
5. bitbake A
If you find the modification useful, make a patch from
On Fri, Jul 06, 2018 at 09:11:35PM +0200, Ulf Samuelsson wrote:
In my current project we have a simplified version in a
”component.bbclass”. It relies on a variable COMPONENT_DIR
defined in our local.conf.
A recipe located in ”recipe-//_$PV.bb” doing
inherit component
will find its
externalsrc.bbclass?
In my current project we have a simplified version in a ”component.bbclass”.
It relies on a variable COMPONENT_DIR defined in our local.conf.
A recipe located in ”recipe-//_$PV.bb” doing
inherit component
will find its source code in $COMPONENT_DIR/, making the recipe
On Fri, Jul 6, 2018 at 11:20 AM, Simon Chamlian
wrote:
> Hi,
>
> Is there a way to keep the source code of a package to be able to modify
> it and then compile?
>
> For example, with LTIB ( Linux Target Image Builder ), it was possible
> with a command to extract the source code from a package,
Hi Simon,
> Is there a way to keep the source code of a package to be able to
modify it and then compile?
Yes, there is. devtool greatly simplifies this type of workflow. Please
refer to
https://www.yoctoproject.org/docs/2.5/mega-manual/mega-manual.html#using-devtool-in-your-sdk-workflow
for
Hi,
Is there a way to keep the source code of a package to be able to modify it
and then compile?
For example, with LTIB ( Linux Target Image Builder ), it was possible with
a command to extract the source code from a package, make modifications and
then re-compile?
Thanks,
S
--
11 matches
Mail list logo
