From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20082 invoked by alias); 10 Jan 2013 13:16:43 -0000 Received: (qmail 20057 invoked by uid 22791); 10 Jan 2013 13:16:42 -0000 X-SWARE-Spam-Status: No, hits=-4.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-lb0-f175.google.com (HELO mail-lb0-f175.google.com) (209.85.217.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 10 Jan 2013 13:16:38 +0000 Received: by mail-lb0-f175.google.com with SMTP id gg13so458509lbb.20 for ; Thu, 10 Jan 2013 05:16:37 -0800 (PST) X-Received: by 10.112.83.202 with SMTP id s10mr30057889lby.101.1357823797114; Thu, 10 Jan 2013 05:16:37 -0800 (PST) Received: from [192.168.178.23] (217-75-21-200.pool.cyberlink.ch. [217.75.21.200]) by mx.google.com with ESMTPS id bf3sm797556lbb.16.2013.01.10.05.16.35 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Jan 2013 05:16:36 -0800 (PST) Message-ID: <50EEBF34.4040701@gmail.com> Date: Thu, 10 Jan 2013 13:16:00 -0000 From: Bob Brusa User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: ecos discuss Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: [ECOS] uint32_t and similar definitions are not resolved in eclipse X-SW-Source: 2013-01/txt/msg00011.txt.bz2 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