Re: [lwip-users] lwip building on different platforms

[Conover John]

Thanks Marty,

 

                I’ve been doing embedded systems for 20 years so the difficulty is not in understanding the

design of the functional code, but of the build interdependencies.  The lack of documentation in

this area makes it very frustrating trying to use other parts of lwip. The wiki has some very good

information, but what it (and every other place I’ve looked) does not have is a detailed description

of the layout and how some .h files reference other files within the directory tree. This is a condition

of having to support multiple hardware platforms but it does not make it any easier to use (at least

for me.)

                The contirbs area has a lot of great stack examples, but again no make files to help me. It

looks like the lwIP_Demo_Rowley_ARM7 has a make file that I should be able to use.

 

Thanks for the help!

 

John C.

 

 

From: address@hidden [mailto:address@hidden On Behalf Of Pomeroy, Marty
Sent: Wednesday, September 12, 2012 7:45 AM
To: Mailing list for lwIP users
Subject: Re: [lwip-users] lwip building on different platforms

 

 

>>  Does anyone know of examples that have left the original lwip directory  

>>  tree in place and simply referenced it in a make file? 

 

Check out the wiki at http://lwip.wikia.com/wiki/LwIP_Wiki, especially under Getting Started (from that page), the Platform Developer's Manual.  Just be aware that the documentation is a bit like Linux man pages: good enough if you know what you are doing.  Coding and features are the strength of the lwIP community.  So working with this stack is difficult for inexperienced developers.

 

There are examples.  In the FreeRTOS download, lwIP_Demo_Rowley_ARM7 is a 1.1 port that kept the tree.  My port of lwIP 1.4.0 keeps the tree as is.  You can also look in the contrib portion of the sources at http://cvs.savannah.gnu.org/viewvc/contrib/apps/?root=lwip.

 

Adding or dropping files from your build depends entirely on what features you enable in lwip_opts.h.

 

Hope this helps!

 

Marty