Kaz> --- sanei/Makefile.in 1998-05-08 15:38:53+09 1.1
Kaz> +++ sanei/Makefile.in 1998-05-08 15:43:57+09
Kaz> @@ -51,12 +51,14 @@
Kaz> sanei_save_values.lo sanei_load_values.lo \
Kaz> sanei_scsi.lo sanei_config.lo sanei_pio.lo
Kaz> -TARGETS = libsanei.a
Kaz> +TARGETS = $(LIBSANEI_LTOBJS) libsanei.a
Kaz> TESTPROGRAMS = test_wire
Kaz> .SUFFIXES:
Kaz> -.SUFFIXES: .c .o
Kaz> +.SUFFIXES: .c .lo .o
Kaz> .c.o:
Kaz> + $(COMPILE) $<
Kaz> +.c.lo:
Kaz> @$(LIBTOOL) $(MCOMP) $(COMPILE) $<
Kaz>
Kaz> all: $(TARGETS)
I believe this would have the effect of compiling each file _three_
times when not specifying --disable-shared. Not a good thing.
I don't want to make libsanei shared because that would make it harder
to distribute backends. Right now, you can install a new (e.g.,
third-party) backend simply by installing the backend's shared
libraries & configuration file. If libsanei were shared too, we would
have to do library versioning on it to make sure things would work
properly when two backends want incompatible versions of libsanei.
--david
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com