Nick Bowler wrote: > If you want to test this specific use case, you can still easily use > libtool to link the test program. > > installcheck_LDFLAGS = -R$(DESTDIR)$(libdir) > installcheck_LDADD = -Wc,-L$(DESTDIR)$(libdir),-lfoo > > On Windows, libtool will generate a wrapper executable which finds the > dll installed in $(DESTDIR)$(bindir) when you do this.
Please read my email entirely before replying to part of it. > I really don't see how directly invoking the C compiler and trying to > re-implement features which libtool already has is going to be productive. Please read my email entirely before replying to part of it. > Is there actually a scenario where the .la file which libtool produced > has correct dependency information but the shared library which libtool > produced has erroneous dependency information? Just happened to me today on Cygwin [1]. > If there are inter-library dependencies, then a simple -lfoo (unless > you use the libtool library...) won't work at all on systems which don't > support such dependencies Yup, and an 'installcheck' target that is written to use libtool will not uncover this problem. Only an 'installcheck' target that uses -L and -l options directly does. Bruno [1] https://github.com/gnu-gettext/ci-check/actions/runs/15757241055
