Jump to content

Recommended Posts

Let me start with some context

 

We have to differentiate from a Production environment (to produce data) and Development environment (to develop test and debugging).

 

Our code (very simplified) is organized in this way

 

- Tests (Actual vi that will produce results)

- System files (support vi, drivers, common functions etc.)

 

 

Both are under source control

 

We have decided to make VIPM's (residing in vi.lib) for all System files and leave the Tests files where they are (random folder under source control).

 

This means the all the vi's inside Tests will have links to the System Files (inside vi.lib now) and that works pretty well for the Production Environment, but when we want to use the Tests in the development environment (Tests and System Files in a random folder) we need to re-link all the Tests to point to the local files and not the System Files inside vi.lib.

 

The question is:

 

Is there any way to manually update the references of the Tests so we can choose from where we want to get the System Files?

 

 

Link to post
Share on other sites

Short answer is no. you can't easily modify dependency locations.

 

Longer answer is yes. you can modify environment search paths to point to the new target and delete the old target files to force re-linking, but this is really the hard way and it's going to get you into re-linking trouble/hell.

 

Correct answer is that you're not using vi packages correctly. The code that goes into a VI package should be able to stand on its own. You should be able to debug/test/validate all VI package source code before you build it into a package. Think of a VI package as formally released reusable source code. If you feel the need to constantly switch between built packages and source code, then you're not adequately validating/testing before building the package.

 

Hope this helps.

  • Like 2
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.

  • Similar Content

    • By javier_r
      VIPM.io now allows you to post LabVIEW Resources, Ideas, and Tools. For example, you could post a link to a video tutorial or blog article about a package. You can also post ideas, like feature requests or new tools. Best of all, package developers are notified when you post your ideas and resources, and you can comment and discuss posts with the community. Take a look at this video to learn more: https://www.vipm.io/posts/664960df-f111-4e13-989a-24be8207182d/

    • By javier_r
      Hello everybody!
      Wondering how many people have tried the new vipm.io site. We have added a ton of features to make it easy to Discover LabVIEW Tools and there are some cool ones coming soon.
      Check it out and let me know what you think 😀
       
      Javier

    • By dblk22vball
      I am using the newest version (2020.1) of VIPM, but I had this same issue with the release of 2020.
      For two of the packages that I have created for internal repos, VIPM has decided that I need a System Package.   The posts I have seem from JKI indicate that this is a sub-package that is used internally to the main package, and should be automatically included.
      However, after I am seeing issues on any PC other than the PC where the package was built.
      Is there a setting I am missing?
       
      Showing the (System) package as a dependency:

       
      Package Configuration in the VI Package Configuration Editor
       

       
      Package installed, on the PC where the package was initially created (no issues, no exclamation mark)
       

       

       
      Package when installed on another PC (NOTICE: the System Package name has changed and there is a red exclamation mark, but there are no errors shown on install of the package).

       


    • By ThomasGutzler
      Hi,
      Over night something changed on my windows 10 build server and I can now no longer open VIPM. It just shows the splash screen and then closes again.
      Here's the log file:
      =========== START of VIPM 2018.0.0 (build 2025) Error Message ===========
      An internal VIPM 2018.0.0 (build 2025) Error has occured on: Tuesday August 20, 2019 at 03:19:48 PM
      = Automated Message Start = 
      Error 8 occurred at Open/Create/Replace File in NI_LVConfig.lvlib:Parse Config to 
      Queue.vi->NI_LVConfig.lvlib:Load.vi->NI_LVConfig.lvlib:Open Config Data 
      (compatibility).vi->DDEFA056211BA4DA4D215C322E067D90->621BFCD461979D3C7127139A69154E03->762BBE85A007
      171D5A65B48289D23361->46803A2448FAC5F85BFF8F5C199E9C6F->OGPM 
      Class.lvlib:7D7C5CD8C5D361C01081DF5613237E15->OGPM 
      Class.lvlib:D69AB3997B80ACD75689430E3922612C->OGPM Class.lvlib:OGPM Init.vi->VIPM Splash.vi
      Possible reason(s):
      LabVIEW:  File permission error. You do not have the correct permissions for the file.
      =========================
      DMA hardware error detected.
      C:\ProgramData\JKI\VIPM\cache\ngene_lib_deepltk_fpga_addon-1.0.0.45.spec
      = Automated Message End =
      = User Defined Message Start = 
          Error(s) Generated in Splash Window
      = User Defined Message End =
      = Error Handler Call Chain Start =
          VIPM Splash.vi
      = Error Handler Call Chain End =
      =========== END of VIPM 2018.0.0 (build 2025) Error Message ===========
      Any idea where the files are that it doesn't have the right permissions for?
    • By JKSH
      This is an offshoot of https://lavag.org/topic/19414-can-i-save-as-a-vipb-file-in-vipm-and-keep-the-old-palette-if-i-change-the-source-directory/. That thread discusses hand-modifying the XML data in a *.vipb file, which Jim Kring himself seems to accept as a viable solution in some cases. However, when I try that, VIPM says, "VI Package Builder was unable to open the build spec due to an error."
      I initially thought this was new behaviour introduced in VIPM 2016, but downgrading to VIPM 2014 SP2 didn't change anything. I'm now unable to downgrade any further, as my PC is convinced that 2014 SP2 is still installed (even though it's not...)
      Could someone kindly try the attached *.vipb file and see if it opens? It's a bare minimum default file, with only a description summary added. I've hand-modified the summary from "Lorem ipsum" to "Larem ipsum" and now VIPM refuses to open it.
      Thanks!
       
      Dummy.vipb
×
×
  • Create New...

Important Information

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