Also, I have heard that the default install path definition is wrong in the package in testing. It tries to set the KISYSMOD env var to /usr/local/share/kicad/modules, while the footprints are installed to /usr/share/kicad/modules.
You can fix this by setting -DDEFAULT_INSTALL_PATH=/usr when invoking cmake. Also, the RC2 has now been released. Remember to update the KICAD_BUILD_VERSION string when you upgrade the source :) 2015-11-04 20:26 GMT+01:00 Nick Østergaard <oe.n...@gmail.com>: > Hi Gregor, > > Please do as suggested by Wayne here: > https://www.mail-archive.com/kicad-developers@lists.launchpad.net/msg15285.html > > I realise that it is not well documented yet, but anyways that is the > way to do it for now. > > A note to everyone maintaining auto builders, please add > "-DKICAD_REPO_NAME=stable -DKICAD_BUILD_VERSION=4.0.0-rc1" to your build > configuration to generate the correct build version string. > > > 2015-11-04 18:40 GMT+01:00 Gregor Riepl <onit...@gmail.com>: >>> I shall upload the fixed revision soon, and include your hints. >> >> Ok, so I got kicad-4.0.0~rc1 from the package server today. >> >> There's one thing I noticed: Version information seems to be missing. >> The project window title shows "no-vcs-found-product". >> I believe there's a script that generates version.h that does not work >> correctly when the sources aren't bzr-augmented. >> IMHO, the solution would be to just create this file with static contents for >> the release/rc builds. They probably forgot to include it in the upstream >> source package? >> >> I also hit the problem that KiCad would not find the footprint libraries, but >> that was a quick fix: I had them installed into /usr/share/kicad/footprints >> previously, but they are in /usr/share/kicad/modules now. So I just changed >> the path. >>
