What you are missing is csoundMessage0, not csoundMessage. Various people
have implemented it, e.g. in ccsound.c. This function does not take Csound *
as its first parameter. I did not create this function. I guess that it was
created to be an implementation of message that does not take a Csound
pointer as its first argument. I would prefer if all calls to message DID
take Csound * (or whatever it's called). The default implementation could
then simply ignore the pointer and print with vfprintf, as csoundMessage0
does.

The justification for passing the Csound instance to every message call is
that the API cannot know that the client of the API does not need to route
each instance's messages to a separate stream, text box, list, database, or
whatever. If the message call received Csound *, it could also get userdata,
which could be anything and could contain a binding to the per-instance
message sink.

If that's too much trouble, add csoundMessage0 to the API in csound.c and
make it the default message callback, so that nobody needs to implement it.


============================================
Michael Gogins
gogins at pipeline period com
Irreducible Productions
CsoundVST, an extended version of Csound for programming music and sound
Available at http://sourceforge.net/projects/csound/
============================================


----- Original Message ----- 
From: "Robert McNulty Junior" 
To: "Csound Developers Discussion List" 
Sent: Wednesday, December 03, 2003 10:02 PM
Subject: [CSOUND-DEV:3620] error messages in envext


> I get the following error messages in Envext. What is csoundMessage()
> and where is it located?
>
> libtool: link: warning: library `/usr/lib/libstdc++.la' was moved.
> libtool: link: warning: library `/usr/lib/libstdc++.la' was moved.
> /usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../../i686-pc-cygwin/bin/ld:
> warning
> : cannot find entry symbol _WinMainCRTStartup; defaulting to 00401000
> sndinfo.o(.text+0x243): In function `sndinfo':
> /home/sherlock/csoundcvs/csound/util2/envext/../../csound/sndinfo.c:89:
> undefine
> d reference to `_csoundMessage0'
>
sndinfo.o(.text+0x2f1):/home/sherlock/csoundcvs/csound/util2/envext/../../cs
> ound
> /sndinfo.c:110: undefined reference to `_csoundMessage0'
>
sndinfo.o(.text+0x323):/home/sherlock/csoundcvs/csound/util2/envext/../../cs
> ound
> /sndinfo.c:114: undefined reference to `_csoundMessage0'
>
sndinfo.o(.text+0x3e2):/home/sherlock/csoundcvs/csound/util2/envext/../../cs
> ound
> /sndinfo.c:88: undefined reference to `_csoundMessage0'
>
sndinfo.o(.text+0x403):/home/sherlock/csoundcvs/csound/util2/envext/../../cs
> ound
> /sndinfo.c:72: undefined reference to `_csoundMessage0'
>
sndinfo.o(.text+0x435):/home/sherlock/csoundcvs/csound/util2/envext/../../cs
> ound
> /sndinfo.c:77: more undefined references to `_csoundMessage0' follow
> collect2: ld returned 1 exit status
> make: *** [envext.exe] Error 1
>
> sherlock@bobby-junior ~/csoundcvs/csound/util2/envext
> $
>

OK. I'll work on that right now.
Bobby

-----Original Message-----
From: owner-csound-dev@eartha.mills.edu
[mailto:owner-csound-dev@eartha.mills.edu]On Behalf Of Michael Gogins
Sent: Wednesday, December 03, 2003 9:57 PM
To: Csound Developers Discussion List
Subject: [CSOUND-DEV:3621] Re: error messages in envext


What you are missing is csoundMessage0, not csoundMessage. Various people
have implemented it, e.g. in ccsound.c. This function does not take Csound *
as its first parameter. I did not create this function. I guess that it was
created to be an implementation of message that does not take a Csound
pointer as its first argument. I would prefer if all calls to message DID
take Csound * (or whatever it's called). The default implementation could
then simply ignore the pointer and print with vfprintf, as csoundMessage0
does.

The justification for passing the Csound instance to every message call is
that the API cannot know that the client of the API does not need to route
each instance's messages to a separate stream, text box, list, database, or
whatever. If the message call received Csound *, it could also get userdata,
which could be anything and could contain a binding to the per-instance
message sink.

If that's too much trouble, add csoundMessage0 to the API in csound.c and
make it the default message callback, so that nobody needs to implement it.


============================================
Michael Gogins
gogins at pipeline period com
Irreducible Productions
CsoundVST, an extended version of Csound for programming music and sound
Available at http://sourceforge.net/projects/csound/
============================================


----- Original Message -----
From: "Robert McNulty Junior" 
To: "Csound Developers Discussion List" 
Sent: Wednesday, December 03, 2003 10:02 PM
Subject: [CSOUND-DEV:3620] error messages in envext


> I get the following error messages in Envext. What is csoundMessage()
> and where is it located?
>
> libtool: link: warning: library `/usr/lib/libstdc++.la' was moved.
> libtool: link: warning: library `/usr/lib/libstdc++.la' was moved.
> /usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../../i686-pc-cygwin/bin/ld:
> warning
> : cannot find entry symbol _WinMainCRTStartup; defaulting to 00401000
> sndinfo.o(.text+0x243): In function `sndinfo':
> /home/sherlock/csoundcvs/csound/util2/envext/../../csound/sndinfo.c:89:
> undefine
> d reference to `_csoundMessage0'
>
sndinfo.o(.text+0x2f1):/home/sherlock/csoundcvs/csound/util2/envext/../../cs
> ound
> /sndinfo.c:110: undefined reference to `_csoundMessage0'
>
sndinfo.o(.text+0x323):/home/sherlock/csoundcvs/csound/util2/envext/../../cs
> ound
> /sndinfo.c:114: undefined reference to `_csoundMessage0'
>
sndinfo.o(.text+0x3e2):/home/sherlock/csoundcvs/csound/util2/envext/../../cs
> ound
> /sndinfo.c:88: undefined reference to `_csoundMessage0'
>
sndinfo.o(.text+0x403):/home/sherlock/csoundcvs/csound/util2/envext/../../cs
> ound
> /sndinfo.c:72: undefined reference to `_csoundMessage0'
>
sndinfo.o(.text+0x435):/home/sherlock/csoundcvs/csound/util2/envext/../../cs
> ound
> /sndinfo.c:77: more undefined references to `_csoundMessage0' follow
> collect2: ld returned 1 exit status
> make: *** [envext.exe] Error 1
>
> sherlock@bobby-junior ~/csoundcvs/csound/util2/envext
> $
>

OK. I added csoundMessage0() in there, and in pvlook.c.
I am recompiling it now.
It's raining out there. Darn it.
Means I'll probably lose communication before the night is over.
I tried adding ccsound in envext, but that did not work out.
I can't recall the exact file where I added csoundMessage0() to.


-----Original Message-----
From: owner-csound-dev@eartha.mills.edu
[mailto:owner-csound-dev@eartha.mills.edu]On Behalf Of Michael Gogins
Sent: Wednesday, December 03, 2003 9:57 PM
To: Csound Developers Discussion List
Subject: [CSOUND-DEV:3621] Re: error messages in envext


What you are missing is csoundMessage0, not csoundMessage. Various people
have implemented it, e.g. in ccsound.c. This function does not take Csound *
as its first parameter. I did not create this function. I guess that it was
created to be an implementation of message that does not take a Csound
pointer as its first argument. I would prefer if all calls to message DID
take Csound * (or whatever it's called). The default implementation could
then simply ignore the pointer and print with vfprintf, as csoundMessage0
does.

The justification for passing the Csound instance to every message call is
that the API cannot know that the client of the API does not need to route
each instance's messages to a separate stream, text box, list, database, or
whatever. If the message call received Csound *, it could also get userdata,
which could be anything and could contain a binding to the per-instance
message sink.

If that's too much trouble, add csoundMessage0 to the API in csound.c and
make it the default message callback, so that nobody needs to implement it.


============================================
Michael Gogins
gogins at pipeline period com
Irreducible Productions
CsoundVST, an extended version of Csound for programming music and sound
Available at http://sourceforge.net/projects/csound/
============================================


----- Original Message -----
From: "Robert McNulty Junior" 
To: "Csound Developers Discussion List" 
Sent: Wednesday, December 03, 2003 10:02 PM
Subject: [CSOUND-DEV:3620] error messages in envext


> I get the following error messages in Envext. What is csoundMessage()
> and where is it located?
>
> libtool: link: warning: library `/usr/lib/libstdc++.la' was moved.
> libtool: link: warning: library `/usr/lib/libstdc++.la' was moved.
> /usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../../i686-pc-cygwin/bin/ld:
> warning
> : cannot find entry symbol _WinMainCRTStartup; defaulting to 00401000
> sndinfo.o(.text+0x243): In function `sndinfo':
> /home/sherlock/csoundcvs/csound/util2/envext/../../csound/sndinfo.c:89:
> undefine
> d reference to `_csoundMessage0'
>
sndinfo.o(.text+0x2f1):/home/sherlock/csoundcvs/csound/util2/envext/../../cs
> ound
> /sndinfo.c:110: undefined reference to `_csoundMessage0'
>
sndinfo.o(.text+0x323):/home/sherlock/csoundcvs/csound/util2/envext/../../cs
> ound
> /sndinfo.c:114: undefined reference to `_csoundMessage0'
>
sndinfo.o(.text+0x3e2):/home/sherlock/csoundcvs/csound/util2/envext/../../cs
> ound
> /sndinfo.c:88: undefined reference to `_csoundMessage0'
>
sndinfo.o(.text+0x403):/home/sherlock/csoundcvs/csound/util2/envext/../../cs
> ound
> /sndinfo.c:72: undefined reference to `_csoundMessage0'
>
sndinfo.o(.text+0x435):/home/sherlock/csoundcvs/csound/util2/envext/../../cs
> ound
> /sndinfo.c:77: more undefined references to `_csoundMessage0' follow
> collect2: ld returned 1 exit status
> make: *** [envext.exe] Error 1
>
> sherlock@bobby-junior ~/csoundcvs/csound/util2/envext
> $
>

CsoundMesage0 was a quick hack when I was creating a FLTK interface for 
the OSX system.  It was intended to be printf, but capturably by the GUI.  
For csound5 it really should not exist
==John ff

Would it be OK to get rid of it?
It was in Csound4, which working now for Cygwin.
I really need to get back to Csound5.
I'm learning what works and what does not.
I hacked pvl_main.c and another file.
Bobby

-----Original Message-----
From: owner-csound-dev@eartha.mills.edu
[mailto:owner-csound-dev@eartha.mills.edu]On Behalf Of John ffitch
Sent: Thursday, December 04, 2003 1:19 AM
To: Csound Developers Discussion List
Subject: [CSOUND-DEV:3625] Re: error messages in envext


CsoundMesage0 was a quick hack when I was creating a FLTK interface for 
the OSX system.  It was intended to be printf, but capturably by the GUI.  
For csound5 it really should not exist
==John ff

I found and fixed the linking problem.  

"Robert McNulty Junior"  writes:

> Would it be OK to get rid of it?
> It was in Csound4, which working now for Cygwin.
> I really need to get back to Csound5.
> I'm learning what works and what does not.
> I hacked pvl_main.c and another file.

Please don't hack pvl_main.c or anything else.  Just CVS up.

This means the sources I put at NEU are busted too, so don't go there.

John