Cross post from NI forums:
I have project file that includes lvlibp library, functions from inside are called from many places inside application.
Now this library resides in directory A, I want to do disk cleaning and load the same PPL but from another place on disk.
I have played with it and I can not do this... When I remove currently used ppl it goes to dependencies. When I add to project library from new path there is hundreds of confilcts that can not be resolved.
Is there a simple catch that I am missing?
I have an application that uses PPL (Packed project library). During the build process of my application LabVIEW copies the PPL to build/My App Folder/data. I can run the application afterwards. If the PPL is deleted or moved later from this ../data/ directory I no longer can run the app.
Is there a way to dynamically link and load PPL from another location? I've tried using viSearchPath for this but unfortunately it doesn't work.
also posted here http://forums.ni.com/t5/LabVIEW/Create-a-link-to-PPL-Packed-Project-Library-in-Application/td-p/3555902
Anyone using, are there recommendations or tips to share? Following to my whines for a serious internal SCC, I got my IT to install Gitlab CE on an internal server, and I'm happily tucking with it so far. I see that Gitlab should have a product called Gitlab CI (continuous integration) as well as the option of webhooks to external services, I wonder what else it would take to have the functionality working, with private availability of the build. E.g. which build script, where sits LV, cross-platform builds if relevant, periodicity of the build (every commit? nightly? tagged? only last?) etc.
General pointers to how automated builds (specifically LV) are handled by other SCC also appreciated, for my education.