unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: phodina <phodina@protonmail.com>
To: Peter Polidoro <peter@polidoro.io>
Cc: Guillaume Le Vaillant <glv@posteo.net>, help-guix@gnu.org
Subject: Re: Kicad missing symbols and footprints
Date: Tue, 17 Oct 2023 18:14:35 +0000	[thread overview]
Message-ID: <F2-0-PgObQCMYHch0x0yHJwwmVZQsdPxXA1i-ZGvl3xEo15xFUlS1TG07ty1szN0ZsEbEkVjGBrmOKnOYy5k4N41Gp5LZazod7C4KiLeEXs=@protonmail.com> (raw)
In-Reply-To: <87a5shjr14.fsf@polidoro.io>

[-- Attachment #1: Type: text/plain, Size: 562 bytes --]

Hi Peter and Guillaume,

thanks for the help.

I've tried to use the Guix shell to have a complete environment for Kicad but for some reason it does not work (at least for me)

So here are the steps to reproduce:

$ guix shell kicad kicad-footprints kicad-symbols -- kicad

I start I new project and when I get the dialog about the components I wish to use in the project it all starts to go wrong.

The path to the symbols and footprints is also attached.

I've removed all files from `~/.config/kicad` and `~/.local/share/kicad`.

----
Petr
 

[-- Attachment #2: step4.png --]
[-- Type: image/png, Size: 21480 bytes --]

[-- Attachment #3: step5.png --]
[-- Type: image/png, Size: 14601 bytes --]

[-- Attachment #4: step1.png --]
[-- Type: image/png, Size: 12809 bytes --]

[-- Attachment #5: step6.png --]
[-- Type: image/png, Size: 31096 bytes --]

[-- Attachment #6: step2.png --]
[-- Type: image/png, Size: 80023 bytes --]

  reply	other threads:[~2023-10-17 18:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17  6:12 Kicad missing symbols and footprints phodina via
2023-10-17  9:10 ` Guillaume Le Vaillant
2023-10-17 13:46   ` Peter Polidoro
2023-10-17 18:14     ` phodina [this message]
2023-10-18 13:42       ` Peter Polidoro
2023-10-26 15:24       ` Peter Polidoro

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='F2-0-PgObQCMYHch0x0yHJwwmVZQsdPxXA1i-ZGvl3xEo15xFUlS1TG07ty1szN0ZsEbEkVjGBrmOKnOYy5k4N41Gp5LZazod7C4KiLeEXs=@protonmail.com' \
    --to=phodina@protonmail.com \
    --cc=glv@posteo.net \
    --cc=help-guix@gnu.org \
    --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. 
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).