Handle a single inline execution unit

[rtzoeller]

• [x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

Executes a single inline execution unit as part of the custom device engine.

Only supports running a single inline execution unit, using the default behavior provided by the interface.

Classes are manually flattened during compilation and unflattened during deployment, to work around bug 1131018.

Disables automated builds for non-Windows targets.

Why should this Pull Request be merged?

This partially unblocks execution unit development, and adds much of the scaffolding for future compilation and engine work.

What testing has been done?

I modified the default implementation of the interface to print to the system event log and deployed the custom device. The VIs were invoked as expected. Only tested on Windows, other OSes are expected to fail because of missing dependencies in the XML.

[rtzoeller]

Marking this as a draft until I can sort out the build.toml changes needed.

[niveristand-diff-bot]

Bleep bloop!

LabVIEW Diff Robot here with some diffs served up hot for your pull request.

Notice something funny? Help fix me on my GitHub repo.

Communication Bus Template Engine.lvlib--Finalize Execution Units.vi.png


Communication Bus Template Engine.lvlib--Initialize Execution Units.vi.png


Communication Bus Template Engine.lvlib--Read from Execution Units.vi.png


Communication Bus Template Engine.lvlib--RT Driver VI.vi.png


Communication Bus Template Engine.lvlib--Start Execution Units.vi.png


Communication Bus Template Engine.lvlib--Unflatten Compiled Data.vi.png


Communication Bus Template Engine.lvlib--Write to Execution Units.vi.png


Communication Bus Template System Explorer.lvlib--ActionVIOnCompile.vi.png


Communication Bus Template System Explorer.lvlib--Compile Data Refs.vi.png


[niphilj]

• [x] Source/Custom Device/Engine/RT Driver VI.vi

  1. Should the Process cluster not be a type def?
  2. Label of "RT State Variables in" as "RTStateVariables"

• [x] Source/Custom Device/System Explorer/ActionVIOnCompile.vi

  1. Surprised that Group cluster isn't a type def since it's part of the VS API

[niveristand-diff-bot]

Bleep bloop!

LabVIEW Diff Robot here with some diffs served up hot for your pull request.

Notice something funny? Help fix me on my GitHub repo.

Communication Bus Template Engine.lvlib--Finalize Execution Units.vi.png


Communication Bus Template Engine.lvlib--Initialize Execution Units.vi.png


Communication Bus Template Engine.lvlib--Read from Execution Units.vi.png


Communication Bus Template Engine.lvlib--RT Driver VI.vi.png


Communication Bus Template Engine.lvlib--Start Execution Units.vi.png


Communication Bus Template Engine.lvlib--Unflatten Compiled Data.vi.png


Communication Bus Template Engine.lvlib--Write to Execution Units.vi.png


Communication Bus Template System Explorer.lvlib--ActionVIOnCompile.vi.png


Communication Bus Template System Explorer.lvlib--Compile Data Refs.vi.png


[rtzoeller]

This project doesn't own either of those clusters, so making them type defs is out of scope for this PR. I agree that they probably should be.

[niveristand-diff-bot]

Bleep bloop!

LabVIEW Diff Robot here with some diffs served up hot for your pull request.

Notice something funny? Help fix me on my GitHub repo.

Communication Bus Template Engine.lvlib--Finalize Execution Units.vi.png


Communication Bus Template Engine.lvlib--Initialize Execution Units.vi.png


Communication Bus Template Engine.lvlib--Read from Execution Units.vi.png


Communication Bus Template Engine.lvlib--RT Driver VI.vi.png


Communication Bus Template Engine.lvlib--Start Execution Units.vi.png


Communication Bus Template Engine.lvlib--Unflatten Compiled Data.vi.png


Communication Bus Template Engine.lvlib--Write to Execution Units.vi.png


Communication Bus Template System Explorer.lvlib--ActionVIOnCompile.vi.png


Communication Bus Template System Explorer.lvlib--Compile Data Refs.vi.png