04-16-2020 03:19 AM - modifié 04-16-2020 03:20 AM
Hello,
I developped Packed Lib using NI ADCS toolkit (18.5). My customer wants to use it in his LabVIEW project but lvlibp Vis are broken if only the NI ADCS runtime is installed. (It works fine if activate the licence) Any explanation?
LV2016
NI ADCS 18.5
NI XNET 18.5
Thank you
le 05-18-2020 01:51 PM - dernière modification le 12-17-2024 12:09 PM par Content Cleaner
Hello,
No immediate explaination, sorry.
From the product page, I've read "Using the ADCS Toolkit, you can develop a single application and deploy it as often as you like without additional deployment or run-time licenses." So it should be a way to distribute your code, based on this toolkit without deployment licencing (and this toolkit is also not referenced in this page, so...).
Perhaps the way you build your packed library do not include properly the ADCS toolkit components. Check the Addional Exclusions. From my understanding, I guess that Exclude dependent packed libraries and Exclude dependent shared libraries should remain unchecked. that's the default configuration (just chechek with LV 2018), so if you did not modify them, it should be ok.
What does look like the generated files ? (preview screenchot)
Regards,
le 05-19-2020 01:55 AM
Hello Mathieu,
Thank you to take the time to answer me.
I found the solution, I have to load the lvlibp dynamically, build an executable and it works.
It’s not possible to add it directly in LabVIEW project, which is normal after all because it would be too simple to just do a wrapper of the toolkit ans use it for development without licence.
Regards
JP