A proposal for CMT tag unification

Nomenclature

We can split architecture related CMT tags into two categories

• Host tags: these are tags that CMT will find by itself, these tags should always appear no matter if one executes CMT inside a project environment or not. Examples are: Darwin, Linux, gcc345, slc45, …
• Target tags: These are tags we want to compile our software for. The most important one is the string set to the CMTCONFIG environment variable. From this string we usually derive other tags, such as slc4-ia32, gcc34, optimized, …

Our current situation

We are using at the moment two different sets of tags, i.e. the “LCG/AA and LHCb” tags and the “Atlas” tags which have the same meaning, e.g. slc4_ia32_gcc34 == i686-slc4-gcc34-opt In LCGCMT/LCG_Settings where all tag information is stored we are currently using in several cases the same tag name for a “host tag” and for a “target tag”. E.g. we are deriving gcc34 both from slc4_ia32_gcc34 and from gcc345.

The goal is to

• unify the tag names, i.e. to use only one set of tags
• clear up the inconsistencies with derived tags used in the “host” and “target” context.

A proposal for change

Concerning point 1 of the goals the proposal is to use the “Atlas” versions of tags because

Advantages of this proposal

Compatibility layer

-- StefanRoiser - 03 Oct 2008