From: David Bonnin <dboml@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] use custom kernel headers
Date: Wed, 10 Apr 2013 23:26:33 +0200 [thread overview]
Message-ID: <5165D909.1060104@free.fr> (raw)
Hello,
We have modify/create linux kernel drivers (out of tree build with an
other toolchain).
We try to include theses custom headers from our user space application.
What is the good way to handle these custom headers without rebuild
toolchain each we modify our kernel driver?
We use for BR, an externel toolchain build with CTNG.
For the moment we've used a very dirty absolute include path in the
Makefile.
-D/src/project/linux/drivers/myDriver/include/
Watch your experience in use of specific drivers headers?
I didn't seen a standard way to handle this in BR...
Thanks for any help.
reply other threads:[~2013-04-10 21:26 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=5165D909.1060104@free.fr \
--to=dboml@free.fr \
--cc=buildroot@busybox.net \
/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