@@ -171,6 +171,7 @@ C library, C++ support, largefile suppor
IPv6 support, wchar support, or dynamic library support. Some packages
can only be built on certain target architectures, or if an MMU is
available in the processor.
These dependencies have to expressed with the appropriate 'depends on'
statements in the Config.in file. Additionally, for dependencies on
toolchain options, a +comment+ should be displayed when the option is
@@ -180,6 +181,14 @@ made visible in a comment: since it is u
freely choose another target, it makes little sense to show these
+The +comment+ should only be visible if the +config+ option itself would
+be visible when the toolchain option dependencies are met. This means
+that all other dependencies of the package (including dependencies on
+target architecture and MMU support) have to be repeated on the
++comment+ definition. To keep it clear, the +depends on+ statement for
+these non-toolchain option should be kept separate from the +depends on+
+statement for the toolchain options.
The general format of a dependency +comment+ for package foo is:
foo needs a toolchain w/ featA, featB, featC