TwistedMetalGear
2[H]4U
- Joined
- Jun 19, 2005
- Messages
- 2,199
So at work I maintain and fix bugs on a huge library of code for various backend services. The amount of files is ridiculous and the header files are spread out over 300+ directories.
Now the code is grouped under a logical directory structure but the header files are located across 300+ directories.
Typically we work on a small amount of files usually located in a single folder. Each "group" of code has its own make file and pulls from the appropriate sources of course.
I thought that instead of using vi and grepping for references across countless files, I could maybe use something like VC++ 2010 so that I would have access to a call hierarchy and other quick-referencing features.
So I set up the project, copied all of the code over, included it in the project... Then I had to set up the include path. Something like 300-400 folders of header files. I included them all and got rid of *most* of the invalid references.
The problem is that every time I edit/save a file, it seems to re-parse everything and go into a "scanning #includes" thing across 40,000 files. CPU spikes to 80-100% and this goes on for 15+ minutes. During this time none of the features work. No syntax highlighting, no intelli-sense, etc... I can still edit files but I have none of the features that I wanted to begin with.
Am I stuck with using vi because this project is too complex for an IDE to handle?
Now the code is grouped under a logical directory structure but the header files are located across 300+ directories.
Typically we work on a small amount of files usually located in a single folder. Each "group" of code has its own make file and pulls from the appropriate sources of course.
I thought that instead of using vi and grepping for references across countless files, I could maybe use something like VC++ 2010 so that I would have access to a call hierarchy and other quick-referencing features.
So I set up the project, copied all of the code over, included it in the project... Then I had to set up the include path. Something like 300-400 folders of header files. I included them all and got rid of *most* of the invalid references.
The problem is that every time I edit/save a file, it seems to re-parse everything and go into a "scanning #includes" thing across 40,000 files. CPU spikes to 80-100% and this goes on for 15+ minutes. During this time none of the features work. No syntax highlighting, no intelli-sense, etc... I can still edit files but I have none of the features that I wanted to begin with.
Am I stuck with using vi because this project is too complex for an IDE to handle?