Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

Doxygen plugin

<< < (5/53) > >>

Cryogen:

 Hi Jens,


--- Quote ---This is a problem with the wxWidgets in Ubuntu 9.10, that is not binary compatible with the version of wxWidgets.org .
There are several posts about this, to fix the problem.

--- End quote ---

Yes, I have tried them all, including your pages. :-)


--- Quote ---Nevertheless, I will see what I can do to build and run your plugin on linux .

--- End quote ---

Thanks, that would be wonderful. If you can suggest how I should proceed on Ubuntu Karmic that would also be great.

Cheers.

Jenna:

--- Quote from: Cryogen on February 26, 2010, 12:04:16 am ---Thanks, that would be wonderful. If you can suggest how I should proceed on Ubuntu Karmic that would also be great.

--- End quote ---
Compiling on linux was no problem, I attach the project-file that works for me.
I did not (yet) test the functionality.

To use C::B on Karmic, you have to either remove all wxwidgets 2.8.10 packages shipped with ubuntu and use the ones from apt.wxwidgets.org (in this case you can use my repo), or remove all packages from apt.wxwidgets.org and use the packages shipped with Karmic.

In the second case you have to build C::B yourself with automake system or use the repo provided by pasgui (he provides a special version for Karmic) : http://forums.codeblocks.org/index.php/topic,11875.msg80825.html#msg80825 .

[attachment deleted by admin]

MortenMacFly:

--- Quote from: Cryogen on February 25, 2010, 11:42:38 pm ---Fair comment. Funny what we assume, isn't it? Do you think that it would be best as a sub-menu in the Plugins menu or is it worthy of a new menu to itself?

--- End quote ---
Do an own one. (That's just my opinion.)


--- Quote from: Cryogen on February 25, 2010, 11:42:38 pm ---I hadn't thought of that as I don't use it but it sounds useful. What do you mean by "in the build log"?

--- End quote ---
If you write a HTML log file then in the build log a message (link) to the HTML log file appears which you can click. This opens the internal HMTL viewer of C::B. I meant have a look at the code how it's done.


--- Quote from: Cryogen on February 25, 2010, 11:42:38 pm ---I think that'll have to happen if I include any more default options, anyway.

--- End quote ---
Mmmh... I was under the impression that the stand-alone config dialog was that big... probably it was the container - I'll have another look


--- Quote from: Cryogen on February 25, 2010, 11:42:38 pm ---Keep 'em coming. I want this to be useful to the community at large so I'm open to change.

--- End quote ---
Hehe... I'll give you one more: When choosing to add a doxygen comment at the current cursor position you could parse the following code for a function signature and pre-process the lines added accordingly. Meaning: If I choose to add the comment before a line like:

--- Code: ---int MyFunc(double par1, int par2);
--- End code ---
...it could add the params and the return value automatically. like:

--- Code: ---/**
 * \brief MyFunc
 * \param par1
 * \param par2
 * \return
 */

--- End code ---
...whereas for:

--- Code: ---void MyFunc();
--- End code ---
...it would just add:

--- Code: ---/**
 * \brief MyFunc
 */

--- End code ---
Surely this is a bit complicated but would save some time typing. :lol:

Cryogen:

 Hi,


--- Quote ---If you write a HTML log file then in the build log a message (link) to the HTML log file appears which you can click. This opens the internal HMTL viewer of C::B. I meant have a look at the code how it's done.

--- End quote ---

Aah, is that what that is for. I've clicked on some and nothing happens. I just tried again after running HTML docs, which produces said link, still nothing. I couldn't find any HTML viewer in the menus but then I saw that the man viewer's title bar actually says "Man/HTML". Is that it? Either way it doesn't work for me in SVN 6130. Or I haven't found it.  :)


--- Quote ---Mmmh... I was under the impression that the stand-alone config dialog was that big... probably it was the container - I'll have another look
--- End quote ---

I checked too with and without the plug-in installed. It has slipped a bit and become larger. I think I can restore it to the original size by splitting across tabs.


--- Quote ---Hehe... I'll give you one more: When choosing to add a doxygen comment at the current cursor position you could parse the following code for a function signature and pre-process the lines added accordingly.
--- End quote ---

In fact I hope to go one step further than that. I'd like it to be able to document the project automatically. I've seen code around that does that. I think it will require some dabbling in regexes, which I'm no expert with but, if I can get that working, this would be a logical contraction of that. Thanks.

Cheers.

Cryogen:

--- Quote from: jens on February 26, 2010, 07:28:15 am ---
--- Quote from: Cryogen on February 26, 2010, 12:04:16 am ---Thanks, that would be wonderful. If you can suggest how I should proceed on Ubuntu Karmic that would also be great.

--- End quote ---
Compiling on linux was no problem, I attach the project-file that works for me.
I did not (yet) test the functionality.

--- End quote ---

 Yeah, I can build it, too. I just can't run it in any way. Thanks for that I'll compare it with mine and see what shows up.


--- Quote ---To use C::B on Karmic, you have to either remove all wxwidgets 2.8.10 packages shipped with ubuntu and use the ones from apt.wxwidgets.org (in this case you can use my repo), or remove all packages from apt.wxwidgets.org and use the packages shipped with Karmic.

--- End quote ---

Yes, I did that. Something may have been out of place so I'll give it another go and report progress.


--- Quote ---In the second case you have to build C::B yourself with automake system or use the repo provided by pasgui (he provides a special version for Karmic) : http://forums.codeblocks.org/index.php/topic,11875.msg80825.html#msg80825 .

--- End quote ---

My build hangs as described. Reason unknown. pasgui's repo didn't work either. As I said I tried eeeeeeeeverything. :?
However, there's every chance I screwed things up. I can get around on Linux without trouble but I don't have the same depth of knowledge that I do with Winblows systems. For example, is the installation order critical? Is there anything I need to ensure happens a certain way at some stage?

Cheers.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version