Re: [lwip-users] Issue in err.c for lwIP 2.0.0

2016-11-30 Thread Dirk Ziegelmeier
No, the solution is in errno.h: Choose one of: - #define LWIP_PROVIDE_ERRNO 1 - #define LWIP_ERRNO_INCLUDE "path/my_header_file_containing_errno.h" HTH Dirk On Wed, Nov 30, 2016 at 7:45 PM, Amit Ashara wrote: > Hello All, > > When integrating FreeRTOS with lwIP 2.0.0 the following gives an e

[lwip-users] Useful web server for Netconn API

2016-11-30 Thread Brian Stull
Hi everyone, I'm wondering if anyone has had success getting an HTTP server working using the Netconn API. I know there is an example program using the Netconn API but it is too basic to be of much use for me. I do have it up and running but it doesn't include any support for POST, header decoding

[lwip-users] Issue in err.c for lwIP 2.0.0

2016-11-30 Thread Amit Ashara
Hello All, When integrating FreeRTOS with lwIP 2.0.0 the following gives an error for missing defines. #if !NO_SYS /** Table to quickly map an lwIP error (err_t) to a socket error * by using -err as an index */ static const int err_to_errno_table[] = { 0, /* ERR_OK 0

Re: [lwip-users] Issue in arch.h for lwIP 2.0.0

2016-11-30 Thread Amit Ashara
Hello Freddie That helped too. I added the include in the arch/cc.h for the device port. Regards Amit On Wed, Nov 30, 2016 at 3:14 AM, Freddie Chopin wrote: > On Wed, 2016-11-30 at 07:45 +0100, Dirk Ziegelmeier wrote: > > I added it, thanks for reporting! > > It was behaving the same way in th

Re: [lwip-users] Issue in arch.h for lwIP 2.0.0

2016-11-30 Thread Amit Ashara
Hello Simon We are using 1.4.1 and we get a lot of queries on when we will migrate to 2.0.0 The other being to correct the LLDP stack as was being discussed in the Another thread. Regards Amit Ashara > On Nov 30, 2016, at 6:58 AM, Simon Goldschmidt wrote: > > Amit Ashara wrote: >> Is ther

Re: [lwip-users] Issue in arch.h for lwIP 2.0.0

2016-11-30 Thread Simon Goldschmidt
Amit Ashara wrote: > Is there going to be an incremental release of lwIP Yes. 2.0.1 will be coming as soon as we'll need it (i.e. as soon as there are enough bugs fixed from 2.0.0 to justify releasing it). The time from 1.4.1 to 2.0.0 was way too long. This mainly was because the integration of

Re: [lwip-users] Issue in arch.h for lwIP 2.0.0

2016-11-30 Thread Amit Ashara
So what is the final solution. Adding the stdlib.h in arch/cc.h or as what Dirk has made changes? Is there going to be an incremental release of lwIP or should I make the same changes as Dirk and use lwIP-2,0.0 ~Amit On Wed, Nov 30, 2016 at 4:34 AM, Dirk Ziegelmeier wrote: > Since it was alrea

Re: [lwip-users] Issue in arch.h for lwIP 2.0.0

2016-11-30 Thread Dirk Ziegelmeier
Since it was already included in several lwIP .c/.h files, I simply decided to move it to a central place: arch.h. So my change should not break anything or make lwIP less portable as it was before. Dirk On Wed, Nov 30, 2016 at 11:07 AM, Simon Goldschmidt wrote: > Freddie Chopin wrote: > > It

Re: [lwip-users] Issue in arch.h for lwIP 2.0.0

2016-11-30 Thread Simon Goldschmidt
Freddie Chopin wrote: > It was behaving the same way in the git version prior to 2.0.0 and I > guess the "standard" approach to that was to include in your > arch/cc.h file. I think that such issue was reported to the mailing > list in the past and that was the suggested approach. It was like tha

Re: [lwip-users] Issue in arch.h for lwIP 2.0.0

2016-11-30 Thread Freddie Chopin
On Wed, 2016-11-30 at 07:45 +0100, Dirk Ziegelmeier wrote: > I added it, thanks for reporting! It was behaving the same way in the git version prior to 2.0.0 and I guess the "standard" approach to that was to include in your arch/cc.h file. I think that such issue was reported to the mailing list