[Olsr-dev] libnetlink, linux and olsr
Fri Oct 19 11:06:36 CEST 2012
Ok. Here's the diff. I must verify a few things with you:
- The way to 'transport' a configuration value to the module is now via
global variables and 'extern' definitions in the yacc file. Which is
IMHO, a kludge - ugly C. I couldn't find an example of how to do this
properly in other lq plugins though.
- I have assumed that the $(OS) definitions as used in the Makefile
aren't somehow mutually inclusive. That is, 'android' doesn't also
- I made adjustments to Makefile.inc in what I don't know are the right
- The configuration names as in the lex file are the result of my
imagination. I camelcased what I thought would be proper. Feel free to
- There is still no way to separate out the older libnl libraries (which
have completely different names). So keep expectations low - I expect
On Fri, 2012-10-19 at 10:33 +0200, Henning Rogge wrote:
> On 10/18/2012 04:48 PM, Kees-Jan Hermans wrote:
> > I have patched the nl80211 link quality module, so that it would be used
> > under linux (but not under Android, because that was problematic), but I
> > still have way too many variables (and way too few machines and
> > configurations) to be sure about whether what I've made now actually
> > compiles without problems in most places. Those variables come about
> > mainly because libnetlink is a rather quickly moving target, with not
> > much in the way of backwards compatiblity - both in headers, source and
> > binary form.
> yes, LibNL can be a mess...
> > To put it simply: I need to push a patch and see whether any of you have
> > any problems with compiling it still. Is that Ok?
> You could just post the patch here on the mailing list first... if it
> looks okay, you could push it to a branch of its own.
> Henning Rogge
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 13215 bytes
More information about the Olsr-dev