unsubscribe On Tue, Nov 26, 2024 at 3:21 AM Slava Knyazev <sl...@knyazev.io> wrote:
> unsubscribe > > > > On Nov 25, 2024, at 4:50 PM, Paolo Amarillento <o7...@yahoo.com.INVALID> > wrote: > > > > unsubscribe > > > > > > > > > > > > > > > > On Monday, November 25, 2024 at 09:21:17 PM GMT+8, V R < > veneree.randrianari...@gmail.com> wrote: > > > > > > > > > > > > unsubscribe > > > > Le lun. 25 nov. 2024, 00 h 10, Adamus, Piotr > > <piotr.ada...@brooks.com.invalid> a écrit : > > > >> Hi Jens, > >> Yes, I contacted Chris. He was very helpful and confirmed that currently > >> the C++ implementation would need some work to optimize it for size. > >> He wasn’t aware of any “pure C” Thrift implementations that would work > >> under Zephyr. C Glib is the closest but that hasn’t been ported to > Zephyr > >> so far. > >> > >> At the moment, It looks like the only option for Thrift under Zephyr is > >> C++ which is a bit big, unfortunately. > >> > >> > >> On 2024/11/14 11:34:55 Jens Geyer wrote: > >>> Hi, > >>> > >>> I See. Did you try to contact cfried? He's way more an expert in that > >> matter. > >>> > >>> JensG > >>> > >>> Sent from mobile device. > >>> ________________________________ > >>> From: Adamus, Piotr <pi...@brooks.com.INVALID> > >>> Sent: Thursday, November 14, 2024 2:01:55 AM > >>> To: user@thrift.apache.org <us...@thrift.apache.org> > >>> Subject: RE: Question about Thrift support for plain C and binary image > >> size of the example Zephyr code > >>> > >>> Hi Jens, > >>> > >>> Thank you for your response. > >>> > >>> I looked at the the c_glib implementation but it requires Glib ( > >> http://www.gtk.org/) and that doesn't seem to be available for zephyr - > >> happy to be corrected here if I missed something. > >> > >>> > >>> Thank you for the suggestion. I will reach out to Chris. > >>> > >>> Best regards, > >>> Piotr A. > >>> > >>> Hi, > >>> > >>> there is a c_glib implementation, did you try that one? > >>> > >>> > binary size when compiling for Zephyr [...] Does anyone know any > good > >> strategies to minimize [...] > >>> > >>> You may want to contact https://github.com/cfriedt, he has implemented > >> a bunch of stuff in Apache Thrift for Zephyr. > >>> > >>> Have fun, JensG > >>> > >>> > >>> Am 06.11.2024 um 04:11 schrieb Adamus, Piotr: > >>>> Hi All, > >>>> > >>>> I am currently investigating/learning Thrift and wanted to ask whether > >> anyone knew any good Thrift implementation in pure C (if it exists… 😊 > )? > >> > >>>> If not, does anyone know if there are any plans to introduce it in the > >> near future? > >>>> > >>>> Also, I wanted to ask about binary size when compiling for Zephyr. > >> After building the example code I realized that the binaries are ~400kB > for > >> TCP/IP. Does anyone know any good strategies to minimize the size of the > >> code in this environment? > >> > >>>> I tried enabling aggressive size optimization and played with some > >> other settings but only managed to shave ~15kB of space. > >> > >>>> > >>>> I would be very grateful for any help or information. > >>>> > >>>> Best regards > >>>> Piotr Adamus > >>>> > >>>> _____________________________________________________________________ > >>>> > >>>> This email message, including any attachments, may contain > >>>> confidential and proprietary information for the sole use of the > >> intended recipient. If you are not the intended recipient, please notify > >> the sender and delete this message from your system, without making any > >> copy or distribution. Our website and email privacy policy is available > >> athttps://www.brooks.com/privacy > >> > >>> _____________________________________________________________________ > >>> > >>> This email message, including any attachments, may contain confidential > >> and proprietary information for the sole use of the intended recipient. > If > >> you are not the intended recipient, please notify the sender and delete > >> this message from your system, without making any copy or distribution. > Our > >> website and email privacy policy is available at > >> https://www.brooks.com/privacy > >> > >>> > >> _____________________________________________________________________ > >> > >> This email message, including any attachments, may contain confidential > >> and proprietary information for the sole use of the intended recipient. > If > >> you are not the intended recipient, please notify the sender and delete > >> this message from your system, without making any copy or distribution. > Our > >> website and email privacy policy is available at > >> https://www.brooks.com/privacy > >> > >
