delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2018/03/21/17:41:33

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Wed, 21 Mar 2018 22:40:17 +0100 (CET)
From: Roland Lutz <rlutz AT hedmen DOT org>
To: "Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject: Re: [geda-user] gnetlist not finding symbol libraries
In-Reply-To: <16061151-e533-af35-6869-410872ff47ae@fastmail.com>
Message-ID: <alpine.DEB.2.20.1803212232550.2689@nimbus>
References: <16061151-e533-af35-6869-410872ff47ae AT fastmail DOT com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
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

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--8323329-1619556078-1521668417=:2689
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Wed, 21 Mar 2018, Girvin Herr (gherrl AT fastmail DOT com) [via 
geda-user AT delorie DOT com] wrote:
> I have several local custom symbol libraries in my home directory which 
> are not part of the gEDA system symbol libraries. Up until now, I had to 
> explicitly define these library paths in order for them to show up in 
> the gschem insert symbol list. […] Now, it seems gschem is finding these 
> libraries without my explicit declarations in the gafrc file.

This is weird.  Are you sure you didn't define them in one of the 
configuration files gschem executes at startup (they are listed in the 
"Status" tab at the bottom of the window) or via a geda.conf file?

If you did, removing all but one declaration in your gafrc file should 
work.

> If I leave them in my gafrc file, gschem reports duplicate library names 
> when it processes the gafrc file.

This could also happen if the name of one of your libraries matches the 
name of a pre-defined library.  You can circumvent this by giving a 
(different) library name as the second argument to component-library.

--8323329-1619556078-1521668417=:2689--

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019