int32 CVICALLBACK EveryNCallback on gcc

[cylnu]

Hello,

I am configuring a code for continuous sampling using NI-DAQmx (6255). In the ANCI C sample codes, the following is used:

int32 CVICALLBACK EveryNCallback(...

Is this only for CVI environment or can I use it on gcc too?

Cheers

[andmboa7]

Reference here:

https://forums.ni.com/t5/Multifunction-DAQ/How-Can-I-Use-The-NI-DAQmx-ANSI-C-Function-Library-With-G...

Using NI-DAQmx in Text Based Programming Environments

https://www.ni.com/en/support/documentation/supplemental/21/using-ni-daqmx-in-text-based-programming...

Learn 10 Functions in NI-DAQmx and Handle 80 Percent of Your Data Acquisition Applications

https://www.ni.com/en/support/documentation/supplemental/06/learn-10-functions-in-ni-daqmx-and-handl...

How Can I Use the NI-DAQmx ANSI C Function Library with Borland C and Delphi?

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P9udSAC&l=en-US

[cylnu]

Nope, I have already generated the necessary library for the gcc compiler. I just want to know whether  " int32 CVICALLBACK EveryNCallback " works on gcc. I am not sure since it calls CVICALLBACK. I was able to compile the sample code. But I dont know if it will work fine with the device.

[bstreiff]

CVICALLBACK is just a #define to (ultimately) tell the compiler to use the __cdecl calling convention:

#if defined(__linux__) || defined(__APPLE__)
#define __CFUNC
#define __CFUNC_C
#define __CFUNCPTRVAR
#define CVICDECL
#define CVICALLBACK     CVICDECL
#else
#define __CFUNC         __stdcall
#define __CFUNC_C       __cdecl
#define __CFUNCPTRVAR   __cdecl
#define CVICDECL        __cdecl
#define CVICALLBACK     CVICDECL
#endif

Assuming that gcc understands the __cdecl keyword it should work fine.

(In this context "CVICALLBACK" isn't specific to CVI, it refers to any C environment. The "CVI" prefix is present for historic reasons.)