X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Sun, 27 Nov 2022 17:01:48 +0100 (CET) From: Roland Lutz To: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" Subject: Re: [geda-user] some new friction between gschem and pcb In-Reply-To: Message-ID: <9038298-1119-906d-acb5-ec8d48a3dd9@grinsen-ohne-katze.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk Hi Britton, in recent versions of gEDA/gaf, backends can come in a Python version and a Guile version. PCB invokes the Guile version of the `pcbfwd' backend. This is a file called `gnet-pcbfwd.scm' which should have been installed into the proper path by PCB. So either PCB didn't install the file into the correct path, or gEDA/gaf isn't configured to look for it in the correct path. This most likely happens when you install gEDA/gaf and PCB to different prefixes. You can fix this by adding the directory where `gnet-pcbfwd.scm' has been installed to your Guile search path. To do so, add a line (scheme-directory "/the/path") to your gafrc or gnetlistrc file (preferably the global one in ~/.gEDA/ so it doesn't depend on the working directory passed by PCB). You can check if this worked via `gnetlist --list-backends'. If it shows [PG] pcbfwd then both the Python version (packaged with gEDA/gaf) and the Guile version (packaged with PCB) are visible to gnetlist. Roland