Link Search Menu Expand Document
Converted document
 Chapter 10: FEBio Plugins Up Chapter 10: FEBio Plugins Section 10.2: Error Messages 

10.1Using Plugins

A plugin is compiled into a dynamic library (dll or dylib) or shared object (so) and containes the compiled code of the library. In order to use this plugin, you must add the path to and name of the plugin file in the FEBio configuration file (see Chapter 9↑ for a discussion of the configuration file). For each plugin, an import item has to be added in this configuration file. For example,
<import>myplugin.dll</import>
You may need to add the full path to the plugin if FEBio has problems locating the plugin.
<import>C:\path\to\my\plugins\myplugin.dll</import>
When FEBio starts, it will first load all the plugins that are defined in the configuration file before it reads the input file. This way, sections in the input file that require the plugin's capabilities will already be available for use.
An alternative way for loading a plugin is using the -import command line option.
>febio -i input.feb -import myplugin.dll
In this example, FEBio will look for the file myplugin.dll in the current working directory. If the plugin file is located in a different folder than the current working directory, you must prepend the relative or absolute path to the file. Note that if the path contains spaces, you need to wrap it in quotes.
>febio -i input.feb -import "C:\path\to\my custom plugin\myplugin.dll"
 Chapter 10: FEBio Plugins Up Chapter 10: FEBio Plugins Section 10.2: Error Messages