On Jan 8, 2010, at 7:22 PM, Guy Harris wrote:
On Jan 8, 2010, at 12:56 PM, Guy Harris wrote:
You might want to call it ARCHIVELIBS, by analogy to LIBS.
Another possibility, if the routines are in an installed library,
would be to just add that library to LIBS. The shared libpcap will
On Jan 8, 2010, at 12:56 PM, Guy Harris wrote:
> You might want to call it ARCHIVELIBS, by analogy to LIBS.
Another possibility, if the routines are in an installed library, would be to
just add that library to LIBS. The shared libpcap will be linked with all the
libraries in LIBS, so program
On Jan 7, 2010, at 12:22 PM, Christian Bell wrote:
> libpcap.a: $(OBJ)
> @rm -f $@
> - ar rc $@ $(OBJ) $(ADDLARCHIVEOBJS)
> + if test -n "$(ADDLARCHIVES)"; then \
> + EXTRA_OBJS=`ar t $(ADDLARCHIVES) | tr '\n' ' '`; \
> + ar x $(ADDLARCHIVES); \
> + fi; \
> +
From: Christian Bell
This patch allows libpcap.a and libpcap.so to include object files from a
static library archive instead of just a list of .o files.
I'm only including the Makefile.in part because I just want feedback on whether
this would be acceptable practice. I'm preparing a larger sub
