KDevelop's QMake Manager

Andreas Pakulat apaku at gmx.de
Sat Nov 25 23:49:25 UTC 2006


On 25.11.06 18:15:57, Steven T. Hatton wrote:
> On Monday 20 November 2006 19:22, Andreas Pakulat wrote:
> > On 20.11.06 16:56:23, Steven T. Hatton wrote:
> > > On Sunday 19 November 2006 14:50, Andreas Pakulat wrote:
> > > > On 19.11.06 14:09:22, Steven T. Hatton wrote:
> > > > > But are there .h files that include those?  If there are, the rpp is
> > > > > probably picking them up that way.
> > > >
> > > > No, it's picking up the .h files that are "deeper" in the hierarchy.
> > >
> > > That's really what I meant.  On my system those .h files #include the
> > > standard headers.  It appears I was wrong however.  The rpp doesn't
> > > appear to recurse through the #includes.  Understandably.  See
> > > http://bugs.kde.org/show_bug.cgi?id=137644
> >
> > I don't think I fully understand. However creating a PCS database for
> > /usr/include/c++/gcc4.x here works perfectly. Of course this might get
> > some unwanted stuff like gcj-header in.
> 
> I agree that an effective PCS db can be created for GCC.  It works because 
> most everything is in a file with a .h filename extension.  With OSG, that is 
> not the case.  In that situation all I have are the <osg/Geometry>, 
> <osg/Node> etc.  There are no corresponding <osg/geomery.h> and the like.  
> I /can/ copy the entire OSG include directory to a pcs-include, giving the 
> extensionless filenames .h extensions, and then running the PCS tool against 
> that.  That is a work-around, not a real solution.
> 
> What I thought might work, but didn't was to put all the extensionless file 
> names into a .h file as #include directives, and then point the PCS at that.  
> The proposition was that PCS would follow the #includes, but it doesn't.

Hmm, this should be considered a bug in kdevelop. It shouldn't rely on
the file extension to find out the type. 

I'd suggest to file a bugreport about this, though I'm not sure this
will be fixed in 3.4. It may take until 4.0 to fix this, anyway I'll
promise to have an eye on this issue (i.e. determining file type _not_
via file-extension, or at least not only on file-extension).

Andreas

-- 
Good night to spend with family, but avoid arguments with your mate's
new lover.




More information about the KDevelop-devel mailing list