All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steve Scott" <sscott@san.rr.com>
To: <yocto@yoctoproject.org>
Subject: how to install files in nativesdk
Date: Fri, 5 Oct 2018 22:16:35 -0700	[thread overview]
Message-ID: <001201d45d33$c247aee0$46d70ca0$@san.rr.com> (raw)

Hi:

I'm a list newbie, so let me know if this should be posted somewhere else.

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?

Thanks.

-steve scott






             reply	other threads:[~2018-10-06  5:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-06  5:16 Steve Scott [this message]
2018-10-08 11:10 ` how to install files in nativesdk Burton, Ross
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='001201d45d33$c247aee0$46d70ca0$@san.rr.com' \
    --to=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.