From: Robert Schuster <theBohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: bbclass providing some level of scratchbox compatibility
Date: Fri, 23 Nov 2007 15:14:29 +0100 [thread overview]
Message-ID: <4746E045.2070805@gmx.net> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1235 bytes --]
Hi,
I am using OE to build binaries that can be run from within Maemo
scratchbox.
The binaries I create are for the native architecture (the one of the
host CPU) not the emulated one. Such binaries need a special rpath. What
the bbclass does is simply putting that special rpath in LD_RUN_PATH
before configuring and compiling. This has the effect that all built
binaries have it in.
Together with a halfway compatible toolchain (CS gcc3.4.4, glibc2.3.x)
that allows me to run those binaries in Maemo's scratchbox.
I am using this for Jalimo[0] and would like to push it upstream. I am
open for suggestions.
File a bug?
Regards
Robert
[0] - http://jalimo.org/wiki/doku.php?id=doc:howto:cacaoandecjinscratchbox
# By adding this class to your build all binaries get the special rpath
# "/scratchbox/host_shared/lib/:/scratchbox/tools/lib/"
# Doing so makes libraries and programs runnable inside the Scratchbox
# environment as native binaries (not for the CPU that Scratchbox is
# emulating).
do_configure_prepend () {
export LD_RUN_PATH="/scratchbox/host_shared/lib:/scratchbox/tools/lib"
}
do_compile_prepend () {
export LD_RUN_PATH="/scratchbox/host_shared/lib:/scratchbox/tools/lib"
}
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next reply other threads:[~2007-11-23 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 14:14 Robert Schuster [this message]
2007-11-23 15:46 ` bbclass providing some level of scratchbox compatibility Koen Kooi
2007-11-23 17:09 ` Robert Schuster
-- strict thread matches above, loose matches on Subject: below --
2007-11-23 14:15 Robert Schuster
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=4746E045.2070805@gmx.net \
--to=thebohemian@gmx.net \
--cc=openembedded-devel@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 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.