Jump to content

Thoric

Members
  • Content Count

    24
  • Joined

  • Last visited

  • Days Won

    2

Thoric last won the day on February 19

Thoric had the most liked content!

Community Reputation

10 Good

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. So I often leave VIP builder open when I'm working on a package that's being rebuilt multiple times whilst I work out bugs and issues. If I leave VIP Builder open overnight on my PC (Windows 7 SP1) then the following morning, as soon as I edit the Build Specification and click Save I get a cyclical error code 1 that I cannot close and I'm forced to kill VIPM.
  2. As a workaround, that's what I did. Then built it a second time to get the expected build number and restore the previous VIP file. This wouldn't be an issue if I wasn't keeping every build, of course, so I guess most users will just choose to overwrite the existing VIP.
  3. I'm building a package, frequently, in VIPM Builder. I'm up to Build number 98. Normally the build number auto-increases, but today it stayed the same as it was the last time I ran the builder. Consequently it is popping up an error message "The package "xxxxx.vip" already exists, do you wish to replace it?". If you choose not to replace it, VIPM then stops the build instead of increasing the build number. The Build number is a disabled field, so I can't change it myself. How do I get VIP Builder to increase the build number and not overwrite an existing output VIP file? (without hacking t
  4. However, take note that if your path is potentially too long here, consider how long it will be when placed into the "C:\Program Files\National Instruments\LabVIEW\vi.lib" folder! It's quite possible it won't be of an acceptable length and the package installation will fail.
  5. Just some useful information for others who might encounter error code 6 during a package build. I received this today, and when I took a careful look at the VI Path field included in the error data, the path was 266 characters long. This is longer than is supported under Windows. The reason? VIPM uses the %TEMP% folder as a working folder, which is typically "C:\Users\Username\AppData\Local\Temp\vpbtmp\src\", which is already quite long. Until the "Confiigurable temp folder" idea is available, a temporary solution is to change your defined %TEMP% folder in Windows to something s
  6. OK, so I've managed to do this, finally, with a bit of guidance from a grand master at JKI (thank you!) There are instructions included in the LabVIEW help on how to prepare your VIs for the Example Finder. This information can be found in the help, go to the Index and type "Prepare", then select "Prepare Example VIs for NI Example Finder dialog box". The help refers to a LabVIEW tool used to create a database file known as as a bin3 file that defines your example VIs by location, category and keyword. Make sure your example VIs are already in the <LabVIEW>\examples folder, under a s
  7. I'm attempting to create my first VIP package which will be to create an installer for a toolkit that includes some example VIs. Folllowing NI's help documentation, one has to create a ".bin3" file using the "Prepare Example VIs for NI Example Finder" and place the resultant bin3 file in the following location: <labview>\examples\exbins\ In VIPM Package Builder there is a destination for the examples called "Examples" and it points to a subfolder in <labview>\examples specific to the toolkit - which is great, but there's nothing for exbins. So I'm creating my own Destinatio
×
×
  • Create New...

Important Information

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