Jump to content


  • Content Count

  • Joined

  • Last visited

Posts posted by T.L.

  1. Hello Ashish,


    when I put everything into a single package, the VIs NOT placed under <LabVIEW>\vi.lib are NOT correct relinked to them. When opening the top level VIs LabVIEW starts searching for the VIs which are now installed in LabVIEWs folder structure.


    Actually I have this workaround:

    I have to 2 projects and 2 packages.

    In 1st project/package everything to put into LabVIEWs folder structure.

    And a 2nd project/package to use the VIs previously installed. This installs my code to "C:\ProgrammData\MyProject\..".


    Does it help?


    Best regards


  2. I want/have to build a package, where most of the VIs are located under LabVIEW ..\vi.lib path and some top VIs should be placed in "C:\ProgrammData\MyProject".

    All VIs are placed at there correct destinations after installing my package(s).




    When I open my top level VIs from "C:\ProgrammData\MyProject" LabVIEW starts searching for the subVIs and finds them in "C:\Program Files (x86)\National Instruments\LabVIEW 2014\vi.lib\MyProject\.."


    LabVIEW warns me for new dependency paths for my subVIs.


    a) if I put all in a single package the expacted path is "C:\labview\vi.lib\MyProject.."

    B) if I build 2 packages 1st installing vi.lib-stuff and 2nd installing top level VIs the expacted path is "..\..\..\..\..\..\MyProject.."


    Why are my top VIs not properly relinked to there subVIs?

    How can I get them linked correctly?


    Best regards


  • Create New...

Important Information

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