James McNally
James McNally
This is probably a nice thing! However we should check that our detection VI for this still works and probably expose this as a public API so that tool builders...
Since restructuring the integration tests the packed library support now fails. It appears to fail to launch into LabVIEW.
The existing documentation needs work. We have documentation in the wiki on github but it isn't very intuitive to navigate. Should look at generating a static site or organise the...
For v3.0.0 I'm going to propose an install from source for the main G-CLI proxy so that isn't delaying things while I work out supporting packaging across supported distros. We...
Needs more testing but saw on a local run that despite having 32 bit and 64 bit installed and detected and no -x64 flag set. Confirm if this is the...
In order to build with a suitably old glibc I created a centos7 dev container for building the packages. I believe this is currently rebuilt in each CI run. We...
Getting errors to powershell is a pain. It doesn't report an error based on return code and by default doesn't error if stderr contains data (I thought this would fix...
Can we generate the help documentation based on the option parser? Similar to the library used in the C# application.
Right now we are dependent on an agreed format and the NI service locator to pass the port details to G-CLI. This could be a weak link because: * Any...
Create a guide on the best way to setup LabVIEW for working with this tool. Include the ini tokens from https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000001De1JSAS&l=en-GB Probably makes sense to put this on the LabVIEW...