12-20-2011 10:02 AM
I have recently begun using packed libraries to group functions together within my project.
I have a sub-project for each packed library that I create. The top-level project depends on the packed libraries, each of which may contain sub-libraries. For example:
<Top Level Project> depends on:
I have found it to be very annoying that I cannot re-compile a packed library while I have a higher level project open. So, if I discover a bug and need to make a change to "Packed Library 3", I need to close my top-level project, close "Packed Library 2", recompile "Packed Library 3", open and recompile "Packed Library 2", and then I can open the top level project and see if my fix worked. If it didn't, then round and round I go. It is very inefficient. Luckily, this particular project doesn't take very long to open, but I have other, larger projects which take longer to open and can make this process nearly unusable.
While I understand the reason for this restriction, I really think there should be a better way. Is there a way to instruct labview to "unload" a library from a project so that it can be recompiled? Clearly the dependent VIs would be broken while the library is unloaded, but I would find that preferable to having to go through the above process. Or is there another, better way to do this?
Thanks!
Solved! Go to Solution.
12-20-2011 11:06 AM
While in active development, you can use a normal library (*.lvlib) in place of the packed library. Work all the bugs out with the delelopment code. Once you are ready, you can compile the packed libraries. Then, go the top level project, right-click on the library, select "Replace with packed library" and browse to the compiled version.
12-21-2011 11:46 AM
Thank you, codeman!