ccbuild - A strict developer's build utility - Problem solving with ccbuild

[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ A ] [ B ] [ next ]

# `ccbuild` - A strict developer's build utility
Chapter 6 - Problem solving with ccbuild

This is a collection of possible real usage examples for `ccbuild`. If you don't want to take the time to read the manual pages, this is a more problem oriented listing of the same.

## 6.1 You changed a class interface

When you change a class interface, a large collection of your code will probably break down. But which parts? Well, a hint of which files will be affected can be seen using `ccbuild` `check`. However, this won't show you whether these sources still compile or not. The only way to test that is by simply running `ccbuild`.

Solution: Use an editor running in the background (something that returns after using the command). An example is using the gedit command when you already have a window open: new files will be opened in a tab and the gedit command will return immediately. So, using gedit, the easiest way to get an overview of your problems would be: `ccbuild` --brute --xof "gedit"

[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ A ] [ B ] [ next ]

`ccbuild` - A strict developer's build utility