Jump to content

Michael

Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. 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?
  2. 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?
×
×
  • Create New...

Important Information

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