Slashdot Mirror

← Back to Stories (view on slashdot.org)

Visualising Code Structure in Large Projects?

Posted by Cliff on from the 100k-LOC dept.

TheMaccLads asks: "I've recently joined a new C++ project, and it's in a terrible state. There are 100-odd source directories, dozens of libraries, and a couple of dozen executables and DLLs. Some executables pull in (i.e. compile themselves) the occasional source file from a library, instead of using the libraries. My job is to port a subset to unix, but I need a tool to visualise all the relationships between directories, projects, libraries, and so on, because my brain will overheat soon otherwise. Preferably a tool that will do it by parsing the MS Dev studio projects and workspaces, but if I have to write it myself in Perl, I will! Anyone know of any tools? Or suggest an approach?"

4 of 47 comments (clear)

  1. Sounds rough by Anonymous Coward · · Score: 1, Interesting

    Use visio.

    Rational may have some software as well...

    Visio's definitely the way to go, though.

    1. Re:Sounds rough by Anonymous Coward · · Score: 1, Interesting

      Since when did visio parse MSVC project files?

    2. Re:Sounds rough by Anonymous Coward · · Score: 1, Interesting

      .dsp files are nothing more than a collection of compiler flags, there's no magic about them in regards to understanding the structure of the program.

  2. snavigator by Anonymous Coward · · Score: 1, Interesting

    Source Navigator. Free since red hat bought out cygnus.

    rpm's for most distros.

    Great tool for what you're talking about. I'm just surprise no one else mentioned it.

    -Jay