[glideplan_swproj] Re: CMake
- From: Kuba Marek <blue.cube@xxxxxxxxx>
- To: glideplan_swproj@xxxxxxxxxxxxx
- Date: Sun, 1 Jan 2012 14:05:45 +0100
Just one more thing to be sure the package detection is working ... try
it once more with clean cache if you already didn't (delete
build/CMakeCache.txt or the whole build/ directory)
The warnings probably appeared because I added -Wall compiler flag.
For me it added a lot of warnings from osg includes, but on gcc these
were silenced by specifying include paths as system.
(
https://github.com/updraft/updraft/commit/e3afe9fcd8bc6f29952d17b6ff35bdde70e8687e#L1R68
)
... and yes, every plugin must inherit from QObject for the
QPluginLoader to work.
K
> Thank you for hint, Kuba.
> I only set the two mentioned variables in CMake and it works...looks
> very nice.
>
> Now I encounter another 2 problems:
> 1)
> There are thousands of compiler warnings from Qt files.
> It seems that these warnings are only thrown when compiling moc files.
>
> Is it possible that it has something to do with Cestmir's commit?
> https://github.com/updraft/updraft/commit/5be96d907e1cd78aeb11e3ba5c8b771b4131ffe7
>
> There are lot moc files...is it necessary for each plugin to inherit
> QObject?
>
> 2)
> I'm also unable to run the application...it fails in function
> osgEarth::MapNode::findMapNode even when the passed argument seems to
> be valid (not null).
>
> ...Is anybody able to run the last version on Windows? And compile it
> without all the warnings?
>
> Tom
>
> > ------------ Původní zpráva ------------
> > Od: Kuba Marek <blue.cube@xxxxxxxxx>
> > Předmět: [glideplan_swproj] Re: CMake
> > Datum: 31.12.2011 15:23:55
> > ----------------------------------------
> > 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
> >
> >
> >
>
> To visit archive or unsubscribe, follow:
> //www.freelists.org/list/glideplan_swproj
Other related posts:
