That's a good point, I forgot all about this. In fact, I'm not sure I even saw
the link posted.
--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=49548#49548
___
osg-users mailing list
osg-users@lists.o
Hi,
Actually You have to redirect both stdout and stderr
osgviewer cow.osg > foo.txt 2>&1
On windows "standard" way of logging is to use OutputDebugString function
that connects application to windows debugging facilities (i.e output window
of visual studio). Many libraries print debug messages t
it seems to helps a lot
--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=48499#48499
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-
This is pretty obvious (I know) but it helps a lot to link with the debug
libraries... :D
--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=21464#21464
___
osg-users mailing list
osg-users@lists.opensce
Paul,
I moderated the original mailing list post on the OSG forum to show your
reformatted version of the tips. And I added a few links.
--
Roland
--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=10495#10495
___
5 matches
Mail list logo