When finished, I would like to put in a dedicated GitHub repository (not the official repository), to be imported by any user in KiCAD via the plugin manager.
I know I have to create some json file, so that the URL can be correctly interpreted by KiCAD.
The problem is: I have not clue whether or not exists a tool to make it, or I should write line-by-line.
In the last case: there is a syntax to follow but where can I find the documentation please?
Jon linked to the docs explaining how to create a package and add it to the official repo. If you want your own repo there is one more small bit remaining, create the repository.json and packages.json files. That process is not documented but it’s trivial if you managed to create the package itself. Just follow the example of the official repo:
Change the description and maintainer info, change the links to resources and packages file, change the update time and either remove the hash or update it to be correct hash for your files.
packages.json is even simpler, it’s just an array of package metadata.
being the first time, I just wanted to create my own repo just to get some familiarity with procedures.
Indeed to be “official” I read there are more constraint.
So per steps:
first trying to create my repo and in case I have problems: learn how to solve them
then: apply to be in the official list.
NOTE: I suppose the SHA also in the link you gave me is optional …
If your end goal is to have your package in official repo than it’s easier to just follow the steps described in official docs and also in the readme of the packages repo KiCad / KiCad Addons / Package Metadata · GitLab
One of the steps there involves testing the package you created, it will automatically generate a testing repository for you.
now … in one of the links it specifies the folder structure I must respect and make it a zip.
In the second screenshot there is the folder structure for my library
Is it correct?
NOTE: there are not footprints and not any 3D model (not necessary), thus no *.pretty nor .3dshapes
ok so, I modified it. The archive root is
NE-Nuova_Elettronica-library
Inside it I have a directory called “symbols”, in which I have all the .kicad_sym
then again I created a directory called “resources” inside it I put the PNG with the logo
So I have validated it yes … but ti’s not sufficient.
I mean: the metadata.json should contain the package SHA, the Package size and the Install size
But at the same time that metadata.json, as far as I understood, should be inside that .ZIP … am I right? … but this alters the above mentioned data. so it will always fail the Kicad repository validation.
The file metadata.json: should or not be into the .ZIP file?
So if not: fine.
If “yes”: then the SHA etc, must be the one of the .ZIP without the .JSON inside?
NOTE: I put on GitHub so that each time I upload a new version, the RAW address that I have to write into that JSON changes. Hence the internal JSON is different than the one I have on my machine
NOTE 2: what seems to be clear to anyone is familiar with this, it’s NOT with one that’s fully new.
Your icon file has to be called icon.png, you can’t name it an arbitrary filename. I’m not sure why the symbols are giving validation errors, at first glance. Can you post your entire metadata file?