Arch Linux User Repository

A binary repo with the pre-built nightly packages is available here:

https://gitlab.com/kicad/packaging/kicad-arch/kicad-arch-builder#binary-repo

# Nightly builds for KiCad
[kicad-nightly]
SigLevel = Optional TrustAll
Server = https://kicad.gitlab.io/packaging/kicad-arch/kicad-arch-builder/

Thank you to all those who've made us aware of some recent build system changes that broke things - we'll work on a patch and issue corrected files in the next day or two. Apologies for being slow to get back to this.

benx45h: There are two major differences between the two packages.

The first is that this one isn't just "whatever the latest is in Git", but rather is pinned to a particular commit each day so as to aid reproducability and try and help guarantee a usable build each update

The second is that kicad-git cannot be installed along side kicad, which means if you want to use both a kicad-git nightly build and stable on the same machine, it's just not possible.. This package on the other hand is designed to be side-by-side installed so suffixes on -nightly and puts both config and binaries in a different location to allow all this to work seamlessly.

gkeeth: ah, ok.. I wasn't aware anyone was using the AUR without a helper - my helper (yay) automatically blows away the build as in makepkg -sic once the package is built.

I can add support for that style of update cycle though, yes. I'll try and make that available in today's nightly

Understood about requiring full builds; what about changing it to mkdir -p build along with adding ninja clean to make sure it's a full rebuild? Or automatically deleting the build dir if it exists? Or maybe a git clean?

This is a little unconventional, but this is the only aur package on my system where I can't update with just a git pull and makepkg -si. And given that I'm rebuilding this package every day, well... :)

gkeeth: Because of the sheer amount of flux in the repo at the moment, full clean builds every time are required so I am electing to not make that change for now. CMake doesn't deal with this situation well, tending to cause damaged builds to come out, so while inconvenient it is for the better.

Can you change mkdir build to mkdir -p build in build() so the build directory doesn't have to be deleted for each rebuild? Thanks!

benx45h: There are two major differences between the two packages.

The first is that this one isn't just "whatever the latest is in Git", but rather is pinned to a particular commit each day so as to aid reproducability and try and help guarantee a usable build each update

The second is that kicad-git cannot be installed along side kicad, which means if you want to use both a kicad-git nightly build and stable on the same machine, it's just not possible.. This package on the other hand is designed to be side-by-side installed so suffixes on -nightly and puts both config and binaries in a different location to allow all this to work seamlessly.

What's the difference between this package and kicad-git?

reverb_1: I had my wife check by compiling KiCad-nightly fresh having never had it installed before and it worked flawlessly for her.

I can only surmise given what you're seeing vs the package deps and my own experiences with building KiCad, that your installation of Boost is screwed up or you've got something set in your shell that is causing proper detection of Boost to fail. Please review your .bashrc (or other config for your shell, whichever one you happen to use) as something you are doing is causing the failures.

I have tried setting the environment variable to /usr/include/boost but it still is not working. I am at a loss of what I am missing.

Edit(11/19): Strangely it complied when I ssh into the machine. For some reason it cannot find the Boost components: filesystem system

CmakeLists.txt from Successful compile:

//The directory containing a CMake configuration file for Boost.
Boost_DIR:PATH=/usr/lib64/cmake/Boost-1.72.0

Boost_FILESYSTEM_LIBRARY_RELEASE:STRING=/usr/lib64/libboost_filesystem.so.1.72.0

//Path to a file.
Boost_INCLUDE_DIR:PATH=/usr/include

Boost_SYSTEM_LIBRARY_RELEASE:STRING=/usr/lib64/libboost_system.so.1.72.0

Boost_UNIT_TEST_FRAMEWORK_LIBRARY_RELEASE:STRING=/usr/lib64/libboost_unit_test_framework.so.1.72.0

Original Post: I have tried setting the environment variable to /usr/include/boost but it still is not working. I am at a loss of what I am missing.

-- Found Boost: /lib64/cmake/Boost-1.72.0/BoostConfig.cmake (found version "1.72.0") found components: unit_test_framework 
-- Configuring done
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
/home/reverb/.cache/yay/kicad-nightly/src/kicad/libs/kimath/Boost_INCLUDE_DIR
   used as include directory in directory /home/reverb/.cache/yay/kicad-nightly/src/kicad/libs/kimath
/home/reverb/.cache/yay/kicad-nightly/src/kicad/utils/kicad2step/Boost_INCLUDE_DIR
   used as include directory in directory /home/reverb/.cache/yay/kicad-nightly/src/kicad/utils/kicad2step
Boost_INCLUDE_DIR

There are a dozen or so of these below:

CMake Error in thirdparty/clipper/CMakeLists.txt:
  Found relative path while evaluating include directories of "clipper":

"Boost_INCLUDE_DIR-NOTFOUND"

ah, thank you DCengineer for providing me a reason for making it optional.

I'd back-and-forth'd about it in the 1BitSquared community Discord and we figured to make it a normal dependency in favour of ease of use, however as this screws up your use case that's a good reason to me to drop it back to optional.

I will make this change for today's nightly.