Debian Patches
Status for libftdi1/1.5-12
Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
---|---|---|---|---|---|---|
01-cmake-multiarch.diff | no | |||||
02-kfreebsd.diff | no | |||||
03-cmake-project.diff | [PATCH] CMakeLists.txt: fix paths when FTDIPP is set 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 |
Fabrice Fontaine <fontaine.fabrice@gmail.com> | no | 2020-07-17 | ||
04-swig-4.3.diff | [PATCH] python: update for SWIG 4.3 SWIG 4.3 comes with an API change to the SWIG_Python_AppendOutput() function, so switch to the recommended SWIG_AppendOutput() instead. Because the new function is a macro in fact also switch to the {..} delimiters as the code needs to be preprocessed. The change is compatible with the previous SWIG releases 4.2 and 4.1 at least. |
William S Fulton <wsf@fultondesigns.co.uk> | no | 2024-10-18 | ||
05-boost-dependency.diff | [PATCH] C++ wrapper: get rid of the Boost dependency The C++ wrapper relies on boost::shared_ptr, likely due to the lack of a standard smart pointer at the time of the C++ wrapper implementation. However, std::shared_ptr has been available by default in GCC since version 6.1, and even with GCC 4.7 when explicitly using the -std=c++11 option. This commit replaces all usages of boost::shared_ptr with std::shared_ptr, eliminating the dependency on the Boost library. Since the smart pointer is only used in private member variables and both types have the same size, this change does not affect the ABI. |
Aurelien Jarno <aurelien@aurel32.net> | no | 2025-05-13 |