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? Quote Link to comment Share on other sites More sharing options...
Benjamin Rouffet Posted March 19, 2015 Report Share Posted March 19, 2015 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 Quote Link to comment Share on other sites More sharing options...
Benjamin Rouffet Posted April 17, 2015 Report Share Posted April 17, 2015 Hi Michael, I just wanted to let you know that I was able to find a workaround the behavior by using Post-Install Custom Action to re-write the DLL path using the wildcard format. Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted December 16, 2020 Report Share Posted December 16, 2020 Updating this thread with an example post-install custom action that modifies Call Library Function Node paths. Example File: Post-Install Custom Action.vi Screenshot: Quote Link to comment Share on other sites More sharing options...
Dataflow_G Posted December 13, 2021 Report Share Posted December 13, 2021 Per this issue over on github, here's a version which attempts to update the CLFN paths of instances of malleable VIs. The instance VI itself can't be edited, so the vim is replaced with the updated CLFN version of itself: It could probably use some tweaking, but the basic idea is there. Post-Install Custom Action.vi Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.