[FROG] Yocto Recipe for FRR

[Amol Lad]

Thanks Donald.

Is there a reason why FRRouting is not already a part of some Yocto layer (such as meta-networking from OpenEmbedded)? Supporting FRRouting in Yocto will open a whole new domain for its use in embedded systems. From web, I can see many have struggled to add FRR in Yocto and no clarity if there was any success or not.

Amol


The information in this email communication (inclusive of attachments) is confidential to 4RF Limited and the intended recipient(s). If you are not the intended recipient(s), please note that any use, disclosure, distribution or copying of this information or any part thereof is strictly prohibited and that the author accepts no liability for the consequences of any action taken on the basis of the information provided. If you have received this email in error, please notify the sender immediately by return email and then delete all instances of this email from your system. 4RF Limited will not accept responsibility for any consequences associated with the use of this email (including, but not limited to, damages sustained as a result of any viruses and/or any action or lack of action taken in reliance on it).-----Original Message-----
From: Donald Sharp <sharpd at cumulusnetworks.com>
Sent: Monday, 14 January 2019 10:27 PM
To: Amol Lad <Amol.Lad at 4rf.com>
Cc: frog at lists.frrouting.org
Subject: Re: [FROG] Yocto Recipe for FRR

Amol -

I believe that there was some discussion here:

https://github.com/FRRouting/frr/issues/2131

about this issue.

donald

On Mon, Jan 14, 2019 at 12:23 AM Amol Lad <Amol.Lad at 4rf.com> wrote:
>
> Hi,
>
>
>
> Please advise if there is any Yocto recipe for FRRouting? If not, how to go about creating one for FRR? Yocto Recipe for FRR will hugely simplify integrating FRR in Yocto based embedded linux distributions. So please advise if there are any plans to develop this recipe?
>
>
>
> Thanks
>
> Amol
>
>
>
> ________________________________
> The information in this email communication (inclusive of attachments) is confidential to 4RF Limited and the intended recipient(s). If you are not the intended recipient(s), please note that any use, disclosure, distribution or copying of this information or any part thereof is strictly prohibited and that the author accepts no liability for the consequences of any action taken on the basis of the information provided. If you have received this email in error, please notify the sender immediately by return email and then delete all instances of this email from your system. 4RF Limited will not accept responsibility for any consequences associated with the use of this email (including, but not limited to, damages sustained as a result of any viruses and/or any action or lack of action taken in reliance on it).
> _______________________________________________
> frog mailing list
> frog at lists.frrouting.org
> https://lists.frrouting.org/listinfo/frog