At this point, I'm assuming that most people who actively develop the source code use some sort of IDE to sift through the source files (poking through each file individually is inefficient and often leads to fruitless searches).
Is there a particular IDE that works well for keeping the source organized? Or would something like Code::Blocks work fine (just so long as I tell it to use the existing Makefile)?
A better way to sift through the source
Moderator: Board moderators
-
SilverNexus
- Junior member
- Posts: 165
- Joined: Mon Jun 25, 2012 5:33 pm
- Location: Planet Earth
A better way to sift through the source
That SilverNexus guy? You needn't worry about him.
He is level negative 4 in oratory, and his singing is worse.
He is level negative 4 in oratory, and his singing is worse.
I've not used an IDE, but cscope can be very useful:
http://cscope.sourceforge.net/
It can be really useful when making some change that hits a lot of files (change return value or number of parameters to a function). While a lot of that can be done with grep, cscope is aware of the language so knows the different of FLAG_FOO vs FLAG_FOO_BAR, which can be harder to control with things like grep.
So not really an IDE, but is a nice way to sift through source.
http://cscope.sourceforge.net/
It can be really useful when making some change that hits a lot of files (change return value or number of parameters to a function). While a lot of that can be done with grep, cscope is aware of the language so knows the different of FLAG_FOO vs FLAG_FOO_BAR, which can be harder to control with things like grep.
So not really an IDE, but is a nice way to sift through source.
-
SilverNexus
- Junior member
- Posts: 165
- Joined: Mon Jun 25, 2012 5:33 pm
- Location: Planet Earth