The option KICAD_SCRIPTING_PYTHON3 doesn't even exist anymore. I
recommend that people who are having issues get rid of your CMake
cache and start fresh, you have a lot of left over variables that may
be confusing things. When we remove a variable from our CMake
configuration, many times it does
You don't need to specify the type, but cmake will accept it as well and
that is how it is written by cmake in the CMakeCache.txt.
On Wed, 16 Jun 2021 at 20:51, Kevin Cozens wrote:
> On 2021-06-15 6:32 a.m., Marco Ciampa wrote:
> > On Tue, Jun 15, 2021 at 12:22:42AM +0300, Eeli Kaikkonen wrote:
On 2021-06-15 6:32 a.m., Marco Ciampa wrote:
On Tue, Jun 15, 2021 at 12:22:42AM +0300, Eeli Kaikkonen wrote:
[snip]
That's where cmake UIs come handy. Try ccmake or cmake-gui (they are
[snip]
Exactly, Kevin is right but using the cmake-gui command it was very easy
to figure out how to change
OpenCascade is now the default when building KiCad. This includes the
5.1 branch. This was done because OCC fixes a few bugs in OCE and OCE
support will eventually be removed.
Package developers should adjust the platform build and install
dependencies to OCC as required. If a platform does
4 matches
Mail list logo
