On Sun, 24 Sep 2006 22:59:25 -0500 Nicolas Williams wrote:
> If libcmd:b_xxx() are truly intended to be public then the main problem
> with renaming/moving libcmd (assuming consumers don't access it through
> AST's libdll) would be the need to go change third party application
> build systems to know about this.
> And again, that's assuming they're not going through the libdll wrapper
> to dlopen()/dlsym()/...
I hope this eventually makes it to the list (for the nth time)...
-lcmd is used three ways:
compile/link time (cc)
exec time (ld.so)
run time (dlopen())
the naming conventions w.r.t. build, installation, and portability,
are cross-purpose for installing the -lcmd shared-lib/dll in any other
place than as handled by LD_LIBRARY_PATH (and mutations) for ld and ld.so
and -L* -l* for cc/ld
and please don't post another pseudo code fragment on how we can
code the -ldll wrapper to map "cmd" to some other name/dir
we've already done that (years ago) for true plugins
true plugins don't belong in (/usr)/lib proper
we know that
and don't do that
-lcmd is a hybrid as mentioned above and is not amenable to such mappings
-- Glenn Fowler -- AT&T Research, Florham Park NJ --
