File: readme.txt

package info (click to toggle)
cccc 1:3.1.4-11
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 3,984 kB
  • sloc: ansic: 33,244; cpp: 10,527; java: 622; makefile: 158; sh: 11
file content (148 lines) | stat: -rw-r--r-- 7,979 bytes parent folder | download | duplicates (6)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
README.TXT for CCCC version 3.1.1
=================================

This is a new version of the program CCCC (C and C++ Code Counter).  This 
program exists to analyze and report measurements on source code in C, C++
and Java.  The languages Ada83 and Ada95, which were supported in previous
versions are presently not supported.
The Internet site for CCCC development is: http://cccc.sourceforge.net 
(hosting kindly donated by sourceforge.net to whom I am grateful).

CCCC is a command line tool, originally implemented for Linux and other 
POSIX-style platforms, but also buildable on the Win32 platform.  
Files to be analyzed are listed (typically on the command line, although 
support does exist for the list of files to be read from standard input.   
The program analyzes the files and generates a one or more reports in HTML 
or XML format on the content.  

This distribution is intended to be a single package containing everything
which is required to compile and install CCCC on either a POSIX or Win32 
platform.  Whereas previous distributions contained only a single directory,
containing the source code of CCCC, this distribution is divided into a 
number of subdirectories, with the following contents:
* A full distribution of the Purdue Compiler Construction Toolset (PCCTS) by
  Terence Parr and others, now maintained by Tom Moog of Polhode Inc. 
  PCCTS is required to compile CCCC: in the past the distribution has relied
  on the existence of a PCCTS package on the compilation platform, while this
  distribution chooses to include it as part of CCCC's own package.
* The source of a new version of CCCC, which I hope will turn out to be more
  efficient, accurate and useful than previous versions, although it is very
  similar in spirit and interface.
* The source of an accessory program called CcccDevStudioAddIn.dll which 
  provides integration between the command line CCCC program and the 
  Microsoft Visual Studio IDE (version 5.0 or 6.0).
* A directory of minimal test cases for the command line CCCC tool.
* Miscellaneous batch files, makefiles and Microsoft Visual Studio workspace 
  and project files to support building, testing and installing the software 
  under POSIX and Win32.

The pccts directory contains software for which I am not the original 
author.  The software has been placed in the public domain, with
the expectation that appropriate credit will be given for use.  

Since version 3.pre63, the recommended way of building the software is by
using the BAT and SH scripts in the top directory of the distribution as
appropriate for your platform.  On Win32, the script build_w32vc.bat 
builds the software with Microsoft Visual C++ version 5 or 6 (locations
within the script may need to be modified according to which you have
and whether it is installed at the default position in the filesystem).
On Linux and similar platforms the shell script build_posixgcc.sh should work. 

As of the current release, version 3.1.1, the reference build tool for the
Win32 platform is the freely distributed Microsoft Visual C++ Toolkit 2003.
As this toolkit does not contain a 'make' style program the script 
build_w32vct2003.bat has been written which automates all parts of the build.

If you wish to try the Visual Studio integration, there are some additional
steps to perform.  Within Visual Studio, select menu option 
"Tools/Customize", then click on the "Macros and AddIns" tab.  Within this 
control, click on the "Browse" button, change the file type from "*.dsm" 
to "*.dll", browse to the directory C:\Program Files\CCCC, and select the
CcccDevStudioAddIn.dll file before pressing "OK".  This should cause 
Visual Studio to load the add-in, and a tool bar should appear with 
four different icons containing the text "C4" and six white icons.  The
fourth of the "C4" icons has a device like a steering wheel on it and is 
used to configure the add-in.  Press this icon and a dialog box should appear
containing 8 strings, of which the first should read 
"C:\Program Files\CCCC\CCCC.EXE" and the next should contain some path to 
Internet Explorer (IEXPLORE.EXE).  Verify that the path to IE is valid 
(or substitute a path to Netscape, Mozilla, Opera or any other HTML browser 
according to your tastes).  

The add-in can now be used to run CCCC on either the current file (the "C4" 
icon with a "f" subscript), all files in the current active project ("C4"
with a "p" subscript), or all files in any project in the current workspace 
("C4" with a "w" subscript).  The add-in can also have up to 6 other commands
set in the configuration dialog defined above, which will be bound to
the six blank icons on the toolbar.  Each command will run in character
mode and standard output from each should be captured and redirected to
the "Macros" tab in the Visual Studio Output window.  This may be useful
for programs which generate messages in the same format as the Visual 
Studio compiler error messages or Find in Files, as conformance to this
format allows Visual Studio to implement the convenient "jump to source
line" behaviour.  I have on my list of issues for CCCC to convert the 
parser syntax error messages to this format, but it hasn't happened yet.
The add-in is experimental at this stage.  I am aware of some issues 
with projects in locations with spaces in the path, and I have also found
that the logic I am using to deduce the home directories of .dsp and .dsw 
files is not always correct.

The add-in requires use of MFC libraries which are not provided as a part 
of Microsoft Visual C++ Toolkit 2003, hence it is not built by the 
build_w32vct2003.bat script, however the add-in should still be buildable 
using Visual C++ or Visual Studio 5.0 or 6.0 (and is any case 
useless to developers who don't have and IDE of this kind).  

As well as the addin, the current version includes a directory which contains
a script to build a wizard-style installer for the program under Win32.
The binary release provides Windows start menu access to a DOS prompt 
set up with an environment to enable CCCC to be run  easily, and also 
provides a shortcut to the HTML documentation. The  installer can be 
built from the supplied scripts using the splendid free Inno Setup 
and Extensions packages by Martijn Laan (Inno Setup) and Jordan
Russell (extensions), available from http://www.jrsoftware.org.

Previous versions of CCCC have been released like PCCTS into the public
domain with no restrictions, other than the pious hope that should anyone
base a derivative work on it I will be given due credit.  The current version 
is released under the GNU Public License.

CCCC was originally developed as a proof-of-concept tool for some ideas 
relating to software metrics which I was investigating as an academic 
research project.  I have now completed the project and been awarded 
my PhD.  

With this release, I am choosing to declare the project in a dormant 
state.  I have no plans to do further releases, either to add new features
or to correct existing defects. I am happy to provide advice to users of 
CCCC via email, and I encourage all users to exercise the rights granted 
them under the GPL to tinker with the code if this helps the software 
to meet their needs better.

I am grateful to a number of people for assistance on this project, including
Terence Parr and his co-workers, and Tom Moog for the development and ongoing
maintenance of the excellent PCCTS tool; my academic supervisor, Dr Thomas
O'Neill; a number of developers who have contributed source patches; and
many people who have mailed me with constructive suggestions or merely to 
confirm that they were using the tool. Feedback on the value or otherwise 
of CCCC will always be welcome.


Tim Littlefair (tim_littlefair@hotmail.com)
updated January 2005
--------------

This and past distributions of CCCC and related tools should be
available for the forseeable future from http://cccc.sourceforge.net