How Can I Include .mnu Files in a Built LLB?

Updated May 2, 2018

Reported In

Software

  • LabVIEW Application Builder Module
  • LabVIEW Professional

Issue Details

I am trying to distribute my code by creating an LLB.  I get the following error when I try to build the LLB:

"The build was unsuccessful. Possible reason: Error copying files.
Source: ...\Program Files\National Instruments\LabVIEW 2010\menus\Categories\Mathematics\anlinalg.mnu
Destination: ...\builds\P482_DQT\DQT_Phase2_V1.0\data\support.llb\anlinalg.mnu

Unknown LLB file type."

Details:

"Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:

Error 1 occurred at <Call Chain>

Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
"

How can I build this library without getting an error?

Solution

There are three options for troubleshooting this error:
  • Upgrade to LabVIEW 2011 or newer (may or may not resolve the issue).
  • If the mnu file has been included as a dependency, but is unused.  Place a check-mark next to Remove unused members of project libraries.
  • If the mnu file does not need to be included in the library, add the mnu file to the source files of the project, choose to always include the file, and make sure it is assigned to go to a support directory.

Additional Information

Prior to LabVIEW 2010, mnu files were treated as "non-LV" files and therefore could not be included in an LLB. They were always put in a support directory.  Changes to Application Builder in 2010 allowed mnu files to be recognized as LabVIEW files, but there was not support for copying mnus into LLBs.  This behavior has been fixed in LabVIEW 2011 for most mnu files, but some math functions will still cause the error.

WAS THIS ARTICLE HELPFUL?

Not Helpful