Lines Matching full:plugin

7 run a Clang Plugin.
15 simple clang plugin.
21 handle plugin command line options. The ``PluginASTAction`` base class declares
22 a ``ParseArgs`` method which you have to implement in your plugin.
36 Registering a plugin
39 A plugin is loaded from a dynamic library at runtime by the compiler. To
40 register a plugin in a library, use ``FrontendPluginRegistry::Add<>``:
44   static FrontendPluginRegistry::Add<MyPlugin> X("my-plugin-name", "my plugin description");
88 The members of ``ParsedAttrInfo`` that a plugin attribute must define are:
113 To see a working example of an attribute plugin, see `the Attribute.cpp example
119 Let's look at an example plugin that prints top-level function names.  This
124 Running the plugin
131 The Clang driver accepts the `-fplugin` option to load a plugin.
133 line via the `fplugin-arg-<plugin name>-<argument>` option. Using this
134 method, the plugin name cannot contain dashes itself, but the argument
135 passed to the plugin can.
146 If your plugin name contains dashes, either rename the plugin or used the
153 To run a plugin, the dynamic library containing the plugin registry must be
156 `-plugin` option. Additional parameters for the plugins can be passed with
157 `-plugin-arg-<plugin-name>`.
169 For example, to run the ``print-function-names`` plugin over a source file in
170 clang, first build the plugin, and then call clang with the plugin from the
182             -plugin -Xclang print-fns
184 Also see the print-function-name plugin example's
191 Using `-fplugin=plugin` on the clang command line passes the plugin
192 through as an argument to `-load` on the cc1 command line. If the plugin
193 class implements the ``getActionType`` method then the plugin is run
194 automatically. For example, to run the plugin automatically after the main AST
195 action (i.e. the same as using `-add-plugin`):
199   // Automatically run the plugin after the main AST action