Hi John R and all,

Trying out ccsound.c, the linker is missing a few functions.  

oload.o(.data+0x1d0): undefined reference to `csoundOpenLibrary'
oload.o(.data+0x1d4): undefined reference to `csoundCloseLibrary'
oload.o(.data+0x1d8): undefined reference to `csoundGetLibrarySymbol'

These are available in jpff_glue.c.  What I had done previously to
replace jpff_glue.c with csound.c was to copy these three functions into
csound.c.  (They're empty stubs, so shouldn't be a big deal).  

These seem appropriate to place in csound.c and not ccsound.c.  

I've gone ahead and added those to csound.c and committed that.  If you
do not manually change Makefile to use ccsound.c and csound.c, then
these changes do not affect you at all and jpff_glue.c will be used.  

The one thing I get with using ccsound.c is:

0=(nil)

twice before, and once after running csound.  Will look into later.

Thanks,
steven

stevenyi  writes:

> Hi John R and all,
> 
> Trying out ccsound.c, the linker is missing a few functions.  
> 
> oload.o(.data+0x1d0): undefined reference to `csoundOpenLibrary'
> oload.o(.data+0x1d4): undefined reference to `csoundCloseLibrary'
> oload.o(.data+0x1d8): undefined reference to `csoundGetLibrarySymbol'
> 
> These are available in jpff_glue.c.  What I had done previously to
> replace jpff_glue.c with csound.c was to copy these three functions into
> csound.c.  (They're empty stubs, so shouldn't be a big deal).  
> 
> These seem appropriate to place in csound.c and not ccsound.c.  

To avoid this problem, I build my library with -DLOSE_LOAD_LIBRARY.

When I build without real time support and without -DLINUX, I also build
with -DLOSE_MIDI_TTY.

Sorry, I should have not made people guess these procedures.  I just
quickly knocked off the code and contributed it as I found it useful.
(It's stolen from the looping driver that shows the bug on Windows
with MinGW.)

John

stevenyi  writes:

> The one thing I get with using ccsound.c is:
> 
> 0=(nil)
> 
> twice before, and once after running csound.  Will look into later.

This output is from line 692 in main.c.

I think csoundReset causes one write before and one write aftward, but
I don't know what causes the other write.  (csoundReset calls
MAINReset.)

John

Thanks John for the heads up.  It's not a big deal so will leave it in.  
Looks like debug code to check that O has been set to nil, yes? 

steven

John D. Ramsdell wrote:

>stevenyi  writes:
>
>  
>
>>The one thing I get with using ccsound.c is:
>>
>>0=(nil)
>>
>>twice before, and once after running csound.  Will look into later.
>>    
>>
>
>This output is from line 692 in main.c.
>
>I think csoundReset causes one write before and one write aftward, but
>I don't know what causes the other write.  (csoundReset calls
>MAINReset.)
>
>John
>
>
>
>  
>