Jump to content

Call Library Function Node 32- and 64-bit


Recommended Posts

I'm developing a library that ships with 32- and 64-bit DLLs. In LabVIEW, I use Call Library Function Node with mylibrary*.*, which picks mylibrary32.dll and mylibrary64.dll correctly, depending on LabVIEW's bitness.


When I use the VIPM, the path "mylibrary*.*" gets overwritten to "mylibrary32.dll." So the installed code doesn't work correctly on 64-bit LabVIEW. Is this a known issue? Is there a workaround or a fix?

Link to comment
Share on other sites

  • 2 months later...

Hi Michael,


I have the same issue the VIs use to build the VI packages use the * wildcard to make the reference to the shared library platform independent. During the VIP build process it seems that LabVIEW replaces the reference by the appropriate file extension and the appropriate bitness (32 or 64).


There is an option on Source File Settings page called Do Not Compile on Build which should avoid this behavior but it is not included in the Free version :(

Link to comment
Share on other sites

  • 4 weeks later...
  • 5 years later...
  • 11 months later...

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.