Lines Matching refs:framework

55   library/framework developers even use ``__underscored`` names
464   ``conflict``      ``framework``  ``requires``
493 …``explicit``:sub:`opt` ``framework``:sub:`opt` ``module`` *module-id* *attributes*:sub:`opt` '{' *…
500 …framework`` qualifier specifies that this module corresponds to a Darwin-style framework. A Darwin…
504   Name.framework/
505     Modules/module.modulemap  Module map for the framework
506     Headers/                  Subdirectory containing framework headers
507     PrivateHeaders/           Subdirectory containing framework private headers
510     Name                      Symbolic link to the shared library for the framework
719 …framework`` specifier, the enclosing module shall have a ``framework`` specifier; the submodule's …
726 …``explicit``:sub:`opt` ``framework``:sub:`opt` ``module`` '*' *attributes*:sub:`opt` '{' *inferred…
737 * Have the ``framework`` specifier, if the
738   *inferred-submodule-declaration* has the ``framework`` specifier
888 A *link-declaration* specifies a library or framework against which a program should be linked if t…
893     ``link`` ``framework``:sub:`opt` *string-literal*
895 The *string-literal* specifies the name of the library or framework against which the program shoul…
897 …-declaration* with the ``framework`` specifies that the linker should link against the named frame…
1059 When writing a private module as part of a *framework*, it's recommended that:
1061 * Headers for this module are present in the ``PrivateHeaders`` framework
1064   public framework prefixed, like ``Foo_Private`` above. Clang has extra logic