All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marty Leisner" <leisner@rochester.rr.com>
To: "Linux Kernel list" <linux-kernel@vger.kernel.org>
Cc: martyleisner@yahoo.com, martin.leisner@xerox.com
Subject: Prepending include paths when building out of tree modules
Date: Tue, 23 Feb 2010 17:11:47 +0000	[thread overview]
Message-ID: <201002231711.o1NHBl0q010699@dell2.home> (raw)

I'm building thirdparty cryptography modules (which define they're own
crypto/* files, which was more fully populated in the 2.6.24-26 range and 
conflicts with headers in my thirdparty modules. 

Since I want to use my crypto/* hierarchy instead of the kernels, and
the source has

 #include "crytpo/aes.h"

I want to prepend paths to the kernel header search.

I added the -I to NOSTDINC_FLAGS and it works but:
     a) it doesn't seem right
     b) is there a better/more clear way?

Something like PREPEND_INCLUDE_PATH or something?  (I didn't see anything in gcc to get around this)

marty
~


                 reply	other threads:[~2010-02-23 17:11 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=201002231711.o1NHBl0q010699@dell2.home \
    --to=leisner@rochester.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.leisner@xerox.com \
    --cc=martyleisner@yahoo.com \
    /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.