It would be nice if vipm supported optional dependencies. This could be done by the use of conditional disable structures. The same could be applied for different OS or bitness or LV Version. Think of some simple cmake switches.
You could define some syntax, and add an option to enable this ability for single VIs. A parser would then scan the VI for CDS, enable the matching page and delete the CDS during deployment. Ideally, vipm would ask the user for his preference for defined options before installation.
This would allow to opt-in additional features, that may not be needed by everyone. And the prackage developer could "burn in" os dependent code, which often leeds to compilation difficulties.
Question
Simon Klein
It would be nice if vipm supported optional dependencies. This could be done by the use of conditional disable structures. The same could be applied for different OS or bitness or LV Version. Think of some simple cmake switches.
You could define some syntax, and add an option to enable this ability for single VIs. A parser would then scan the VI for CDS, enable the matching page and delete the CDS during deployment. Ideally, vipm would ask the user for his preference for defined options before installation.
This would allow to opt-in additional features, that may not be needed by everyone. And the prackage developer could "burn in" os dependent code, which often leeds to compilation difficulties.
Link to comment
Share on other sites
0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.