< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] Packaging for Debian



On 27/02/07 21:54, Adam Roach wrote:
> Daniel Pocock wrote:
>> Robert Sparks wrote:
>>  
>>> Probably the right thing to do.
>>>
>>> MIT's ares is still at 1.1.1 (circa 2001) - there doesn't seem to be
>>> anyone there to take changes back anyhow.
>>> There is at least one other fork that's done different things.
>>>
>>> So, lets plan to change the name of this library to resip-ares and
>>> update our wiki/etc. to reflect it.
>>>
>>>     
>> Can a shared library have a hyphenated name?  If not, what will we
>> call the shared library file, e.g. libresipares.so, or libaresr.so
>> perhaps?
>>
>>   
> 
> libresip_ares?

Time to revive a very old thread...

I've committed some autotools stuff that I did here;

http://svn.resiprocate.org/viewsvn/resiprocate/branches/b-dpocock-autotools/

This is a first attempt to build for Linux - it doesn't replace all the
functionality of the existing build system, and doesn't run all the test
cases.

a) autotools is working and builds a test case and a working repro:

svn co
http://svn.resiprocate.org/rep/resiprocate/branches/b-dpocock-autotools
resip-autotools

cd resip-autotools
autoreconf --install
./configure  CFLAGS="-Iwhatever -g" LDFLAGS="-Lwhatever" etc
make
make check
cd repro
./repro   (this invokes a wrapper created by automake, the wrapper knows
where the compiled shared libraries are, etc)

- must follow the autotools convention of using CFLAGS and LDFLAGS to
specify non-standard locations for dependencies (e.g. libdb)

b) some very primitive but working Debian packages can be built too:

svn co
http://svn.resiprocate.org/rep/resiprocate/branches/b-dpocock-autotools
resip-autotools

cd resip-autotools
autoreconf --install
fakeroot debian/rules build
fakeroot debian/rules binary
cd ..
ls *.deb

c) for comment and/or future work before this becomes suitable for
merging into trunk:

- new config.h approach?  how to make this work between autotools and
the Visual Studio build?

- what to do about ares and other contrib stuff?  how to build them with
autotools, and how to package them?

- re-incarnate some of the old configure features, e.g. optional SSL,
ARES options, support for MinGW

- which other stuff to benefit from autotools and packaging - reTurn,
apps/*, etc?

- adding all the other unit tests - see the example for the one I did
already, although maybe this will be a pain to replicate and it could be
done with cppunit:

http://svn.resiprocate.org/viewsvn/resiprocate/branches/b-dpocock-autotools/rutil/test/Makefile.am?revision=9251&view=markup

- RPM packaging: resip.spec will become resip.spec.in, created by configure

- OpenCSW: once the autotools stuff is solid, I have an account on the
OpenCSW build server and I'm happy to put the resip packages up there

- dev and user documentation (release process howto, etc)