Not sure if this works but -V sometimes traces loading and errors.

Quoting SimonKenny <digithree@gmail.com>:

> Hi all
>
> I'm testing a plugin that I've written. It works fine on OSX and now I'm
> testing it on Linux. I've gotten my code to build into a shared object
> library but I'm not having any success adding this to the csound runtime
> program. When I use the --opcode-lib option to add the library I just get
>
> ...
> Creating orchestra
> Creating score
> Loading command-line libraries:
> rtaudio: ALSA module enabled
> rtmidi: ALSA Raw MIDI module enabled
> ....
>
> Which is followed by an error message when the parser reaches CSD code which
> uses my opcode. I notice that there is no output giving an error (or
> otherwise) after "Loading command-line libraries:". Incidentally if I use an
> incorrect file name, i.e. --opcode-lib=adsada.so the output is the same.
>
> Basically I've no idea how to find out why the library isn't being loaded as
> there's no error information. Anyone any idea how I might be able to do
> this?
>
>
> Thanks for your time
> Simon
>
>
>
> --
> View this message in context:  
> http://csound.1045644.n5.nabble.com/Opcode-plugin-on-linux-problem-tp5729221.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug trackers
> csound6:
>             https://sourceforge.net/p/csound/tickets/
> csound5:
>             https://sourceforge.net/p/csound/bugs/
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"