Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Doxygen plugin
Cryogen:
Some notes for Windows users.
Jens' patch doesn't update the Windows workspace for contrib plug-ins. To do so you need to do a few things:
1. Add DoxyBlocks' project to the contrib plugins workspace manually.
Now, because my installation doesn't match what C::B expects and config doesn't build the wx library with the name it expects (anyone care to advise me on this?)...
2. Open DoxyBlocks' build settings, select the "default" build and then the "Linker settings" tab and change the first entry under "Link libraries:" from "wx_msw$(WX_SUFFIX)-2.8.dll" to "wxmsw28$(WX_SUFFIX)".
If you have used a different wx library pattern on your system, replace mine with that.
3. Open the "Search directories" tab and on the "Compiler" sub-tab change "$(#wx.lib)\wx\include\msw-unicode-release-2.8" to "$(#WX.lib)\gcc_dll$(WX_CFG)".
Again, if your wx build directory tree is different, use the correct pattern for your installation.
Finally, for consistency with the other projects...
4. Open the "Pre/post build steps" tab and remove the line that starts "zip -j9 DoxyBlocks.cbplugin ..." from the "Post-build steps" window, unless you want the .cbplugin to be built, and check the checkbox at the bottom entitled "Always execute, even if target is up-to-date".
You should now be able to build DoxyBlocks with the other contrib plug-ins in a consistent way.
Cheers,
Gary.
[EDIT:] Do this, too, so that you can debug the plug-in from the contrib workspace:
5. In the "Project" menu select "Set program's arguments" whilst DoxyBlocks' project is active. In the resulting dialogue enter "--debug-log -na -ns -nd" under "Program's arguments" and "..\..\..\devel\codeblocks.exe" under "Host application".
codeur:
--- Quote from: Cryogen on March 22, 2010, 09:06:11 pm --- Hi Morten,
. . .
OK, cool. I will look at this because I like to build in as much flexibility as possible and, in general, it seems like a good idea.
I guess that having to add to system paths could be a bit of a nuisance and having another option is definitely a "good thing". :)
. . .
--- End quote ---
Thanks for this Gary.
I don't think adding to the CB-internal system path instead would really be a nuisance, but, since they are there already, your 4 or 5 paths to the executables are a useful reminder to nubies of the tool requirements of doxygen.
Cryogen:
Hi Guys,
Released version 1.3.236 of DoxyBlocks
-Added: Configuration of EXTRACT_PRIVATE and EXTRACT_STATIC. Requested by ptDev.
-Updated: Changed the generated doxyfile to doxygen 1.6.3.
-Updated: For consistency, changed HTML_TIMESTAMP default to YES.
-Updated: For consistency, changed EXTRACT_LOCAL_METHODS default to NO.
-Added: Macro expansion in path prefs so that you can use things like "$(CODEBLOCKS)" in paths. Requested by Codeur.
I have added the features requested by ptDev and Codeur. Let me know how they go for you, guys. They worked well here.
I have also updated the generated doxyfile to version 1.6.3. I checked through the current default values set by Doxygen and changed those mentioned to match doxygen's defaults. The timestamp is useful and local methods are only useful for Objective C users. DoxyBlocks inherited settings from jomeggs' script, which was not configurable and therefore set some default values that were thought to be widely used. Most of those are configurable in DoxyBlocks. The remaining settings that are not set to doxygen's defaults and not configurable in DoxyBlocks are:
SettingPurposeValueFULL_PATH_NAMESPrepend the full path before files name in the file listNOGENERATE_TREEVIEWGenerate index tree view in side panelYESCALL_GRAPHHave dot generate a call dependency graphYES
The purest way to do things would be to provide configuration for any setting that is not set to doxygen's default. I think that those three settings are pretty fair as they are but some folks might prefer other settings. Should these be set to doxygen's defaults and accessible via doxywizard? Should these, or other settings, be added to DoxyBlocks configuration panel? Does anyone have any thoughts on this?
Cheers.
LordCB:
I can´t still install ya plugin
and in sourceforge i see only version 1.2.209
could anybody illuminate me
codeur:
--- Quote from: Cryogen on March 23, 2010, 06:01:05 am --- ...
Released version 1.3.236 of DoxyBlocks
I have added the features requested by ptDev and Codeur. Let me know how they go for you, guys. They worked well here.
--- End quote ---
After a quick check, the executable paths using CB variables in "preferences" work well for me too. Many thanks.
I can place a portable CB based on BN 6190 onto a USB HDD and get DoxyBlocks to work immediately on any XP SP3 computer around (I cannot test on other systems).
--- Quote from: LordCB on March 23, 2010, 09:35:34 am ---I can´t still install ya plugin
and in sourceforge i see only version 1.2.209
could anybody illuminate me
--- End quote ---
Gary is currently trying to get a CB install that will allow him to produce .cbplugin (s) that work for all of us. He is making good progress, but until he succeeds we build DoxyBlocks from subversion with modified projects on our own systems in order to test working plugins on our systems (the possibility of having the doxygen plugin on the next release is what motivates us to test it in these conditions despite the inconvenience). The SVN on SourceForge is at version 1.3.236.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version