CatalystThe Gentoo catalyst project develops and supports the catalyst release building tool. The design of catalyst is meant to be easy to use, cutomize, and maintain. It is also used in other Gentoo projects, such as GNAP. The catalyst FAQ attempts to answer commonly asked questions related to catalyst and its usage. The goal of the catalyst project is to provide a single multi-faceted tool that can reliably build all aspects of a Gentoo Linux release: stage tarballs, GRP package sets, and install CDs. Our specific development goals for catalyst include the following: ensuring it provides high-quality builds of Gentoo Linux, and for the tool to be easy to use, customize, extend and maintain. The catalyst tool is intended to be used by those who wish to create their own customized versions of Gentoo Linux, or their own customized LiveCDs. Our goal is to make catalyst a powerful tool that's a pleasure to use, and to ensure that the code we write is maintainable and of high-quality.
All developers can be reached by e-mail using nickname@gentoo.org. Catalyst supports a number of architectures. In catalyst-speak, an "architecture" is a general type of CPU platform. Here is a complete list of architectures supported by catalyst:
For each architecture, catalyst supports a number of "sub-architectures." A sub-architecture is a specific variant of the architecture. For example, pentium4 is a sub-architecture of the x86 architecture. Here is a list of all sub-architectures supported by catalyst:
You'll notice that all architectures have a sub-architecture with the same name as the architecture. This sub-architecture is meant to represent a "generic" build that should work on all systems in that architecture.Each sub-architecture has an associated set of CFLAGS, CXXFLAGS, as well as a CHOST and set of USE variables that are enabled on that sub-architecture. The USE settings are intended to enable any CPU-specific options, such as mmx or altivec.
|
|
