Eclipse Community Forums: C / C++ IDE (CDT) » Not your everyday can't resolve uint32

Home » Language IDEs » C / C++ IDE (CDT) » Not your everyday can't resolve uint32_t(type uint32_t could not be resolved)

Not your everyday can't resolve uint32_t [message #1772418]

Fri, 08 September 2017 18:46

Eclipse User

Hello all.

These files compile just fine.

So I get the dreaded red underline and marker in my main.c where I have uint32_t used as a parameter.

I know what the problem is, just not how to fix it.

I look in my CDT Global Build Console
and I see this....

#define __UINT32_TYPE__ long unsigned int

No I believe this is due to the fact that newlib-stdint.h is being included????

I'm not sure... that's my guess and I'm sticking to it...

I just don't know how to fix this.

Thanks.
-stv

Re: Not your everyday can't resolve uint32_t [message #1772605 is a reply to message #1772418]

Tue, 12 September 2017 21:33

Eclipse User

It depends on the compiler used.
unsigned int is compatible with long unsigned int with GCC but not with Visual Studio,

With GCC, uint32_t should be compatible with __UINT32_TYPE__;
It is defined in stdint.h but only if the dialect is c++11 or better
and then only if a long unsigned int is really 32 bits.

GCC example:
index.php/fa/30719/0/

If they are different types with your compiler you may be stuck unless you do a lot of type casting
https://stackoverflow.com/questions/11611467/type-of-unsigned-long-is-different-from-uint32-t-and-uint64-t-on-windows-vs2010

This is off-topic for this forum which is for CDT related problems.
You should address further questions to forums such as stackoverflow.

Attachment: uin32_2017-09-12_21-31-31.png
(Size: 11.38KB, Downloaded 1985 times)

[Updated on: Tue, 12 September 2017 22:01] by Moderator

Previous Topic:	How to Activate a Plugin when leaving the "New Project" Wizard
Next Topic:	OpenOCD compatibility

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Mar 21 11:07:11 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter