This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
uint32_t and similar definitions are not resolved in eclipse
- From: Bob Brusa <bob dot brusa at gmail dot com>
- To: ecos discuss <ecos-discuss at ecos dot sourceware dot org>
- Date: Thu, 10 Jan 2013 14:16:36 +0100
- Subject: [ECOS] uint32_t and similar definitions are not resolved in eclipse
Hi,
My project uses eCos for a AT91sam7s-based platform, but shows a problem
in eclipse juno: It can not resolve uint32_t and similar definitions.
The file stdint.h of the eCos library I generated has a sequence:
...cut
#if __STDINT_EXP(INT_MAX) == 0x7fffffffL
typedef signed int int32_t;
typedef unsigned int uint32_t;
#define __int32_t_defined 1
cut...
For unknown reasons, the term INT_MAX is not accessible to eclipse and
hence this whole stuff is "ifed" out. The funny thing is, that the build
process is able to resolve these uint32_t etc. Hence somewhere it must
be defined. Does anyone have good advice how to fix that? Its not nice
to have error-cluttered views in eclipse.
Thanks and regards - Bob
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss