Showing results for 
Search instead for 
Did you mean: 

How to omit Config.Mnu file from packed project library (lvlibp)?

I've created a project library and carefully set the access scope so that only my 'top level' vi is public. However, after compiling into a packed library, I noticed that it included a config.mnu file. I did a "Find Project Items" search for config.mnu and found that it is attributed to NI_LVConfig.lvlib. My understanding that that the mnu file has to do with showing the library VIs in the fucntion pallette at edit time, but confused as to why it would be included in a packed library. Why is this mnu file included in my packed project library? How do I remove, omit it or hide it from the final lvlibp file?




CAUTION! New LabVIEW adopters -- it's too late for me, but you *can* save yourself. The new subscription policy for LabVIEW puts NI's hand in your wallet for the rest of your working life. Are you sure you're *that* dedicated to LabVIEW? (Check out this lengthy post of mostly complaints)
0 Kudos
Message 1 of 1