Generally you can use three different ways:
- Use WinBuilder's Tools button >> Convert tab to generate a WinBuilder script.
- Copy the plugin's folder into the WinBuilder project tree, e.g. into 'Apps'
This means the complete folder inclusive *.inf, *.xml and maybe additional files and / or a files subfolder. Do not copy *.cab files only; they are not recognized!
Winbuilder will 'translate' the plugin on the fly and process it.
- Map plugins into your project:
Inside %ProjectDir%\Apps\folder.project define the plugin(s) in the section [Link].
- A complete Repository like:
- Some single plugins like
In all cases the project tree shows the plugins besides the scripts. You can select or deselect them in the known way, to include or exclude them in the build.
WinBuilder needs some [Variables] definitions to work with BartPE plugins.
These definitions are made by including Basic >> Build >> InfSupport.Script to the build.
This script can also be used to add a plugin collection. Attention: this removes all previous present mappings!
InfSupport.Script is for nativeEx_based projects only! Other projects must define the variables in their way.
Please always remember:
WinBuilder does not claim to be a BartPE clone which has all functionality BartPE has.
It gives you however the ability to process many BartPE plugins into your WinBuilder PE.
There are rarelly situations that WinBuilder cannot process a plugin correctly. In this case the issue is mentioned in the log. In this case you can try to convert the plugin manually into a script and to edit the script and add some other necessary information.
One situation which cannot be handled by WinBuilder is e.g. the @GetEnvironment function of Nu2Menu
Have fun with testing!
BTW: You can download a 'Tutorial' nativeEx_barebone_075 project here.