Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Julian Pietron <julian@whisper-net.de>
To: openembedded-devel@lists.openembedded.org
Subject: Install SDKs for multiple machines in parallel
Date: Sat, 26 May 2012 21:00:59 +0200	[thread overview]
Message-ID: <4FC1286B.8020200@whisper-net.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]

Hallo,

while switching from OE classic to OE-core, some questions arised
concerning SDK generation in OE-core. In OE-Classic, I used to set
SDKPATH so that each of my machines (I have several different machines I
need to build my distribution for) had its separate directory under
/opt/sdk/<mymachine>, so that all files belonging to the toolchain were
installed there. The advantage of this configuration was, that I could
have bitbake create a debian package for the toolchain for each machine
and install these toolchain packages for different machines at the same
time, because there were no file collisions.
In OE-core, however, I realized that setting SDKPATH my usual
configuration wouldn't work out because there are the
nativesdk-packages, that seem to be machine-independent. So what I'd
need would be a way to split the generated toolchain into the nativesdk
path that is the same for each machine, and the cross-compiler, sysroot
etc. that is different for each machine, so that I'd be able to install
them as separate debian packages.
How would one do this with OE-Core?

Thanks for your suggestions,
Julian


[-- Attachment #2: 0xD8407950.asc --]
[-- Type: application/pgp-keys, Size: 9859 bytes --]

                 reply	other threads:[~2012-05-26 19:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4FC1286B.8020200@whisper-net.de \
    --to=julian@whisper-net.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox