All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: sscott@san.rr.com
Cc: Yocto-mailing-list <yocto@yoctoproject.org>
Subject: Re: how to install files in nativesdk
Date: Mon, 8 Oct 2018 12:10:30 +0100	[thread overview]
Message-ID: <CAJTo0LaK6P5x1ciFJZDFudnemD4i7eEtVYbC2pV-GuPah2RHKw@mail.gmail.com> (raw)
In-Reply-To: <001201d45d33$c247aee0$46d70ca0$@san.rr.com>

On Sat, 6 Oct 2018 at 06:18, Steve Scott <sscott@san.rr.com> wrote:
> I am able to generate a standard SDK with native and target
> sysroots. The target sysroot has header files for my custom
> libraries. The header files are generally installed in
> <path-to-sdk-target-sysroot>/usr/include/
>
> We use cmake and googletest running on the *host* for testing some of
> our libraries. So I need to build googletest and the test apps using the
> host (x86_64) tools. The test apps need to include the target's library
> header files.
>
> I tried specifying the SDK's *target* usr/include as an include directory to
> the compiler, but files in this tree preempted the standard compiler (g++)
> system include files. I can avoid this problem by installing the library
> header files under the SDK's native sysroot; i.e. in
> <path-to-sdk-native-sysroot>/usr/include/
> and setting this directory as an include directory on the compiler
> command line.
>
> However, I cannot grok how to get these files into the SDK's native
> tree. It seems related to
>    BBCLASSEXTEND = "native nativesdk"
> but I'm just chasing my tail trying to figure out the magic incantation.
>
> Does anyone know how to do this? Or is there a better approach?

Assuming the recipe is correctly written, simply adding:

BBCLASSEXTEND = "native nativesdk"

Will give your recipe (eg foo.bb) native and nativesdk variant
(foo-native and nativesdk-foo).  The class extension automatically
changes the paths so in general that's all you need to do.  Then just
add nativesdk-foo to your SDK using TOOLCHAIN_HOST_TASK_append = "
nativesdk-foo".

Ross


  reply	other threads:[~2018-10-08 11:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-06  5:16 how to install files in nativesdk Steve Scott
2018-10-08 11:10 ` Burton, Ross [this message]
2018-10-09  1:19   ` Steve Scott

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=CAJTo0LaK6P5x1ciFJZDFudnemD4i7eEtVYbC2pV-GuPah2RHKw@mail.gmail.com \
    --to=ross.burton@intel.com \
    --cc=sscott@san.rr.com \
    --cc=yocto@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.