Hi,
On Mon, 11 Aug 2008, Sergei Steshenko wrote:
> One more thing. In the same directory I also have named pipes.
>
> I think if ecasound (or any other program for that matter) opens a named
> pipe for reading, it will just get stuck waiting for data in that named
> pipe.
I think that's exactly what happens.
> So, if you are not going to change code so it will try to grab only DLLs,
> all this should be in the manpage, at least a strong recommendation to
> have only DLLs in the plugins directories.
I could change the code, but I don't know how. I really don't want to
hardcode known plugin filename extension types to ecasound. Ecasound can
be run on any POSIXish systems (not just Linux, OS X and Win32), so making
this type of assumptions can cause nasty side-effects for some users.
-- ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Ecasound-list mailing list Ecasound-list@email-addr-hidden https://lists.sourceforge.net/lists/listinfo/ecasound-listReceived on Sat Aug 16 16:15:02 2008
This archive was generated by hypermail 2.1.8 : Sat Aug 16 2008 - 16:15:02 EEST