Michael Posted January 6, 2015 Report Share Posted January 6, 2015 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 More sharing options...
Ashish Posted January 6, 2015 Report Share Posted January 6, 2015 Did you select the correct OS bit version while building the package? https://di0skkm50b972.cloudfront.net/files/54112a85b1fa09d470000001/1c64e7ec8a8f3a625208342f47fae2b2ac79af06-e40e8e634e82fcec551598ed164aae3b7d75cd0e/vipb.png Link to comment Share on other sites More sharing options...
Michael Posted January 6, 2015 Author Report Share Posted January 6, 2015 Yes, I did. Did you select the correct OS bit version while building the package? https://di0skkm50b972.cloudfront.net/files/54112a85b1fa09d470000001/1c64e7ec8a8f3a625208342f47fae2b2ac79af06-e40e8e634e82fcec551598ed164aae3b7d75cd0e/vipb.png Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.