Skip to content

Releases: LabVIEW-Open-Source/Caraya-CLI-extension

LV2020 Upgrade

14 Oct 20:05
Compare
Choose a tag to compare
  • [Feature: 3] Wrapper methods Caraya and RunCaraya now installed in G-CLI folder
  • [Fix: 4] Quitting LabVIEW is now optional when done, with -q as a required tag to Exit LabVIEW when done
  • [Feature: 5] Paths will now resolve relative to the Working Directory when passed as relative.

Updated to call "Run Tests" method

10 Mar 00:40
Compare
Choose a tag to compare

This is a fix for issue #1 and #2

Requires installation of Caraya >= 1.1.0.x and G-CLI >= 2.3..x

https://github.com/JKISoftware/Caraya
https://github.com/JamesMc86/G-CLI

Point to "CarayaCLIExtensionEngine.vi" which installs in the Caraya root folder under <vi.lib\addons\Caraya>.
Follow the syntax as described in the Caraya wiki, but replacing the LabVIEW path with the G-CLI call, as shown in the example below:

g-cli --lv-ver <LABVIEW_VERSION> "<LABVIEW_DIR>\vi.lib\addons\_JKI Toolkits\Caraya\CarayaCLIExecutionEngine.vi" -- -s "<SOURCE_TEST_FOLDER>" -x "<OUTPUT_FILEPATH>"

Optional modifiers: https://github.com/JKISoftware/Caraya/wiki/Command-Line-Interface

ex:
image

G-CLI support for Caraya

05 Jan 18:08
Compare
Choose a tag to compare

Requires installation of Caraya >= 1.0.0.67 and G-CLI >= 2.1.0.1522=0

https://github.com/JKISoftware/Caraya

https://github.com/JamesMc86/G-CLI

Point to "CarayaCLIExtensionEngine.vi" which installs in the Caraya root folder under <vi.lib\addons\Caraya>.
Follow the syntax as described in the Caraya wiki, but replacing the LabVIEW path with the G-CLI call, as shown in the example below:

g-cli --lv-ver <LABVIEW_VERSION> "<LABVIEW_DIR>\vi.lib\addons\_JKI Toolkits\Caraya\CarayaCLIExecutionEngine.vi" -- -s "<SOURCE_TEST_FOLDER>" -x "<OUTPUT_FILEPATH>"

Optional modifiers: https://github.com/JKISoftware/Caraya/wiki/Command-Line-Interface

ex:
image