All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: STAGING_KERNEL_DIR
Date: Tue, 15 Jun 2010 10:11:27 +0200	[thread overview]
Message-ID: <hv7cjf$9kc$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTilHhuvcQFQBwVWkW6_Nf7xQPd6xDQlZzv4kvnel@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 15-06-10 07:36, Andrew Tverdohlebov wrote:
> Hello,
> 
> I am developing a recipe for a code that needs to obtain kernel
> configuration parameters
> in order to compile correctly.

If your recipe is really machine specific, add PACKAGE_ARCH =
"${MACHINE_ARCH}"

If not, add:

# We want a kernel header for armv7a, but we don't want to make mplayer
machine specific for that
STAGING_KERNEL_DIR =
"${STAGING_DIR}/${MACHINE_ARCH}${TARGET_VENDOR}-${TARGET_OS}/kernel"

regards,

Koen


> 
> According to the manual there is a variable STAGING_KERNEL_DIR that is
> supposed to point to the kernel staging dir.
> In my case it points to staging/mips-linux where I don't see '.config' file.
> The '.config' file is located in staging/xls4lte-linux (xls4lte - is a
> name assigned to MACHINE in local.conf)
> 
> My question: - what is a correct way to refer to a directory where
> kerenel's config file is located.
> 
> The second question is - what is a point in several directories in staging dir ?
> 
> In my case I have:
> i686-linux
> i686-linux-sdk
> mips-linux
> xls4lte-linux
> 
> I thought that this might be a property of my distro and checked
> angstrom for beagleboard and saw the same picture there:
> 
> while working on my custom linux distro based on openembedded if noticed.
> armv7a-angstrom-linux-gnueabi
> armv7a-linux
> beagleboard-angstrom-linux-gnueabi
> i686-linux
> 
> In both cases at least two separate dirs are created in staging. One
> ${MACHINE}-linux and another ${TARGET-ARCH}-linux.  What are they for
> ?
> And how to properly refer to staging/${MACHINE}-linux ?
> 
> Any help will be hugely appreciated.
> Andrew

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMFzWvMkyGM64RGpERApsQAJ0Wmg02kVDp5rl0jnb8nxEClBW7AACfdwLj
JFufKD77LgRZ5pOdT9YXegk=
=oHiS
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-06-15  8:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-15  5:36 STAGING_KERNEL_DIR Andrew Tverdohlebov
2010-06-15  8:11 ` Koen Kooi [this message]
2010-06-15 12:15   ` STAGING_KERNEL_DIR Andrew Tverdohlebov

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='hv7cjf$9kc$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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.