Dynamically Linked Libraries

[JamesTerm]

Originally Posted by wireties

The great advantage of shared libraries is that there is only one copy in physical memory, hard to see that as an issue in FRC since there is only one user application running in user space (besides the system and NI daemons).

An example of that... (i.e. an issue in FRC when multiple instances occur due to a static library setup)... would be if someone wishes to use SmartDashboard... I had SmartDashboard in its own library as static... in my win32 environment, and had multiple DLLs in use. Network Tables must have only one instance to work properly... so I had to make a DLL version of it to work correctly... luckily this was all win32 environment so it was easy to do.

For the eclipse environment if something similar needed to be done (which I couldn't see happening, but could if all vision processing was done on roboRIO)... The static library solution may not work... in which case the one project multi folder technique may give the best results... so far I've been leaning towards that as a workflow. I'm going to thank Jeff Downs for that suggestion from his workflow tips on the eclipse old cRIO solution. It gives the benefit for shared libraries, while allowing code to be separate... built time is still very fast too.