Implement a usefull way for debugging LVLIBPS

[aptivo]

Since a few days I'm struggling to debug a packaged library. The project library works when called with development system. If called by the corresponding executable I’m only getting error 1498 and there is no way (to my knowledge) to obtain more/usefull information. Even inside the LVInternalReports folder no information is stored. REALLY useful as well would be the bugfix of CARS #684847 which is reported since version 2016, which prevents to show the block diagram of nested PPL if called from the executable…

So please give a more convenient way to debug packed libraries and fix the mentioned CARS.

[crossrulz]

Speaking specifically to your error (1498), there are only 2 reasons I can think of that a PPL should report being broken: 1) cannot find a VI or 2) trying to load in an incompatible Runtime Engine.  In the case of 1, it would be very helpful why the library is broken such as "Cannot find vi PPL2.lvlibp::XYZ.vi".  In the case of 2, that information should also be available to be reported.