Quantcast
Channel: LabVIEW topics
Viewing all articles
Browse latest Browse all 69380

Windows, RT, and packed libraries

$
0
0

I'm trying to generate a common codebase for use across many test systems. These systems run both Windows and NI Linux RT. There are many code modules and low level libraries that do literally the same thing whether on a PC or an RT target. We started to use packed libraries recently but these are posing challenges when designing code to be cross target. Since PPL's are compiled code, they have to be compiled for specific target type. In one case, I've made two PPL's, one for Windows and the other for RT. I've added conditional disable structures in the main vi so the proper PPL is called depending on what target the vi runs on. However, LabVIEW tells me every time I open the vi that it can't load compiled code for a target other than what the vi is running on. Is there a way around this? The intention of the PPL's was to keep code modular (plug in style) and protect from inadvertent changes.

 

Likewise, if I want to build another layer of PPL but within the library there exists these conditional disable structs, am I asking for trouble? 

 

Any suggestions for developing common code across targets with the goal of modular and protected code? 

 

LV2017, PC's and cRIO-903x's


Viewing all articles
Browse latest Browse all 69380

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>