lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [lwip-users] hi - compiling lwip questions...


From: Vasuki Setlur
Subject: RE: [lwip-users] hi - compiling lwip questions...
Date: Sun, 7 Mar 2004 17:56:47 -0800

Wot is the version of lwipp u r using?
Also check the from the compiler manual, if it supports the attribute directive.
Can u also pls send out the exact compilation error ur getting
-----Original Message-----
From: address@hidden [mailto:address@hiddenOn Behalf Of Eric Shufro
Sent: Thursday, March 04, 2004 7:58 AM
To: address@hidden
Subject: [lwip-users] hi - compiling lwip questions...

I am new to lwip and have many questions. I have read most of the documentation, but the puzzle is still a bit unclear.

 

For starters, after downloading the distribution from Savanna, what other files are necessary?

 

I found a port of lwip for UCOS-II which I currently have running well on a Motorola hcs12 microcontroller.

 

The port contained lib.c, sys_arch.c cc.h, perf.h and sys_arch.h.

 

I found cpu.h, debug.h, and lwipopts.h by searching the web (after getting compiler errors that they were missing)

 

I am unsure what lwip files I need to actually include into my project. Do I just use the files in the API directory? I read the docs and noticed a description of how to send and receive using different api’s, but some of these functions are in tcp.c – do make calls to the functions in this file?

 

Its quite unclear at this point.

 

Additionally, when I try to compile sockets.c, I get all kinds of errors like ; missing and typdef name expected, type specifier mismatch, missing ) etc.. in ip_addr.h in this area…

 

PACK_STRUCT_BEGIN

struct ip_addr {

  PACK_STRUCT_FIELD(u32_t addr);

} PACK_STRUCT_STRUCT;

PACK_STRUCT_END

#ifdef PACK_STRUCT_USE_INCLUDES

#  include "arch/epstruct.h"

#endif

 

/* For compatibility with BSD code */

struct in_addr {

  u32_t s_addr;

};

 

I don’t see anything obviously wrong, but I am new to this and don’t really understand the pieces fully.

 

Thanks for the help,

 

--eric shufro


---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.594 / Virus Database: 377 - Release Date: 2/24/2004


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.594 / Virus Database: 377 - Release Date: 2/24/2004


reply via email to

[Prev in Thread] Current Thread [Next in Thread]