On Fri, Oct 18, 2013 at 6:20 AM, Chris Morgan <[email protected]> wrote: > On Friday, October 18, 2013, Anders Larsen wrote: >> >> On 2013-10-18 10:20, xantares 09 wrote: >>> >>> >>> > From: [email protected] >>> > Date: Thu, 17 Oct 2013 14:09:19 -0400 >>> > Subject: Proper include path for ftdi.h >>> > To: [email protected] >>> > >>> > Hello. >>> > >>> > I wanted to confirm the proper include path for libftdi. >>> > >>> > libmpsse is doing: >>> > >>> > #include <libftdi1/ftdi.h> >>> > >>> > But the code in some of the ftdi examples is doing: >>> > >>> > #include <ftdi.h> >>> > >>> > >>> > I suspect mpsse is doing this for compatibility with both libftdi 0.x >>> > and 1.x. What is the recommended include format? >>> > >>> > Chris >>> >>> Definetely #include <ftdi.h>, as LIBFTDI_INCLUDE_DIR is set to >>> <prefix>/include/libftdi1 in the cmake config. >>> x. >> >> >> LIBFTDI_INCLUDE_DIR is internal to libftdi; external applications (e.g. >> libmpsse) must still use >> >> #include <libftdi1/ftdi.h> >> >> Cheers >> Anders >> -- >> libftdi - see http://www.intra2net.com/en/developer/libftdi for details. >> To unsubscribe send a mail to [email protected] > > > > So if I'm using cmake and find_package, shouldn't the include directories > variable point to the parent of what it does today? I asked the original > question because today it points to libftdi1, wherever it is found by the > script file. > > I'm following the example cmake file in /cmake. > > Chris > >
Anyone? Chris -- libftdi - see http://www.intra2net.com/en/developer/libftdi for details. To unsubscribe send a mail to [email protected]
