From: "Denys Dmytriyenko" <denis@denix.org>
To: Kevin Kettinger <kkettinger@gmail.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] opkg package manifest file is not generated by bitbake
Date: Fri, 5 Jun 2020 02:53:11 -0400 [thread overview]
Message-ID: <20200605065311.GL17660@denix.org> (raw)
In-Reply-To: <c5efd245-ec33-c182-ea8c-8bc246c512c0@gmail.com>
bitbake package-index
On Fri, Jun 05, 2020 at 08:48:22AM +0200, Kevin Kettinger wrote:
> Hello,
>
> i want to use my yocto build sever as opkg package source for
> updating some packages directly, but it seems after generating an
> image the "Packages" file for opkg is not created.
>
> In the ./<build>/tmp/deploy/ipk folder, there are these folders
> ---------------------------------------------------------------------
> all
> apalis_imx6
> cortexa9hf-neon
> cortexa9t2hf-neon
> cortexa9t2hf-neon-mx6qdl
> ---------------------------------------------------------------------
> but no "Packages" or "Packages.gz" file.
>
> My local.conf:
> ---------------------------------------------------------------------
> BB_NUMBER_THREADS ?= "${@oe.utils.cpu_count()}"
> PARALLEL_MAKE ?= "-j ${@oe.utils.cpu_count()}"
> MACHINE ??= "apalis-imx6"
> MACHINE_HOSTNAME ?= "b2qt-${MACHINE}"
> DL_DIR ?= "${TOPDIR}/../downloads"
> SSTATE_DIR ?= "${TOPDIR}/../sstate-cache"
> DISTRO ?= "b2qt"
> PACKAGE_CLASSES ?= "package_ipk"
> EXTRA_IMAGE_FEATURES = "debug-tweaks"
> USER_CLASSES ?= "buildstats image-mklibs"
> PATCHRESOLVE = "noop"
> BB_DISKMON_DIRS = "\
> STOPTASKS,${TMPDIR},1G,100K \
> STOPTASKS,${DL_DIR},1G,100K \
> STOPTASKS,${SSTATE_DIR},1G,100K \
> ABORT,${TMPDIR},100M,1K \
> ABORT,${DL_DIR},100M,1K \
> ABORT,${SSTATE_DIR},100M,1K"
> CONF_VERSION = "1"
> INHERIT += "image-buildinfo"
> INHERIT += "internal-build"
> ACCEPT_FSL_EULA = "1"
> LICENSE_FLAGS_WHITELIST = "commercial"
> QT_SDK_PATH = ""
> PRSERV_HOST = "localhost:0"
> include conf/distro/include/${MACHINE}.pre.inc
> INHERIT+="toaster buildhistory"
> BUILDHISTORY_COMMIT = "1"
> ---------------------------------------------------------------------
>
> My image.bb file does provider "package-management":
> ---------------------------------------------------------------------
> IMAGE_FEATURES += "\
> package-management \
> ssh-server-dropbear \
> tools-debug \
> tools-profile \
> debug-tweaks \
> hwcodecs \
> "
> ---------------------------------------------------------------------
> (opkg is working on the embedded device)
>
> Output after building an image:
> ---------------------------------------------------------------------
> BB_VERSION = "1.42.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING = "universal"
> TARGET_SYS = "arm-poky-linux-gnueabi"
> MACHINE = "apalis-imx6"
> DISTRO = "b2qt"
> DISTRO_VERSION = "2.7.3"
> TUNE_FEATURES = "arm vfp cortexa9 neon thumb callconvention-hard"
> TARGET_FPU = "hard"
> SDKMACHINE = "x86_64"
> ---------------------------------------------------------------------
>
> A appreciate any help.
>
> Mit freundlichen Grüßen / Best regards,
> Kevin Kettinger
>
next prev parent reply other threads:[~2020-06-05 6:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 6:48 opkg package manifest file is not generated by bitbake kkettinger
2020-06-05 6:53 ` Denys Dmytriyenko [this message]
2020-06-05 6:57 ` [yocto] " Kevin Kettinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200605065311.GL17660@denix.org \
--to=denis@denix.org \
--cc=kkettinger@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.