[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: add-on lib versioning (concrete example g-wrap) -- what to do?
From: |
Rob Browning |
Subject: |
Re: add-on lib versioning (concrete example g-wrap) -- what to do? |
Date: |
Fri, 13 Dec 2002 16:53:41 -0600 |
User-agent: |
Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i386-pc-linux-gnu) |
Christopher Cramer <address@hidden> writes:
> What have the other languages (i.e. Perl, Python) done wrt this
> problem? They have presumably made a choice already and are dealing
> the consequences.
AFAIK they don't really have the problem because they just don't
encourage direct C linking to add-on libs for things like
scm_make_u8_vector or gwrap_foo. So they can just put .so's in
lib/perl* or lib/perl*/VERSION and not worry about it.
I presume that if you did try to create a C library that linked
against libperl which exported perl_do_something () for public use via
plain vanilla -L/-l linking, you'd have exactly the same problem.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4