You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addition to the LLBs actually used for deployment, the EDS custom device build produces the following directories.
JKI JSON Serialization.lvlib_JSON Deserializer
JKI JSON Serialization.lvlib_JSON Lexer
JKI JSON Serialization.lvlib_JSON Parser
JKI JSON Serialization.lvlib_Lexer
JKI JSON Serialization.lvlib_Parser
JKI Serialization.lvlib_Deserializer
NI_Data Type
VariantType
These are all due to name collisions between items in the different lvlibs and deprecated files in the GXML dependency. We should try to find a way to eliminate all these extra directories and get everything into just the LLBs.
The text was updated successfully, but these errors were encountered:
The JKI JSON tool (which was used in this version of VS) has this issue. However, before trying to fix that, I would strongly advise to move away from the JKI and use RapidJSON tool. This will allow higher configuration speeds, it will allow you to load the Capabilities Offline, and possibly will fix this issue above. The only problem is that you have to "drop" support for versions before LV/VS 2017 since the UI doesn't support previous versions. Also, keep in mind that there is a new API from SLSC R&D that allow you to integrate those changes better: https://github.com/ni/slsc-capability-explorer
In addition to the LLBs actually used for deployment, the EDS custom device build produces the following directories.
These are all due to name collisions between items in the different lvlibs and deprecated files in the GXML dependency. We should try to find a way to eliminate all these extra directories and get everything into just the LLBs.
The text was updated successfully, but these errors were encountered: