Building vi.lib/Utilities in a Packed Library searches

[DuncanW]

If I build a VI in a packed library, which contains some items from the vi.lib/Utilities folder, the build produces the 'Searching' dialog.

For example a VI containing the 'Check if File or Folder Exists.vi' produces this symptom (see screenshot attached).

I've tried mass compiling my project and also mass compiling the vi.lib/Utilities folder and it doesn't fix it.

If I uncheck 'Remove unused polymorphic VI instances' & 'Remove unused members of project libraries' from the Additional Exclusions build page, it does fix it, but my build is 1/3rd bigger in file size than if I wait for all the dependencies to be searched for & found.

Is there a reason anyone knows why it's doing this and is there a better solution than bloating the compiled file?

[ThiCop]

Hello Duncan,

Can you post some example code illustrating the issue?

[DuncanW]

Hi Thierry, thank you for replying.

Sorry it's taken me a couple of days to reply.

I've attached a little project, which comprises an exe, which calls a VI inside a packed library. The child VI displays it's call path and checks if the path exists.

Just as an extra, I've included a little pice of code to write an ini file as that's another example of something which generates the Searching dialog.

When I build this, I get quite a few paths searched for!

I've zipped it up & attached it (The project was in the folder D:\National Instruments\VI Lib Searching)

Many thanks

Duncan

[ThiCop · Accepted solution]

Hello Duncan,

I have tested it with LabVIEW 2011 and everything seems to work.

Which version of LabVIEW are you using?

[DuncanW]

Hi Thiery,

I've just realized this was still marked as unresolved.

I was using LabVIEW 2010, but I tried this in 2012 SP1 and it works fine.

Cheers

Duncan

[ThiCop]

Thanks for doing the update! 🙂