From: Stephen Boyd <sboyd@codeaurora.org>
To: linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Detecting system includes in drivers
Date: Thu, 20 Jul 2017 11:44:49 -0700 [thread overview]
Message-ID: <20170720184449.GA19878@codeaurora.org> (raw)
I've run into a problem where I have a driver C file and a header
file for that driver that are in the same directory. The C file
has an include like
#include <driver.h>
instead of
#include "driver.h"
and building this in tree fails, but building it out of tree with
the O= option doesn't fail. Is there anyway that building out of
tree can be made to fail as well? The difference seems to be that
we include the directory for the drivers/ path when compiling the
C file out of tree, but we don't do that when building in tree.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
reply other threads:[~2017-07-20 18:44 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=20170720184449.GA19878@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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