DIAdem

cancel
Showing results for 
Search instead for 
Did you mean: 

Linking Error trying to recompile 32-bit DLL with DIAdem GPI

Hello, our team is currently trying to migrate all of our diadem 2017 scripts to diadem 2024. In this process we are trying to adapt our 32-bit dll's to be 64-bit. I have gotten quite close in Visual Studio using the 2017 build tools we used to build the original dll's. However, a handful of functions seem to be going unrecognized as if they aren't defined in the included GPI libraries. I have ensured that I have loaded the libraries and the include folders into visual studio, and tried multiple different ways to load them but to no avail. I've deduced that all of these functions seem to be coming from the gfswemi.lib library included in the diadem GPI extension driver development kit (https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000x0dVCAQ&l=en-US). Any ideas as to what might be the cause for the issue at this point? 

I'm also vaguely aware that there may or may not have been an automated tool to do the 32-bit to 64-bit conversion for these dll's but I cannot find it anywhere. 

OS: Windows 11
Visual Studio 2022 (using VS 2017 build tools)
Windows SDK: 10.0.18362.0

pingu_pongo_1-1738263554170.png

pingu_pongo_2-1738263848439.png

 

 

0 Kudos
Message 1 of 2
(114 Views)

Did you activate Unicode as Codesetting7 in your project.
When I remember right the methods of x64 GPI have an ending W when working with strings.

In your screenshot it is looking for char* without the leading W.

 

So either you are using a wrong header or some settings are not correct.
Ideas:

- unicode

- stdcall or cdecl

 

Maybe this gives some hint.

0 Kudos
Message 2 of 2
(61 Views)