[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Runtime library structure
From: |
Rob Browning |
Subject: |
Re: Runtime library structure |
Date: |
Wed, 12 Nov 2003 12:14:28 -0600 |
User-agent: |
Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (gnu/linux) |
Andreas Rottmann <address@hidden> writes:
> - Have one shared lib with all the non-generated stuff that almost
> every wrapset would need. This would include my runtime wrapper
> stuff and probably g-wrap-wct.c; name this something like
> libgwrap-runtime.
Sounds reasonable, depending on what's included.
> - For each wrapper shlib, directly link in the support functions
> needed. I can see the need for explicitly compiling linking against
> those support functions from other wrapsets, but I think we should
> get rid of it (this is certainly possible with runtime wrapper
> creation).
>
> - Can't a wrapset compile/link against a wrapset shlib? If it can, I
> don't see a need for separation into support wrapper shared
> libraries.
Can you elaborate on these a bit? I'm not sure I completely
understood the proposal.
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
- Re: Runtime library structure,
Rob Browning <=