runtime licence

[GlennPierce]

I have been adding scripting support to my cvi app. To aid this I have created python bindings for the cvi runtime.

I have thought about releasing these bindings but am not sure if this would be allowed / encouraged.

The runtime is freely downloadable as is. However my bindings allow cvi development without the cvi development
environment.

Any advice would be appreciated.

[Sarah_Coleman_NIUK]

Hi,

I believe what you are suggesting would be in violation of our licensing agreement. Is there anyway you can prevent the development of CVI code in your application?

[GlennPierce]

Ok.

It was just a proof of concept.

I will use Gtk instead.

Thanks

[GlennPierce]

Actually Just to be sure is it also against the terms to call into one of your own dll's you create with cvi ?

ie I have an imageviewer dll that I created using cvi that I use in larger microscope application aquisition code can I
call into that dll with python or .Net pinvoke ? Or is that not allowed either or is calling directly into the cvi runtime the only dll I can not do that with ?

Thanks

[Sarah_Coleman_NIUK]

Making calls to a DLL should be fine. You would only be violating the licensing agreement if your tool allowed CVI development. DLLs made with the standard CVI package are freely distributable.

[GlennPierce]

Ok thanks that good enough for me.

Just to be clear we do own a copy of cvi.

PS.

I wont do this

but by the previous logic of allowing a dll you make yourself what would stop one making a thin dll wrapper around the runtime and then calling that dll at runtime.

Ie

My_ProcessMessages -> ProcessMessages
My_NewPanel -> NewPanel
etc ..

🙂

You don't need to answer that.

Thanks I will just call my imageviewer.dll that all the functionality I need.

[Wendy L]

Hello GlennPierce,

Thank you for being forthcoming on this issue.  An official response to your question is that the LabWindows/CVI Run-Time Engine is made available solely for the purpose of running executables or using DLLs created with the LabWindows/CVI development environment.  Use of the LabWindows/CVI Run-Time Engine with your Python bindings would be a violation of the Software License Agreement that is included in the LabWindows/CVI Run-Time Engine installer, and releasing such bindings would be illegal.  For reference, the Software License agreement can also be found at ni.com/legal.

Thanks

[GlennPierce]

Thanks for finding out the details.
I will find someother solution.