rMake

Some reasons to use rMake include the following:

• Consistent Build Environment: rMake provides developers with assurance about what software is installed in the build environment used to develop packages and groups. Without this assurance, a developer using local build environments may have certain libraries, for example, installed on one build machine and not on another, resulting in different builds from each.
• Build Against Specified Group: rMake can ensure that developers are using the correct versions of a set of packages or group. For example, rMake can help a developer wanting to build specifically against version 1.0 of an appliance.
• Build and Test Binaries Before Committing Source: rMake lets developers build and test a binary before committing the source. This includes the option to build a set of binaries to ensure they work together before committing any of them.
• Package Order Handling: rMake will build multiple packages in the appropriate order according to their dependencies upon each other.

rMake Reference

• rMake Architecture
• rMake Basic Workflow
• rMake Quick Reference Page
• rMake commands
• rMake and RPM
• Appliance Building with rMake

Getting Started with rMake

Use the following links as a reference for getting started with a rMake-based system:

• Installing and Configuring rMake
• Building Software with rMake
• rMake Build Considerations
• Application to Appliance: A Hands-on Guide

Package Software

Users can package software to take advantage of Conary and rMake features. Use the following links to find instructions and reference for Conary packaging:

• Conary Packaging, including instructions and reference for:
  • Setting up a build environment
  • Recipe writing