public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Stephen Kelly <steveire@gmail.com>
To: crossgcc@sourceware.org
Subject: Finding include directories in the sysroot
Date: Mon, 20 May 2013 18:38:00 -0000	[thread overview]
Message-ID: <519A6DBD.2030403@gmail.com> (raw)

Hi there,

I have a rootfs which has Qt installed in /usr. So for example, qobject.h
exists at /usr/include/QtCore/qobject.h.

My rootfs is at ~/rpi/rasp-pi-rootfs.

I invoke

  arm-linux-gnueabihf-g++-4.7 --sysroot=/home/stephen/rpi/rasp-pi-rootfs \
   -I/usr/include/QtCore  -v -c myfile.cpp

and I see this:

  ignoring nonexistent directory "/usr/include/QtCore"
  #include "..." search starts here:
  #include <...> search starts here:
  /usr/lib/gcc-cross/arm-linux-gnueabihf/4.7/include
  /usr/lib/gcc-cross/arm-linux-gnueabihf/4.7/include-fixed
  /usr/lib/gcc-cross/arm-linux-gnueabihf/4.7/../../../../arm-linux-
gnueabihf/include
  /home/stephen/rpi/rasp-pi-rootfs/usr/include/arm-linux-gnueabihf
  /home/stephen/rpi/rasp-pi-rootfs/usr/include
  End of search list.


So, it's not finding /usr/include/QtCore in my host root file system, and
it
is not looking in the sysroot I passed, as I expected. I also tried using
the -isysroot option, with a similar result.

Is my expectation incorrect? What can I really expect from the sysroot
option?

My goal is implementing proper sysroot handling for the cmake buildsystem
tool, so I need to understand how it is intended to work and what can be
expected of it.

Thanks,

Steve.


--
For unsubscribe information see http://sourceware.org/lists.html#faq

             reply	other threads:[~2013-05-20 18:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 18:38 Stephen Kelly [this message]
2013-05-20 18:52 ` Yann E. MORIN

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=519A6DBD.2030403@gmail.com \
    --to=steveire@gmail.com \
    --cc=crossgcc@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).