Open mpokorny opened 7 years ago
This wouldn't be worth the effort at this stage, because the vys configuration file has but a single element, and the vys.h file defines just 5 structures,10 functions (one being a pure utility function), and a few supporting macros. It's probably not a significant issue for any user that wants to use libvys but not libvysmaw to just build and install this entire project. The set of users writing applications of that sort currently very likely contains only me! Gonna label this as wontfix.
Split out the vys
configurationlibrary into its own project. This might be overkill, but it would be the cleanest way to export that functionality for use by the CBE.