Ports Search

This is quite a simple library that provides an easy interface to the common gateway interface, known as CGI. The purpose is to provide an easy to use interface to CGI if you need to write your program in C instead of perl.

nose provides an alternate test discovery and running process for unittest, one that is intended to mimic the behavior of py.test as much as is reasonably possible without resorting to magic. By default, nose will run tests in files or directories under the current working directory whose names include "test". nose also supports doctest tests and may optionally provide a test coverage report.

CppTest is a portable and powerful, yet simple, unit testing framework for handling automated tests in C++. The focus lies on usability and extendability. Several output formats, including simple text output, compiler-like output and HTML, are supported and new ones are easily added.

CppUTest is a C /C++ based unit xUnit test framework for unit testing and for test-driving your code. It is written in C++ but is used in C and C++ projects and frequently used in embedded systems. CppUTest's core design principles: * Simple to use and small * Portable to old and new platforms * Build with Test-driven Development in mind

This port of SCO / USL's 'cscope' lets one easily navigate large C programs. It's designed to answer questions like where symbols are defined and used, where variables are assigned, and much more. The Santa Cruz Operation (SCO) has made this available under a very friendly, BSD-style Open Source License.

CSSC is the GNU Project's replacement for SCCS. SCCS is a proprietary suite of tools which is provided with most commercial versions of Unix. The purpose behind CSSC is to provide a work-alike for SCCS which can be used on the various Free versions of Unix. SCCS was the only major form of source code control on Unix platforms for many years, until RCS came along. SCCS was an effective method for small projects, but these days it is less popular, particularly for projects involving large numbers of files. A certain amount of old software is still in SCCS form, and CSSC is designed to retrieve that software. Once retrieved, it is recommended to bring the source under the control of a more modern source code control system, such as git or Apache Subversion. However, SCCS (and CSSC) is still perfectly adequate for small projects. For example, if you are familiar with SCCS, it is not unreasonable to control the files in /etc and /usr/local/etc on your private FreeBSD machine with CSSC.

cvsdelta summarizes the difference between a CVS project and its local version. It detects files that have been added and removed, and of existing files it counts the number of lines that have been added, deleted, and changed. It filters project changes by using .cvsignore files, both system-wide and locally. Requires ruby.

cvslines extends the capability of the cvs commit command, to provide extra support in managing multiple concurrent lines of development. cvslines is a "wrapper" facility that helps out with merging changes between various cvs branches, where the branches represent different lines of development.

CxxTest is a JUnit/CppUnit/xUnit-like framework for C++. Its advantages over existing alternatives are that it: - Doesn't require RTTI - Doesn't require member template functions - Doesn't require exception handling - Doesn't require any external libraries (including memory management, file/console I/O, graphics libraries) This makes it extremely portable and usable.

Cflow reads files as C program source and attempts to print a graph of the program's function call hierarchy to the standard output. Called functions are indented with respect to their calling functions, and printed only once, in the order they occur. This is version 2.0.