--- In [email protected], Dimitris Lampridis <d.lampri...@...> wrote: > > Dear all, > > I've recently completed the design of my first board with Kicad and I'm > extremely happy with it. What a great piece of software it is! > > However, I ran into a small problem: > > I've put my design under version control (using Git) so that I can > access it and update it from multiple computers, whether I'm at work, > at home, or travelling. > > When I "pull" the latest version from Git, I noticed that most of the > paths to custom components are absolute. In other words, a custom > module for a footprint that I've created is linked with its aboslute > path (eg. if my project is stored at "/home/xxx/projects/yyy", then a > custom module could be /home/xxx/projects/yyy/custom_modules/kk-ll.mod). > > Of course, not all of the computers have the same installations and > folder structures (or user names for home folders), so this approach > fails. > > Especially under version control, the problem becomes bigger: if I > modify the paths to match one system, then commit my changes, the > project will stop working on every other computer... > > To solve this, I manually changed all paths that point to custom > components (for library symbols, footprint modules and 3D models) into > relative ones (eg. ./custom_modules/kk-ll.mod). > > This worked for symbols and footprints like a charm, but the 3D viewer > refuses to draw the components that are given with relative paths. > > Anybody knows why this is happening? Any solutions? > > Thanks, > Dimitris >
Hi Dimitris, I'm running kicad on linux also, what I would make sure is where the libraries are pointing to. I initially assumed it was /usr/share/kicad/lib etc which was a local installed version of kicad. However I had installed at /usr/local/kicad which made a lot of difference. If you can create a public temp git repository, I'd have a look see if I can spot anything.
