LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Avoid auto-generated CHM files in your build - Please add to next version roadmap

I have an exe build where the source includes some DAQmx functions.  Apparently this causes LabVIEW to autogenerate some CHM help files for these native functions when I build my exe.  I do not want these files included for multiple reasons.  My ask for the next release is to provide the default to not include the offline CHM files, and to allow us a method to include them if desired.  Native functions should not, in my opinion, autogenerate these files, nor should anything else for that matter.  The default should always be to not include them.

In my case I can't exclude the functions, nor can I see where any of them have a help file path property set, so I have to assume this issue root is with this LV release.  I'm currently at 2023Q3 but have also seen this issue with a 2024 build.  I am hoping this gets to the NI development folks.

Thank you.

Message 1 of 4
(47,875 Views)

This issue is being tracked as Bug 2870271.


Christina Rogers
Principal Product Owner, LabVIEW R&D
Message 2 of 4
(47,741 Views)

where can i find the explanation of the solution to this bug?
how can i get around it?

0 Kudos
Message 3 of 4
(37,440 Views)

There is no current work around. It is a matter of NI fixing their build process. Ironically, this bug was created due to a fix for another bug in the build process.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 4 of 4
(37,428 Views)