07-14-2017 04:25 PM
Hi,
I have two built applications that use code in a Labivew library (lvlib). Currently, I include the lvlib in my two labview projects.
However, the code in the lvlib gets updated frequently. Every time it gets updated, I need to re-compile the two applications. It also becomes annoying to record the changes and do version control for two applications when only the shared code changes.
I am thinking to separate the code in the lvlib from the built applications. The applications just dynamically load the code when needed. This way I can have changelog and version control for the two applications and lvlib. So I can create three installers for the user.
What is the best way to achieve this? Should I use the source code distribution for my code in lvlib? If so, is there a way to create an installer for the source code? Or use .dll. or some packaged library? I can do more research if I know my options.
Thanks,
Joseph
Solved! Go to Solution.
07-14-2017 06:38 PM
I would build into a Packed Project Library (PPL). Then you just update that one file in the installed applications without needing to update the executables.
08-22-2017 05:59 PM
@crossrulz wrote:
I would build into a Packed Project Library (PPL). Then you just update that one file in the installed applications without needing to update the executables.
Tried packed project library and it works great!
Thanks,
Joseph