libftdi Archives

Subject: Re: 1.0 vs 0.16 include path change

From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
Cc: Albert ARIBAUD <albert.aribaud@xxxxxxx>
Date: Thu, 26 Nov 2009 09:41:11 +0100
Salut Albert,

On Thursday, 26. November 2009 07:58:13 Albert ARIBAUD wrote:
> I've come across a problem compiling OpenOCD with LIBFTDI, both from
> latest git: LIBFTDI puts headers in /usr/include/libftdi while OpenOCD
> expects them to be in /usr/include, and fails compiling files which have
> a #include <ftdi.h>.
> 
> This header location is a departure from older LIBFTDI, such as 0.16,
> where headers went to /usr/include. For instance, see
> <http://packages.debian.org/squeeze/amd64/libftdi-dev/filelist> which is
> for 0.16.
> 
> I bisected the issue to commit 0b2d00fcee8dee36c47060e933d4adbefa05a56e
> which introduced CMakeLists. This is the file that defines the LIBFTDI
> include path to be /usr/include/libftdi.
> 
> I am just pointing out the change in order to make sure you know it
> happened (the changelogs did not mention that explicitely) and can
> decide if that was your intention or not--anyway, I believe OpenOCD
> should use pkg-config to find out about the includes and libs of libftdi.

Interesting findings. Like you said the correct solution is to use
pkgconfig or the libftdi-config script.

I guess this is a cmake vs. autoconf suite issue.
Which one did you use to create the makefiles?

Cheers,
Thomas

--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx   

Current Thread