Locate libi2c-dev include paths
Tue Mar 5 18:13:00 GMT 2013
On Tue, Mar 5, 2013 at 11:55 AM, Michael Powell <firstname.lastname@example.org> wrote:
> On Tue, Mar 5, 2013 at 11:13 AM, Michael Powell <email@example.com> wrote:
>> In particular for linux/i2c-dev.h, and in particular in particular,
>> for the i2c_smbus_write_i2c_block_data keyword.
> Is there any straightforward way to patch the crosstool-ng source with
> the latest I2C dev lib? I'd like to avoid compounding technical debts
> of rewriting anything.
For the moment, looks as though I include -I/usr/local and pick up the
I2C static inline header/source (for now).
> Particularly, we literally have more application level things to be
> concerning ourselves with than dealing with such a low-level thing at
> this time.
>> I've installed libi2c-dev, which i2c_smbus_write_i2c_block_data
>> apparently depends upon; i2c-tools won't do the trick.
>> When I build for x86, it works. When I build using our ARM
>> crosstool-ng cross compiler, the process complains about;
>> I have several paths to choose from when I find for the i2c-dev.h
>> file. I can make a couple of educated guesses, but if someone had any
>> recommendations, that'd be great.
>> Michael Powell
For unsubscribe information see http://sourceware.org/lists.html#faq
More information about the crossgcc