* [ECOS] uint32_t and similar definitions are not resolved in eclipse
@ 2013-01-10 13:16 Bob Brusa
0 siblings, 0 replies; only message in thread
From: Bob Brusa @ 2013-01-10 13:16 UTC (permalink / raw)
To: ecos discuss
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-01-10 13:16 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-01-10 13:16 [ECOS] uint32_t and similar definitions are not resolved in eclipse Bob Brusa
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).