Use the same project name (i.e. libftdi1 and not libftdipp1) when FTDIPP is enabled as suggested by Aurelien Jarno in http://developer.intra2net.com/mailarchive/html/libftdi/2020/msg00044.html
Without this change, the libftdi1.pc config file defines the include path as /usr/local/include/libftdipp1 while the ftdi.h file is actually installed in /usr/local/include/libftdi1 This is an issue for example for libsigrok which will fail on: In file included from src/hardware/asix-sigma/protocol.c:27: src/hardware/asix-sigma/protocol.h:28:10: fatal error: ftdi.h: No such file or directory 28 | #include <ftdi.h> | ^~~~~~~~ Fixes: - http://autobuild.buildroot.org/results/1427f44e36752c337791597fab47a1889552a2fe Signed-off-by: Fabrice Fontaine <fontaine.fabr...@gmail.com> --- CMakeLists.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CMakeLists.txt b/CMakeLists.txt index 5aecafc..3b0b87c 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -136,7 +136,7 @@ endif () add_subdirectory(src) if ( FTDIPP ) - project(libftdipp1 C CXX) + project(libftdi1 C CXX) add_subdirectory(ftdipp) endif () if ( PYTHON_BINDINGS ) -- 2.27.0 -- libftdi - see http://www.intra2net.com/en/developer/libftdi for details. To unsubscribe send a mail to libftdi+unsubscr...@developer.intra2net.com