LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Best Method for Deploying/Distributing non-LabVIEW Code?

Solved!
Go to solution

I have written some methods in LabVIEW that make calls to Python to do some tasks a colleague wrote up and it's quite nice and fluid.  I have the Python src in my project and have a proper folder structure with project as root.  The plan is to distribute as a packed library (or it was).  In the project the python source and labview source are all inside an .lvlib and from there, I am attempting to make a packed library from the lvlib.  However, when it is built, the python src and all necessary files for it are just in the folder with the packed library.  Having lost its own necessary folder structure.  But now my code doesn't know how to find it as it is assuming the packed library as root.  What is the better or best method to distribute and deploy labview with python scripts?  Are there tricks in the packed library build properties I am unaware of?

0 Kudos
Message 1 of 2
(654 Views)
Solution
Accepted by topic author LuminaryKnight

NVM - resolved.  Just needed to build the destinations and source file settings properly.

0 Kudos
Message 2 of 2
(639 Views)