kicad-developers team mailing list archive

["Steven A. Falco" <stevenfalco@xxxxxxxxx>]

On 7/20/20 5:37 PM, Seth Hillbrand wrote:
> Hi Steve-
>
> This looks like a build setup issue, not in our CMake code.  We can build out of tree (in fact, we really prefer it) right now.  From the log, the broken command is
> /usr/bin/cmake -S . -B x86_64-redhat-linux-gnu -DCMAKE_C_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_CXX_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_Fortran_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DCMAKE_INSTALL_PREFIX:PATH=/usr -DINCLUDE_INSTALL_DIR:PATH=/usr/include -DLIB_INSTALL_DIR:PATH=/usr/lib64 -DSYSCONF_INSTALL_DIR:PATH=/etc -DSHARE_INSTALL_PREFIX:PATH=/usr/share -DLIB_SUFFIX=64 -DBUILD_SHARED_LIBS:BOOL=ON -DKICAD_SCRIPTING=ON -DKICAD_SCRIPTING_MODULES=ON -DKICAD_SCRIPTING_PYTHON3=ON -DKICAD_SCRIPTING_WXPYTHON=ON -DKICAD_SCRIPTING_WXPYTHON_PHOENIX=ON -DKICAD_SCRIPTING_ACTION_MENU=ON -DKICAD_USE_OCC=ON -DKICAD_INSTALL_DEMOS=ON -DKICAD_BUILD_QA_TESTS=OFF -DBUILD_GITHUB_PLUGIN=ON -DKICAD_SPICE=ON -DKICAD_VERSION_EXTRA=r19086-6d8fb94d -DCMAKE_BUILD_TYPE=Debug .
>
> You can modify this in your .spec.template file.

I understand that, and I use out-of-tree builds for most of my local KiCAD builds.  But that is not how the nightlies work.  They are built on the Copr website, and they use the normal RPM build mechanism.

You are correct that there is nothing wrong with our CMake code, and we can fix our build setup.  But it is more than just compiling the source.  There are lots of other components that get built, and the location of the files that get rolled into the package will also change a bit.  So the changes will take some time to sort out, especially given how long it takes to test a build.  Hence the proposal of the workaround.

	Steve