Thanks for your help.
I will study Kscope because I didn't know this tool.
Regards.
Message du 25/08/09 à 10h32 De : mansoor@iwavesystems.com A : coreboot@coreboot.org Copie à : "Harald Gutmann" harald.gutmann@gmx.net Objet : Re: [coreboot] Development IDE
I use Kscope for both kernel development and coreboot
http://kscope.sourceforge.net/
On 24.08.2009 22:45, Harald Gutmann wrote:
On Monday 24 August 2009 22:36:35 Carl-Daniel Hailfinger wrote:
On 24.08.2009 19:02, congedete@voila.fr wrote:
I wanted to know which development IDE do you use to develop coreboot: Eclipse, Netbeans ... I can't find anything, any project under Eclipse or any other IDE.
I use vim and grep. There is no IDE for coreboot development.
Interesting, but do you use any extensions for vim? I really love vim, and use it for all kinds of text modification. :)
Some time ago I came across this article: http://www.swaroopch.com/notes/Vim_en:Programmers_Editor and some things in there are really useful to use vim as IDE.
IMHO a few bits of advice on that page encourage writing mediocre code (like focusing on typing speed instead of thinking), but making up for it with sheer size. Then again, this is probably a cultural thing.
The only "special" vim features I use are syntax highlighting (always) and bracket bouncing (rarely). Autoindent is off. Each helper tool is run in a separate window, usually even on a different virtual desktop. I usually use 3-4 virtual desktops for development, each with another window open at the same time. Ctrl-Alt-Arrow for moving between virtual desktops in a 4x2 grid. Top row of desktops is for development, bottom row is for communication (web, mail, IRC). The exact window layout differs depending on the task (code/datasheet cross-checking, writing new generic code, writing new chip-specific code, or changing the architecture of some code). Window manager is fvwm2. ctags/cscope are nice, but I hardly ever need them outside orientation phases (and during orientation phases I usually read _all_ related code to avoid using ctags/cscope later). While using ctags/cscope can be a great timesaver, it is often even faster if you don't need them at all.
Regards, Carl-Daniel
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
DISCLAIMER: This e-mail and any attachment (s) is for authorised use by the intended recipient (s) only. It may contain proprietary material, confidential information and/or be subject to the legal privilege of iWave Systems Technologies Private Limited. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from retaining, using, copying, alerting or disclosing the content of this message. Thank you for your co-operation.
DISCLAIMER: This e-mail and any attachment (s) is for authorised use by the intended recipient (s) only. It may contain proprietary material, confidential information and/or be subject to the legal privilege of iWave Systems Technologies Private Limited. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from retaining, using, copying, alerting or disclosing the content of this message. Thank you for your co-operation.
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
____________________________________________________
Envie de partager vos photos de vacances ? Voila vous offre 1 Go d’espace de stockage sur http://macle.voila.fr
in v3 I had a kscope target, such that make kscope would set up kscope for the sources used for your mainboard only. Have not done this yet on v2. I intend to at some point.
Sometimes, this kind of thing is handy.
ron
On Wed, 2009-08-26 at 09:13 -0700, ron minnich wrote:
in v3 I had a kscope target, such that make kscope would set up kscope for the sources used for your mainboard only. Have not done this yet on v2. I intend to at some point.
Sometimes, this kind of thing is handy.
ron
A while ago I was using the OpenGrok webapp for this kind of stuff.. it's just like lxr, but a bit more evolved (VCS-aware)
An instance of it running can be seen at http://src.opensolaris.org/source/
For those who don't know, lxr can be seen at http://fxr.watson.org
I'll try to get it installed and tracking our code on a regular basis.
Cristi.