Jump to content

Recommended Posts

Hi all,

I wrote some code that uses functionalities from lvanlys.dll, so it appears as dependant item in project explorer just like other dlls that I'm linking to (e.g. nivision.dll).
When I want to distribute my code as lvlib, lvanlys.dll is copied to destination directory (and worse it becomes part of the lvlib) what causes future conflicts in a project where I use created library. No other dlls are acting like this, only lvanlys.dll. What is the difference between them? How i can avoid of copying this file?

Best regards,

Link to comment

Thanks for reply.

I'm not using any Call Library Function Node directly. lvanlys.dll jumps into dependences automatiacally when I place some standard LV functions, e.g. mean.vi. Similar situation takes place when I use one of NI Vision VI but with this difference that "vision.dll" isn't included to my source distribution.

Best regards,

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.