Hi, I already wrote about searching for OSG and OSGEarth two or three mails ago. There's no need to set up all of the paths that you see in the cmake gui, all of them are filled automatically from the variables OSG_DIR and OSGEARTH_DIR. It should work exactly the same way that as Qt does. I'm not sure if include dirs are handled in any way (I didn't write anything for that, but maybe it's handled by some cmake internal magic). It needs testing on windows and mac, that's why I didn't close the issue. K > Hi Cestmir and Kuba, > I see you have already changed the CMakeLists.txt, please write a > short e-mail, describing how to properly configure it and what has > been changed. > > Is there some automatical searching of osg and osgEarth libraries > implemented? Why are there so many variables to set? - I mean for > example osgutil_include_dir, osgdb_include_dir and other osg dirs, > while there could be, and almost sure is, only one include dir for > all osg libs. > > It's not comfortable to set so many paths...is it possible to have > only 6 following variables: osg(debug+release), osg > dependencies(debug+release) and osgEarth(debug+release) ? ...I think > that rest paths are relative to these ones. > > Tom > > To visit archive or unsubscribe, follow: > //www.freelists.org/list/glideplan_swproj