From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20291 invoked by alias); 12 Oct 2007 10:33:57 -0000 Received: (qmail 20282 invoked by uid 22791); 12 Oct 2007 10:33:56 -0000 X-Spam-Check-By: sourceware.org Received: from ug-out-1314.google.com (HELO ug-out-1314.google.com) (66.249.92.173) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 12 Oct 2007 10:33:48 +0000 Received: by ug-out-1314.google.com with SMTP id 23so569059ugr for ; Fri, 12 Oct 2007 03:33:45 -0700 (PDT) Received: by 10.78.159.7 with SMTP id h7mr2125488hue.1192185224878; Fri, 12 Oct 2007 03:33:44 -0700 (PDT) Received: by 10.78.202.7 with HTTP; Fri, 12 Oct 2007 03:33:44 -0700 (PDT) Message-ID: Date: Fri, 12 Oct 2007 10:33:00 -0000 From: "=?ISO-8859-1?Q?=D8yvind_Harboe?=" To: "eCos Discussion" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Google-Sender-Auth: d26fc85e6fc3725b 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] Problems with application to use lwIP X-SW-Source: 2007-10/txt/msg00070.txt.bz2 I'm trying to use lwIP, but I run into problems because lwIP uses macros, e.g. #define read(a,b,c), which screws things up. I've seen some posts about people wishing for/thinking about making lwIP more compatible with a "standard" eCos TCP/IP stack. Rather than try to adapt the code that is going to use lwIP(it currently uses eCos FreeBSD + POSIX) or changing lwIP, I was wondering if I could somehow pull off the following: - Use the standard include files from eCos instead of lwIP include files so application continues to compile fine. - Link w/lwIP only instead of trying to compile with it. This would require adding a .c file that implemented functions that used the lwIP include files and exported function calls that were compatible with lwIP. Any thoughts on this approach? lwIP is attractive to us as it is small enough to fit into the fastest RAM available for our project, we do have enough RAM for FreeBSD, but it is dog slow as it needs to use DRAM instead of SRAM. --=20 =D8yvind Harboe http://www.zylin.com - eCos ARM & FPGA developer kit -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss