Documentation

Create a package description with all configurations resolved.

This function takes a GenericPackageDescription and several environment parameters and tries to generate PackageDescription by finding a flag assignment that result in satisfiable dependencies.

It takes as inputs a not necessarily complete specifications of flags assignments, an optional package index as well as platform parameters. If some flags are not assigned explicitly, this function will try to pick an assignment that causes this function to succeed. The package index is optional since on some platforms we cannot determine which packages have been installed before. When no package index is supplied, every dependency is assumed to be satisfiable, therefore all not explicitly assigned flags will get their default values.

This function will fail if it cannot find a flag assignment that leads to satisfiable dependencies. (It will not try alternative assignments for explicitly specified flags.) In case of failure it will return the missing dependencies that it encountered when trying different flag assignments. On success, it will return the package description and the full flag assignment chosen.

Flatten a generic package description by ignoring all conditions and just join the field descriptors into on package description. Note, however, that this may lead to inconsistent field values, since all values are joined into one field, which may not be possible in the original package description, due to the use of exclusive choices (if ... else ...).

TODO: One particularly tricky case is defaulting. In the original package description, e.g., the source directory might either be the default or a certain, explicitly set path. Since defaults are filled in only after the package has been resolved and when no explicit value has been set, the default path will be missing from the package description returned by this function.

Parse a configuration condition from a string.

Extract buildable condition from a cond tree.

Background: If the conditions in a cond tree lead to Buildable being set to False, then none of the dependencies for this cond tree should actually be taken into account. On the other hand, some of the flags may only be decided in the solver, so we cannot necessarily make the decision whether a component is Buildable or not prior to solving.

What we are doing here is to partially evaluate a condition tree in order to extract the condition under which Buildable is True. The predicate determines whether data under a CondTree is buildable.

Transforms a CondTree by putting the input under the "then" branch of a conditional that is True when Buildable is True. If addBuildableCondition can determine that Buildable is always True, it returns the input unchanged. If Buildable is always False, it returns the empty CondTree.