unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Aurora <rind38@disroot.org>
To: Zhu Zihao <all_but_last@163.com>
Cc: Ryan Prior <rprior@protonmail.com>, guix-devel@gnu.org
Subject: Re: Guix as a system vs as an end-user dev tool (re: Building a software toolchain that works)
Date: Sun, 20 Mar 2022 11:15:36 -0400	[thread overview]
Message-ID: <87zglkd59j.fsf@disp3269> (raw)
In-Reply-To: <86sfrdxcwy.fsf@163.com>


Zhu Zihao <all_but_last@163.com> writes:

> Make Guix available on Windows platform will be a painful job.
>
> 1. Windows doesn't allow user to create symbolic link without admin
> permission, which guix use intensely.
>
> 2. There's no RUNPATH for Windows DLL, so all dynamic library
> dependencies should in the same directory to allow Windows find it.
>

I think it's worth noting that the use of VM-based mechanisms in a
similar way to Docker for Desktop, suggested in the OP, would limit
these issues somewhat.

Native Guix would be exactly as troublesome as you suggest.

It might be possible to just rely on WSL.


      parent reply	other threads:[~2022-03-20 19:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-19  0:20 Guix as a system vs as an end-user dev tool (re: Building a software toolchain that works) Ryan Prior
2022-03-19  9:06 ` Liliana Marie Prikler
2022-03-19 10:27 ` Jonathan McHugh
2022-03-19 13:21 ` zimoun
2022-03-19 18:18   ` Ryan Prior
2022-03-19 22:57     ` Yasuaki Kudo
2022-03-21 10:26     ` zimoun
2022-03-20  8:04 ` Zhu Zihao
2022-03-20 10:47   ` Josselin Poiret
2022-03-20 15:15   ` Aurora [this message]

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87zglkd59j.fsf@disp3269 \
    --to=rind38@disroot.org \
    --cc=all_but_last@163.com \
    --cc=guix-devel@gnu.org \
    --cc=rprior@protonmail.com \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).