From: Bob Brusa <bob.brusa@gmail.com>
To: ecos discuss <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] uint32_t and similar definitions are not resolved in eclipse
Date: Thu, 10 Jan 2013 13:16:00 -0000 [thread overview]
Message-ID: <50EEBF34.4040701@gmail.com> (raw)
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
reply other threads:[~2013-01-10 13:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50EEBF34.4040701@gmail.com \
--to=bob.brusa@gmail.com \
--cc=ecos-discuss@ecos.sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).