On Thursday, July 02, 2015 09:09:43 AM Ferro, Alasdair wrote: > Hi, > > [Using Doxygen 1.8.9.1, on CentOS6.6] > > I'm adding Doxygen to a fairly new project, which uses Qt. I've added some of > the Qt header directories to Doxygen's INPUT list, so that Doxygen can > extract some information (mostly class hierarchy & methods). However, this > also causes *lots* of warnings to be emitted, for the Qt headers, which I > don't own (obviously) so cannot fix. Is there any way to turn off warnings > for those files, but keep them turned on for our code? When compiling, I use > GCC's -isystem option to disable warnings from headers in those directories - > does / could Doxygen have something similar? > > BTW, I also get "QGDict::hashAsciiKey: Invalid null key" appearing (around > 2800 times) - I guess it caused by the undocumented code in the Qt headers? > Is this a known issue or should I submit a bug report? > > Thanks for a great tool! > Alasdair,
You want to point to the Qt tags files, not process the Qt headers directly. as described in: http://stackoverflow.com/questions/22244779/doxygen-generated-documentation-with-auto-generated-links-to-qt-project and http://www.stack.nl/~dimitri/doxygen/manual/external.html ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ Doxygen-users mailing list Doxygen-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/doxygen-users
