Re: [Kicad-developers] github plugin

On 1/15/19 5:19 PM, Seth Hillbrand wrote: > Am 2019-01-15 16:42, schrieb Steven A. Falco: >> A recent commit, "pcbnew: Prevent GITHUB plugin from being >> registered", seems to have caused my copr build to fail. > > Hi Steve- > > Sorry about that.  Missed a config.h include for the io_mgr file. 

[Kicad-developers] Build failed in Jenkins: linux-kicad-full-gcc-head #4526

See Changes: [hillbrand] pcbnew: Fix missing config.h from 9458ae8221 -- [...truncated 155.33 KB...] [ 86%] Building CXX object

[Kicad-developers] Jenkins build is back to normal : kicad-qa #5086

See ___ 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] github plugin

Am 2019-01-15 16:42, schrieb Steven A. Falco: A recent commit, "pcbnew: Prevent GITHUB plugin from being registered", seems to have caused my copr build to fail. Hi Steve- Sorry about that. Missed a config.h include for the io_mgr file. Should be fixed shortly. -S

[Kicad-developers] github plugin

A recent commit, "pcbnew: Prevent GITHUB plugin from being registered", seems to have caused my copr build to fail. Fedora has "BUILD_GITHUB_PLUGIN=ON". I get this error: [ 18%] Building CXX object common/CMakeFiles/pcbcommon.dir/__/pcbnew/io_mgr.cpp.o cd

Re: [Kicad-developers] SIGTRAP crash with ngspice

I had a corrupted repo - I fixed that and the build is now running. I'll let you know how it goes... Steve On 1/15/19 4:07 PM, Steven A. Falco wrote: > I opened a bug here: https://bugzilla.redhat.com/show_bug.cgi?id=1666505 > > I've made the necessary changes in "fedora-packaging"

Re: [Kicad-developers] SIGTRAP crash with ngspice

I opened a bug here: https://bugzilla.redhat.com/show_bug.cgi?id=1666505 I've made the necessary changes in "fedora-packaging" but right now I'm getting an unreleated build failure: [ 18%] Building CXX object common/CMakeFiles/pcbcommon.dir/__/pcbnew/io_mgr.cpp.o cd

[Kicad-developers] Build failed in Jenkins: linux-kicad-full-gcc-head #4525

See Changes: [hillbrand] pcbnew: Prevent GITHUB plugin from being registered [hillbrand] pcbnew: Don't update coords on add -- [...truncated 70.40 KB...] [ 37%]

Re: [Kicad-developers] SIGTRAP crash with ngspice

Yes, I am fine with using it in the copr builds for now. Do we need to submit a PR for the libngspice package to let the packager pick it up more easy? I have not seen any activity from him. On Tue, 15 Jan 2019 at 20:58, Steven A. Falco wrote: > On 1/15/19 9:21 AM, Wayne Stambaugh wrote: > > Hi

[Kicad-developers] Build failed in Jenkins: kicad-qa #5085

See Changes: [hillbrand] pcbnew: Prevent GITHUB plugin from being registered [hillbrand] pcbnew: Don't update coords on add -- Started by an SCM change Building remotely on debian8

Re: [Kicad-developers] SIGTRAP crash with ngspice

On 1/15/19 9:21 AM, Wayne Stambaugh wrote: > Hi Steve, > > On 1/15/2019 8:51 AM, Steven A. Falco wrote: >> I'll look at that. The worst burst of backspaces is about 7 characters >> long, so I could accumulate 14 chars or so before making a decision. In >> other words, run a circular buffer,

Re: [Kicad-developers] KiCad Snapshot version with enabled GTK+3 and wxPython4.0 scripting in Debian experimental

Hey Carsten, On 1/15/2019 2:18 AM, Carsten Schoenert wrote: > Hi Wayne, > > Am 15.01.19 um 00:28 schrieb Wayne Stambaugh: >>> I'm a bit supersized that there is no plan to configure the current >>> KiCad development version at least with GTK+3 backend as default given >>> the original plan to

Re: [Kicad-developers] What is the difference between the use of 3d model search path entries and normal path variables (environment variables)?

Am 2019-01-11 12:25, schrieb Rene Pöschl: Could someone detail how this would be used? Would it clash with the use of normal path variables (after all our official footprints all use the KISYS3DMOD path variable)? Which of the two is preferred assuming these two are meant to serve the same

[Kicad-developers] Jenkins build is back to normal : kicad-qa #5084

See ___ 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] What is the difference between the use of 3d model search path entries and normal path variables (environment variables)?

Sadly these do not really answer my questions. On 15/01/19 17:25, Mário Luzeiro wrote: Hi Rene, Not sure if it is documented. Cirilo was the main person on the development of the 3D searching paths. Searching the mailing list there may be some hints to this questions, but it may not be

[Kicad-developers] Build failed in Jenkins: linux-kicad-full-gcc-head #4523

See Changes: [hillbrand] pcbnew: code style cleanup [hillbrand] Eeschema: prevent schematic images with bad scales -- [...truncated 155.85 KB...] [ 87%] Building

Re: [Kicad-developers] What is the difference between the use of 3d model search path entries and normal path variables (environment variables)?

Hi Rene, Not sure if it is documented. Cirilo was the main person on the development of the 3D searching paths. Searching the mailing list there may be some hints to this questions, but it may not be totally true or updated at this moment:

[Kicad-developers] Build failed in Jenkins: kicad-qa #5083

See Changes: [hillbrand] pcbnew: code style cleanup [hillbrand] Eeschema: prevent schematic images with bad scales -- Started by an SCM change Building remotely on debian8 (clang

[Kicad-developers] Build failed in Jenkins: linux-kicad-full-gcc-head #4522

See -- [...truncated 156.10 KB...] [ 88%] Building CXX object cvpcb/CMakeFiles/cvpcb_kiface.dir/__/pcbnew/pcb_general_settings.cpp.o [ 88%] Building CXX object

[Kicad-developers] Build failed in Jenkins: linux-kicad-full-gcc-head #4521

See Changes: [Wayne Stambaugh] Do not set wxSetAssertHandler on non-debug builds. -- [...truncated 155.53 KB...] [ 87%] Building CXX object

Re: [Kicad-developers] SIGTRAP crash with ngspice

Hi Steve, On 1/15/2019 8:51 AM, Steven A. Falco wrote: > I'll look at that. The worst burst of backspaces is about 7 characters long, > so I could accumulate 14 chars or so before making a decision. In other > words, run a circular buffer, and when I see the first non-backspace after a >