From: Mariano Lopez <just.another.mariano@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v4 0/4] Feature to use symbolic links to binaries for ptest
Date: Tue, 9 Apr 2019 00:44:11 -0500 [thread overview]
Message-ID: <cover.1554787765.git.just.another.mariano@gmail.com> (raw)
Some binaries are renamed by update-alternatives class at build time
and some ptest run against a binary belonging to another package. Take
for example busybox or util-linux.
This series adds a directory within the ptest with symlinks to the
binaries produced by the package, so just adding this directory to the
PATH will test the correct binaries.
To use this feature just add PTEST_BINDIR = "1" to the recipe.
v2 changes:
Add busybox recipe to use this method of symlinks generation.
Refactor the way the binary ptest directory is generated. Now the
directory will contain only symlinks to binaries that were renamed by
update-alternatives and not symlinks to all the package's binaries. This
have some advantages:
- Less lines and the code is cleaner.
- There is no need to have symlinks for every binary.
- Reuse existing update-alternatives functionality, don't need to add
new features to the class.
v3 changes:
Fix white space mismatch
v4 changes:
Check for PTEST_ENABLED to add the functionality, this will solve the
issue when building nativesdk packages
The following changes since commit ffa5a1bda6741f5dc9f1b8db1bb37b0c6f103c99:
asciidoc: specify XML catalogue to use (2019-04-03 14:56:27 +0100)
are available in the Git repository at:
git://github.com/justanotherboy/poky bug13238v4
https://github.com/justanotherboy/poky/tree/bug13238v4
Mariano Lopez (4):
update-alternatives.bbclass: Add function to get metadata
ptest.bbclass: Add feature to populate a binary directory
util-linux: Use PTEST binary directory
busybox: Use PTEST binary directory
meta/classes/ptest.bbclass | 32 +++++++++
meta/classes/update-alternatives.bbclass | 70 ++++++++++++-------
meta/recipes-core/busybox/busybox.inc | 16 +----
meta/recipes-core/util-linux/util-linux.inc | 5 +-
.../util-linux/util-linux/run-ptest | 4 ++
5 files changed, 86 insertions(+), 41 deletions(-)
--
2.19.2
next reply other threads:[~2019-04-09 5:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 5:44 Mariano Lopez [this message]
2019-04-09 5:44 ` [PATCH v4 1/4] update-alternatives.bbclass: Add function to get metadata Mariano Lopez
2019-04-09 5:44 ` [PATCH v4 2/4] ptest.bbclass: Add feature to populate a binary directory Mariano Lopez
2019-04-11 20:11 ` Richard Purdie
2019-04-13 16:19 ` Mariano Lopez
2019-04-09 5:44 ` [PATCH v4 3/4] util-linux: Use PTEST " Mariano Lopez
2019-04-09 5:44 ` [PATCH v4 4/4] busybox: " Mariano Lopez
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=cover.1554787765.git.just.another.mariano@gmail.com \
--to=just.another.mariano@gmail.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox