> Although do you really mean cygwin? You should only use that for applications that run on cygwin. For tools built > with e.g. arm-elf-gcc, you should use arm-elf-size.
Of course I mean cygwin ;-) (I currently haven't installed the ARM cross-compiler...) > Anyway, in the output of 'size', text is the size of code, data is the size of static/global initialised data, and > bss is the size of static/global data with no specific initialiser (i.e. initialised to 0). Maybe the trouble I have comes from the fact that I'm compiling with (MS-) cl.exe and checking with cygwin size, which seems to get the sections wrong (either data or bss was always 0). I'm currently having some troubles compiling a netif with cygwin gcc, since I don't have the libpcap (and can't find it or any references to it on the net)... I'll check with ARM or NIOS-II, whichever I install first. Simon _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
