64 bit library NIDAQmx.lib in a UNIX format ".a" ?

[INGDEV]

Hello,

Currently in a software migration time, I have to compile a 64 bit application with a C++ IDE programming software (Embarcadero C++ builder 10.2). I found the files NIDAQmx.lib in a 32 and a 64 bit version under the installation directories: C:\Program Files (x86)\National Instruments\Shared\ExternalCompilerSupport\C\lib64(or lib32)\msvc\NIDAQmx.lib.

But, for a compilation on a 64 bit target platform, this IDE programming software is able to work only with a UNIX format of libraries with respectively,  an extension ".a" (replacement of ".lib" which works on 32 bit) to compile an executable for all platforms types.

So, after read a lot of posts about this topic, two solutions are available :

1. A first solution is to create manually a library 64 bit ".a" by a specific tool named MKEXP.exe (that is provided by embarcadero) but I need the source file(s) NIDAQmx.dll or ".def" that is not available under the respective installation directories of NI.Therefore, my request is, could-you provide us the source file ".dll" or where can I find it ? (standard solution when we are using external libraries...)

2. A second solution is, could you provide us directly a 64 library file with the extension ".a" or where can I find it? 

For information, right now, we are working on Windows 10 - 64bit version and have to do a migration to 64 bit for approximately 60 stations with hardware acquisition boards from NI.

Please, let me know if you have any question?

Best regards,

S.Ruchet

[DesasterMaster]

Hi,

here is were you can find the location of the 64bit library:

Compile Linking Error 64-bit NI-DAQmx C Lib File Location - National Instruments

The 64bit lib is a native 64bit lib, there is no a file available.

[bstreiff]

The NIDAQmx.lib import library refers to entrypoints in the library "nicaiu.dll"[1], which is installed into the Windows System32 or SysWOW64 directories by the NI-DAQmx runtime installer. I don't know about the Embarcadero compiler, but I think this might be sufficient for your "mkexp" tool.

[1] Yes, this is not really an intuitive name, but unfortunately it can't change because of historic reasons.