On Fri, Jun 13, 2025 at 12:46 PM Thomas Jarosch
<thomas.jaro...@intra2net.com> wrote:
>
> Hi Yegor,
>
> You wrote on Fri, Jun 13, 2025 at 09:59:39AM +0200:
> > From: Yegor Yefremov <yegorsli...@googlemail.com>
> >
> > Link to ftdi1-static if only STATICLIBS is enabled.
> > ---
> > ftdi_eeprom/CMakeLists.txt | 7 ++++++-
> > 1 file changed, 6 insertions(+), 1 deletion(-)
> >
> > diff --git a/ftdi_eeprom/CMakeLists.txt b/ftdi_eeprom/CMakeLists.txt
> > index 3958b66..38147b5 100644
> > --- a/ftdi_eeprom/CMakeLists.txt
> > +++ b/ftdi_eeprom/CMakeLists.txt
> > @@ -36,7 +36,12 @@ configure_file(
> > )
> >
> > add_executable(ftdi_eeprom main.c)
> > -target_link_libraries(ftdi_eeprom ftdi1 ${CONFUSE_LIBRARIES})
> > +if (NOT SHAREDLIBS AND STATICLIBS)
> > + target_link_libraries(ftdi_eeprom ftdi1-static)
> > +else()
> > + target_link_libraries(ftdi_eeprom ftdi1)
> > +endif ()
> > +target_link_libraries(ftdi_eeprom ${CONFUSE_LIBRARIES})
> > if (LIBINTL_FOUND)
> > target_link_libraries(ftdi_eeprom ${LIBINTL_LIBRARIES})
> > endif ()
>
> applied, thanks!
>
> I played around with different build configurations but didn't catch this one.
Building under Buildroot helps a lot to discover such issues as you
get exactly specified environments. No side effects with the normal
system libraries.
Yegor
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscr...@developer.intra2net.com
