liblo-devel Mailing List for LibLO

Hi,

On Wednesday, November 10, 2010 12:32:21 am Stephen Sinclair wrote:
> Cool to hear about your port, if you have any suggestions for what can
> be changed to support embedded systems please let us know!

* Do not use the GNU autotools, which actually make porting harder on "exotic" 
and/or non-GNU platforms. Since you have few source files, in my opinion a 
plain Makefile would suffice and people can easily hack it to port liblo to their 
new platform. I can also suggest you write your own "configure" script from 
scratch if you want to stick to the de-facto standard, instead of using the 
unmodifiable gibberish puked out by autoconf.
* Separate the code into a "networking" part and a "core" part that does the 
parsing, registering/calling methods, etc. So people wanting to use liblo on a 
system with a non-UNIX-like IP stack (LWIP etc.) or with a lighter one (like 
RTEMS that I'm using, which does not support many features needed by liblo) 
can use the "core" part only and hook it to their custom networking code. 
You'll also want to make the "address" type opaque when used in the message 
structure, so that the "core" part is totally network independent.
For my port I basically stripped out all the networking code from the library 
and re-implemented it in the application. I'm aware this isn't very upstream-
friendly, but I have a product to get out of the door, lots of work and 
lacking time and developers, so I just took the fastest option.

Kind regards,
S.

On Tue, Nov 9, 2010 at 7:58 AM, Sébastien Bourdeauducq
<seb...@mi...> wrote:
> Hi,
>
> I am developing a port of liblo for embedded systems (see
> https://github.com/lekernel/liboscparse) and I'm quite surprised to see that
> lo_server_free does not try to free memory allocated by any queued events.
> Won't this cause a memory leak if lo_server_free is called when events are
> queued?

Possibly, I'd have to investigate further.  Feel free to patch it ;)

Cool to hear about your port, if you have any suggestions for what can
be changed to support embedded systems please let us know!

Steve

Hi,

I am developing a port of liblo for embedded systems (see 
https://github.com/lekernel/liboscparse) and I'm quite surprised to see that 
lo_server_free does not try to free memory allocated by any queued events. 
Won't this cause a memory leak if lo_server_free is called when events are 
queued?

S.