> On Mar 9, 2022, at 4:59 AM, Daniel Squires wrote:
>
> Just to be absolutely clear, here is the result of having run bitbake
> build-essential having first removed and thus started with a clean tmp dir.
>
> dan@melon:/home/dan/workspace_ssd/kas/build$ find tmp/deploy/deb/
> tmp/deploy/deb/
Just to be absolutely clear, here is the result of having run bitbake
build-essential having first removed and thus started with a clean tmp dir.
dan@melon:/home/dan/workspace_ssd/kas/build$ find tmp/deploy/deb/
tmp/deploy/deb/
tmp/deploy/deb/all
Yes, in RDPENDS, here's an example of an attempt at the equivalent of Ubuntu's
build-essential package:
DESCRIPTION = "Informational list of build-essential pacakages"
inherit packagegroup
PACKAGES = "\
${PN} \
"
RDEPENDS:${PN} = "\
libc6-dev \
g++ \
gcc \
make \
"
INSANE_SKIP:${PN} =
Just want to add that it seems to run the do_package task but not the
do_package_write_deb one for each of the dependencies.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56405): https://lists.yoctoproject.org/g/yocto/message/56405
Mute This
On Wed, Mar 9, 2022 at 5:24 AM Daniel Squires wrote:
>
> We have our image and it is working as we need.
> We have an apt repo setup and working so that we can install additional
> packages within a deployment of the image.
> However when we manually bitbake additional packages (e.g bitbake
>
We have our image and it is working as we need.
We have an apt repo setup and working so that we can install additional
packages within a deployment of the image.
However when we manually bitbake additional packages (e.g bitbake
my-optional-recipe) which we want to make available within this apt
