RE: renaming the .so in C->python

On Tue, 25 May 2004 William.Fulton@xxxxxxx wrote:

> >From: swig-admin@xxxxxxxxxxxxxxx [mailto:swig-admin@xxxxxxxxxxxxxxx]On
> >Behalf Of Martin F Krafft
> >Sent: 25 May 2004 15:22
> >To: swig people
> >Subject: [Swig] renaming the .so in C->python
> >
> >
> >I grok the _lib.so naming and interaction with lib.py. However,
> >since I want to use libtool, I am forced to name my libraries
> >lib*.so. it sucks.
> >
> >So my question: since _lib.so is hardcoded in lib.py as 'import
> >_lib', is there a better way to customise the name of the .so than
> >sed?
> >
> 
> You could get libtool to generate _lib.so by adding in a new 'all' target. 
> Adding this to your Makefile.am might work:
> 
> _lib.so : libwhatever.so
>   cp libwhatever.so _lib.so
> 
> all-local: _lib.so

the automake mailing list recently had a thread about the libtool library
naming enforcement, see

  http://mail.gnu.org/archive/html/automake/2004-05/msg00106.html

This article raises my hope that the handling of library naming in
automake and libtool could be relaxed some day. Perhaps the swig community
should reveal their special requirements for automake and libtool on the
automake list.

To cite from the mentioned article:

  AFAIC naming a convenience library libfoo.a instead of foo.a is not a
  big deal. Finally, I'm surprised this discussion hasn't come up before 
  (or did it?)

Regards
Volker
-- 
Dr. Volker Börchers
System Engineer
TECON Systems AG, Perlengraben 2, 50676 Köln, http://www.tecon.de
Tel: +49-221-92007-55, Fax: +49-221-92007-77
_______________________________________________
Swig maillist  -  Swig@xxxxxxxxxxxxxxx
http://mailman.cs.uchicago.edu/mailman/listinfo/swig