Steven,

I managed to build a shared fltk lib here with mingw,
and you'll find it interesting that the keyboard
pops up correctly as in other platforms. So it was a
good guess of yours that proved correct.

Now if you want to try it yourself, you can do this
to fix the fltk build.

1. ./configure --enable-shared

2. src/Makefile needs to be corrected by hand. Add
the following macro (at about line 191):

LDLIBS = -lgdi32 -lkernel32 -lws2_32 -ladvapi32 -luser32
-lcomdlg32 -lole32 -luuid -lfltk_jpeg -lfltk_png -lfltk_z
-lfltk_gl

Then run make. The dlls will be created in src; the
build will fail again on fluid, but it's after the
libs were built, so we are OK.

Copy all the *dll* files from src to /usr/local/lib,
either rename or delete the fltk .a static libs.

Then build csound. There will be some funny link messages,
but I ignored them. In fact I only deleted widgets.dll
and virtual.dll and ran scons again.

Then I ran
csound -odac examples/fl.csd -M0 -+rtmidi=virtual

and all the three FLTK windows appeared for me!

Well done for suggesting it. Now, it will be worth
checking if this set-up (with noFLTKThreads=1 and
shared libs) also works for CsoundVST, so that we
can remove the threading code once and for all.

Victor





>
> Hi Victor,
>
> I did see an fltk.dll in the bin directory of the install,
> and the sizes of the dll's seemed very different with the
> one I built much bigger.  I am *really* hoping this is it
> as I feel like I've been hitting my head against the wall
> on this one! =P  I also want to say that I remember having
> things working on Win2K previously with both the keyboard
> and the widgets, but I honestly don't remember if that's
> true.  If so, then it wouldn't be a dynamic library issue
> (but I'm still hoping!).
>
> steven
>
>
> On 11/19/06, Victor Lazzarini 
> > wrote: The shared lib issue would explain why it worked
> > on OSX and on Linux, as in these systems csound
> > uses dynamic libs.
> >
> > Possibly Mike's releases uses it as well. Did you
> > check for any fltk.dll files in your system after
> > installation?
> >
> > I think FLTK might be re-entrant only provided that we
> > are using the same image (nothing to back this up,
> though) >
> > Victor
> >
> > >
> > > Hi All,
> > >
> > > I've spent a few hours today on this (and that was a
> > > few hours more than I wanted to! :P ) and have gotten
> > > nowhere with the Virtual Keyboard, trying all manners
> > > of combinations of using flush(), wait(), idle
> > > callbacks, and everything else I could possibly think
> > > of.  The best I got was getting the keyboard to draw
> > > correctly but without receiving any events of any kind
> > >  and also killing the CPU. I also tried recompiling
> > > the FLTK library but I can't manage to compile it in
> > > any way except as static libraries.
> > >
> > > The one thing I did do was download Michael Gogins'
> > > 5.04 release. Installing that and using the keyboard
> > > that came with it, I was able to run with an orchestra
> > > that has FLTK widgets.
> > >
> > > Now, the latest thought I have is that by not having
> > > FLTK compiled with --enable-shared, the fltk code
> > > that's linked with the virtual keyboard might be
> > > interfering with the fltk code that's linked with the
> > > fltk widget opcode library.
> > >
> > > Could someone who has FLTK compiled with
> > > --enable-shared try compiling the latest keyboard code
> > > from CVS and running it with Iain McCurdy's
> > > HarmonicAdditiveSynthesis2.csd? (It's available at
> > > http://www.csounds.com/rtcat/).
> > >
> > > Also, a question for Michael, when you did your build,
> > > was it done with or without fltkThreads?
> > >
> > > Thanks for any help!
> > > steven
> > >
> > >
> > >
> ----------------------------------------------------------
> > > --------------- Take Surveys. Earn Cash. Influence the
> > > Future of IT Join SourceForge.net's Techsay panel and
> > > you'll get the chance to share your opinions on IT &
> > business topics through brief surveys - and earn cash >
> >
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > > _______________________________________________
> > > Csound-devel mailing list
> > > Csound-devel@lists.sourceforge.net
> > >
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> > >
> ----------------------------------------------------------
> > --------------- Take Surveys. Earn Cash. Influence the
> > Future of IT Join SourceForge.net's Techsay panel and
> > you'll get the chance to share your opinions on IT &
> > business topics through brief surveys - and earn cash
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > Csound-devel mailing list
> > Csound-devel@lists.sourceforge.net
> >
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> >
>
> ----------------------------------------------------------
> --------------- Take Surveys. Earn Cash. Influence the
> Future of IT Join SourceForge.net's Techsay panel and
> you'll get the chance to share your opinions on IT &
> business topics through brief surveys - and earn cash
>
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net