Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Doxygen plugin
codeur:
DoxyBlocks is misbehaving here without any doubt, but your test did not present it with the issue in question.
To reproduce the issue:
- load the provided example project into codeblocks,
- press "Extract Documentation" in the Doxyblocks menu to get the success message, then
- press "Run HTML" in the Doxyblocks menu to obtain the "Index.html not found" message.
You obtain:
--- Code: ---Extracting documentation for CbLauncher.
DoxyBlocks is working, please wait a few moments...
Found existing doxyfile...
Success.
Your documents are in: C:\Temp\CbLauncher\doxygen\
Done.
Index.html not found at C:\Temp\CbLauncher\doxygen\html/index.html.
--- End code ---
The provided project doxyfile specifies the output directory as ../doc
Doxygen does the right thing and generates the documentation in ..\doc
DoxyBlocks is unaware of this output directory and assumes that the documentation is in the default "doxygen" subdirectory.
For how that output path was set originally for this project:
--- Quote from: codeur on February 03, 2011, 06:20:22 am ---The path to the output directory is set in the doxyfile by using the doxywizard (project -> expert tab).
--- End quote ---
The output directory ../doc was originally entered in the "output directory" field on that page.
Latest Codeblocks, latest Doxyblocks, XP (the issue was the same with previous versions of Codeblocks and previous versions of DoxyBlocks).
I think you must have re-generated a new doxyfile and therefore erased the output path from the project doxyfile prior to your test, so it could not show the issue.
If it is too much work to fix this issue, I can personally live with it. It's not a big hassle.
Cryogen:
--- Quote from: codeur on February 06, 2011, 05:14:02 am ---I think you must have re-generated a new doxyfile and therefore erased the output path from the project doxyfile prior to your test, so it could not show the issue.
--- End quote ---
Yes, you're right. I see the problem now. I'll look into it.
Thanks.
Cryogen:
Hey Codeur,
I've discovered what's going on here. There are several parts to it. Firstly, when you use something other than "doxgen" as the doc dir. you need to set the OUTPUT_DIRECTORY field on the "Doxygen Defaults" tab. The help tooltip explains the options. At the same time, DoxyBlocks doesn't support having the doxyfile in one place and the docs in another. The problem is that it looks at its prefs to determine the output dir., not in the doxyfile, and it assumes that that is where the doxyfile lives, too.
So, firstly, while I think that DoxyBlocks should support that, since doxygen does, it will take some work reviewing all of the path management code and I don't have time to do that at present. Secondly, I have fixed a bug or two and made some improvements. You can still run things as you are now, if you wish, but DoxyBlocks won't run the docs. If you enter the path in the prefs, DoxyBlocks will write a new doxyfile there, ignore the doxygen dir. and then behave correctly, although not exactly as you desire. The best solution is to move your doxfile to ../doc and then everything will be reported and run correctly without any intervention. If you are happy with that, I think you are in business.
I will create a TODO item for posterity. The patch will be available shortly.
Thanks again.
Cryogen:
Released version 1.7.655 of DoxyBlocks
-Fixed: Hard coded doxygen directory name.
-Updated: Directory creation code.
Patch available from the Patchorama link below.
Cheers.
codeur:
Thanks for the update Gary,
I'll place the doxyfile with the documents, no problem.
But before I can try that I need to find your patch. I searched for it on the wxsmith_addons branch on berlioz without luck. Can you give me a more precise hint of where it is?
EDIT: I have found it, thanks.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version