home/killerbot/Projects/Test/Project/doxygen/doxyfile was not created. Quote -ĭoxyBlocks is working, please wait a few moments.įailed. Here's a project that now fail with the doxygen plugin, where it used to work in the past. Gonna try to post a little project here, showcasing the failure this evening, It used to work before, now it no longer works. Maybe Make Targets are intended to be used whenĮclipse is generating the makefile, which is not my case.Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins developmentīefore I forget, in on e of the last changes something got broken, with respect to output directory or position position of the cbp file or the doxygen file. Furthermore, just for organization purposes: I don't know what is theĬonnection between this kind of Make Target and a Build configuration as In my opinion and experience, it's unnecessary, and probably outdated, since Eclox has been unmaintained for years. Eclox also offers an editor for the Doxyfile. However, the Builder is just another External Tool that gets run automatically. The Builder can be configured to run after the normal builder on an auto-build, or on a manually-triggered build.
The output again goes to the build console, so it is parsed by Eclipse, so this should be OK. add a Make Target, in which you can configure the executable and target (read: arguments to the executable) to be run.They might have some advantages, though they didn't work for me. YMMV.Īlso, I mentioned that there are other ways to launch Doxygen builds without Eclox. Note that I'm doing this in a CDT "Makefile project with existing code" project, which gives you more configuration freedom than other kinds of projects. and at this point I thought that I would have to configure my own Doxygen error parser, but no! Turns out that the Doxygen warnings are similar enough to gcc or make warnings that the normal parsers will already detect them. When you run this build (which can be done from the toolbar), the Doxygen output will go to the build console, and so will get analyzed by the CDT error parsers.
ECLIPSE DOXYGEN PLUGIN HOW TO
How to do it? Just add a C/C++ build configuration which, instead of running make, will run your Doxygen executable, in the expected work directory, with "build target" the appropriate Doxyfile. Īnd turns out that one of these ways not only allow you to launch the Doxygen building of docs, but will detect and highlight the Doxygen-reported warnings and problems!
One can do the same in a variety of ways in the naked Eclipse/CDT. There is the Eclox plugin for Eclipse, but it is almost useless: all it does is run Doxygen on configurable Doxyfiles, and offer a button to do so from the toolbar. A particular missing feature is that errors in the comments are not highlighted in any way and that's what made me look for a better alternative.
Eclipse (or is it the CDT?) has, by default, some Doxygen integration: if the preferences are set appropriately, Doxygen-style comments are highlighted differently, and Doxygen commands in those comments are further highlighted.īut that's about it.
0 kommentar(er)
