I built a minimal csound.dll a while back using qmake and it functions
nicely when using the c api, but I've recently tried building
csound.exe against it and I'm getting some strange behavior on the
command line.  When csound.exe is run it prints no messages to the
console and exits immediately but leaves the csound process running
until the .csd file is done rendering.  Conversely, when stepping
through it using the debugger everything appears normal and I can set
breakpoints that get hit when expected.  Does anybody have an idea as
to how or why this is happening?  I'm stumped.

I've attached the build output in case it helps.

Cheers,
~ andy.f

Disregard.  The answer came to me first thing when I woke up this
morning.  I was using the wrong subsystem for linking.

Cheers,
~ andy.f



On Fri, Jul 23, 2010 at 1:37 AM, andy fillebrown
 wrote:
> I built a minimal csound.dll a while back using qmake and it functions
> nicely when using the c api, but I've recently tried building
> csound.exe against it and I'm getting some strange behavior on the
> command line.  When csound.exe is run it prints no messages to the
> console and exits immediately but leaves the csound process running
> until the .csd file is done rendering.  Conversely, when stepping
> through it using the debugger everything appears normal and I can set
> breakpoints that get hit when expected.  Does anybody have an idea as
> to how or why this is happening?  I'm stumped.
>
> I've attached the build output in case it helps.
>
> Cheers,
> ~ andy.f
>

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net