delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to geda-user-bounces using -f |
X-Authentication-Warning: | envy.delorie.com: dj set sender to dj AT delorie DOT com using -f |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | geda-user AT delorie DOT com |
Subject: | Re: [geda-user] pcb vs gschem |
In-Reply-To: | <339a45aa-0be9-0dc4-4d7e-5eca99133061@earthlink.net> |
(geda-user AT delorie DOT com) | |
Date: | Mon, 13 Mar 2023 17:32:08 -0400 |
Message-ID: | <xnjzzkuylj.fsf@envy.delorie.com> |
MIME-Version: | 1.0 |
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 |
Both installs have to have the same --prefix= for one tool to find the other tool's files. The pcb build installs he pcbfwd plugin (gnet-pcbfwd.scm iirc) in its $prefix but gschem looks for it in its $prefix. A symlink should suffice for your case. Probably something like this: ln -s /usr/share/gEDA/scheme/gnet-pcbfwd.scm /usr/local/share/gEDA/scheme/gnet-pcbfwd.scm (or ln -s <pcb's location> <assumed gschem location>)
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |