From: Michael R. <re...@eu...> - 2003-10-04 07:57:38
|
Hi Ronald, first I want to thank you for your support! Ronald Landheer-Cieslak wrote: > The attached patch will partly fix that. What still needs fixing after this > patch is using Libtool to build the object files needed by DRIVERS, but > that means changing configure.in to set up drivers correctly (i.e. using > $(OBJEXT) in stead of .o) > > The patch also re-enables Libtool in configure.in, but doesn't fix DRIVERS > (yet). Ok, I applied your patch, and changed all .o to .$OBJECT in configure.in (without parens!) It works, at least for me. I checked all the cnages into CVS! But there are several questions: - is the .$OBJEXT (instead of .$(OBJEXT) correct? > I've also attached a bootstrap script for lcd4linux. - what the ehck is a bootstrap script? - should it be included - in CVS - in the distribution tarball? - is AM_PROG_LIBTOOL necessary in configure.in? (it's deactivated at the moment) - should the local 'libtool' script be included - in CVS - in the distribution tarball? - lcd4linux (the main program) is linked against the shared liblcd4linux. Is it possible to build liblcd4linux as it is now, but lcd4linux as a real standalone application (without liblcd4linux?) Would this make sense? Martin, you like small applications very much :-) Would you prefer lcd4linux depending on the shared lib, or as a independent application? Martin, Patrick: does the new version work for you? bye, Michael -- netWorks Vox: +43 316 698260 Michael Reinelt Fax: +43 316 692343 Geisslergasse 4 GSM: +43 676 3079941 A-8045 Graz, Austria e-mail: re...@eu... |