From: Christopher Howard <christopher@librehacker.com>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 48336-done@debbugs.gnu.org
Subject: bug#48336: kicad cannot see libngspice
Date: Fri, 21 May 2021 15:05:42 -0800 [thread overview]
Message-ID: <49206b66a4d3a10966e9ed4b622d7730506124e4.camel@librehacker.com> (raw)
In-Reply-To: <87im3doz0v.fsf@kitej>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
Thank you. I ran a simulation based on a tutorial and the results of
the simulation were identical.
-----Original Message-----
From: Guillaume Le Vaillant <glv@posteo.net>
To: Christopher Howard <christopher@librehacker.com>
Cc: 48336-done@debbugs.gnu.org
Subject: Re: bug#48336: kicad cannot see libngspice
Date: Thu, 20 May 2021 21:50:40 +0000
Christopher Howard <christopher@librehacker.com> skribis:
> In Kicad Eeschema, if I try to use the Tools >> Simulator menu entry,
> Iget an error in a pop-up window that libngspice cannot be found,
> andthen the whole Kicad application closes. I see that libngspice is
> adependency of kicad so I'm not quite sure what is wrong.
> I asked at #kicad at they said that Kicad does not have any gui-
> adjustable path settings for ngspice or libngspice, so I don't think
> Ihave the application configured wrong.
Fix pushed as f7d2ae57543ae6afe14434877d7480b15dcbb5b7.I checked that
the libngspice library is detected and that thesimulation window opens
correctly, but I have not tried makingsimulations of electronic
circuits.Please open another bug if you find a problem.
[-- Attachment #2: Type: text/html, Size: 1913 bytes --]
prev parent reply other threads:[~2021-05-21 23:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 17:58 bug#48336: kicad cannot see libngspice Christopher Howard
2021-05-20 21:50 ` Guillaume Le Vaillant
2021-05-21 23:05 ` Christopher Howard [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=49206b66a4d3a10966e9ed4b622d7730506124e4.camel@librehacker.com \
--to=christopher@librehacker.com \
--cc=48336-done@debbugs.gnu.org \
--cc=glv@posteo.net \
/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).