Sign Up
EU Cyber Resilience Act (CRA) — First Deadline September 2026
If you sell LabVIEW-based software and systems in the EU, please be aware that new CRA regulations may require you to implement security vulnerability reporting starting September 11, 2026. The VIPM Team has prepared guides to help you understand how this applies to your software applications and published packages, since it's important you understand these regulatory requirements (click the Learn More link to read these guides). Thank you for your help in keeping security front-and-center within the LabVIEW community.
Learn more
VIPM › Posts › Use same LabVIEW version when generating documentation file

suggestion

Use same LabVIEW version when generating documentation file

Suggestion shared 6 months, 4 weeks ago by Ashwini Pandit
Related Packages: Antidoc CLI
   

Details

Hi,

I noticed that when using Antidoc via the command line, it launches a new instance of LabVIEW. I’m currently using LabVIEW 2024 64-bit, but Antidoc opens the 32-bit version instead.

It would be great if Antidoc could detect and use the same bitness of LabVIEW that’s already installed or in use.

Thanks!

Comments

Wovalab Hi Ashwini, The Antidoc CLI tool relies on G CLI. G CLI is the one that is responsible of launching LabVIEW. To launch the 64-bit version of LV, you need to add the -x64 tag to the command that invock Antidoc. The command should look like `g-cli --lv-ver 2014 --x64 antidoc…` You can find more info about G CLI usage here --> https://g-cli.github.io/G-CLI/getting_started.html#launching-a-vi Hope this help you use Antidoc.
 •  Reply • 6 months
Ashwini Pandit Thank you @Wovalab for your prompt and helpful response.
  1
 •  Reply • 6 months
Wovalab For the record, I've just updated the documentation to refer to the G-CLI doc --> https://wovalab.gitlab.io/open-source/docs/cli-tool-for-antidoc/latest/CLI.html
 •  Reply • 6 months
 •  Reply • 6 months

Please sign in to leave a comment.