[Olsr-dev] (no subject)
Tue May 20 01:34:24 CEST 2008
Sounds good, that would be good. I'm just confused exactly how to do
that. This is what I'm currently doing.
extern export_route_function olsr_addroute_function;
olsr_addroute_function = my_addroute_function;
But this doesn't work. The olsr_addroute_function can't be found. For
some reason, I think the version-script.txt could help, but I don't
really know. Any hints?
On 5/19/08, Sven-Ola Tuecke <(spam-protected)> wrote:
> eh? for what? Simply assign your function address to the
> olsr_addroute_function function pointer variable. An interative table of
> function pointers adds overhead for nothing.
> // Sven-Ola
> ----- Original Message -----
> From: "Stanley Koteks" <(spam-protected)>
> To: "Hannes Gredler" <(spam-protected)>
> Cc: <(spam-protected)>
> Sent: Monday, May 19, 2008 9:53 PM
> Subject: Re: [Olsr-dev] (no subject)
>> Any chance on getting them back?
>> On 5/18/08, Hannes Gredler <(spam-protected)> wrote:
>>> afaik sven-ola has slashed those functions a while ago ...
>>> unsure about his reasoning ...
>>> On Sun, May 18, 2008 at 02:59:41PM -0700, Stanley Koteks wrote:
>>> | Looks good, but where are the functions olsr_addroute_remove_function
>>> | and olsr_addroute_add_function? I grepped the source directory of
>>> | olsrd, and couldn't find it in stable or the latest development
>>> | version. If these functions exist, this is exactly what I need.
>>> | Thanks,
>>> | Stan
>>> | On 5/18/08, Aaron Kaplan <(spam-protected)> wrote:
>>> | > Stanley,
>>> | >
>>> | > please take a look on this one... it is not finished yet.. but
>>> | > release early and often etc :)
>>> | > Please in case you generalize it, do feed back the changes the the
>>> | > main branch.
>>> | >
>>> | > I am not happy with the convert_ip_* function - some generalization
>>> | > and clean way of doing it is probably better :)
>>> | >
>>> | > a.
>> Olsr-dev mailing list
More information about the Olsr-dev