mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Sekhar Nori <nsekhar@ti.com>, Jonathan Cameron <jic23@kernel.org>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools: iio: add ability to pass kernel headers
Date: Thu, 20 Apr 2017 08:27:33 -0700	[thread overview]
Message-ID: <fda2abcc-abbf-f883-e564-160b977d88a2@infradead.org> (raw)
In-Reply-To: <b59f1267-b30e-4c64-0a93-8f75b17fcdfb@ti.com>

On 04/20/17 06:53, Sekhar Nori wrote:
> On Tuesday 18 April 2017 03:42 PM, Sekhar Nori wrote:
>> Hi Jonathan, Randy,
>>
>> On Friday 14 April 2017 08:53 PM, Jonathan Cameron wrote:
>>> On 14/04/17 16:23, Randy Dunlap wrote:
>>>> On 04/14/17 07:42, Jonathan Cameron wrote:
>>>>> On 11/04/17 12:06, Sekhar Nori wrote:
>>>>>> Very often, especially when cross compiling, there is a need
>>>>>> to pass kernel headers different from those installed on the
>>>>>> build machine.
>>>>>>
>>>>>> Add support for doing this for iio utils by using the
>>>>>> 'INSTALL_HDR_PATH' environment variable. This is supported by
>>>>>> 'make headers_install' for installing kernel headers at a
>>>>>> user specified location. So you will do:
>>>>>>
>>>>>> $ make headers_install ARCH=arm INSTALL_HDR_PATH=<absolute-path>
>>>>>> $ make -C tools/iio ARCH=arm INSTALL_HDR_PATH=<absolute-path>
>>>>>>
>>>>>> Signed-off-by: Sekhar Nori <nsekhar@ti.com>
>>>>>
>>>>> It's a bit of an oddity as that usually refers to where to put
>>>>> the headers rather than where they are.
>>>>>
>>>>> Is there a more general solution?  I couldn't find anything
>>>>> particularly consistent in tools.
>>>>
>>>> Whatever the solution is, it should be used for all tools/, not just iio.
>>>>
>>> Agreed!
>>
>> Alright, I will try to come up with something more generic and post
>> another version.
> 
> I have been looking at this, and coming up with something generic is
> more complicated than I thought. The problem is the flexibility thats
> allowed in building many of the tools. For example, you can build the
> led tools using any of these three methods:
> 
> $ make -C <kernelsrcdir> tools/leds
> $ make -C <kernelsrcdir>/tools leds
> $ make -C <kernelsrcdir>/tools/leds
> 
> The last one is specifically complicated because it totally bypasses all
> top level makefiles. I think adding dependency with a top level makefile
> will be a step backwards at least for leds.
> 
> Currently the leds makefile adds '-I../../include/uapi' to CFLAGS to
> access the latest kernel headers. Something similar is done for some
> other tools too. This makes it work for all the build cases above. I
> propose we do something similar for iio too.

Thanks for diving into all of that.  I am not surprised at
what you have found.

I believe that you can go ahead with your iio proposal.


-- 
~Randy

      reply	other threads:[~2017-04-20 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11 11:06 Sekhar Nori
2017-04-14 14:42 ` Jonathan Cameron
2017-04-14 15:23   ` Randy Dunlap
2017-04-14 15:23     ` Jonathan Cameron
2017-04-18 10:12       ` Sekhar Nori
2017-04-20 13:53         ` Sekhar Nori
2017-04-20 15:27           ` Randy Dunlap [this message]

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=fda2abcc-abbf-f883-e564-160b977d88a2@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nsekhar@ti.com \
    --cc=pmeerw@pmeerw.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

all inboxes | Powered by JetHome®