Jump to content
TonP

Using Custom Target with absolute path results in empty VIP

Recommended Posts

I am trying to build a Glyph set. Unfortunately the Default Data Directory is not available in VIPM, so I added that as a custom target, with an absolute path.

 

However the files are not added to the VIP file.

If I move one of the files (all are PNGs) to a supported folder ( for instance), that file is added to the VIP file.

The attachment has my full project:

-Icons (contains the VIPB file and all the PNGs to be included)

-the resulting VIP packages with only one PNG included.

 

Details:

VIPM 2012.0.0 build 1780

LabVIEW 2011 f1

Win XP English

 

Ton

buildingCustomTarget.zip

Share this post


Link to post
Share on other sites

Ton,

 

I was able to configure the package and deploy it under the Glyphs folder.

 

Here is the screenshot of my Destination configuration in VI Package Builder: http://screencast.com/t/ut6ZKWjsW

 

Here is how the LabVIEW Icon Editor Glyphs interface looks after the package is deployed: http://screencast.com/t/Ae4p9IDDaK

 

I hope this helps.

Share this post


Link to post
Share on other sites

Ton,

 

I was able to configure the package and deploy it under the Glyphs folder.

 

Here is the screenshot of my Destination configuration in VI Package Builder: http://screencast.com/t/ut6ZKWjsW

 

Here is how the LabVIEW Icon Editor Glyphs interface looks after the package is deployed: http://screencast.com/t/Ae4p9IDDaK

 

I hope this helps.

Yes that would work IF my LabVIEW folder was in the default location (which it isn't since I have multiple LabVIEW versions).

I still consider this a bug.

 

I was wondering if the same happenend on yoursystem.

 

Ton

Share this post


Link to post
Share on other sites

Ton,

 

Now I know what you mean. I was able to recreate the behavior described by you and have submitted the issue (Case 13780) for review by VIPM team.

 

Thanks for recording your observations.

 

I was curious about your non-standard LabVIEW folders for multiple LabVIEW versions. I have multiple LabVIEW versions on my PC as well and I did let it install the components in the default locations. Am I missing anything?

Share this post


Link to post
Share on other sites

I use multiple directories because:

  • I have seperate configurations for the Code Capture Tool
  • Endevo/Symbio GOOP got confused
  • It's the default probe location, and it's kinda pity that LV 2011 resaves my LV 2009 probes

 

And I use a custom location because 'My Documents' is being hosted on a network drive. And I am not always connected, but LabVIEW uses the Data Directory as the 'auto backup location'

 

Ton

Share this post


Link to post
Share on other sites

So I think the main problem is that you have no source files with a target destination beneath LabVIEW in the package. You are basically trying to create a pure System Components package, not a LabVIEW package with some system components. In the context of VIPM, 'System Components' are any files that are not beneath the LabVIEW install location on disk. This is a use-case that we are planning to address in a future release. For now, I think a workaround for you is to create a dummy blank VI in your source and set the destination to some location under LabVIEW. This should work.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...

Important Information

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