Have a shell account on the CVS server. 2. Create a publicprivate key pair on the client.
7.1.1 Getting Started with Indent
The indent program may be used as a command or as a pipe. In the command mode, the program has a general format as shown below: indent [options] [input filename] [-o output filename] The following two lines show the simplest use of the indent program. It takes hello.c as input file and creates hello.c as output file and hello.c~ as backup file. [rootboota indent] indent hello.c [rootboota indent] If you want to create an output file with a different name without modifying the original file, you can use the –o option with indent. When multiple input files are specified, indent reformats each file and creates a backup file for each input file. Wild card characters can also be used with indent so that you can indent all C source code files with the “ indent .c” command. The output of another command can also be piped into the indent command. The fol- lowing command does the same thing as indent hello.c but writes the output on STDOUT instead of writing it to a file. cat hello.c | indent 206 Chapter 7 • Miscellaneous Tools This is sometimes useful if you just want to test the behavior of indent without modify- ing a file. The most efficient use of indent is through a shell script that goes into each directory of the source code tree and indents each and every file in the project. You may also create a rule in the makefile of a project to indent all files in one or all directories. A typical makefile rule may look like the following: indent: indent .c indent .cpp indent .h In the case of a project with multiple subdirectories, you can have a more sophisticated rule. Taking an example from Chapter 4, where we have four subdirectories, you can use the fol- lowing rule to go into each directory and indent all C source code files. SUBDIRS = COMDIR FTPDIR TFTPDIR DNSDIR indent: for i in SUBDIRS ; do \ cd i ; indent .c ; \ done Keep in mind that after indenting all of the files, you may have to build the whole project because source code files have been modified. In big projects this process may take a while. Indent uses a configuration file called .indent.pro, which should be present in the current directory or in your home directory. You can use this file to set options that you always use. If the file is present in the current directory, it is used instead of the file in the home direc- tory of the user. By creating a different .indent.pro file in different directories of a project, you can apply different indentation rules in different directories. This is especially useful when a project uses multiple languages. For example, indentation rules may be different for C, C++ and assembly language files.7.1.2 Selecting Coding Styles
Different coding styles are in use by programmers. Some common styles are defined in indent program and these may be invoked by a single option at the command line. The most common style of coding in the open source is the GNU style. This style can be applied using – gnu option at the command line. Options, which are used with the GNU style, are listed below: -nbad -bap -nbc -bbo -bl -bli2Parts
» the linux development platform 2003
» Requirement Gathering Life Cycle of a Software Development Project
» Writing Functional Specifications Life Cycle of a Software Development Project
» Creating Architecture and Design Documents
» Implementation and Coding Life Cycle of a Software Development Project
» Testing Life Cycle of a Software Development Project
» Technical documentation developed during the development process. This includes
» Technical documentation prepared for technical support staff. This includes technical
» End-user manuals and guides. This is the documentation for the end user to assist the
» Software Releases Support and New Features
» Hardware Platform Components of a Development System
» Operating System Components of a Development System
» Editors Components of a Development System
» Compilers and Assemblers Components of a Development System
» Debuggers Components of a Development System
» Version Control Systems Components of a Development System
» Selection Criteria for Hardware Platform Selection Criteria for Software Development Tools
» Creating Deadlines Managing Development Process
» Managing the Development Team
» Resolving Dependencies Managing Development Process
» Libraries Linux Development Platform Specifications LDPS and Linux
» Open Source Developers Network at http:www.osdn.org
» Extensibility What to Look for in an Editor
» References and Resources the linux development platform 2003
» Target machine. This is the machine for which the newly built compiler will generate
» Post-Installation Tasks Installing GNU Compiler
» Compiling to Intermediate Levels
» Compilation with Debug Support
» Compilation with Optimization Compiling a Program
» Compiling Source Code for Other Languages
» Linking a program Assembling a Program
» Creating Libraries the linux development platform 2003
» Standard Libraries the linux development platform 2003
» Compiling Fortran Programs the linux development platform 2003
» Smalltalk Oberon Other Compilers
» The target 2. Dependencies Basic Terminology
» The explicit rules 2. The implicit rules
» Input Files Introduction to GNU make
» Typical Contents of a Makefile
» Running make Introduction to GNU make
» Shell to Execute Commands Include Files
» The ftp server The The dnsresolver
» FTPOBJS OBJS Another Example of Makefile
» Explicit Rules The make Rules
» Implicit Rules The make Rules
» Defining Variables Types of Variables
» Pre-Defined Variables Automatic Variables
» Makefile in The Top Directory
» Makefile in common-dir Directory
» Makefile in the ftp-dir Directory
» Makefile in the tftp-dir Directory Makefile in the dns-dir Directory
» Building Everything Working with Multiple Makefiles and Directories
» The ifdef Directive Control Structures and Directives
» The ifndef Directive Control Structures and Directives
» Compilation Getting the Latest Version and Installation
» Most Commonly Used gdb Commands
» Passing Command Line Arguments to the Program Being Debugged
» The step and finish Commands
» Introduction to GDB Working with the Stack
» Displaying Program Variables Displaying Variables
» Automatic Displaying Variables with Each Command
» Displaying Environment Variables Displaying Variables
» Modifying Variables Displaying Variables
» Disabling Break Points Enabling Break Points
» Debugging Optimized Code the linux development platform 2003
» Debugging Running Processes the linux development platform 2003
» The kdbg Debugger Other Open Source Debuggers
» The ddd Debugger Other Open Source Debuggers
» The xxgdb Debugger Other Open Source Debuggers
» CVS Policies the linux development platform 2003
» Project Management and Communication
» Remote Repositories Checking out a Project
» Finding the Status of a Project
» Finding Differences Using the CVS Client
» Resolving Conflicts Using the CVS Client
» Checking the Project Back In Adding Files to a Project
» Removing Files from a Project
» Tags and Releases Using the CVS Client
» System Requirements Introduction to jCVS
» Installation Instructions Introduction to jCVS
» Using jCVS Introduction to jCVS
» Installing pcl-cvs Using Emacs with CVS
» Using pcl-cvs Using Emacs with CVS
» Have a shell account on the CVS server. 2. Create a publicprivate key pair on the client.
» Selecting Coding Styles Using indent Utility
» Formatting Braces Using indent Utility
» Formatting Declarations Using indent Utility
» Breaking Long Lines Using indent Utility
» Summary of Options Using indent Utility
» Using sed Utility Using cscope and cbrowser
» Generating C Function Prototypes from C Source Code Using cproto
» Using ltrace and strace Utilities
» Value 2. Type Name Using the nm Utility
» Using the ranlib Utility Using the strip Utility
» Using the strings Utility Using the addr2line Utility
» Host Machine Introduction to the Cross-Platform Development Process
» Target Machine Introduction to the Cross-Platform Development Process
» Cross Platform Development Cycle
» Embedded Systems and Moving Parts
» Embedded Systems and Power Consumption
» Embedded Operating Systems What are Embedded Systems?
» Knowledge of Target System Hardware
» Software Emulators Cross Compilations
» Using gdbserver with GNU Debugger
» Attaching to a Running Process Using gdbserver
» Arcom SBC-GX1 Board Hardware Used for Cross-Platform and Embedded Systems
» Artesyn PMPPC Mezzanine Card
» References the linux development platform 2003
» Java Compiler Java Virtual Machine
» Kaffe the linux development platform 2003
» The Jboss Java Development System
» Getting and Installing Java SDK from Sun Creating jar Files
» Creating Source Code File Compiling Java Code
» Running Java Applications Building Java Applications
» Using gcj to Build Java Applications
» Building Applets the linux development platform 2003
» Testing Applets with Netscape
» Jikes for Java the linux development platform 2003
Show more