Re: [Kicad-developers] Build error.

Ditto! > On 27 Feb 2021, at 13:55, Wayne Stambaugh wrote: > > Thanks! > ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help :

Re: [Kicad-developers] Build error.

Thanks! On 2/27/21 8:54 AM, Jon Evans wrote: > Should be fixed now. > > On Sat, Feb 27, 2021 at 7:48 AM Wayne Stambaugh > wrote: > > Looks like a commit in the last 24 hours broke KiCad builds with Python > enabled.  Here is the build error on Linux using

Re: [Kicad-developers] Build error.

Should be fixed now. On Sat, Feb 27, 2021 at 7:48 AM Wayne Stambaugh wrote: > Looks like a commit in the last 24 hours broke KiCad builds with Python > enabled. Here is the build error on Linux using gcc 9.3.0. > > In file included from >

[Kicad-developers] Build error.

Looks like a commit in the last 24 hours broke KiCad builds with Python enabled. Here is the build error on Linux using gcc 9.3.0. In file included from /usr/include/x86_64-linux-gnu/c++/9/bits/c++allocator.h:33, from /usr/include/c++/9/bits/allocator.h:46, from

Re: [Kicad-developers] Build error

All good here. Thanks. On 6/10/20 8:52 AM, Jeff Young wrote: > I’ve merged an attempted fix. (Of course the previous one compiled fine on > CLang too, so I’m not 100% confident in it -- but it seem to fit the error > GCC was generating.) > >> On 10 Jun 2020, at 12:59, Wayne Stambaugh wrote:

Re: [Kicad-developers] Build error: Now compiles for me.

On Wed, Jun 10, 2020 at 3:18 PM Dino Ghilardi wrote: > > No more build error on my machine (gcc 6.3.0) > > > Cheers, > Dino. > I've been able to build master ( d7d877241 ) ok with GCC 9.3.0: Application: Pcbnew Version: (5.99.0-1936-gd7d877241), debug build Libraries: wxWidgets 3.0.4

Re: [Kicad-developers] Build error: Now compiles for me.

Thanks, Dino! > On 10 Jun 2020, at 14:18, Dino Ghilardi wrote: > > No more build error on my machine (gcc 6.3.0) > > > Cheers, > Dino. > > On 10/06/20 14:52, Jeff Young wrote: >> I’ve merged an attempted fix. (Of course the previous one compiled fine on >> CLang too, so I’m not 100%

Re: [Kicad-developers] Build error: Now compiles for me.

No more build error on my machine (gcc 6.3.0) Cheers, Dino. On 10/06/20 14:52, Jeff Young wrote: I’ve merged an attempted fix. (Of course the previous one compiled fine on CLang too, so I’m not 100% confident in it -- but it seem to fit the error GCC was generating.) On 10 Jun 2020, at

Re: [Kicad-developers] Build error

I’ve merged an attempted fix. (Of course the previous one compiled fine on CLang too, so I’m not 100% confident in it -- but it seem to fit the error GCC was generating.) > On 10 Jun 2020, at 12:59, Wayne Stambaugh wrote: > > I forgot to mention, lead devs please do not commit any new code

Re: [Kicad-developers] Build error

I forgot to mention, lead devs please do not commit any new code until this gets fixed. On 6/10/20 7:14 AM, Wayne Stambaugh wrote: > As of commit 4138c8554 I'm getting the following build error on linux. > > /home/wayne/src/kicad-trunk/pcbnew/drc/drc_rule_parser.cpp: In > constructor

[Kicad-developers] Build error

As of commit 4138c8554 I'm getting the following build error on linux. /home/wayne/src/kicad-trunk/pcbnew/drc/drc_rule_parser.cpp: In constructor ‘DRC_RULES_PARSER::DRC_RULES_PARSER(BOARD*, const wxString&, const wxString&)’: /home/wayne/src/kicad-trunk/pcbnew/drc/drc_rule_parser.cpp:36:26:

Re: [Kicad-developers] build error on macos on 5.1 branch

It's all fixed. Thanks! On Thu, Jul 11, 2019 at 5:32 PM Adam Wolf wrote: > > Thanks! > > On Thu, Jul 11, 2019, 2:36 PM Seth Hillbrand wrote: >> >> Ah, I see Jeff fixed up my commit for OSX in the master branch. I've >> cherry-picked his fix for 5.1. Let me know if it doesn't fix it. >> >>

Re: [Kicad-developers] build error on macos on 5.1 branch

Thanks! On Thu, Jul 11, 2019, 2:36 PM Seth Hillbrand wrote: > Ah, I see Jeff fixed up my commit for OSX in the master branch. I've > cherry-picked his fix for 5.1. Let me know if it doesn't fix it. > > Best- > Seth > > On 2019-07-11 13:59, Adam Wolf wrote: > > Builds at at 044b4a6d4 on master

Re: [Kicad-developers] build error on macos on 5.1 branch

Ah, I see Jeff fixed up my commit for OSX in the master branch. I've cherry-picked his fix for 5.1. Let me know if it doesn't fix it. Best- Seth On 2019-07-11 13:59, Adam Wolf wrote: Builds at at 044b4a6d4 on master went through fine. Adam On Thu, Jul 11, 2019 at 11:04 AM Seth Hillbrand

Re: [Kicad-developers] build error on macos on 5.1 branch

Hi Adam- This looks like the result of a cherry-pick I did the other day. Do you get this error in the master branch as well? -S On 2019-07-11 11:55, Adam Wolf wrote: Hi folks! Running into a build error on my macOS jobs for 5.1: I'm adding what I think is the appropriate message...

[Kicad-developers] build error on macos on 5.1 branch

Hi folks! Running into a build error on my macOS jobs for 5.1: I'm adding what I think is the appropriate message... 05:46:01 default: [ 69%] Building CXX object pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/import_gfx/graphics_import_mgr.cpp.o 05:46:04 default: In file included from

Re: [Kicad-developers] Build error.

Hi Wayne, On 29 March 2019 22:30:27 GMT, Wayne Stambaugh wrote: > > I don't know if I want to force this even though I think it's a good > idea. So few of the source files in KiCad adhere to this that it would > confuse new developers. However, devs should be aware of the issue. Sure, it's

Re: [Kicad-developers] Build error.

Hey John, On 3/29/2019 9:44 AM, John Beard wrote: > Hi Wayne, > > Duh, it's a Boost version thing, and I ran it though different > platforms *except* the old-Boost one. Face, meet palm. > > Funnily enough, as this header is often included first, this one > *should* be immune to ordering issues.

Re: [Kicad-developers] Build error.

Hi Wayne, Duh, it's a Boost version thing, and I ran it though different platforms *except* the old-Boost one. Face, meet palm. Funnily enough, as this header is often included first, this one *should* be immune to ordering issues. Also, I sent a proposal for a modification to the Coding Policy

Re: [Kicad-developers] Build error.

Hey John, Thanks for the quick fix. It could be due to header ordering in the source files. I generally try to compile the headers separately to catch issues like this. There is helpful instructions in the coding policy on how to do this. Given the number of headers included in the KiCad

Re: [Kicad-developers] Build error.

Hi Wayne, Thanks for the heads up. I've pushed a fix to both branches. I'm not sure why that ever worked silently on Linux GCC/Msys2 GCC/MSVC, but using std:: is certainly correct. Perhaps a header has a sneaky type alias somewhere. Cheers, John On Fri, Mar 29, 2019 at 12:30 PM Wayne Stambaugh

[Kicad-developers] Build error.

Commit ad76ebd8 broke builds when compiling with clang. home/wayne/src/kicad-trunk/qa/unit_test_utils/include/unit_test_utils/unit_test_utils.h:121:24: error: unknown type name 'nullptr_t'; did you mean 'std::nullptr_t'? struct print_log_value ^

Re: [Kicad-developers] Build error on Fedora KiCad copr

Thank you, I can confirm that this was the last change that made the fedora build happy. :) On Mon, 5 Nov 2018 at 20:33, Wayne Stambaugh wrote: > > John, > > I merged your patch. > > Thanks, > > Wayne > > On 11/5/2018 9:49 AM, John Beard wrote: > > Gah! Wrong patch! Try this. > > On Mon, Nov 5,

Re: [Kicad-developers] Build error on Fedora KiCad copr

John, I merged your patch. Thanks, Wayne On 11/5/2018 9:49 AM, John Beard wrote: > Gah! Wrong patch! Try this. > On Mon, Nov 5, 2018 at 2:43 PM Steven A. Falco wrote: >> >> On 11/5/18 5:24 AM, John Beard wrote: >>> Hi, >>> >>> This appears to be because something in the build is setting the

Re: [Kicad-developers] Build error on Fedora KiCad copr

On 11/5/18 9:49 AM, John Beard wrote: > Gah! Wrong patch! Try this. That's better! I got a clean build with your new patch. Please commit it, and thanks! Steve > On Mon, Nov 5, 2018 at 2:43 PM Steven A. Falco wrote: >> >> On 11/5/18 5:24 AM, John Beard wrote: >>> Hi, >>> >>> This

Re: [Kicad-developers] Build error on Fedora KiCad copr

Gah! Wrong patch! Try this. On Mon, Nov 5, 2018 at 2:43 PM Steven A. Falco wrote: > > On 11/5/18 5:24 AM, John Beard wrote: > > Hi, > > > > This appears to be because something in the build is setting the CMake > > BUILD_SHARED_LIBS option to ON (the default is not set at all). See > > build log

Re: [Kicad-developers] Build error on Fedora KiCad copr

On 11/5/18 5:24 AM, John Beard wrote: > Hi, > > This appears to be because something in the build is setting the CMake > BUILD_SHARED_LIBS option to ON (the default is not set at all). See > build log line 124. > > qa_utils is not explicitly declared STATIC like the rest of KiCad > internal

Re: [Kicad-developers] Build error on Fedora KiCad copr

Hi, This appears to be because something in the build is setting the CMake BUILD_SHARED_LIBS option to ON (the default is not set at all). See build log line 124. qa_utils is not explicitly declared STATIC like the rest of KiCad internal libs, but it depends on common, which is. This causes Bad

[Kicad-developers] Build error on Fedora KiCad copr

The following discussion is from [KiCad/fedora-packaging] Handle ambiguous Python shebang (#20). I'm cross-posting to kicad-developers since I'm not sure who sees the fedora-packaging emails. Please don't hate me. :-) On 11/4/18 6:05 AM, nickoe wrote: > The patch was merged upstream, I

Re: [Kicad-developers] Build error

Jeff fixed it with d62145fba9c35916631b3d. ma 15. lokak. 2018 klo 23.11 Eeli Kaikkonen (eeli.kaikko...@gmail.com) kirjoitti: > > > ma 15. lokak. 2018 klo 22.59 Wayne Stambaugh (stambau...@gmail.com) > kirjoitti: > >> The latest round of commits causes the following build error (at least >> on

Re: [Kicad-developers] Build error

ma 15. lokak. 2018 klo 22.59 Wayne Stambaugh (stambau...@gmail.com) kirjoitti: > The latest round of commits causes the following build error (at least > on windows). > > error: 'else' without a previous 'if' > In Linux, too. -Eeli Kaikkonen ___

[Kicad-developers] Build error

The latest round of commits causes the following build error (at least on windows). C:/msys64/home/wstambaugh/src/kicad-trunk/pcbnew/pcb_edit_frame.cpp: In member function 'void PCB_EDIT_FRAME::InstallFootprintPropertiesDialog(MODULE*, wxDC*)':

Re: [Kicad-developers] Build error

Sorry, you did and I missed it. A dependency was missed. I think the following might fix it. in pcbnew/CMakeLists.txt -add_dependencies( pcbnew_kiface specctra_lexer_source_files ) +add_dependencies( pcbnew_kiface_objects specctra_lexer_source_files ) On 06/03/18 13:10, Nick Østergaard wrote:

Re: [Kicad-developers] Build error

On 03/05/2018 06:55 PM, Nick Østergaard wrote: > I reproduce in a clean workspace like this: > git clone https://github.com/KiCad/kicad-source-mirror.git kicad_steven > cd kicad_steven/ > mkdir build > cd build/ > cmake .. -DKICAD_SCRIPTING=OFF -DKICAD_SCRIPTING_MODULES=OFF >

Re: [Kicad-developers] Build error

I just gave you hints on how to reproduce this. I suspect the most important part is the high number of make jobs. I use cmake version 3.10.2 on archlinux. 2018-03-06 1:03 GMT+01:00 hauptmech : > If you have any hints on how to reproduce the failure I can try to help. > The

Re: [Kicad-developers] Build error

If you have any hints on how to reproduce the failure I can try to help. The cmake version being used might help. On 06/03/18 12:55, Nick Østergaard wrote: I reproduce in a clean workspace like this: git clone https://github.com/KiCad/kicad-source-mirror.git kicad_steven cd kicad_steven/ mkdir

Re: [Kicad-developers] Build error

I reproduce in a clean workspace like this: git clone https://github.com/KiCad/kicad-source-mirror.git kicad_steven cd kicad_steven/ mkdir build cd build/ cmake .. -DKICAD_SCRIPTING=OFF -DKICAD_SCRIPTING_MODULES=OFF -DKICAD_SCRIPTING_WXPYTHON=OFF make -j40 On 5.0.0-rc2-dev-101-gf7ef010fe

Re: [Kicad-developers] Build error

Ok, now I also see that issue. It could very easily be that RPATH commit making the build system unstable. It is a problem that the generated files are not in the build dir, but in the source dir. 2018-03-05 23:22 GMT+01:00 Nick Østergaard : > It also seem to build correctly

Re: [Kicad-developers] Build error

It also seem to build correctly on jenkins. 2018-03-05 23:16 GMT+01:00 Steven A. Falco : > I'm going to retract this report. It builds correctly on copr, so the > problem must be something in my local setup. > > Sorry for the noise. > > Steve > >

Re: [Kicad-developers] Build error

I'm going to retract this report. It builds correctly on copr, so the problem must be something in my local setup. Sorry for the noise. Steve ___ Mailing list: https://launchpad.net/~kicad-developers Post to :

Re: [Kicad-developers] Build error

I ran a bisection, and it looks like the first bad commit is: e0b33ee8a Fix RPATH not removed in shared object file for python I can build its predecessor, 62bcf4fde41, without any problems. I attached the bisect log, showing which commits I tried to build, and the results. Steve On

Re: [Kicad-developers] Build error

Yes it does. I'm building on Fedora via the "mock" tool, which always starts from an empty directory. Just to be sure, I removed the entire "mock" working area, and I even re-downloaded the source repositories. I'll try pushing the build up to the Copr build-system, and I'll report back with

Re: [Kicad-developers] Build error

Does the compile error exist after you make clean and re-make? 2018-03-05 10:20 GMT-08:00 Steven A. Falco : > I just got a build error on Linux, at git commit 218f66a08, which appears > to be the latest commit. > > In file included from

[Kicad-developers] Build error

I just got a build error on Linux, at git commit 218f66a08, which appears to be the latest commit. In file included from /builddir/build/BUILD/kicad-r12311-218f66a0/pcbnew/specctra_import_export/specctra.h:36:0, from

Re: [Kicad-developers] Build error on MSVC

Merged, thank you Simon! Regards, Orson On 09/19/2017 09:14 PM, Simon Richter wrote: > Hi, > > I'm getting a compile error on MSVC: > > eeschema\lib_pin.cpp(588): error C2228: left of '.utf8_str' must have > class/struct/union > > I can't prove easily whether this code is legal or illegal

[Kicad-developers] Build error on MSVC

Hi, I'm getting a compile error on MSVC: eeschema\lib_pin.cpp(588): error C2228: left of '.utf8_str' must have class/struct/union I can't prove easily whether this code is legal or illegal according to the C++ specification, which is probably a good reason to change it. Simon From

Re: [Kicad-developers] Build Error with wxWidgets >3.1.0

Sure… https://bugs.launchpad.net/kicad/+bug/1678623 Regards, Bernhard > On 2. Apr 2017, at 16:12, Chris Pavlina wrote: > > Looks like it should cause breakage, please don't merge. I'll have a > look at this later - wx

Re: [Kicad-developers] Build Error with wxWidgets >3.1.0

Looks like it should cause breakage, please don't merge. I'll have a look at this later - wx 3.1 is unsupported, but it should be relatively easy to resolve this and reduce future breakage if we ever upgrade. Could you please file a bug report? On Sun, Apr 02, 2017 at 04:08:32PM +0200, Bernhard

[Kicad-developers] Build Error with wxWidgets >3.1.0

Hi,KiCad doesn’t build (at least for me on OSX) with a current wxWidgets master, I guess it won’t since wxWidgets change [1] and new component selector.Attached is a patch for a workaround/fix which makes compiler happy again and doesn’t seem to brake anything obvious in the new component