[sane-devel] How best to distribute the m4 directory?

[Chris Bagwell]

Ah yes, I hadn't thought about looking at iscan source code yet; 
although I'd recently installed the binary to play with on my new Epson 
Artisan 800.  I just looked at iscan now and it is indeed a great 
starting point for this task and I like the diff approach to ltmain.sh

Olaf, if you have suggestions on how to proceed then please let me 
know.  Based on your past work, I'm guessing you could whip this up 
pretty fast... I also don't mind diving right in and know I can get it 
completed soon as well.  I can provide some draft patches soon.

I don't think we can split the work very well but definitely can use 
each other to test on variety of autotool versions (those issue tend to 
be limited to configure.ac though).

Chris

m. allan noah wrote:
> Sounds good. Chris- can you coordinate with Olaf to do something
> similar with sane's copy of ltmain?
>
> allan
>
> On Mon, Jan 12, 2009 at 7:43 PM, Olaf Meeuwissen
> <olaf.meeuwissen at avasys.jp> wrote:
>   
>> "m. allan noah" <kitno455 at gmail.com> writes:
>>
>>     
>>> [switching sane build system to autotools]
>>> You (and others on this list) have more experience with these tools
>>> than I, so I am willing to defer to your judgement. But watch out for
>>> the sane-specific copy of libtool. We have some hacks in there to make
>>> each sane backend's .so export symbols so that it can be linked
>>> directly.
>>>       
>> The iscan sources include these changes as a patch to ltmain.sh and
>> uses a little bootstrap script to apply it.
>>
>> I'd be happy to help out with converting the SANE build system to an
>> autotool based one.  FWIW, iscan started out with SANE's build system
>> and I've converted it to use autotools a few years ago.
>>
>> Hope this helps,
>> --
>> Olaf Meeuwissen, LPIC-2           FLOSS Engineer -- AVASYS Corporation
>> FSF Associate Member #1962               Help support software freedom
>>                 http://www.fsf.org/jf?referrer=1962
>>
>>     
>
>
>
>