[asterisk-dev] repost: fixes to zaptel makefile
Tzafrir Cohen
tzafrir.cohen at xorcom.com
Mon Nov 6 15:19:29 MST 2006
On Mon, Nov 06, 2006 at 02:41:29PM -0600, Kevin P. Fleming wrote:
> Tzafrir Cohen wrote:
> > One simple source for the list of modules to build: MOD_LIST
> > * A simple name: a module in the current directory
> > * A name that ends with '/': a subdirectory. So far only
> > works for kernel 2.6
>
> Looks fine to me, but we will need to ensure that building on kernel 2.4
> still works.
2.4 were already broken by moving to subdirectories. This should help in
unbreaking them. But at least now you have a list of those
subdirectories.
How can you tell what exactly you need to build for 2.4 in a
subdirectory? For 2.6 we have Kbuild.
Would you rather that xpp/ would provide a dummy 2.4 Makefile (using the
same technique as in wct4xxp/ and thus the build of .4 would just
recursively travese all the MOD_DIRS ?
>
> > rev 1462: takes a stab at simplifying the name of libtonezone .
> >
> > http://svn.digium.com/view/zaptel?rev=1462&view=rev
> >
> > Could anybody explain to me why is it overly-complex?
>
> This is standard procedure for installed libraries. The 'real' filename
> is the fully-qualified version, and there are symlinks that provide the
> shortened (no minor version, no version at all) names for applications
> to link against. However, I believe ldconfig itself will create these
> links if they do not exist.
>
> Also, the 'soname' in the library is important; if an application links
> against 'libtonezone.so' (by using -lso argument to the linker), you
> want the resulting binary to actually reference libtonezone.so.1.0. This
> way, if a newer (incompatible) version is installed, the application
> won't try to use it at runtime, and will fail to link at linktime. This,
> again, is standard procedure for userspace libraries.
>
> In spite of the fact that it is highly unlikely that libtonezone will
> ever have an incompatible future release, it's still safer to have the
> applications have a proper reference to the version-numbered library.
Well, is there anything broken from my suggested change? It does make
things look more readable.
--
Tzafrir Cohen
icq#16849755 jabber:tzafrir at jabber.org
+972-50-7952406 mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
More information about the asterisk-dev
mailing list