Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Doxygen plugin
Jenna:
--- Quote from: rcoll on February 23, 2010, 02:27:08 pm ---
--- Quote from: killerbot on February 22, 2010, 10:16:54 pm ---in linux version would be nice to try to incorporate the wxchm (i don't knwo it, but it sounds interesting) :-)
--- End quote ---
A *.chm file is compiled HTML; does linux have a way of reading those?
Ringo
--- End quote ---
Yes, several apps that can read chm-files are available on linux.
JGM:
a chm file could be said it is a zip file with the files inside organized in a standar way
codeur:
--- Quote from: Cryogen on February 22, 2010, 07:32:34 pm --- Hi Codeur,
. . .
If you could provide the details and try upgrading your version and report your results that would be appreciated.
. . .
--- End quote ---
Thanks for trying to guess why I am having this issue. I do not myself have time to investigate this, so I am not asking for help on this.
Just to answer your question, The error I get when installing the .cbplugin is:
------------------------------------------------
"one or more plugins were not installed successfully:
G:\down\Program........\DoxyBlocks.cbplugin"
------------------------------------------------
A pop-up windows comes up from the task bar:
-------------------------------------------------------------
One or more plugin were not loaded.
This usually happen when a plugin is built for a different version
of the Code::Block SDK. Check the application log for more info.
List of failed plugins:
DoxyBlocks.dll
-------------------------------------------------------------
Obviously this does not tell us much new. (Except that it is an answer to your question: A plugin built from a recent svn is very unklikely to run in CB 8.02.)
It also tells me that upgrading my version would indeed probably fix the issue. I'll do that sometime, but don't hold your breath as this is an installation common to about 200 people. I do not change it just to install a new plugin, even one as useful as Doxygen.
MortenMacFly:
--- Quote from: Cryogen on February 22, 2010, 09:25:29 pm ---I've now uploaded a new version that adds quite a lot of new functionality:
22 February 2010
released version 0.2.172 of DoxyBlocks
--- End quote ---
I gave it a try and it looks quite good. :P
Hence I have some suggestions to make:
1.) It was hard to me to find out how I actually use this. Until I found the toolbar which gives access to the functions. An extra "doxygen" menu would be fine.
2.) In addition some of the options should go into the editors context menu, too (like "add doxygen comment at current editor position) for convenience.
3.) The "DOT_PATH" is written twice if you setup the DOT executable. You just need to remove the additional line:
--- Code: ---sText += _T("DOT_PATH =\n");
--- End code ---
4.) Having the possibility to view the HTML file in the internal HTML viewer of C::B would be really convenient, too. You can have a look how it's done in the build log.
5.) The project file needs some clean up as there are absolute path's included that make installation fail. You should consider to put all path's relative to the "contrib" plugin folder. That's what most people expect I'd say.
6.) The setup dialog is quite huge and although I personally don't really care I think users with small screen resolutions will complain sooner or later.
Besides this I just started using it and having fun. :)
Cryogen:
Hi Guys,
Thanks for all of the discussion and feedback, much appreciated. Thanks, Morten, for the detailed response. I'll respond to that separately.
I have just uploaded V0.2.178. Changes since 172:
-Updated: Documentation.
-Fixed: Prefs dlg order and improved the layout slightly.
-Added: Warning checkbox toggles other warnings which I forgot to add before.
-Updated: The entire project to run from \src\plugins\contrib\. Hopefully that will solve some problems.
Note in particular that last, which speaks to one of Morten's comments.
Now then, I spent, or rather lost, an entire day (more like 16 hrs than 8!) trying to get the thing to run under Ubuntu and have ended up very frustrated. Firstly, the SVN version I built just won't run. It just hangs without output, even on the command line. I then spent hoooooooooooooours chasing down the solution to this error:
--- Quote ---codeblocks: relocation error: /usr/lib/libcodeblocks.so.0: symbol _Z18wxSafeConvertWX2MBPKw, version WXU_2.8.2 not defined in file libwx_baseu-2.8.so.0 with link time reference
--- End quote ---
I have tried every solution that I could find, every package, repository, custom build, you name it. Nothing works and it then took me more hours to recover to 8.02. The only good that came from it is that I seem to have acquired a later version of wxSmith in the process which now has the Extra Code field that was stopping me before.
OK, so now I can build DoxyBlocks but will it run? No way. Not for anything. More wasted hours. It seems, from a comment of Jens', that there is an inherent problem with third-party plug-ins that causes the correct paths to be lost during start-up and therefore the thing fails looking for plug-in zip files. To say that I'm not impressed is an understatement. :?
Result: I give up. I can build it and will post a version for others to try shortly but it seems that it won't run properly until such time as it's pre-built and supplied with C::B. That's just terrible. If anyone that knows more about this can help, that'd be great but it seems terminal thus far.
On to the good news. It installs and behaves as expected for me. There's a .cbplugin available now that was built from the C::B \src\ tree. I hope that that will remove some issues experienced by others. I have replaced the $(#CB) env. var., which I'm sure was provided by the project wizard, and used relative paths to be consistent with other plug-ins. It now only uses $(#WX), which should be standard with one exception. I have been unable to find any way to build wx with the "$(#WX.lib)\gcc_dll$" style path. After much searching, the only method I could get to work was creating my own dirs within the wx tree for each build, so I have this style of thing:
...\wxWidgets-2.8.10\msw-release-mono\lib\...
so the one path that I think you'll have to change is this one:
$(#wx.lib)\wx\include\msw-unicode-release-2.8
to this, I think:
$(#WX.lib)\gcc_dll$(WX_CFG)\msw$(WX_SUFFIX)
Again, if anyone would care to educate me on how to achieve the paths that C::B expects by default, that wold be good as I currently have to edit every instance which, you might say, is sub-optimal. :)
Here's a new snapshot:
and, finally, the docs are now online at:
http://doxyblocks.sourceforge.net/
Cheers,
Cryo.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version