x-applocal Phase 2 -- extensible interface for ports

[ras0219-msft]

Still in progress, however the draft interface is to create a file named <dll filename>.plugin.json with the plugin metadata. For example, bin/Qt5Core.dll.plugin.json might be

{
  "patterns": {
    "bin/Qt5Gui.dll": "Qt5Gui.dll",
    "bin/plugins/*.dll": "plugins/",
    "share/openni2/config/**": "config/"
  }
}

The three patterns are:

1. Exact File (no wildcards) -- This can do renaming.
2. Prefix+suffix non-recursive file match (/A*B, A & B are optional) -- Destination needs to be a directory. Case-sensitive (?).
3. Full recursive deployment -- No filters possible, deploys the entire subtree. Destination should be a directory.

[Neumann-A]

I missing the condition of deployment here. What is the trigger which would lead to a deployment of a plugin?

[ras0219-msft]

What is the trigger which would lead to a deployment of a plugin?

The trigger doesn't change from today; it would be having a reference to Qt5Core.dll in your DLL imports.

Specifically, if we deploy bin/Qt5Core.dll, we will follow the plugin deployments listed in bin/Qt5Core.dll.plugin.json.

[dg0yt]

Please edit the initial example to resolve the confusion about Qt5Core vs. Qt5Gui.
And please give an indication about handling:

• plugins in otherwise static ports
• non-Windows platforms.