SciTools Blog » Uncategorized

CMake and Understand

KevinG — Tue, 03 Apr 2012 23:01:51 +0000

If your team uses cmake to build your projects, you can use it to generate your Understand project. It will add all of the files, setup the correct macro definitions for each file, and setup the correct include files for each file in the project. The advantage of creating an Understand project like this is that the project will be much more accurate than can be created by hand, allowing you to have easier access to all the features of our new strict parser.

In order to use this,

Navigate to your build directory
Edit CMakeCache.txt and set CMAKE_EXPORT_COMPILE_COMMANDS to ON.
Run make again, you’ll see a file called compile_commands.json in your build directory.
To import into an understand project run the following from the command line (skip the red part for existing projects):
und -db path/to/db.udb create -languages C++ add path/to/build/dir/compile_commands.json settings -c++AddFoundFilesToProject on analyze

Structure 101 adds support for Understand

KevinG — Fri, 09 Mar 2012 22:30:10 +0000

Structure101 has several great tools for analyzing and refactoring your code base, and they have just finished adding the ability to import Understand projects into their tools. You should definitely check it out.

As an extra incentive, they are offering a free license to the first 3 Understand users who demo one of their tools and send an exported image such as the one below of any part of their code or an Open Source project. Just send it to hwsupport@headwaysoftware.com and tell them Kevin sent you

To be fair to another great partner, Lattix can also import your Understand projects and is a great tool for organizing and refactoring your code, so give them a look.

Running CodeCheck from the Command Line

heidi — Wed, 11 Jan 2012 20:47:19 +0000

CodeCheck can be set up to run from the command line using Und if that is your preferred work environment, or if you are looking to automate the task. To see all of the options available in Und, run und help. For specific documentation on each option run und help optionName.

To run CodeCheck from the command line, first you will need to export the CodeCheck configuration file from the Understand GUI that has the checks you wish to run selected.

Once that is saved to a file, the command line option is

und codecheck C:\path\to\configuration.ini C:\path\to\OutputDir

Where configuration.ini is my saved configuration file and the results are saved to the OutputDir.

Understand on Facebook – Become a fan

KevinG — Wed, 02 Sep 2009 16:32:26 +0000

Help us prove that not all programmers are anti-social, join our Facebook Fan page!

Understand on Facebook

.NET API for Understand

KevinG — Wed, 02 Sep 2009 00:26:11 +0000

One of our users, Chris Johnson, has developed a .NET sdk wrapper for the Understand API.

I have written a .NET sdk wrapper around the understand API during the early spring and last fall. I wrote it because I didn’t want to use Perl anymore, and I wanted the strong type safety of .NET along with it’s wonderful debugging tools.
The API is written in managed C++ (i.e. C++/CLI), and once compiled, can be accessed by any programming language that targets the .NET framework.

More details at http://www.scitools.com/support/forum/viewtopic.php?p=5550

Thanks, Chris!

CVS commands in Understand

KevinG — Fri, 12 Jun 2009 04:05:00 +0000

Several users have asked for a CVS user tool similar to the one Ken created for SVN

This is easy to do, and you can create your own User Tools to do many different things.

I went and bundled some CVS commands into a User Tool. Just import it via the Tools | Configure User Tools | Import button.

Download CVS User Tool

I haven’t used CVS in years, so let me know if I got anything wrong

Totally Personal Posting

ken — Wed, 16 Jul 2008 21:40:21 +0000

Some of you may have noticed that the quality and timelyness of our support has improved this week. That is because I’m not there bugging everybody. My son and I are fishing on a lake in upstate New York. Here I am with a 4 lb largemouth bass. Normally I throw them back, but this one seemed just right to feed us this evening. And it was tasty. The trip is almost over, so support will return to its slower lower quality form on Monday.

Understand 2.0 – SDI, MDI, Any DI – Part II: Document Windows

ken — Tue, 08 Apr 2008 10:41:18 +0000

In Part I I described how in Understand 2.0 we are attempting to have not SDI, or MDI, but “Any DI” – where you can put windows where you want and have them stay that way. I described how you can move dock and information windows around in the GUI and anywhere on your monitor(s). In this segment I’ll cover document windows (editor and graph windows).

Here is Understand 2.0 with a couple tabbed editor documents and a tabbed graph:

By default these live in tabs. However, you can “release” any document window out of the tabbed workspace by right clicking on its tab and choosing “Release Window”:

and it floats out of the tabbed workspace where you can put it anywhere you want:

Editor windows work similarly but they also have a mode that toggles new editors to be in our out of the tabbed document workspace. Set this in the Window menu:

If I choose “SDI” Window, then future editors will be created outside the MDI frame:

Finally, how do I put a “Released” window back into the dock? I wish this was a bit more obvious, but here we are for the moment constrained by Qt and portability among all the different platforms we support. Since we couldn’t put a “capture” button next to the close, iconize and kill buttons – we added a dimple menu in the upper right of the window document itself. Just choose it and Capture the window back into the tabbed workspace: