Jump to content
JasonW

VIPM 2010 & packed libraries

Recommended Posts

Just a quick question....we were wanting to distribute our "released" re-use library as packed libraries instead of source code like we have been to prevent unintentional modification. We also desired to continue using VIPM as the distribution tool since it does such a great job managing versions. I tried to build one of our simplier tools into a VI package containing only the target packed library but I got an error (see below). Since packed libraries are a new feature of LV2010, I was wondering if VIPM supports them?

 

Thanks

Jason

 

 

=========== START of VIPM Error Message ===========

An internal VIPM Error has occured on: Tuesday March 15, 2011 at 02:58:53 PM

 

= Automated Message Start =

Error 7 occurred at List Folder in

5EC32D65DB893014F50B6BE29714A044->5CD014F79D564136DF7EDCAE8697C8EC->3C8A51DC72B459801102CB2B0DB10462

->F7BEB1F5BC6EFF6645D5C53D6E0C6A60->F9DCFCE23D2FBC8F7420D001A1FDC8CA

Possible reason(s):

LabVIEW: File not found. The file might have been moved or deleted, or the file path might be

incorrectly formatted for the operating system. For example, use \ as path separators on Windows, :

on Mac OS, and / on Linux. Verify that the path is correct using the command prompt or file

explorer.

=========================

NI-488: Nonexistent GPIB interface.

C:\Documents and Settings\jwillis\Local Settings\Temp\VIPB Temp\Source Distribution

= Automated Message End =

 

= User Defined Message Start =

VI Package Builder Error

= User Defined Message End =

 

= Error Handler Call Chain Start =

F9DCFCE23D2FBC8F7420D001A1FDC8CA

= Error Handler Call Chain End =

=========== END of VIPM Error Message ===========

  • Upvote 1

Share this post


Link to post
Share on other sites

Just a quick question....we were wanting to distribute our "released" re-use library as packed libraries instead of source code like we have been to prevent unintentional modification. We also desired to continue using VIPM as the distribution tool since it does such a great job managing versions. I tried to build one of our simplier tools into a VI package containing only the target packed library but I got an error (see below). Since packed libraries are a new feature of LV2010, I was wondering if VIPM supports them?

 

Thanks

Jason

 

Hi Jason,

 

Thanks for posting your test results. Since PPLs are platform and LabVIEW version specific and they don't support external dependencies, we haven't seem many people (outside NI) using them.

 

We'll spend a little time looking into whether we can reproduce your issue and/or get packaging of PPLs working.

 

Thanks,

 

-Jim

Share this post


Link to post
Share on other sites

Jason,

 

As of yet, we do not officially support the packed libraries in VIPM 2012.

 

I have created Case 13647 internally for tracking the status of this since we are working on it for the next release of VIPM.

 

We really want to support this capability and are working through various issues.

 

Thank you.

Share this post


Link to post
Share on other sites

Jason,

 

As of yet, we do not officially support the packed libraries in VIPM 2012.

 

I have created Case 13647 internally for tracking the status of this since we are working on it for the next release of VIPM.

 

We really want to support this capability and are working through various issues.

 

Thank you.

 

Were the use of packed libraries ever looked into? We're running into some real headaches that caused by not being able to deploy a package as a packed library (or even just use a packed library as the source of the package).

 

Our issue is that we have several APIs that we are currently distributing as a package AND those are then getting built into extensible / plugin applications. The goal was for our developers to be able to use the distributed API to develop a plugin for one of our applications. Excluding the VIPM / Palettes stuff, one of the best ways to achieve this was to have our main application use a framework packed library (lets call it Plugin.lvlib with a class PluginParent.lvclass) and then build packed libraries for each plugin. This avoids so much of the hell of all other methods with dependencies etc.

 

However, when we build our Plugin.lvlib:PluginParent.lvclass into a packed library it ends up "swallowing" the API class and renaming it "Plugin.lvlibp:API.lvclass". This means that none of our pallet VIs work (As they are just API.lvclass). If we could distribute our API as a packed library in the first place (either building the packed library before VIPM or as a destination option for VIPM) then the API packed library would not get swallowed and renamed and everything would work.

 

We tried creating an installer using LabVIEW's built in tools which made everything work except for 2 cosmetic issues: 1. we would miss the VIPM versioning etc, 2. we have no palletes (besides building, installing, creating palettes using deployed code, copying to back source and rebuilding, I'm not sure how to sensibly do this outside of VIPM).

Share this post


Link to post
Share on other sites

Packed libraries are still not supported. Thanks for bringing all the issues to our attention as this helps us to decide on where to place resources. There is a topic here, which probably can use your vote:

 

http://ideas.jki.net/topic/116142-distribute-reuse-components-as-packed-project-libraries

 

Also add any comments there to help us develop this feature.

Share this post


Link to post
Share on other sites

Were the use of packed libraries ever looked into? We're running into some real headaches that caused by not being able to deploy a package as a packed library (or even just use a packed library as the source of the package).

 

Our issue is that we have several APIs that we are currently distributing as a package AND those are then getting built into extensible / plugin applications. The goal was for our developers to be able to use the distributed API to develop a plugin for one of our applications. Excluding the VIPM / Palettes stuff, one of the best ways to achieve this was to have our main application use a framework packed library (lets call it Plugin.lvlib with a class PluginParent.lvclass) and then build packed libraries for each plugin. This avoids so much of the hell of all other methods with dependencies etc.

 

However, when we build our Plugin.lvlib:PluginParent.lvclass into a packed library it ends up "swallowing" the API class and renaming it "Plugin.lvlibp:API.lvclass". This means that none of our pallet VIs work (As they are just API.lvclass). If we could distribute our API as a packed library in the first place (either building the packed library before VIPM or as a destination option for VIPM) then the API packed library would not get swallowed and renamed and everything would work.

 

We tried creating an installer using LabVIEW's built in tools which made everything work except for 2 cosmetic issues: 1. we would miss the VIPM versioning etc, 2. we have no palletes (besides building, installing, creating palettes using deployed code, copying to back source and rebuilding, I'm not sure how to sensibly do this outside of VIPM).

 

We'll be supporting packed libraries in VIPM 2014. You will be able to add them as files to a package. But you won't be able to dynamically build them with VIPM. You would have to build them outside of VIPM for now.

 

 

 

Share this post


Link to post
Share on other sites

We'll be supporting packed libraries in VIPM 2014. You will be able to add them as files to a package. But you won't be able to dynamically build them with VIPM. You would have to build them outside of VIPM for now.

 

I was able to select a folder containing a PPL, it shows up in the source files, however, i cannot create a Menu Palette, is this supported in 2014?

 

post-27055-0-06945600-1406125659_thumb.png

 

Thanks,

Share this post


Link to post
Share on other sites

I was able to select a folder containing a PPL, it shows up in the source files, however, i cannot create a Menu Palette, is this supported in 2014?

 

post-27055-0-06945600-1406125659_thumb.png

 

Thanks,

 

Okay, so the work around for this problem is to create a wrapper library of VIs that contains the VI in the Packed Project Library. On the palette set the place contents flag.

 

Please note that you will not be able to include the packed project library in the VIP diue to the builder trying to move or recomplile the VIs within the PPL. So for now I have to manually place my PPL in my user.lib folder.

 

My next attempt at a work-around until this is fixed in VIPM, will be to zip the LVLIPB and create a post install method to unzip the LVLIPB.

 

Hope this helps someone.

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.