Jump to content

Search the Community

Showing results for tags 'vipm'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General Discussion
    • General Discussion
  • VI Package Manager (VIPM)
    • VI Package Manager (VIPM)
  • JKI Tools
    • 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

Calendars

There are no results to display.


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 9 results

  1. 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
  2. Hi, my name is Francesco. I'm Italian and i don't speak good english. I have a problem with the installation relatives VIPM in linux I follow the instruction but appear this message when i launch the command: sudo ./vipm Can't find library liblvrt.so.15.0 Make sure this library is installed in your LD_LIBRARY_PATH search path, or in /usr/lib To download the LabVIEW Runtime engine, go to http://www.ni.com/rteFinder?dest=lvrte&version=15.0&platform=Linux&lang=en How can i resolve this? Thank you so much and sorry for my english!
  3. hemalalitha

    Automatic Update

    Hi, I see an option in VIPM to disable the automatic VIPM update, please see the snippet attached. Is there way to disable this programmatically. Is the value configured in this is stored any ini key?
  4. I tried installing the new VIPM2017 for Linux in a clean Fedora 27 virtual machine just to give it a try but I can't get it to do anything. I followed the two basic steps: 1) install LVRTE 2015SP1 which installs without any problems or errors 2) copy JKI folder to /usr/local as described in the instruction.txt When launching vipm I just get the blunt error: No such file or directory as shown below sudo ./vipm sudo: unable to execute ./vipm: No such file or directory What could be the problem and how could it be resolved?
  5. We're pleased to announce the release of VI Package Manager 2017 for Linux! Our team has worked hard to address several issues that were making Linux support difficult. Click here for more details.
  6. We're pleased to announce the release of VI Package Manager 2017 for Mac! Our team has worked hard to address several issues that were making Mac support difficult. Click here for more details.
  7. When building a simple package in VIPM 2014 of example code in LabVIEW 2016 that is using the new channel wire, I receive the attached error message. The build will work if I choose not to compile the VI during build.
  8. When selecting to build a package for only LabVIEW 64-bit, the package is still displayed in my repository when installing to 32-bit LabVIEW. I noticed in the spec file for the packages there is a tag for: Exclusive_LabVIEW_System="ALL" I assume this is the value intended for 32 or 64-bit LabVIEW, but I do not see this tag update no matter what changes I make to the LabVIEW bitness. I am using the latest version of VI Package Manager Pro (2014.0.2). Kind regards, -R
  9. When selecting to build a package for only LabVIEW 64-bit, the package is still displayed in my repository when installing to 32-bit LabVIEW. I noticed in the spec file for the packages there is a tag for: Exclusive_LabVIEW_System="ALL" I assume this is the value intended for 32 or 64-bit LabVIEW, but I do not see this tag update no matter what changes I make to the LabVIEW bitness. I am using the latest version of VI Package Manager Pro (2014.0.2). Kind regards, -R
×

Important Information

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