Henning Meier-Geinitz wrote: > > +sane-backends will not compile out of the box. You need to follow the > following steps: > + > +- edit configure.in and put all the AC_CONFIG_FILES entry in one line. > > Would it help to use AC_CONFIG_FILES three times?
I don't know. > > + edit acinclude.m4 and remove everything from libtool (about 170kb) > > That's because the libtool that comes with cygwin is newer (or just > different)? I don't know either. I had a lot of trouble with that file and everything started working once I removed it. They seem to be from the same version of libtool though. > > +- edit backend/Makefile.in, and add "-no-undefined" before the > "-version-info" parameter (twice). > > What about checking for windows in configure.in and setting the > variable @NO_UNDEFINED@ based on that check and calling libtool with > that variable in the Makefile? I was thinking about adding a @LIBTOOL_EXTRA_FLAGS@ field for that. > > --- sane-backends-1.0.12.org/backend/Makefile.in 2003-05-13 > 04:39:50.000000000 -0500 > +++ sane-backends-1.0.12/backend/Makefile.in 2003-09-21 21:19:38.000000000 > -0500 > @@ -155,7 +155,7 @@ > > libsane-%.la: %.lo %-s.lo $(EXTRA) $(LIBOBJS) > @$(LIBTOOL) $(MLINK) $(CC) -export-dynamic -o $@ $($*_LIBS) \ > - $(LDFLAGS) $(BACKENDLIBS) $^ -rpath $(libsanedir) \ > + $(LDFLAGS) $(BACKENDLIBS) $^ -rpath $(libsanedir) -no-undefined \ > -version-info $(V_MAJOR):$(V_REV):$(V_MINOR) $(DYNAMIC_FLAG) > > Can "-no-undefined" be harmful on other platforms? I've read the docs > but it looks like I don't really understand what it does :-/ Neither do I. It just doesn't work with it :) > > Otherwise I haven't found anything that may harm non-Windows system so > it's ok for me. I haven't applied the patch, however. > > Could you add some lines to to README.windows about "only SCSI > supported"? README and Makefile.in must be updated, too. Why Makefile.in? Frank.
