-
Posts
11 -
Joined
-
Last visited
-
Days Won
1
Posts posted by LogMAN
-
-
I'm running VIPM BETA (build 2746), which shows an unusual average CPU load of 3-5% when the package manager is open and 10-15% when a package build specification is open. These values are a bit too high for my taste.
A comparison with VIPM 2019 shows an average CPU load of 3-5% in both cases.
-
I have upgraded to the latest build 2746 and can confirm that it is working now 👍
-
Great job!
Built 2746 properly disables the save button during the build process.
-
I did a few more tests and found that the build fails only when there is a accompanying .vipc file (even if that file does not specify any dependencies). Recreating the file does not fix the issue. The only workaround I found is to manually add dependencies.
For comparison, here is a project for which the build succeeds (dependencies were added manually).
-
So there is this new checkbox which isn't explained anywhere.
What does it do?
- 1
-
You can clone the repositories from GitHub and try yourself:
- https://github.com/LogMANOriginal/LabVIEW-Composition
- https://github.com/LogMANOriginal/JSONtext-Object-Serialization
I should probably mention that I'm using LabVIEW 2021 BETA (21.0b10) for the build.
-
Not sure if I'm doing something wrong, but the build process always fails for me and the error message is not helpful (see below).
I have mass-compiled the project and found no broken VIs (build passes with VIPM 2019.0.0).
Steps to reproduce
- Open a package build specification
- Press Build Package
- 1
-
The final message might be due to the build actually failing. I receive the same error when I don't try to break things.
-
Steps to reproduce
- Open package build specification
- Increment the package version (save button must be active - don't press it yet)
- Press Build Package
Notice that the save button is active during the build process.
- Press Save Package Project
The configuration is saved and the dialog will return to edit-mode (build process is still running).
After a few seconds the build process fails with an error.
-
Thanks!
By the way, the link on the download page still says "VIPM 2020", although it correctly links to the 2021 discussion forum.
- 1
Remove Block Diagram after Build with VIPM
in VI Package Manager (VIPM)
Posted
Cross-post: https://lavag.org/topic/22821-remove-block-diagram-after-build-with-vipm
Please always include links when posting in multiple forums.
This appears to be a potential bug in newer versions of VIPM. Here is a related topic: