LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

intmax_t and uintmax_t definition

Solved!
Go to solution

This one is more tricky, as I can't do much as far as the code goes.

LabWindows/CVI 2017, I have this code compilation error:

In file included from p:\3. Engineering\3. R&D\70. OCT-MV\3. Development\2 Work\software development\C code\LabWindowsCVI\FASTTEST_GUI\macros.h:5:

"ansi_c.h"(31,1) In file included from c:\program files (x86)\national instruments\cvi2017\include\ansi_c.h:31:

"inttypes.h"(241,1) error: unknown type name 'intmax_t'

 

In inttypes.h the intmax_t and uintmax_t typedefs are used. They both produce this error.

intmax_t and its unsigned sibling are declared in stdint.h, though, and stdint.h is included both in ansi_c.h just before inttypes.h, and in inttypes.h itself!

So, why can't I have them acknowledged in my source code?

 

0 Kudos
Message 1 of 2
(4,483 Views)
Solution
Accepted by topic author MarinoMaiorino

OK, this one is solved (credits to Wolfgang!)

In the early few days of my CVI 2017 installation, after having read here and there that there were issues with the stdbool.h library and other C99 standard ones, I searched through the files installed and found out that some of them were actually provided by the clang compiler.
So I thought I had to add those includes path.

I am currently trailing another problem with bool, false and true (compiler tells me they are not declared, and you can bet I did include stdbool.h), and Wolfgang replied that he didn't do any such thing like adding extra paths. So I went back to Options->Environment...->Include Paths, deleted the extra path line and... no more complaints about intmax_t and uintmax_t!

That's serendipity!
Thank you, Wolfgang!

0 Kudos
Message 2 of 2
(4,478 Views)