Skip to content
This repository has been archived by the owner on Oct 2, 2020. It is now read-only.

[v6] CI #2984

Open
chschlue opened this issue Sep 19, 2020 · 2 comments
Open

[v6] CI #2984

chschlue opened this issue Sep 19, 2020 · 2 comments
Assignees
Milestone

Comments

@chschlue
Copy link
Contributor

chschlue commented Sep 19, 2020

Minimal requirements

  • symbols
  • footprints

Nice to have

  • footprint-generator
  • library-utils
@cpresser
Copy link
Contributor

I already started on this one.
My WIP stuff is here:

To test it, I also made 3 merge requests:
https://gitlab.com/cpresser/kicad-footprints/-/merge_requests

  • One with errors
  • One without errors
  • One that does not change a footprint

So far that looks good.

@cpresser
Copy link
Contributor

I have started looking into symbols. Yesterday was the first time I ran kicad6.

The documentation (https://docs.google.com/document/d/1AiPZvWT_QBPyVQSyn3ISl6jVntjrrtATEYxzBFJM1HU/edit) has a disclaimer about being outdated, and yes, that seems to be true. For example I can't find the word extends in the docu. But fortunately the format seems to be mostly self explanatory.

I think I can start from pcb/kicad_mod.py since it already has most of the sexpr parsing and convenience functions. Has anyone else already put work into making a python parser for the .kicad_sym files? I want to prevent doing duplicate work here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants