Dan --
> > Comments? Suggestions? Critiques?
>
> This is nifty. Couple'a things:
Thanks. I really want to get enough of a solution together that we can
move the temporary during-development-only ops into a separate oplib
(call it 'devel.ops'). This then becomes proof of the overall approach
an
On Sat, 20 Oct 2001, Gregor N. Purdy wrote:
> Comments? Suggestions? Critiques?
This is nifty. Couple'a things:
*) It points out a huge weakness in the build system. We need something
better to generate shared libraries
*) We definitely need to abstract out the shared library loading
code. dlop
All --
I've been tinkering with loading oplibs via dlopen(). This patch
works on one of my test machines, although I'd expect your mileage
to vary somewhat.
You may have to play with your LD_LIBRARY_PATH environment variable
to get the libcore_ops.so file findable by dlopen(). I had to add
'.' t
