Searched full:plugins (Results 1 – 25 of 710) sorted by relevance
12345678910>>...29
3 Lws now offers apis to manage your own user plugins with `LWS_WITH_PLUGINS_API`.4 Lws uses these apis internally for protocol plugins and event loop plugins12 Lws plugins have a single exported struct with a specified header and a user38 `_class` is shared by your plugins and used to select them from other kinds40 `"myapp xxx plugin"` or whatever shared by all plugins of that class.60 ## Building your own plugins62 Plugins are built standalone, cmake is recommended but you can do what you want.79 ## Bringing in plugins at runtime81 Lws provides an api to import plugins into the process space and another to82 remove and destroy plugins.[all …]
34 **--enable-plugins** and/or define **UCONFIG_ENABLE_PLUGINS=1** to enable the42 The ICU plugin mechanism allows small code modules, called plugins, to be loaded48 attempt to load plugins found in the list. plugins are called and can50 service objects. At u_cleanup time, plugins have the opportunity to57 Some sample plugins are available at:132 Plugins are categorized as "high" or "low" level. Low level are those133 which must be run BEFORE high level plugins, and before any operations137 At load time, ICU first queries all plugins to determine their level,138 then loads all 'low' plugins first, and then loads all 'high' plugins.139 Plugins are otherwise loaded in the order listed in the configuration file.[all …]
34 # Either build the plugins as separate dynamic libs (LWS_WITH_PLUGINS)77 INSTALL_DATADIR="${CMAKE_INSTALL_PREFIX}/plugins"89 list(APPEND LWS_LIB_BUILD_INC_PATHS ../plugins/${PLUGIN_INCLUDE})95 list(APPEND SOURCES ../plugins/${A})101 list(APPEND SOURCES ../plugins/${A})107 list(APPEND SOURCES ../plugins/${A})207 include_directories("${PROJECT_SOURCE_DIR}/plugins/ssh-base/include")223 # plugins229 DESTINATION share/libwebsockets-test-server/plugins230 COMPONENT plugins)[all …]
91 <plugins>111 </plugins>113 <plugins>115 <groupId>org.apache.maven.plugins</groupId>126 <groupId>org.apache.maven.plugins</groupId>139 <groupId>org.apache.maven.plugins</groupId>152 <groupId>org.apache.maven.plugins</groupId>160 <groupId>org.apache.maven.plugins</groupId>170 <groupId>org.sonatype.plugins</groupId>181 </plugins>[all …]
60 <plugins>71 <groupId>org.apache.maven.plugins</groupId>84 <groupId>org.apache.maven.plugins</groupId>107 <groupId>org.sonatype.plugins</groupId>118 <groupId>org.apache.maven.plugins</groupId>138 <groupId>org.apache.maven.plugins</groupId>148 </plugins>157 <plugins>169 </plugins>182 <plugins>[all …]
22 static ManagedStatic<std::vector<std::string> > Plugins; variable32 Plugins->push_back(Filename); in operator =()38 return Plugins.isConstructed() ? Plugins->size() : 0; in getNumPlugins()43 assert(Plugins.isConstructed() && num < Plugins->size() && in getPlugin()45 return (*Plugins)[num]; in getPlugin()
62 The PCM plugins to build can be selected via --with-pcm-plugins63 configure option. Multiple plugins can be passed by separation with64 comma. For example, to select _only_ rate and linear plugins (and65 disable other plugins), pass66 --with-pcm-plugins=rate,linear68 Passing "all" will select all available plugins (which is the default71 When you select "plug" plugin, copy and linear plugins will be119 JACK plugin is moved to alsa-plugins package.
1 //! Infrastructure for compiler plugins.3 //! Plugins are a deprecated way to extend the behavior of `rustc` in various ways.23 /// Structure used to register plugins.26 /// methods to register its plugins.28 /// The `LintStore` allows plugins to register new lints.
25 let mut plugins = Vec::new(); in load_plugins() localVariable35 load_plugin(&mut plugins, sess, metadata_loader, ident) in load_plugins()44 plugins in load_plugins()48 plugins: &mut Vec<PluginRegistrarFn>, in load_plugin()59 plugins.push(fun); in load_plugin()
8 This feature is part of "compiler plugins." It will often be used with the13 `rustc` can load compiler plugins, which are user-provided libraries that27 The usual practice is to put compiler plugins in their own crate, separate from31 # Lint plugins33 Plugins can extend [Rust's lint106 mostly use the same infrastructure as lint plugins, and provide examples of how109 Lints defined by plugins are controlled by the usual [attributes and compiler116 including those provided by plugins loaded by `foo.rs`.
56 <plugins>58 <groupId>org.apache.maven.plugins</groupId>71 </plugins>77 <plugins>79 <groupId>org.apache.maven.plugins</groupId>88 <groupId>org.sonatype.plugins</groupId>98 </plugins>
1 # Maven ignore rules - ignore some Maven dependencies and plugins18 org.apache.maven.plugins maven-assembly-plugin * * * *19 org.apache.maven.plugins maven-javadoc-plugin * * * *20 org.apache.maven.plugins maven-release-plugin * * * *21 org.apache.maven.plugins maven-source-plugin * * * *
62 * <p>Plugins are categorized as "high" or "low" level. Low level are those 63 * which must be run BEFORE high level plugins, and before any operations 68 * <p>At load time, ICU first queries all plugins to determine their level, 69 * then loads all 'low' plugins first, and then loads all 'high' plugins. 70 * Plugins are otherwise loaded in the order listed in the configuration file.</p>132 * Random Token to identify a valid ICU plugin. Plugins must return this 204 * This is appropriate for plugins which cannot be cleaned up.233 * For example, if UPLUG_LEVEL_LOW is returned, then low level plugins may load234 * if UPLUG_LEVEL_HIGH is returned, then only high level plugins may load.289 * Plugins could use this to load data out of their [all …]
62 * <p>Plugins are categorized as "high" or "low" level. Low level are those 63 * which must be run BEFORE high level plugins, and before any operations 68 * <p>At load time, ICU first queries all plugins to determine their level, 69 * then loads all 'low' plugins first, and then loads all 'high' plugins. 70 * Plugins are otherwise loaded in the order listed in the configuration file.</p>132 * Random Token to identify a valid ICU plugin. Plugins must return this 208 * This is appropriate for plugins which cannot be cleaned up.237 * For example, if UPLUG_LEVEL_LOW is returned, then low level plugins may load238 * if UPLUG_LEVEL_HIGH is returned, then only high level plugins may load.293 * Plugins could use this to load data out of their [all …]
4 describe("unittests:: tsserver:: plugins loading", () => {33 it("With local plugins", () => {41 plugins: [54 it("With global plugins", () => {76 plugins: [112 plugins: [{ name: "some-plugin" }]142 plugins: [{ name: "some-other-plugin" }]148 …ts.projectSystem.baselineTsserverLogs("plugins", "gets external files with config file reload", se…
15 <plugins>18 <groupId>org.apache.maven.plugins</groupId>45 <groupId>org.apache.maven.plugins</groupId>55 <groupId>org.apache.maven.plugins</groupId>69 <groupId>org.apache.maven.plugins</groupId>83 <groupId>org.apache.maven.plugins</groupId>97 </plugins>
1 warning: use of deprecated attribute `plugin`: compiler plugins are deprecated. See https://github.…2 --> $DIR/multiple-plugins.rs:9:19 warning: use of deprecated attribute `plugin`: compiler plugins are deprecated. See https://github.…10 --> $DIR/multiple-plugins.rs:10:1
2 // aux-build:multiple-plugins-1.rs3 // aux-build:multiple-plugins-2.rs6 // Check that the plugin registrar of multiple plugins doesn't conflict
49 "plugins": [], array72 "plugins": [], array92 "plugins": [], array103 "plugins": [], array131 "plugins": [], array144 "plugins": [], array158 "plugins": [], array171 "plugins": [], array
24 <plugins>26 <groupId>org.apache.maven.plugins</groupId>44 <groupId>org.apache.maven.plugins</groupId>54 <groupId>org.apache.maven.plugins</groupId>76 <groupId>org.apache.maven.plugins</groupId>127 <groupId>org.apache.maven.plugins</groupId>161 </plugins>
25 /*! \defgroup Protocols-and-Plugins Protocols and Plugins35 * using plugins.37 * Plugins are much preferable compared to cut and pasting code into an260 * as plugins305 * lws_plugins_init() - dynamically load plugins of matching class from dirs314 * Allows you to instantiate a class of plugins to a specified linked-list.318 * To take down the plugins, pass a pointer to the linked-list head to321 * This is used for lws protocol plugins but you can define your own plugin323 * your own plugins to your own list using this api the same way.331 * lws_plugins_destroy() - dynamically unload list of plugins[all …]
9 …ort LD_LIBRARY_PATH=../destdir/usr/local/share/libwebsockets-test-server/plugins:../destdir/usr/lo…12 …ort LD_LIBRARY_PATH=../destdir/usr/local/share/libwebsockets-test-server/plugins:../destdir/usr/lo…15 …ort LD_LIBRARY_PATH=../destdir/usr/local/share/libwebsockets-test-server/plugins:../destdir/usr/lo…18 …ort LD_LIBRARY_PATH=../destdir/usr/local/share/libwebsockets-test-server/plugins:../destdir/usr/lo…21 …ort LD_LIBRARY_PATH=../destdir/usr/local/share/libwebsockets-test-server/plugins:../destdir/usr/lo…24 …ort LD_LIBRARY_PATH=../destdir/usr/local/share/libwebsockets-test-server/plugins:../destdir/usr/lo…28 …ort LD_LIBRARY_PATH=../destdir/usr/local/share/libwebsockets-test-server/plugins:../destdir/usr/lo…31 …ort LD_LIBRARY_PATH=../destdir/usr/local/share/libwebsockets-test-server/plugins:../destdir/usr/lo…34 …ort LD_LIBRARY_PATH=../destdir/usr/local/share/libwebsockets-test-server/plugins:../destdir/usr/lo…37 …ort LD_LIBRARY_PATH=../destdir/usr/local/share/libwebsockets-test-server/plugins:../destdir/usr/lo…[all …]
32 # TODO(lidiz) find a better way for plugins to reference each other33 sys.path.append(os.path.join(PROJECT_ROOT, "tools", "buildgen", "plugins"))77 """Merges build yaml into a one dictionary then pass it to plugins."""82 # Executes plugins. Plugins update the build spec in-place.83 for py_file in sorted(glob.glob("tools/buildgen/plugins/*.py")):
64 <plugins>101 </plugins>103 <plugins>106 <groupId>org.apache.maven.plugins</groupId>120 … <transformer implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">128 </plugins>