LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

CVI version under linux

Hello all,
I just went from 8.0 to 10.0 on both Linux and Windows this morning, so I'm
getting the feel of it.
Thanks for correcting many of the Linux bugs I reported, even if it took so
long, cough, cough.

One thing: _CVI_ is 1000 on Windows but only 1 on Linux. Is that a bug or a
feature ? I rely on some version dependant features, so it breaks them.

Is there a list of all the predefined macros on Linux ? Similar to what we
get on Windows by doing [Build Options][Predefined Macros]
--
Guillaume Dargaud
http://www.gdargaud.net/
0 Kudos
Message 1 of 3
(2,556 Views)
> One thing: _CVI_ is 1000 on Windows but only 1 on Linux. Is that a bug or
> a feature ? I rely on some version dependant features, so it breaks them.

Sorry, I had that has a manual define.

--
Guillaume Dargaud
http://www.gdargaud.net/
0 Kudos
Message 2 of 3
(2,556 Views)

Hi Guillaume,

 

As you've noticed, _CVI_ is not defined when you compile under Linux.

 

You're right, there is very little documentation on which of the CVI predefined macros are available in Linux. We'll be sure to add this to the documentation. In the meantime, these are the macros defined by cvicc, to the best of my knowledge:

 

_NI_unix_ = 1

_NI_linux_ = 1

_CVI_DEBUG_ = 1 (debug builds only)

NDEBUG = 1 (release builds only)

_CVI_C99_EXTENSIONS_ = 0 or 1 (depending on project option)

_TARGET_FILE_VERSION_ = a.b.c.d

_TARGET_PRODUCT_VERSION_ = a.b.c.d

 

0 Kudos
Message 3 of 3
(2,543 Views)