From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] Philip Balister : i2c-tools : Stage i2c-dev.h header as i2c-dev-user.h.
Date: Wed, 15 Dec 2010 14:15:10 +0100 [thread overview]
Message-ID: <4D08BF5E.5050105@opendreambox.org> (raw)
In-Reply-To: <4D08B85B.3000404@balister.org>
On 12/15/2010 01:45 PM, Philip Balister wrote:
> On 12/15/2010 03:29 AM, Martin Jansa wrote:
>> On Wed, Dec 15, 2010 at 09:16:04AM +0100, Koen Kooi wrote:
>>> What are other distributions based on? Pixie dust?
>>
>> I meant distritubions where end-user normally gets only recipes how to
>> build from source
>> on his machine instead of installing prebuilt binary packages shipped
>> by distribution.
>>
> I am not sure there is a lot od software that uses the problematic
> header :)
>
> Khem suggested we put the file in include/i2c-tools/i2c-dev.h. This
> means programs that need the i2c-tools version can adjust the header
> search path with a -I.
I think what Khem suggested was ${include}/i2c-tools/linux/i2c-dev.h,
because otherwise programs including <linux/i2c-dev.h> would still pick
up the kernel header, even if -I${include}/i2c-tools was prepended to
the program's CPPFLAGS.
Regards,
Andreas
next prev parent reply other threads:[~2010-12-15 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1PR45K-0000jK-SU@melo.openembedded.org>
2010-12-14 12:06 ` [oe-commits] Philip Balister : i2c-tools : Stage i2c-dev.h header as i2c-dev-user.h Dr. Michael Lauer
2010-12-14 13:30 ` Philip Balister
2010-12-14 13:37 ` Martin Jansa
2010-12-15 8:16 ` Koen Kooi
2010-12-15 8:29 ` Martin Jansa
2010-12-15 12:45 ` Philip Balister
2010-12-15 13:15 ` Andreas Oberritter [this message]
2010-12-16 6:34 ` Khem Raj
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=4D08BF5E.5050105@opendreambox.org \
--to=obi@opendreambox.org \
--cc=openembedded-devel@lists.openembedded.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