All of
 help / color / mirror / Atom feed
From: "Nicolas Jeker" <>
Subject: Re: [yocto] Yocto recipe for Tailscale #yocto #golang
Date: Fri, 18 Sep 2020 08:26:49 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Mike,

On Thu, 2020-09-17 at 22:43 -0700, Mike Thompson via wrote:
> Does anyone know if there is an existing bitbake recipe for building
> the Tailscale client daemon and CLI tool from the following source? 
> A search on Google yielded no obvious links.

I usually search on the OpenEmbedded layer index:

Seems like you are right, there seems to be no recipe available. Be
aware that not all recipes/layers are listed there, but the majority

> The Tailscale client for Linux looks to be built using the Go
> language which is a complete unknown to me. I've built very simple
> recipes before for basic Makefile and Automake built software, but I
> suppose Go brings a new set of challenges.
> If an existing recipe is not available, any words of wisdom before I
> get started on this?

I never used Go in the Yocto/OpenEmbedded environment, but I'm sure
somebody else who has more experience will be able to help. To get
started with writing a new recipe I usually get my inspiration from
similar recipes (similar language, build system, dependencies, etc.).

> Thanks,
> Mike Thompson

  reply	other threads:[~2020-09-18  6:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18  5:43 Yocto recipe for Tailscale #yocto #golang Mike Thompson
2020-09-18  6:26 ` Nicolas Jeker [this message]
2020-09-18 23:46   ` Mike Thompson
2020-09-19  6:04     ` [yocto] " Khem Raj
2020-09-19 10:13       ` Mike Thompson
2020-09-19 20:58         ` Mike Thompson
2020-09-21 17:30           ` [yocto] " Randy MacLeod
2020-09-23  4:49             ` Mike Thompson
2020-10-13 18:51               ` Mike Thompson
2020-10-13 19:42                 ` [yocto] " Khem Raj

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.