Dev/CI Tools Integration Points

[JamesMc86]

As a tool developer I want to make it as easy as possible to call my tools.

One way we can tool this is to have a CLI Tools directory. If we don't find a VI locally, we can search here.

That way, as a developer, I can install a launcher into this directory for my-tool.vi and then users can just type labview-cli my-tool.vi to launch it.

A future evolution might be to have LabVIEW specific folders to avoid compilations but we will start simple.

[JamesMc86]

I would alter this slightly. Here is what I suggest.

1. We have a "search" directory in vi.lib for tools to install to. This allows tools to be distributed through VIPM and compiled on install for the right version of LabVIEW.
2. A --Tool option with the name (with or without .vi) will call this tool from the VI lib of the relevant version of LabVIEW. Alternatively this could be invoked automatically if the provided parameter does not exist locally (probably better)
3. We could also provide a folder to install batch file "wrappers" so that the tool name can be the main call. i.e. echo-call --lv-ver 2015 -- "parameter"
4. We should include an echo tool as an example.

My goal with this is not to integrate CI tools directly into this package but make it very easy for additional packages to integrate with this.

[JamesMc86]

done the search directory as <vi.lib>\G CLI Tools. Then ratrher than having --tool instead if the file doesn't exist locally we will search this directory.

The name can still use directories so for example wiresmith\lvbuild will extend to <vi.lib>\G CLI Tools\wiresmith\lvbuild.vi

Now need to build a demo tool for testing and demonstration purposes.