Re: [lwip-users] compiling makefsdata.c

[Marc Severo]

> -----Original Message-----
> From: address@hidden [mailto:lwip-
> address@hidden On Behalf Of Nico Sachs
> Sent: Thursday, July 26, 2012 10:08 AM
> To: address@hidden
> Subject: [lwip-users] compiling makefsdata.c
>  
> I've tried to build this file with a gcc toolchain that comes from the
> Posix windows environment cygwin.
> In the makefsdata.c i've seen that this code has some includings from
> the lwip code which should be in the same directory as the contrib
> directory.
> 
> in makefsdata.c there are sourcefiles *.c included, which have other
> includings from lwip. So the compiler needs those including paths
> configured.
> 
> I do not know if this is the correct way doing this. Do i have to
> include the whole lwip code to just compile makefsdata.c? In this case
> i think it would be better to create a makefile for this one. But i
> don't think that this was the plan for makefsdata.c



You shouldn't need to compile the whole lwip code to compile makefsdata.c;
makefsdata.c is my only source file being compiled in that project.

But you do need some of the lwip source handy so that makefsdata.c can
include the necessary c files in its compile. If your lwip source is in a
folder called "lwip" and the lwip and contrib folders are in the same
location, the #include ../../../../lwip/ should work itself out. You will
likely need to add some additional include paths to make everything happy.
For me it looks like:
./lwip/src/include/ipv4
./lwip/src/include
./contrib/ports/win32/include (for an example lwipopts.h)

Marc