sudo cmake -DKICAD_USE_CMAKE_FINDPROTOBUF=ON ../../
sudo make
sudo make install
sudo ldconfig
and when running kicad from:
'/usr/local/kicad/build/release/kicad/kicad`
and trying to open an eeschema file i get the following:
Failed to load shared library '/usr/local/kicad/build/release/kicad/_eeschema.kiface': /usr/local/kicad/build/release/kicad/_eeschema.kiface: cannot open shared object file: No such file or directory
but _eeschema.kiface is located in: â/usr/local/kicad/build/release/eeschema/_eeschema.kifaceâ
thus it is looking for it in the wrong directory same story with pcbnew,
but i am able to open eechema with bash command: /usr/local/kicad/build/release/eeschema/eeschema
so individually this was built correctly.
Adding export KICAD_RUN_FROM_BUILD_DIR to â~/.bashrcâ fixed the problem thanks!
Unfortunately itâs hard to comeby from google even with the term KICAD_RUN_FROM_BUILD_DIR.
Luckily there are great good guys on the forum
If you insist running from the build dir, you donât have to use make install. Just plain make is enough and saves some seconds and some megabytes of hard disk.
But installing is simple on *nix, running from build folder is more useful on Windows.
I guess I would like to run it from the home dir or what ever is the default directory for running kicad in linux.
but since I know is creates the executeable in â/usr/local/kicad/build/release/kicad/kicadâ
I just run it with /usr/local/kicad/build/release/kicad/kicad
am I doing anything out of the ordinary?
By default it should install to /usr/local/, which means it that the main binaries go to /usr/local/bin/, the libraries /usr/local/lib/, etc. The Windows installation replicates more or less the same hierarchy:
Replace â9.0â in that screenshot with â/usr/localâ and you see the similar hierarchy. Having âbuildâ in the installation hierarchy tells itâs not the default installation.