What happened is, I wrote the functions as platform-neutral wrappers for
dlopen and loadLibrary; then I suppose John Fitch decided to ditch them and
code directly to the OS routines for plugin opcodes. So either the
functions should be removed, or we should return to my original plan and
call these wrappers from the plugin opcode loader in csoundLoadExternals. I
can think of reasons why plugin authors might want a platform-neutral means
of loading libraries, so perhaps we should keep the functions.

Original Message:
-----------------
From: steven stevenyi@csounds.com
Date: Tue, 04 Nov 2003 11:52:50 -0800
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:3272] Re: ccsound.c


Dynamically loaded plugin opcodes continue to work.  I'm not sure of the 
function of the these functions; I guessed that they were for csound API 
clients to use to load individual libraries, but didn't look beyond that.

The dynamically loaded library functions from the commandline using 
--opcode-lib happens in main.c and calls csoundLoadExternals().  Maybe 
the code in csoundLoadExternals should be refactored out to fill out the 
other stub functions and then be included into API(?).

steven

gogins@pipeline.com wrote:

>If you define LOSE_LOAD_LIBRARY, I take it that means dynamically loaded
>plugin opcodes don't function? Or do they use other functions? If they use
>other functions, it would be less confusing to use another name for your
>macro. If they don't function, they should; you could either move the
>functions into csound.c or make another.c file with them.
>



--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .