all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mitchell Schmeisser via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Peter Polidoro <peter@polidoro.io>
Cc: guix-devel@gnu.org
Subject: Re: Oniro or Guix on Zephyr kernel?
Date: Sat, 25 Feb 2023 09:15:21 -0500	[thread overview]
Message-ID: <049A1AB4-773C-42C1-8F88-2F31B8A51451@librem.one> (raw)
In-Reply-To: <46B5C87B-E1DA-4174-99DE-0D573C5945EE@polidoro.io>

> Are you also planning on making the firmware that you write to run on top of Zephyr into Guix packages as well? That could make it way easier to synchronize code on both a host machine and an embedded board that need to communicate with each other. 
> 
> I would love to read another blog post about using Guix to manage an entire embedded project including firmware if you are ever up for it!


It’s already written! It will be published shortly but if you want to look at my work https://github.com/guix-zephyr

-Mitchell

> On Feb 25, 2023, at 8:45 AM, Peter Polidoro <peter@polidoro.io> wrote:
> 
> Thank you for all of your great work on packaging the Zephyr SDK for Guix! I had the same feelings about West and its approach to handling dependencies.
> 
> PlatformIO has a similar issue where parts of it are very useful, but it would be great to be able use Guix to manage firmware libraries instead of the platformio.ini files.
> 
> Are you also planning on making the firmware that you write to run on top of Zephyr into Guix packages as well? That could make it way easier to synchronize code on both a host machine and an embedded board that need to communicate with each other. 
> 
> I would love to read another blog post about using Guix to manage an entire embedded project including firmware if you are ever up for it!
> 
> 


  reply	other threads:[~2023-02-25 14:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-23 14:42 Oniro or Guix on Zephyr kernel? Peter Polidoro
2023-02-23 21:43 ` Csepp
2023-02-24 12:43   ` Joshua Branson
2023-02-24 15:19     ` Peter Polidoro
2023-02-24 16:52     ` jbranso
2023-02-24 18:36       ` Mitchell Schmeisser via Development of GNU Guix and the GNU System distribution.
2023-02-24 19:35         ` Tobias Geerinckx-Rice
2023-02-24 19:43         ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-02-25 13:45           ` Peter Polidoro
2023-02-25 14:15             ` Mitchell Schmeisser via Development of GNU Guix and the GNU System distribution. [this message]
2023-02-25 14:16               ` Mitchell Schmeisser via Development of GNU Guix and the GNU System distribution.
2023-02-25 15:19               ` Peter Polidoro
2023-02-25 15:27                 ` Mitchell Schmeisser via Development of GNU Guix and the GNU System distribution.
2023-03-01 21:55                 ` Mitchell Schmeisser via Development of GNU Guix and the GNU System distribution.
2023-02-25 17:06         ` jbranso
2023-02-27 19:10         ` Efraim Flashner
2023-03-01  8:45           ` Ryan Sundberg
2023-03-04 17:26             ` Joshua Branson
2023-03-05  0:42               ` Ryan Sundberg
2023-02-25 18:15 ` Ludovic Courtès

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=049A1AB4-773C-42C1-8F88-2F31B8A51451@librem.one \
    --to=guix-devel@gnu.org \
    --cc=mitchellschmeisser@librem.one \
    --cc=peter@polidoro.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.