> Mike Werner wrote: > > there are no files called 'fltk.lib' or 'fltkgl.lib' in the \lib directory. > > There are files called 'fltkd.lib' and 'fltkgld.lib. > > The /debug/ builds of FLTK include a 'd' on the end, whereas > the /release/ builds do not. > > So if you are building fltk with 'debug' enabled (which for some > reason is the default), those will be the names. If you build fltk > as a release version (by changing that pulldown menu in the center > of the VS screen), the libs won't have the 'd' suffix. > > Debug or Release builds should work equally well, just be sure > to use the correct libs for how you're building your app. > > > If I add both of these to the link list for my app I get only > > 1 unresolved external error for a routine called TrackMouseEvent. > > 'TrackMouseEvent' sounds like a win32 call: > http://msdn.microsoft.com/en-us/library/ms646265(VS.85).aspx > > The Microsoft docs for that function (above) say it's in user32.lib > (see the 'function information' section on that page). > > So it sounds like the user32.lib has not been included during linking. > > I imagine you tried carrying over the same build instructions > from 1.0.11 to 1.1.9, which won't work; there's an 8 year difference > there. > Some of the win32 lib names have changed since then. > > Again, when you build the FLTK cube demo for fltk 1.1.9, > look at the build log when re-building the FLTK test program > you're focused on to see what the compile/link lines are, > and make sure yours are similar. > > > Also, why is it that when I look at the Project Settings for CubeView there > > is no reference to fltk.lib? > > It's in the "Project Dependencies".. you'll see a dependency > on the fltk.lib and fltkgl.lib as being checked off. > > Regardless of where in the VS interface it's configured, you > should see the correct libs in the link lines from the Build Log. > > I highly advise looking at the Build Log, as that shows the actual > compile/link lines, which is where the rubber meets the road. > So I always look there for changes whenever there's a new FLTK release. > > I personally find the Visual Studio GUI interface to be convoluted > and irritating, so I just look at the FLTK build logs to see what > the compile/link commands are, and use that to create a Makefile. > > Why is the fltkgl in the "Project Dependencies" and not in the > project settings? > > I guess it's because the FLTK libs and test programs are all > self-contained > in a complete solution file, so that probably makes the most sense for > the VS studio way of packaging. So that's probably the best config > for FLTK itself, but not good reference for compiling standalone apps. > > HTH.
O.K. Good to know. I was able to resolve all my link problems and get my app compiled and linked under FLTK 1.1.9. That's the good news. The bad news is that I can not get stencil operations to work inside of my application. In fact I can't get any shaded polygons to show up correctly! Lines and polys colored with glColor show up fine. I have been able to extend the CubeView demo and do stencil operations on it in an FL_GL_Window. So I can't blame FLTK for my problems anymore :) Must be something sloppy I'm doing with OpenGL. Thanks for your feedback. _______________________________________________ fltk-opengl mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-opengl
