I don't think it's a good idea to change naming conventions for plugins, especially not suffixes, because this may impose a requirement for nonstandard make rules etc. which would be a burden for novice developers.

A better solution is a standard subdirectory for modules and plugins, called something really obvious like "plugins". If Csound discovers this subdirectory, it doesn't look above it.

Another solution is to simply remove the warning message in question. This may be the best solution.

Regards,
Mike

-----Original Message-----
From: Victor Lazzarini 
Sent: Nov 1, 2005 8:51 AM
To: csound-devel@lists.sourceforge.net
Subject: [Cs-dev] Plugin module naming issues

I was just wondering today whether we should
introduce a naming structure for csound plugin
modules. Now that we have some extra dynamic libs
as the result of frontends, interfaces, etc.,
I keep getting ugly warning messages about libx is
not a csound library or something of the kind, because
my OPCODEDIR, for convenience is the csound5 top-level
directory.

We could introduce, for automatic loading of plugins
only, something like

module.c:

libmodule_plugin.dylib (OSX)
libmodule_plugin.so (Linux)
module_plugin.dll (Windows)

or go for a unified extension for all
platforms, like:

module.csplug

What do you think? We can always leave it
open for any names for manual loading.

Victor

Victor


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel





-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Michael Gogins wrote:

> A better solution is a standard subdirectory for modules
 > and plugins, called something really obvious like "plugins".
 > If Csound discovers this subdirectory, it doesn't look above it.

We already have OPCODEDIR and OPCODEDIR64, and with these being
correctly set up, no warnings should be printed. When Csound 5 is
finally released, it is expected that people will install it rather
than running from the build directory, and the installer will set
up the directory structure and environment as needed.


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net