One of the newer features of LV2009/2010 is that the project app build includes a category called 'Shared Variable Deployment' were you will find a list of all the libraries that were found to be linked to the application and which can be deployed automatically for you when the app executes. If there are any libraries you need that are not 'found' to be linked to your app, you can still include them in the build and they will show up in the list but will not remain checked. If for example you have a library whose only purpose is to be bound to a rt hosted library and is there only to allow the DSC to perform Citadel data logging then you are out of luck. The only way is to put a NSV tag on your diagram and force it to be part of the hierarchy. I think this is a bug.
This is unexpected behavior. This was reported to R&D (CAR ID #256742) for further investigation. In the meantime, I think you've already pointed out the easiest workaround (include at least one variable with a dependency in the lvlib). Thanks for the feedback!
