This is usually handled via another setting in the main project. DEFAULT: Acts as either WANT or DONT_WANT based on the group settings for the module or WANT_BY_DEFAULT option to vtk_module_scan if no other preference is specified.DONT_WANT: The module or group should only be built if required (e.g., via a dependency).WANT: The module or group should be built if possible.NO: The module or group must not be built.YES: The module or group must be built.Modules and groups are enable and disable preferences are specified using a 5-way flag setting: DESCRIPTION: (Recommended) Short text describing what the kit contains.Kits are intended to bring together related modules into a single library in order to reduce the number of objects that linkers need to deal with. The vtk.kit file is parsed similarly to vtk.module files. LICENSE_FILES: A list of license files to install for the module.THIRD_PARTY: If present, this module is a third party module.EXCLUDE_WRAP: If present, this module should not be wrapped in any language.By default, the module name is applied as a label. TEST_LABELS: Labels to apply to the tests of this module. TEST_OPTIONAL_DEPENDS: Modules used by the test suite for this module if available.TEST_DEPENDS: Modules required by the test suite for this module.IMPLEMENTS: A list of modules for which this module needs to register with.This does not mean that the module will be enabled, just guaranteed to build before this module. ORDER_DEPENDS: Dependencies which only matter for ordering.OPTIONAL_DEPENDS: A list of modules which are used by this module if enabled these are treated as PRIVATE_DEPENDS if they exist.PRIVATE_DEPENDS: A list of modules which are required by this module, but not by those using this module.DEPENDS: A list of modules which are required by this module and modules using this module.If the expression is false, the module is completely ignored. CONDITION: Arguments to CMake's if command which may be used to hide the module for certain platforms or other reasons.This allows for enabling a set of modules with a single build option. GROUPS: Modules may belong to "groups" which is exposed as a build option.IMPLEMENTABLE: If present, the module contains logic which supports the autoinit functionality.KIT: The name of the kit the module belongs to (see Kits files for more information).DESCRIPTION: (Recommended) Short text describing what the module is for.For example, a NS::Foo module will have a default LIBRARY_NAME of Foo. It defaults to the module name, but any namespaces are removed. LIBRARY_NAME: The base name of the library file.NAME: (Required) The name of the module.More.Īll values are optional unless otherwise noted. More.Įxport find_package calls for dependencies. More.Īdd compile definitions to a module. More.Īdd include directories to a module. More.įind vtk.module files in a set of directories. Find vtk.kit files in a set of directories.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |