Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Doxygen plugin
Cryogen:
I must be bored... :o
Released version 1.4.366 of DoxyBlocks
-Added: Information about macro expansion to the config. panel path tooltips.
-Cleaned: Removed the .cbplugin creation command from both Windows and Unix projects.
-Added: You can now click the URL displayed in the log window to view the HTML docs.
-Updated: Changed the config Get functions to be constant.
You can now click the link in the log window to run the HTML docs. Nice if you have changed projects, or just for convenience. The link is only written to the log when you run view the HTML using the internal viewer but, once it's available, DoxyBlocks will respect your settings and open the docs in the internal viewer or your browser.
The .cbplugin command in the project files is now gone so it should match the other contrib projects exactly.
Cheers.
maofde:
Hi guys,
sorry for my noob question, but I already struggle in the compiling step:
Using Ubuntu 9.10 with C::B 8.02 or SVN 6196, I chose the DoxyBlocks-unix.cbp project and simply pushed the build-button.
The I get errror messages:
--- Code: ---Can't create object output directory /home/.objs/plugins/contrib/DoxyBlocks/
Can't create output directory /home/devel/share/codeblocks/plugins/
--- End code ---
Do I have to place the doxyblocks source into a special folder? Or what else I'm doing wrong?
Thanks for your support in advance.
Cryogen:
Hi there,
--- Quote from: maofde on March 28, 2010, 03:13:00 pm ---Hi guys,
sorry for my noob question, but I already struggle in the compiling step:
Using Ubuntu 9.10 with C::B 8.02 or SVN 6196, I chose the DoxyBlocks-unix.cbp project and simply pushed the build-button.
The I get errror messages:
--- Code: ---Can't create object output directory /home/.objs/plugins/contrib/DoxyBlocks/
Can't create output directory /home/devel/share/codeblocks/plugins/
--- End code ---
Do I have to place the doxyblocks source into a special folder? Or what else I'm doing wrong?
Thanks for your support in advance.
--- End quote ---
The best bet is to put it in the CodeBlocks source directory structure in src/plugins/contrib/. That will allow it to put the files it builds into the right directories along with the other plugins. Build it, then run the update script and you should have DoxyBlocks in your release version.
If you go one step further and add DoxyBlocks' project to the contrib plugins workspace provided with CodeBlocks source, you can build it along with the others in one fell swoop.
Oh, and it won't work with 8.02. Use the SVN version.
Have fun.
MortenMacFly:
--- Quote from: Cryogen on March 28, 2010, 07:30:51 am ---Released version 1.4.366 of DoxyBlocks
--- End quote ---
BTW: You should add a virtual target named "All" to your project files that would compile the main target. This would ensure that when compiling the C::B workspace (where all projects / target belong also to the virtual target "all") you plugin gets compiled, too. I just realised that. Have a look at other plugins if in doubt.
codeur:
As I start using DoxyBlocks in a few projects myself prior to the big release, I am going to dribble in a few issues as I encounter them. Starting now:
The "default commenting style preferences" is a major one:
In a work place (or an educational institution) that has several programmers, they all use the same style standards that usually define their commenting style and other aspects. In those places, they will always use the same preferences for all projects. These include not only the global preferences that you have listed a few days ago, but many other aspects, like using @ in tags, or selecting the QT style for block comments or the C++ slash style of line comments, etc...
For those people, it would be a pain if they had to set their preferences according to their in-house standards again every time they start a new project. Could ALL the commenting style preferences last used be stored and become the new default commenting style preferences when a new, not yet commented project is started?
And a minor one:
The prototype: int yes( const char *question );
generates: ----- * @param *question constchar ----- for the parameter.
The prototype: bool yes( const string &question );
generates: ----- * @param &question conststring ----- for the parameter.
Can this be easily fixed?
Thanks.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version