[sane-devel] Build system issues.

[Chris Bagwell]

Hmmm, I was going to add it back in but I noticed 1) the old CVS code 
was probably broken and 2) the old CVS code was probably doing what the 
comment said and only creating symlinks for missing symlinks  (I hadn't 
noticed the "test ! -f $${file}" before).  It doesn't appear to be 
fixing symlinks in the way described.

I'll see if libtool upgrade caused a change in behaviour next or if the 
behaviour pre-dates automake/libtool updates.

In case your interested in why old code was broke:  Some key logic it 
uses, I ran by hand and it returns:

../tools/libtool-get-dll-ext libsane-dll.la
so

If I use epson as an example backend then above results in:

file=libsane-epson.so.1

grep dlname= libsane-epson.la | cut -f2 -d
libsane-epson.so.1

lib="libsane-epson.so.1"

and finally it will use above values:

ln -s libsane-epson.so.1 libsane-espon.so.1

Not very useful.

Chris

>>         @# Create library links manually. Actually this is libtool's job but
>> it
>> doesn't
>>         @# seem to work on some platforms.
>>         @# Assume the dll name without any versions is last
>>         @if test "$(USE_LINKS)" = "yes" ; then  \
>>           dllend=`../tools/libtool-get-
>> dll-ext libsane-dll.la`; \
>>           list="$(ALL_BACKENDS)"; cd $(DESTDIR)$(libsanedir) && for be in
>> $$list
>> ; do \
>>             file=libsane-$${be}.$$dllend.$(V_MAJOR); \
>>             lib=`grep dlname= libsane-$${be}.la | cut -f2 -d"'"`; \
>>             if test ! -f $${file} -a -n "$${lib}"; then \
>>               $(LN_S) $${lib} $${file}; \
>>             fi; \
>>           done; \
>>         fi
>>
>>
>> Chris
>>
>>
>>     
>
>
>
>