Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Doxygen plugin
Cryogen:
Hi Jens/Guys,
Released version 1.2.221 of DoxyBlocks
-Fixed: Finally got it to run on Linux with Jens' help by integrating with contrib plug-ins and building from there.
-Updated: Changed my fix from 1.2.218 to Jens' version as it's more efficient.
At long last I've finally seen it running on Linux. :mrgreen:
That's a really nice step forward, thanks for your efforts.
With that and the bug fix we're looking really good.
--- Quote from: Cryogen on March 20, 2010, 08:47:29 pm ---
Hi Jens,
--- Quote from: jens on March 20, 2010, 12:05:45 pm ---Back at home, I created two patches, one against C::B's trunk and one against DoxyBlocks trunk.
--- End quote ---
Thanks. I have done much of that on Linux but, since it fails, haven't incorporated it into SVN. I'll tinker with these later today.
--- End quote ---
My system still had some issues but I finally got it running. It looks like you created your own directory and used lower case. For consistency with the package and my setup, I have changed the couple of instances where your patch used "doxyblocks" to "DoxyBlocks". If you could do the same that would be appreciated. There are:
configure.in (3)
src/ContribPlugins-unix.workspace (1)
src/plugins/contrib/Makefile.am (1)
acinclude.m4 (1)
Attached is a copy of your patch with those changes made. Hopefully that will save you having to mess around.
Thanks again,
Gary.
[attachment deleted by admin]
codeur:
This request is to make doxyblocks usable in portable versions of Code::Blocks.
In order to make DoxyBlocks portable, could the paths to the documentation executables in the general preferences screen be made to use Codeblocks variables? The paths to the tools could then be made relative to the CB installation.
As an example being able to enter something like $(CODEBLOCKS)\tool\Graphviz\bin\dot.exe
rather than E:\Program Files\codeblocks\tool\Graphviz\bin\dot.exe as the path would make doxyblocks usable in a portable CB installation.
Thanks.
MortenMacFly:
--- Quote from: codeur on March 22, 2010, 01:01:28 am ---As an example being able to enter something like $(CODEBLOCKS)\tool\Graphviz\bin\dot.exe
--- End quote ---
@Cryogen: True, you can achieve that easily using a call to macros manager before applying the path's. It's a one-liner per path.
BTW: Really, really: Nice work! I've just upgraded from 0.4 to the SVN... well done!
Jenna:
--- Quote from: Cryogen on March 21, 2010, 04:39:38 am ---My system still had some issues but I finally got it running. It looks like you created your own directory and used lower case. For consistency with the package and my setup, I have changed the couple of instances where your patch used "doxyblocks" to "DoxyBlocks". If you could do the same that would be appreciated. There are:
--- End quote ---
I also had the DoxyBlocks-plugin in a CamelCase-named suubdirectory and only changed it to lower-case, because your svn-directory is in lower-case too.
The contrib-plugins not all use CamelCase (even if I prefer it as you can see at my "own" plugin IncrementalSearch).
In short: it's no problem to me (debian files have to be fixed accordingly, if debian build-scripts are used, of course).
ptDev:
Before anything else, thank you very much for making Doxygen so much easier to use! :D
I have a small feature request: is it possible to add the doxygen flags EXTRACT_PRIVATE and EXTRACT_STATIC explicitly to the "Doxygen Defaults" tab? Although I never check EXTRACT_ALL, the setting is overriden by them, and I would like to have control over the documentation of private class members.
Of course, I can easily edit the generated doxygen settings file to this end, but it would make a big difference for me if I could have it generated the way I need it from the get-go.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version