[Osalp-dev] linking troubles

[Darrick S. <da...@dc...>]

Hello -

I'm new to the list and just started experimenting with the library about a 
week ago.

I first set out to write modules to load Raw and CDR audio files.  I don't 
have any experience writing modules.  But I copied the Wav module and just 
made changes to some of the functions.  Compiled, installed and updated the 
modules_list file.

I've rewritten a program I have to use aflib and it is linked with -lqt 
-lpthread -ldl -lm -lc -laflib and the -rdynamic switch.  Problem I'm having 
is when I use my new aflibRawFile.so module the linking in my app gets 
corrupted.  I've never debugged anything like this before and I'm kind of at 
a loss on how to do so.  Tonight I'll use the example player code to check to 
see how well my module is working.

So what are the steps in dealing with this.  The module works fine the first 
couple of times.  When I call the qt file dialog the program usually crashes. 
 I've looked at info sharedlibrary in gdb and it shows that aflibRawFile.so 
is loaded but the symbols aren't read.  This is after loading a couple of raw 
files.  Got any debugging tips?

I just read the man dlopen and my feeling is a symbol from aflib is getting 
resloved to a symbol in qt.  Possible? 

Sorry I can't be more specific.  This is all on the cutting edge of my 
knowledge.  

Couple other things:

in the makefiles for the format libraries.  why is the module sometimes 
linked to libaudiofile.a and sometimes not.  i.e. aflibAifcFile.o is 
aflibDevFile.o is not.  neither are the mp3 encoders linked to libaudiofile.a 
 I took the line out on all the files and didn't have a problem.

I have more questions but I'll figure out my linking problem first.  Overall 
I like the library.  It seems to do what I need it to do.  What's the word on 
Effect plugins?

Thanks 
Darrick