Home
Managing change and releases
Learn how to manage change and release in the product.
Guide to building software on Linux and UNIX
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.
Issues in multiple platform development
Several issues arise in an environment where developers create and maintain several platform-specific variants of an application.

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
  - HCL VersionVault build concepts
    HCL VersionVault 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 HCL VersionVault build tools
    Learn how to use VersionVault build tools.
  - Working with DOs and configuration records
    You can perform operations on derived objects and configuration records.
  - clearmake makefiles and BOS files
    The HCL VersionVault 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 HCL VersionVault to build C++ programs
    Use clearmake effectively with C++ programs built with various compilers.
  - Using HCL VersionVault 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.
    - Issues in multiple platform development
      Several issues arise in an environment where developers create and maintain several platform-specific variants of an application.
    - Handling source code differences
      Learn how to handle differences in the source code.
    - Handling build procedure differences
      You can handle differences in the build procedure using the following methods.
    - Segregating the derived objects of different variants
      It is essential to keep derived objects (object modules, executables) built for different architectures separate.
    - Multiple architecture example
      Use this content as an example of multiple-architecture development.
  - Setting up a build on a non-VersionVault host
    There is a technique to create configuration records for a build that involves HCL VersionVault data, but is performed on a non-VersionVault host.
- Guide to building software on Windows

Issues in multiple platform development

Several issues arise in an environment where developers create and maintain several platform-specific variants of an application.

The following issues in multiple platform development are:

Different source code is required for different variants. Different UNIX and Linux operating systems might use different functions to implement the same task (for example, strchr(3) or index(3)). Additionally, it might be necessary to include different header files for different variants (for example, string.h and strings.h).
Different variants and various platforms might have different requirements. The differences might involve such particulars as compiler locations, compiler options, and libraries.
Builds for different variants must be kept separate. Because there is one source tree, care must be taken to ensure that the object modules and executables for one architecture are not confused with those for other architectures. For example, the link editor must not try to create an executable using an object module that was built for another architecture.

Additional issues must be addressed if HCL VersionVault does not run on one of the target platforms. For more information about one such issue, see Setting up a build on a non-VersionVault host.