kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #31617
Re: Assertion in dialog_symbol_remap in latest master
On 11/14/2017 06:32 PM, Jon Evans wrote:
> Hi Wayne,
>
> The sym-lib-table file is empty (I didn't create/copy this, I guess
> kicad created it):
>
> $ cat ~/.config/kicad/sym-lib-table
> (sym_lib_table
> )
You need to get a copy of the latest default symbol library table from
the kicad library repo. There is a link to it in blog post on the
website that contains all of the pertinent information on the symbol
library table remapping.
I figured out the github url issue. I just need to find the time to fix it.
>
> I don't have KICAD_SYMBOL_DIR set in my environment:
>
> $ env | grep KI
> KIGITHUB=https://github.com/KiCad
> KICAD_PATH=/usr/share/kicad
>
> -Jon
>
>
> On Tue, Nov 14, 2017 at 8:02 AM, Wayne Stambaugh <stambaughw@xxxxxxxxx
> <mailto:stambaughw@xxxxxxxxx>> wrote:
>
> Jon,
>
> Please send me a copy of your global symbol library table
> (sym-lib-table) located in the kicad folder of your user configuration
> path. There are no sym-lib-table paths with http://github.com/KiCad in
> the default symbol library table. I just checked. Either you have
> copied an invalid symbol library table file or something is broken in
> you configuration. The only other thing I can think of is the somehow
> your KICAD_SYMBOL_DIR environment variable is pointing to
> http://github.com/KiCad. ; It should be point to where the default kicad
> symbol libraries are install.
>
> Thanks,
>
> Wayne
>
> On 11/13/2017 9:30 PM, Jon Evans wrote:
> > Hi Wayne,
> >
> > I just pulled in your recent changes and got a series of assertions when
> > trying to remap the symbol table. I just ignored them and it seemed to
> > work, but something is strange here:
> >
> > ../../eeschema/dialogs/dialog_symbol_remap.cpp(306): assert
> > "aPathA.IsAbsolute()" failed in normalizeAbsolutePaths():
> > https:/github.com/KiCad <http://github.com/KiCad>
> <http://github.com/KiCad> is not an absolute path.
> >
> > (note the single slash after https:)
> >
> > I haven't looked in to it closely but wanted to mention in case you
> > already know what the cause is. If not, I can dig in at some point.
> >
> > -Jon
>
>
References