Hey Jeff, thanks for the reply, what I realy don't like in IDEs is tying building and editing at same tool. I'm a simple guy so I like to keep things simple. I never heard of anybody using IDE's for building C code in linux. I'm considering back to vim since emacs indenting is making me crazy Regards 2015-12-22 17:59 GMT-02:00 Jeff Haran <Jeff.Haran@citrix.com>:
Off list.
I use gvim, make, all the old style tools for kernel development and have been doing so for about 15 years now, but I am an old fart. Your boss needs to understand that a lot of these IDEs, though useful for user space development, don’t help much in kernel space. When the kernel goes bad, the IDE goes with it.
If he is uneducatable on this, you might want to check out this package called kdevelop. You can keep it running in one desktop to make him happy and then do the real work using the tried and true command line tools in another desktop.
Good luck,
Jeff Haran
From: kernelnewbies-bounces@kernelnewbies.org [mailto:kernelnewbies-bounces@kernelnewbies.org] On Behalf Of Daniel. Sent: Tuesday, December 22, 2015 11:28 AM To: kernelnewbies Subject: Developing environments used for kernel development
My boss came to my desk today raiging that I should use more productive tools for developing. Well I don't want to begin an editor war but, yes, I use emacs. I used to use vim before but the integration of emacs and gdb has caught my attention.
To be clear, as "more productive tools" he understands graphical eye candy tools. My argument to use an "simple editor plus makefiles" was, it just works and thats it. So before to downloading eclipse just to make my boss's eyes happy I've decided to make a little research.
What you guys are using today to develope kenrel code?
Best Regards,
- dhs
--
"Do or do not. There is no try" Yoda Master
-- "Do or do not. There is no try" Yoda Master