.rtm files for VI's that are in the lvlib which is the Top-Level library for a Packed Project Library

[GarryG]

I'm building packed project libraries for distribution in a framework baseline.  I only wish to expose the code that I've included in the lvlib.  The only thing in the lvlib are top level VI's (no rtms).  When I build the packed project library with the lvlib as the Top-Level library, and any VI has a custom rtm, the rtm ends up appearing as a public function in the packed project library.  Is this a bug in LabVIEW 2014?  I did a simple example build with a blank diagram VI with a custom rtm, made an lvlib (with only the blank VI included in it) and then when building the packed project library, both the blank VI AND the rtm show up.  Is there something I should be doing to hide the rtms explicitly?

Thanks for your help and thoughts in advance.

[mikeporter]

I have typically found that it was a better approach to not use rtm files, but to build the menus programmatically. It's also faster and more flexible.

Mike...