Fab Posted September 13, 2012 Report Share Posted September 13, 2012 Yeah, that's not quite the same--it doesn't show dependencies. Adding the library to a new project will also yank in all the dependencies so you can get an idea of what else it is linked to. If it drags in a sizeable chunk of your project that could be part of the problem. Well, just tried it and of course it does pull most of the project in the dependencies. Which makes sense, because part of the classes inside each library are the classes intended for the messages for each library. Each message class is a child of the generic message class. So, all the libraries end up having some connection. Now, I have this problem not only when I edit the messages classes, but also when I edit other classes in the libraries that might be unique to each library. It is looking like the solution is to do away with lvlibs. However, like I said before, I really like the organization they provide. Plus it makes it easier to turn each lvlib into a separate VIPM package. Fab Quote Link to comment
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.