From: Peter S. <pe...@st...> - 2012-01-13 13:03:17
|
Xiaofan Chen wrote: > Removing the extra "-lusb-1.0" from examples/Makefile.am solved the > problem. Thanks for testing! > BTW, libtool adds -lobjc in the end for the examples build. It is nice that libtool adds this dependency automatically, but that does not really mean we should not include it in our list of known dependencies for static linking. Does the following change also work? It will add -lobjc into the .pc. diff --git a/configure.ac b/configure.ac index 34be1be..7d59e50 100644 --- a/configure.ac +++ b/configure.ac @@ -65,7 +65,7 @@ case $host in backend="darwin" threads="posix" LIBS="${LIBS} -lobjc" - PC_LIBS_PRIVATE="-Wl,-framework,IOKit -Wl,-framework,CoreFoundation" + PC_LIBS_PRIVATE="-lobjc -Wl,-framework,IOKit -Wl,-framework,CoreFoundation" LTLDFLAGS="${LTLDFLAGS} -Wl,-prebind" AC_CHECK_HEADERS([poll.h]) AC_CHECK_TYPE([nfds_t], > I also find some other projects (e.g.: libftdi legacy branch) > add $(top_builddir) for the LDADD flag. Is this necessary? > > INCLUDES = -I$(top_srcdir)/src -I$(top_srcdir)/ftdipp > LDADD = $(top_builddir)/src/libftdi.la I think it is neccessary only with configure scripts in subdirectoris. Since we have only one configure I think the relative path is OK. I've tested building outside the source directory, which is where I otherwise expected that $top_builddir might have been neccessary. //Peter |