[Kicad-developers] Build failure

What does this mean: By not providing "FindOCE.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "OCE", but CMake did not find one. Could not find a package configuration file provided by "OCE" (requested version 0.16) with any of the follow

[Kicad-developers] Build failure?

I just merged out and my build now fails trying to link the Eagle plugin test. But I can’t find any commits that have anything to do with that (in fact I should have only picked up one commit, which is completely unrelated). Anyone else seeing this? Cheers, Jeff. ___

[Kicad-developers] build failure

I'm having trouble building on mac after enabling OCC. I had both OCC and OCE disabled and I assume that's why 3D viewer didn't show STEP models any more. I installed OCC 7.5.0 using homebrew 'opencascade' formula. Is it possible to disable just kicad2step? [ 30%] Linking CXX static library libkic

Re: [Kicad-developers] Build failure

Do you have Seth's opencascade patch in your tree? Or what is different from the usual? The build flag you are specifying shoulnd be correct IIRC. 2018-03-22 23:56 GMT+01:00 Jeff Young : > What does this mean: > > By not providing "FindOCE.cmake" in CMAKE_MODULE_PATH this project has > asked CMak

Re: [Kicad-developers] Build failure

No, I don’t have Seth’s patch (to my knowledge). I assume it’s something I would have had to install? I’m not sure what’s different. I was trying to get it to build with scripting on and the wheels came off… Cheers, Jeff. > On 22 Mar 2018, at 23:09, Nick Østergaard wrote: > > Do you have

Re: [Kicad-developers] Build failure

Hi Jeff- I assume you have a populated cmake build directory. If so, you can run "make edit_cache" and you should be see what is toggled on and off and adjust. Then hit "c" to reconfigure and "g" to generate your makefiles. You can also delete cache entries using this tool, in case there is cruf

Re: [Kicad-developers] Build failure

It complains that it doesn’t have a CMake dialog available. Could someone dump in their cmake command (and indicate what directory it is executed from)? Thanks Jeff. > On 22 Mar 2018, at 23:32, Seth Hillbrand wrote: > > Hi Jeff- > > I assume you have a populated cmake build directory. If s

Re: [Kicad-developers] Build failure

I think used to do a “make install” inside kicad/build/. But now it says it doesn’t have an install target. (And if I do a “make” that’s when I get the OCE errors.) “make install” works one level higher (in kicad/), but then spews out a whole bunch of CMakeFiles directories as siblings to bui

Re: [Kicad-developers] Build failure

Based on Seth’s "cache cruft" comment I whacked my CMakeCache.txt entirely, and my cmd-line build is running again from kicad/build/. I’m afraid to run QTCreator again, though. > On 23 Mar 2018, at 00:20, Jeff Young wrote: > > I think used to do a “make install” inside kicad/build/. But now

Re: [Kicad-developers] Build failure

First thing I did with QTCreator is to delete all of the default (build/release/etc) build configurations that it sets up when creating/importing a project. Then, I created my own one with the settings I need for KiCad (especially build options and paths). I didn’t have any problems since then.

Re: [Kicad-developers] Build failure?

Hi Jeff- I get a build failure here (Linux): In file included from /home/seth/code/kicad/kicad-launchpad/eeschema/fields_grid_table.cpp:34:0: /home/seth/code/kicad/kicad-launchpad/include/widgets/grid_text_button_helpers.h:51:5: error: ‘wxComboCtrl’ does not name a type wxComboCtrl* Combo()

Re: [Kicad-developers] Build failure?

Hi Seth, That looks different. Is wxComboCtrl not implemented on Linux? (Or perhaps it has a different header file?) Cheers, Jeff. > On 20 Jul 2018, at 19:25, Seth Hillbrand wrote: > > Hi Jeff- > > I get a build failure here (Linux): > > In file included from > /home/seth/code/kicad/kic

Re: [Kicad-developers] Build failure?

Looking at it, the file includes . I think you wanted Does that work on Mac? -S Am Fr., 20. Juli 2018 um 11:28 Uhr schrieb Jeff Young : > Hi Seth, > > That looks different. Is wxComboCtrl not implemented on Linux? (Or > perhaps it has a different header file?) > > Cheers, > > Jeff. > > On 2

Re: [Kicad-developers] Build failure?

Yep, that works on Mac too. Thanks for tracking that down. (And a cache flush of my IDE appears to have fixed the other problem.) Cheers, Jeff. > On 20 Jul 2018, at 19:32, Seth Hillbrand wrote: > > Looking at it, the file includes . I think you wanted > Does that work on Mac? > > -S >

[Kicad-developers] Build failure OSX

"cairo-quartz.h can’t be found” I have such a file at /opt/local/include/cairo/, but that’s evidently not where the dev system is looking. Do I need to copy that somewhere, or does something in my setup need to be updated to look for it there? Thanks, Jeff.

Re: [Kicad-developers] build failure

Ok, I'm now trying to build against OCE instead, as I'm sure that used to work before. I managed to have CMake find my homebrew installed OCE by setting OCE_DIR, however it fails here: make[2]: *** No rule to make target `/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Develop

Re: [Kicad-developers] build failure

You need to make sure you have a clean buid dir and try yo explicitly disable oce and enable occt on your cmake configure line. fre. 5. mar. 2021 11.48 skrev Jonatan Liljedahl : > Ok, I'm now trying to build against OCE instead, as I'm sure that used > to work before. > I managed to have CMake fi

Re: [Kicad-developers] build failure

I've tried with a fresh build dir, still getting this: Undefined symbols for architecture x86_64: "Standard_Type::Register(char const*, char const*, unsigned long, opencascade::handle const&)", referenced from: opencascade::type_instance::get() in libkicad2step_lib.a(oce_utils.cpp.o)

Re: [Kicad-developers] build failure

@Jonatan Liljedahl Please share your cmake commandss On Fri, 5 Mar 2021 at 12:42, Jeff Young wrote: > > I never managed to get this to work (but my kung fu with build systems is > notoriously weak). > > Anyway, my current build flags are: > > -DCMAKE_C_COMPILER=clang > -DCMAKE_CXX_COMPILER=clan

Re: [Kicad-developers] build failure

Ok, I finally made it build with OCC, after uninstalling and reinstalling OCC with homebrew. Not sure what happened.. However, now there are *no* 3D models showing up. I noticed that there's a new KICAD6_3DMODEL_DIR path, which defaults to "/usr/local/3dmodels/" (where I have no 3d models). Is this

Re: [Kicad-developers] build failure

I tried "make install" in case something wasn't in the right place, but now that fails (which used to work fine): -- fixup_bundle -- app='/Users/lijon/Coding/kicad/build/install/KiCad.app/Contents/MacOS/kicad' -- libs='/Users/lijon/Coding/kicad/build/install/KiCad.app/Contents/PlugIns/_cvpcb

Re: [Kicad-developers] build failure

Maybe try the kicad-mac-buidler just to verify your environment works? It should use the same brew stuff as you manually use. https://gitlab.com/kicad/packaging/kicad-mac-builder/ On Fri, 5 Mar 2021 at 17:44, Jonatan Liljedahl wrote: > > I tried "make install" in case something wasn't in the rig

Re: [Kicad-developers] build failure

It is certainly possible that Homebrew is distributing bottles that are linked a little weird, and you'd be getting the MacOS 10.14 reference from that. We've had this happen before. Regarding the libTKVCAF error, it looks like something's not quite right between the library and the fixup_bundle

Re: [Kicad-developers] build failure

On Fri, Mar 5, 2021 at 8:45 PM Adam Wolf wrote: > > It is certainly possible that Homebrew is distributing bottles that > are linked a little weird, and you'd be getting the MacOS 10.14 > reference from that. We've had this happen before. Yes, I think this was the case with my OCE install, OCECo

Re: [Kicad-developers] build failure

Hi Jonatan, I hit the exact same issue (I'm also on 10.15), and after chatting with Adam about it, decided to try using the 10.14 bottle manually: Download https://bintray.com/homebrew/bottles/download_file?file_path=opencascade-7.5.0.mojave.bottle.tar.gz Install with: brew install -f --force-b

Re: [Kicad-developers] build failure

I haven't seen that. I can take a look at a bigger build log if you want. To be clear for others, I'm not advocating carrying around a 10.14 bottle of opencascade; this is troubleshooting in progress :) Adam On Tue, Mar 9, 2021 at 7:02 PM Jon Evans wrote: > > Hi Jonatan, > > I hit the exact sa

Re: [Kicad-developers] build failure

Hi, As I said earlier, it links fine for me now. It might have been some combination of installing CommandLineTools via xcode-select and uninstalling and reinstalling OCC. I did not force a 10.14 bottle. However, 'make install' still fails for me so I'm running kicad from the build dir (which wor

Re: [Kicad-developers] build failure

> As I said earlier, it links fine for me now. It might have been some > combination of installing CommandLineTools via xcode-select and > uninstalling and reinstalling OCC. Well, I did those things too and was still having the same problem :( I guess I can try blowing up homebrew and the tools/s

Re: [Kicad-developers] build failure

On Wed, Mar 10, 2021 at 2:34 PM Jon Evans wrote: > > > As I said earlier, it links fine for me now. It might have been some > > combination of installing CommandLineTools via xcode-select and > > uninstalling and reinstalling OCC. > > Well, I did those things too and was still having the same prob

[Kicad-developers] Build failure w.r.t. wxDateTime

I recently started getting a "Call of overloaded 'wxDateTime(timestamp_t&)' is ambiguous" compilation failure in class_module.cpp line 573. I modified it to static_cast m_LastEditTime, but I'm not sure that is what is intended here. This occurs both on MSVC and MSYS2 builds. (MSYS2 build here: ht

[Kicad-developers] Build failure on linux.

I just pulled the latest changes from the development branch and I'm getting the following build error on linux: /home/wayne/src/kicad-trunk/pcbnew/pcb_edit_frame.cpp: In member function ‘void PCB_EDIT_FRAME::OnRunEeschema(wxCommandEvent&)’: /home/wayne/src/kicad-trunk/pcbnew/pcb_edit_frame.cpp:12

Re: [Kicad-developers] Build failure OSX

I also tried “brew install cairo” to no avail. I assume I need a Cairo.framework in my /system/library/frameworks, but I’m not sure how to get it there. > On 2 Nov 2018, at 10:28, Jeff Young wrote: > > "cairo-quartz.h can’t be found” > > I have such a file at /opt/local/include/cairo/, but

Re: [Kicad-developers] Build failure OSX

How are you building? What are your cmake arguments? Adam On Fri, Nov 2, 2018, 7:33 AM Jeff Young I also tried “brew install cairo” to no avail. I assume I need a > Cairo.framework in my /system/library/frameworks, but I’m not sure how to > get it there. > > > > On 2 Nov 2018, at 10:28, Jeff Y

Re: [Kicad-developers] Build failure OSX

CLion. CMake args: -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_OSX_DEPLOYMENT_TARGET=10.13 -DwxWidgets_CONFIG_EXECUTABLE=../../wxWidgets/wx-bin/bin/wx-config -DKICAD_SCRIPTING=ON -DKICAD_SCRIPTING_MODULES=OFF -DKICAD_SCRIPTING_WXPYTHON=OFF -DKICAD_USE_OCE=OFF -DCMAKE_INSTALL_PRE

Re: [Kicad-developers] Build failure OSX

Hi Jeff, I copied and adjusted your cmake spell, and it works fine for me on macOS 10.13 with cairo installed via brew. One difference I spotted is that I have cairo_quartz.h in /usr/local/Cellar/cairo/1.14.12/include/cairo/. Cheers, Orson On 11/2/18 1:58 PM, Jeff Young wrote: > CLion. CMake ar

Re: [Kicad-developers] Build failure OSX

Hi Orson, Yes, brew seems to have installed a cairo-quartz.h in /usr/local/cellar/cairo/1.16.0/include/cairo/. Might cmake reference a specific version, or do I need to do something to make CMake find it? Cheers, Jeff. > On 2 Nov 2018, at 13:27, Maciej Suminski wrote: > > Hi Jeff, > > I c

Re: [Kicad-developers] Build failure OSX

CLion must have been holding on to something somewhere. Invalidating CLion’s caches and restarting did the deed. So my best guess is that you need to “brew install cairo”, and at least rerun CMake (possibly also needing to flush your devenv's caches). Have we added cairo to the list of pre-req

Re: [Kicad-developers] Build failure OSX

I am not a Mac guru, so I have followed a lazy path of KiCadMacOSPackaging [1] script by Adam Wolf, which got me cairo library as well. Cheers, Orson 1. https://github.com/wayneandlayne/KiCadMacOSPackaging/blob/master/setup.sh#L27 On 11/2/18 8:47 PM, Jeff Young wrote: > CLion must have been hold

Re: [Kicad-developers] Build failure OSX

Take a look at https://github.com/KiCad/kicad-mac-builder which is super awesome and should be better than those shell scripts in every way. :) If the old stuff is better than the new stuff, please let me know how I can improve the new :) Thanks! On Fri, Nov 2, 2018, 4:50 PM Maciej Suminski I a

Re: [Kicad-developers] Build failure OSX

Those are awesome; MUCH better than the old build documentation. I must have missed them when they came out. Cheers, Jeff. > On 2 Nov 2018, at 22:54, Adam Wolf wrote: > > Take a look at https://github.com/KiCad/kicad-mac-builder > which is super a

Re: [Kicad-developers] Build failure w.r.t. wxDateTime

Hi Thomas- Your analysis is correct. m_LastEditTime was recently changed to timestamp_t but holds time_t information and (for now) can be safely cast. I've pushed an update, let me know if it's still problematic. -S (Sorry for the double-email.) 2018-03-29 9:14 GMT-07:00 Thomas Figueroa : >

Re: [Kicad-developers] Build failure on linux.

He he… CLion’s ever-so-helpful automatic #include generator appends them after the last #include… which happens to be inside a #if defined(KICAD_SCRIPTING) block. Fix coming…. Cheers, Jeff. > On 22 Jul 2018, at 23:20, Wayne Stambaugh wrote: > > I just pulled the latest changes from the deve

Re: [Kicad-developers] Build failure on linux.

Fix in. > On 22 Jul 2018, at 23:33, Jeff Young wrote: > > He he… CLion’s ever-so-helpful automatic #include generator appends them > after the last #include… > > which happens to be inside a #if defined(KICAD_SCRIPTING) block. > > Fix coming…. > > Cheers, > Jeff. > > >> On 22 Jul 2018, at

Re: [Kicad-developers] Build failure on linux.

Thanks for the quick fix! On 07/22/2018 06:38 PM, Jeff Young wrote: > Fix in. > >> On 22 Jul 2018, at 23:33, Jeff Young > > wrote: >> >> He he… CLion’s ever-so-helpful automatic #include generator appends >> them after the last #include… >> >> which happens to be inside a #

[Kicad-developers] Build failure on Fedora 29

I had been able to build KiCad successfully for Fedora 29, but something has apparently changed very recently, because I am now getting a build failure. Below is part of my build log. The error relates to an include file called KHR/khrplatform.h: [ 23%] Building CXX object common/CMakeFiles/p

[Kicad-developers] Build failure in Fedora Rawhide

Fedora recently made a change to their cmake macros, to force packages to build "out of tree". The developers responsible for this change plan to go through and fix up the thousand or so packages that may break as a result, so they should eventually fix the official downstream KiCAD package.

Re: [Kicad-developers] Build failure on Fedora 29

Am 2018-12-09 10:24, schrieb Steven A. Falco: I had been able to build KiCad successfully for Fedora 29, but something has apparently changed very recently, because I am now getting a build failure. Below is part of my build log. The error relates to an include file called KHR/khrplatform.h: [

Re: [Kicad-developers] Build failure on Fedora 29

This might be the problem: (not Kicad) https://bugs.freedesktop.org/show_bug.cgi?id=77240 On 12/9/18 9:24 AM, Steven A. Falco wrote: I had been able to build KiCad successfully for Fedora 29, but something has apparently changed very recently, because I am now getting a build failure. Below i

Re: [Kicad-developers] Build failure on Fedora 29

On 12/9/18 10:47 AM, Seth Hillbrand wrote: > Am 2018-12-09 10:24, schrieb Steven A. Falco: >> I had been able to build KiCad successfully for Fedora 29, but >> something has apparently changed very recently, because I am now >> getting a build failure. >> >> Below is part of my build log.  The erro

Re: [Kicad-developers] Build failure on Fedora 29

On 12/9/18 11:53 AM, Steven A. Falco wrote: > On 12/9/18 10:47 AM, Seth Hillbrand wrote: >> Am 2018-12-09 10:24, schrieb Steven A. Falco: >>> I had been able to build KiCad successfully for Fedora 29, but >>> something has apparently changed very recently, because I am now >>> getting a build failu

Re: [Kicad-developers] Build failure in Fedora Rawhide

What does this mean if I want to test this locally? Should I do the following or are there other options enforced in cmake? git clone ...kicad... mkdir build_outside_of_kicad cd build_outside_of_kicad cmake ...kicad... On Mon, 20 Jul 2020 at 23:28, Steven A. Falco wrote: > > Fedora recently mad

Re: [Kicad-developers] Build failure in Fedora Rawhide

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:STRIN

Re: [Kicad-developers] Build failure in Fedora Rawhide

I am not sure I misunderstand the terminology here, but "cmake -S . -B foo -Dnickersej" looks "in tree" to me. On Mon, 20 Jul 2020 at 23:37, 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 i

Re: [Kicad-developers] Build failure in Fedora Rawhide

Re: that.. https://www.spinics.net/lists/fedora-devel/msg274669.html Quote from an Igor: I'm confused by the proposal, it is named "CMake to do out-of-source builds" but the macros seems to do the opposite? On Rawhide (local repo): %__cmake \ -S "%{_vpath_srcdir}" \ -B "%{__cma

Re: [Kicad-developers] Build failure in Fedora Rawhide

On 7/20/20 5:34 PM, Nick Østergaard wrote: What does this mean if I want to test this locally? Should I do the following or are there other options enforced in cmake? git clone ...kicad... mkdir build_outside_of_kicad cd build_outside_of_kicad cmake ...kicad... To test locally, I use our kicad

Re: [Kicad-developers] Build failure in Fedora Rawhide

You should be able to switch the macros: %cmake -> %cmake %make_build -> %cmake_build %make_install -> %cmake_install Then the builds and install will automatically use the proper out of tree directory. See the change proposal page for more details: https://fedoraproject.org/wiki/Changes/CMake_to_

Re: [Kicad-developers] Build failure in Fedora Rawhide

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:STRIN

Re: [Kicad-developers] Build failure in Fedora Rawhide

On 7/20/20 6:01 PM, Ian McInerney wrote: You should be able to switch the macros: %cmake -> %cmake %make_build -> %cmake_build %make_install -> %cmake_install Then the builds and install will automatically use the proper out of tree directory. See the change proposal page for more details: htt

Re: [Kicad-developers] Build failure in Fedora Rawhide

There should be no differences with where things get installed to - and if there are then our "install" targets are incorrect and should be fixed upstream. The changes to the cmake macros are simply for the build system. -Ian On Mon, Jul 20, 2020 at 11:04 PM Steven A. Falco wrote: > On 7/20/20

Re: [Kicad-developers] Build failure in Fedora Rawhide

Good luck. I've been putting off updating the Audacity spec file that I am maintainer on because of the cmake macro changes. But in my case I have to rewrite the entire spec to use cmake since they removed their autotools-based build system and instead introduced a broken cmake build system now -

Re: [Kicad-developers] Build failure in Fedora Rawhide

On 7/20/20 6:01 PM, Ian McInerney wrote: You should be able to switch the macros: %make -> %cmake %make_build -> %cmake_build %make_install -> %cmake_install It does look like it is that easy. I should have a build in another hour or so. Then I'll load it into a VM and test. If that works o

Re: [Kicad-developers] Build failure in Fedora Rawhide

On 7/20/20 8:28 PM, Steven A. Falco wrote: On 7/20/20 6:01 PM, Ian McInerney wrote: You should be able to switch the macros: %make -> %cmake %make_build -> %cmake_build %make_install -> %cmake_install It does look like it is that easy.  I should have a build in another hour or so.  Then I'll

[Kicad-developers] Build failure of 5.1.2 in Fedora rawhide

I've started getting a build error on 5.1.2 in Fedora rawhide. Here is part of the log: [ 68%] Generating pcbnew_wrap.cxx, pcbnew.py cd /builddir/build/BUILD/kicad-5.1.2/pcbnew && /usr/bin/cmake -E make_directory /builddir/build/BUILD/kicad-5.1.2/pcbnew/docstrings cd /builddir/build/BUILD/kicad

[Kicad-developers] Build failure - probably a race generating template_fieldnames_lexer.h

I think I just hit the builder race condition that was discussed a few days ago. I've attached a copy of template_fieldnames_lexer.h. At line 184 there is an #endif, and then part of the file appears to repeat. Thus, I wind up with an unmatched #endif and the compile fails. I tried re-runnin

Re: [Kicad-developers] Build failure of 5.1.2 in Fedora rawhide

Is the swig version 4.0.0? ons. 8. maj 2019 15.39 skrev Steven A. Falco : > I've started getting a build error on 5.1.2 in Fedora rawhide. Here is > part of the log: > > [ 68%] Generating pcbnew_wrap.cxx, pcbnew.py > cd /builddir/build/BUILD/kicad-5.1.2/pcbnew && /usr/bin/cmake -E > make_directo

Re: [Kicad-developers] Build failure of 5.1.2 in Fedora rawhide

https://bugs.launchpad.net/kicad/+bug/1816286 ons. 8. maj 2019 15.40 skrev Nick Østergaard : > Is the swig version 4.0.0? > > ons. 8. maj 2019 15.39 skrev Steven A. Falco : > >> I've started getting a build error on 5.1.2 in Fedora rawhide. Here is >> part of the log: >> >> [ 68%] Generating pcb

Re: [Kicad-developers] Build failure of 5.1.2 in Fedora rawhide

Yes. swig-4.0.0-1.fc31.x86_64 On 5/8/19 9:40 AM, Nick Østergaard wrote: > Is the swig version 4.0.0? > > ons. 8. maj 2019 15.39 skrev Steven A. Falco >: > > I've started getting a build error on 5.1.2 in Fedora rawhide.  Here is > part of the log: > > [

Re: [Kicad-developers] Build failure of 5.1.2 in Fedora rawhide

Here is the top of pcbnew.py, and I'll paste this into the bug report: # This file was automatically generated by SWIG (http://www.swig.org). # Version 4.0.0 # # Do not make changes to this file unless you know what you are doing--modify # the SWIG interface file instead. from sys import version_

Re: [Kicad-developers] Build failure - probably a race generating template_fieldnames_lexer.h

On 2019-06-04 11:07, Steven A. Falco wrote: I think I just hit the builder race condition that was discussed a few days ago. I've attached a copy of template_fieldnames_lexer.h. At line 184 there is an #endif, and then part of the file appears to repeat. Thus, I wind up with an unmatched #endi

Re: [Kicad-developers] Build failure - probably a race generating template_fieldnames_lexer.h

On 6/4/19 12:41 PM, Seth Hillbrand wrote: > On 2019-06-04 11:07, Steven A. Falco wrote: >> I think I just hit the builder race condition that was discussed a few >> days ago.  I've attached a copy of template_fieldnames_lexer.h.  At >> line 184 there is an #endif, and then part of the file appears