Jump to main content

Product Documentation

Customer Support Software Academy Community Forums

DevOps Code ClearCase version 11.0.0

Overview
Installing
Upgrading and migrating
Administering
Developing
Managing change and releases
Integrating
Tutorials
Extending product function
Reference
Glossary

Home
Managing change and releases
Learn how to manage change and release in the product.
Guide to building software on Linux and UNIX
Pointers on using DevOps Code ClearCase® build tools
Learn how to use ClearCase® build tools.

Managing change and releases
Learn how to manage change and release in the product.
- Managing software projects
- Workflow for creating projects
- Workflow for making baselines
- Workflow for recommending baselines
- Guide to building software on Linux and UNIX
  - DevOps Code ClearCase® build concepts
    DevOps Code ClearCase® supports makefile based building of software systems and provides a software build environment closely resembling that of the make program.
  - Derived objects and configuration records
    Learn about derived objects and configuration records.
  - Pointers on using DevOps Code ClearCase® build tools
    Learn how to use ClearCase® build tools.
    - Running clearmake
      You can run clearmake from the command line or from the ClearCase® File Browser (xclearcase).
    - A simple clearmake build scenario
      clearmake is designed to let developers in makefile-based build environments continue working in their accustomed manner.
    - Accommodating build avoidance
      Learn about clearmake build avoidance.
    - Declaring source dependencies in makefiles
      To implement build avoidance based on time stamps, standard make variants require you to declare all the source file dependencies of each build target.
    - Build-order dependencies
      In addition to source dependencies, makefiles also contain build-order dependencies.
    - Problems with forced builds
      Understand the problems with forced builds.
    - How clearmake interprets double-colon rules
      Double-colon rules are a special kind of makefile construct that allows several independent rules for one target, each with a possibly different build script.
    - Continuing to work during a build
      As your build progresses, other developers continue to work on their files and might check in new versions of elements that your build uses.
    - Using config spec time rules
      If you use a UCM view, your config spec is generated by DevOps Code ClearCase®. Do not add time rules to your config spec.
    - Build sessions, subsessions, and hierarchical builds
      Learn about DevOps Code ClearCase® build auditing.
    - Build auditing and background processes
      If some conditions are met, DevOps Code ClearCase® build programs audit background processes correctly.
    - Working with incremental update tools
      The design of the build auditing capability makes it ideal for use with tools that build derived objects from scratch.
    - Adding a version string or time stamp to an executable
      You can incorporate a version string and/or time stamp into a C-language compiled executable using simple techniques.
  - Working with DOs and configuration records
    You can perform operations on derived objects and configuration records.
  - clearmake makefiles and BOS files
    The DevOps Code ClearCase® build program, clearmake can process makefiles.
  - Using clearmake compatibility modes
    clearmake is designed for compatibility with existing make programs, which minimizes the changes you need to make to your makefiles.
  - Using DevOps Code ClearCase® to build C++ programs
    Use clearmake effectively with C++ programs built with various compilers.
  - Using DevOps Code ClearCase® build tools with Java
    The build behavior of Java tools causes various problems for clearmake. Understand the problems and some possible solutions to resolve them.
  - Setting up a parallel build
    Learn the process to set up and run builds that use several hosts in the local area network.
  - Building software for multiple platforms
    Learn how to address the challenge of using a single source tree to develop an application for a variety of hardware and software platforms.
  - Setting up a build on a non-ClearCase® host
    There is a technique to create configuration records for a build that involves DevOps Code ClearCase® data, but is performed on a non-ClearCase host.
- Guide to building software on Windows

Pointers on using DevOps Code ClearCase build tools

Learn how to use ClearCase® build tools.

Presenting some pointers on making the best use of clearmake.

Running clearmake
You can run clearmake from the command line or from the ClearCase File Browser (xclearcase).
A simple clearmake build scenario
clearmake is designed to let developers in makefile-based build environments continue working in their accustomed manner.
Accommodating build avoidance
Learn about clearmake build avoidance.
Declaring source dependencies in makefiles
To implement build avoidance based on time stamps, standard make variants require you to declare all the source file dependencies of each build target.
Build-order dependencies
In addition to source dependencies, makefiles also contain build-order dependencies.
Problems with forced builds
Understand the problems with forced builds.
How clearmake interprets double-colon rules
Double-colon rules are a special kind of makefile construct that allows several independent rules for one target, each with a possibly different build script.
Continuing to work during a build
As your build progresses, other developers continue to work on their files and might check in new versions of elements that your build uses.
Using config spec time rules
If you use a UCM view, your config spec is generated by DevOps Code ClearCase. Do not add time rules to your config spec.
Build sessions, subsessions, and hierarchical builds
Learn about DevOps Code ClearCase build auditing.
Build auditing and background processes
If some conditions are met, DevOps Code ClearCase build programs audit background processes correctly.
Working with incremental update tools
The design of the build auditing capability makes it ideal for use with tools that build derived objects from scratch.
Adding a version string or time stamp to an executable
You can incorporate a version string and/or time stamp into a C-language compiled executable using simple techniques.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Share: Email
Twitter

Disclaimer
Privacy
Terms of use
Cookie Preferences