Hi Brian,
On 1/24/07, Brian Keener <[EMAIL PROTECTED]> wrote:
You are correct. I discovered last evening after my post and seeing you had
posted some updates that a cvs update did resolve the running issue. With a
current cvs I was able to compile in Cygwin and run osgAnimate, osgPlanets,
osgWindows cow.osg and osgViewer cow.osg.
Good to hear some progress. Could you please use the correct case for
examples as its confusing when a NodeKit and a app have the same name
.e. osgParticle and osgparticle, osgViewer and osgviewer are the
NodeKit and respective application. By convention all OSG
applications are lowercase, none of the builds build to any other than
lower case for applications, its only libraries that follow the
osgCapticalStyle. This is a deliberate policy to avoid confusion.
The issue with the paths still seems to be present in that now I must be in the
test data directory even with OSG_FILE_PATH set and I must also have the path
for the osgPlugins not just their parent directory in my PATH variable.
I wonder if this is related to a new addition to osgDB/FileUtils.cpp
where it call the function osDB::getRealPath on the path name. See
line number 208 of FileUtils.cpp:
path = getRealPath(path);
You could try commenting this out and see if it fixes the path finding.
I have discovered as well that osgPlanets completes normally, osgWindows and
osgViewer with the cow.osg will hang when I escape to quit on them and the
interesting one which may help us with these hangs is that when I ran
osgAnimate one time and I was not in the test data directories I got a screen
with the checkerboard but no airplanes and when I exited I returned to console
mode as expected. But when I was in the test data directory and ran osgAnimate
and saw the checkerboard and airplanes then when I escaped to quit the process
hangs.
Could you get a stack trace for this hang?
So far the only thing (besides a lot of prints to the screen to try to debug is
add the X_LIBS value to the OTHER_LIBS value in the CYGWIN section of Makedefs.
I will post that to osg-submissions. I ma unsure why I had to do that butit
cleared up the SwapBuffers and other errors.
Are you building against GraphicsWindowWin32 or GraphicsWindowX11? If
the later then I'd expect you to need X_LIBS, otherwise not.
That was just a WAG but there is something - some part of some of the test
programs that is waiting to exit and causing the main process to hang - see
above about the osgAnimate. By the way - I don't mean to say it is strictly
OSG - their could obviously be an idiosyncracy with Cygwin despite their
success converting Linux apps to Cygwin we might have some oddity here.
Cywiin doesn't seem the most solid of developer platforms as over the
years users have reported both success and failure to run, I don't get
a feeling that things are getting more solid over time.
The exit from osgViewer should be done pretty co-operatively with nice
gentle requests for threads loops to exit, and code that waits till
the exit does happen. There might still be cases that aren't well
handled so it would be worth investigating in the hope that we might
be able to do things slightly different to help Cygwin limber along.
Robert.
_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/
