Message-ID: <c6efee38-51cb-e618-3830-1b5af3fadc4e@earthlink.net>
Date: Mon, 13 Mar 2023 17:30:34 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.8.0
Subject: Re: [geda-user] pcb vs gschem
Content-Language: en-US
To: geda-user AT delorie DOT com
References: <xnjzzkuylj DOT fsf AT envy DOT delorie DOT com>
From: "David W. Schultz (david DOT schultz AT earthlink DOT net) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Organization: State of Total Disorganization
In-Reply-To: <xnjzzkuylj.fsf@envy.delorie.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
Precedence: bulk

On 3/13/23 4:32 PM, DJ Delorie wrote:
> 
> 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>)

Thanks, that helped a lot. But now I am getting some errors from the 
netlist. Alas with not much in the way of a hint of where to look. No 
reference designator anyway.

Good thing the .sch files are human readable as I could quickly find the 
problem.


-- 
http://davesrocketworks.com
David Schultz