Jump to content

Search the Community

Showing results for tags 'vip'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Special Interest Boards
    • Developing LabVIEW Tools and Add-ons
    • Professional User Interface Design in LabVIEW
  • VI Package Manager (VIPM)
    • VI Package Manager (VIPM)
    • Dragon Beta
  • JKI Tools
    • JKI Flat UI Controls
    • JKI Design Palette
    • JKI State Machine
    • JKI State Machine Objects (SMO)
    • Caraya Unit Tester
    • VI Tester
    • JKI JSON
    • HTTP REST Client
    • JKI Simple Localization
    • EasyXML Toolkit
  • Legacy Tools
    • Legacy Tools

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 3 results

  1. Considering the tools developer having multiple binaries (such as PPLs, Shared Libraries) built for different systems ranging from various LabVIEW versions, bitness (32 and/or 64) & OS. A single Package may contain all the required resources to support multiple platforms. But when being installed, only the platform dependent resources actually get installed leaving other resources untouched. A great example for this kind of package is JKI Design Palette. It supports LabVIEW versions from 2015 and beyond, even includes support for both 32 & 64 Bit versions. Tried to replicate it with my package building, but to no avail. While digging deeper I came across the following detail and came know - this is actually possible with the VIPM package building process, But I couldn't find myself how to configure the VI Package Builder to do this. It would be really helpful if there any documentation available to carry out this process with VIPM Package Builder. Also check this post for PPL forward compatibility reference,
  2. Hi, I would like to ask for a help with the following issue: I am trying to distribute VIP file with some dependencies, which are not published on VIPM. Hence, I added them to VIPC and would like to distribute this VIPC with VIP file. Is this somehow possible?
  3. Hi, Please help... I am trying to create a .vip that will install my LabVIEW project as a LabVIEW project template (note: I have done this process a few time before with no issues) I have my project that I want to make into a template, everything works perfectly. I configure the .vipb, I build and install the .vip. I check the destination to see if my files have installed to the correct location, they have. Here's where the problem kicks in...... I open my LabVIEW project that has installed in the destination, and notice that the .png files in my project some are missing and some are saying missing. In my project I have .png files in various .lvlibs. The first .lvlib in the project has the .png's showing, however showing as missing and the expected location is saying C:\ which is incorrect, it should be in the location where my .lvlib is in the destination. The other .lvlib's don't even show the .pngs in the LabVIEW project explorer. Now checking on disk all the png's are there and in the correct location. In summary it looks as if as part of the vip install it is removing the link the .lvproj has to my .png files VI Package Manager Version : 2018.0.0f1 Jul 21 2018 LabVIEW Version : 2016 (32 bit) OS : Windows 10 Pro Version 1803 Any help is greatly appreciated Thanks in advance. Kev
×
×
  • Create New...

Important Information

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