[sane-devel] sane backend build system - help

[Paul Newall]

Progress:
I managed to copy an existing backend, and add it to the build system. So 
now I can start the actual backend writing process.
That was quite hard work. I'm not sure if that was just me, or whether it 
might encourage other people to have a go at writing a backend if there was 
an easier way to get started.

Maybe some experienced backend writer could provide one of the following?

A build and install system for a single backend. I think that would be the 
easiest to understand. And the install process would be faster during 
developement if you were only installing one backend. It would need to be 
easy to change the backend name, perhaps by changing one variable with the 
name in?

Or, provide one empty backend as part of the sane-backends, that you can 
experiment with without having to copy and rename an existing backend.

Also it would be nice to have empty backend files: emptybackend.c 
emptybackend.h emptybackend.conf
with lots of comments in about what you should add in various places.


----- Original Message ----- 
From: "Paul Newall" <p.newalls at ntlworld.com>
To: <sane-devel at lists.alioth.debian.org>
Sent: Sunday, April 24, 2011 8:26 PM
Subject: Re: [sane-devel] sane backend build system - help


> autoreconf -i -f
> seems to have enabled me to make the backends.
> So now I am trying the approach of adding a new backend (copy of an 
> existing one) to the backends to see if I can install that.
>
> Paul
>
> ----- Original Message ----- 
> From: "Chris Bagwell" <chris at cnpbagwell.com>
> To: "Paul Newall" <p.newalls at ntlworld.com>
> Cc: <sane-devel at lists.alioth.debian.org>
> Sent: Sunday, April 24, 2011 7:15 PM
> Subject: Re: [sane-devel] sane backend build system - help
>
>
> Its common to have a newer version of autofoo tools on your system and
> you'll need to update the pre-existing files committed in git.
>
> Try running with install option to get newer versions of files: 
> autoreconf -i
>
> If that doesn't work then use the force option:  autoreconf -i -f
>
> Chris
>
> On Sun, Apr 24, 2011 at 10:17 AM, Paul Newall <p.newalls at ntlworld.com> 
> wrote:
>> I want to write a new backend.
>> Currently the main obstacle is that I find the backend build system very
>> intimidating.
>> I have no experience of autoconf, automake, or libtool.
>> On my system (ubuntu 10.10) I can run autoreconf and ./configure 
>> apparently
>> OK, but when I run make I get these errors:
>>
>> libtool: Version mismatch error. This is libtool 2.2.10, but the
>> libtool: definition of this LT_INIT comes from libtool 2.2.6b.
>> libtool: You should recreate aclocal.m4 with macros from libtool 2.2.10
>> libtool: and run autoconf again.
>> make[2]: *** [libsane_la-dll-s.lo] Error 63
>>
>> How would I recreate aclocal.m4 with macros from libtool 2.2.10 ? I don't
>> have much idea what that means.
>>
>> Is it best to start by adding an empty new backend to the build system? 
>> (in
>> which case I will need to get the build system to work first)
>> Or would it be better to make and install the new backend independently
>> during development? (this might be easier? and it might give me a faster
>> modify, build, test cycle during development? But are there difficulties
>> that I have not discovered yet?)
>>
>>
>> --
>> sane-devel mailing list: sane-devel at lists.alioth.debian.org
>> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
>> Unsubscribe: Send mail with subject "unsubscribe your_password"
>> to sane-devel-request at lists.alioth.debian.org
>>
>
>
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>             to sane-devel-request at lists.alioth.debian.org