Jump to content

Bug? 'Secondary' Dependencies not Included as Internal Dependencies


jgcode

Recommended Posts

VIPM 2010.0.2

 

Steps to reproduce the bug (if it can be reproduced)

Create a Package (e.g. Test Package) which links to a VI in another package (OpenG File IO), and where that VI links to another VI in a different package (OpenG Error)

 

post-2618-0-20826300-1303805920_thumb.png

 

Build your Package (Test Package) so that it has no external dependencies i.e. VIPM will automatically add and rename all VI dependencies to your package internally.

 

The VIPC file shows all dependencies. Only the File IO VI is called directly by my VI.

post-2618-0-37564700-1303805933_thumb.png

 

I do not include any dependencies. I want all calling VIs to be included as internal dependencies.

post-2618-0-10767300-1303805830_thumb.png

 

Expected behavior (what would happen if the bug didn't exist)

Test Package has no dependencies.

 

Actual, observed behavior (the bug)

Test Package has OpenG Error dependency.

 

I uninstall the OpenG Error Package, then load my VI to show the dependency exists.

post-2618-0-90745600-1303805896_thumb.png

 

Additionally, only File IO VIs are included in the _internal_deps dist folder (<vi.lib>\JGCODE\_Test Package_internal_deps).

post-2618-0-31449600-1303805879_thumb.png

 

The VI is installed in its own palette using a Custom Category for easy testing.

post-2618-0-24075400-1303805906_thumb.png

 

I have attached the Package code for testing.

Test Package.zip

Code is in LabVIEW 2009

Link to comment
Share on other sites

  • 3 months later...
  • 7 months later...

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.