LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Shared code between two built applications

Solved!
Go to solution

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

0 Kudos
Message 1 of 3
(2,465 Views)
Solution
Accepted by topic author joezhang

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.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 2 of 3
(2,437 Views)

@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

0 Kudos
Message 3 of 3
(2,278 Views)