From: Michael R. <re...@eu...> - 2003-10-04 09:40:19
|
Hi Martin, you forgot to CC your answer to the list! >> Martin, you like small applications very much :-) Would you prefer >> lcd4linux depending on the shared lib, or as a independent application? > > Well, since usually, the (stripped) statically linked executable is > significantly (ok, 1k is already significant, in the embedded > environment I'm looking at) smaller than the (stripped) binary linked > against the (stripped) shared lib, plus the shared lib. So, unless there > is at least another app that uses that lib, I prefer the statically > linked version. Having said that, I think it would be the "cleaner" > approach to have lcd4linux link dynamically against liblcd4linux. I think so, too. I just feared that the shared lib would have some bad influences on lcd4linux, and therefore preferred not to touch lcd4linux. But if it works clean and fine, I would also use the link against shared liblcd4linux. > Just so I understand this correctly - the way it is now, _all_ I'm > supposed to do is to run configure and make, right? Ppreviously, I also > ran aclocal and autoconf, since without it, it didn't even configure > (let alone compile) on my system. Hmmm... that's what I've never been shure of, too. Whenever something strange happened while compiling, I keyed in 'auto' and pressed Tab twice, so my bash completion showed me all executables starting with 'auto'. I started them all several timne, and after a while, everything worked again :-) I think it depends wheter you're using the CVS version or the distribution tarball, because different files are included in each. I also have never been shure which files to include in either archive. Ronald? 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... |