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

See Changes: [hillbrand] Ratsnest: iterate only over dirty nets -- [...truncated 149.42 KB...] [ 86%] Building CXX object

Re: [Kicad-developers] [PATCH] Fuzzable PCB parsing test harness

Hi Wayne, Could you try to build with VERBOSE=1 so I can see what the failed link command line looks like and compare to Jenkins? Cheers, John On 17 October 2018 13:17:34 BST, Wayne Stambaugh wrote: >Hey John, > >Close but no cigar. I'm still getting a single link error. >

Re: [Kicad-developers] [PATCH] Add preferences dialog hotkey

Hi, I see, I thought the HIG comment was about Cmd vs Ctrl. My mistake. I have no really strong feelings (plus hotkeys are customisable). It's certainly not weird to use Ctrl-,. At least, some Mac-esque programs on Linux also use that. I don't think it's that problematic to have the defaults

Re: [Kicad-developers] [PATCH] Add preferences dialog hotkey

I don't think my last post communicated what I wanted so I'll try again. Michael chose ctrl+',' as the hotkey because it matches the Mac Human Interface Guidelines. https://developer.apple.com/design/human-interface-guidelines/macos/user-interaction/keyboard/ On the Mac platform, starting

[Kicad-developers] Jenkins build is back to normal : linux-kicad-full-gcc-head #4164

See ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe :

Re: [Kicad-developers] UTF-8 change please test on Windows/Mac

On 2018-10-17 12:19, jp charras wrote: OK, I'll need to look at this more deeply.  Does W7 work with the example unicode ?  This is the one given in the bug report that crashes Linux. -Seth It is incorrectly displayed in dialogs, but it does not create issues in eeschema and pcbnew. I

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

See Changes: [Wayne Stambaugh] Replace log debugging output with tracing. -- [...truncated 143.65 KB...] [ 83%] Building CXX object

Re: [Kicad-developers] Build broken in master

Oops! I'm not sure how I managed to do that but it's fixed now. Thanks for the heads up. On 10/17/2018 3:20 PM, s...@hillbrand.org wrote: > Hi All- > > I think the latest commits have broken the build (at least on Linux).  > Error is: > >

[Kicad-developers] Build broken in master

Hi All- I think the latest commits have broken the build (at least on Linux). Error is: /home/seth/code/kicad/kicad-launchpad/kicad/tree_project_frame.cpp: In member function ‘void TREE_PROJECT_FRAME::FileWatcherReset()’:

[Kicad-developers] 5.1

Now that the Eeschema gal code has been merged into the development branch and things seem reasonably stable, we need to start thinking about the 5.1 release. I would like to merge Thomas' python 3 code and Orson's cairo print code as soon as they are ready to go so we can get some additional

Re: [Kicad-developers] UTF-8 change please test on Windows/Mac

Le 17/10/2018 à 17:55, s...@hillbrand.org a écrit : > On 2018-10-17 09:21, jp charras wrote: >> Le 17/10/2018 à 14:01, jp charras a écrit : >>> Le 17/10/2018 à 13:45, jp charras a écrit : Le 17/10/2018 à 01:51, Seth Hillbrand a écrit : > Hi All- > > Our UTF-8 routines are mildly

Re: [Kicad-developers] UTF-8 change please test on Windows/Mac

On 2018-10-17 09:21, jp charras wrote: Le 17/10/2018 à 14:01, jp charras a écrit : Le 17/10/2018 à 13:45, jp charras a écrit : Le 17/10/2018 à 01:51, Seth Hillbrand a écrit : Hi All- Our UTF-8 routines are mildly fragile and didn't play nicely with higher-order unicode sequences [1] causing

Re: [Kicad-developers] Edit text and graphic properties behavior

Hi Jeff, On 10/17/2018 12:01 AM, Jeff Young wrote: > I think one of the original justifications of dyn_cast<> was that it was > faster. Do I have that wrong, or do we not believe it to be material? It probably is faster, as comparing values can be inlined, while dynamic_cast<> cannot. Whether

Re: [Kicad-developers] KiCad 5 PPA does not have a kicad package for Ubuntu 18.10

Hi Seppe, I'm currently working on that point... Should be ok soon... Regards, Le 17/10/2018 à 14:12, Seppe Stas a écrit : > Hey Jean-Samuel and people dealing with the KiCad PPA / linux packaging > > The "official" (at least it is the documented approach on how to install > KiCad on Ubuntu

Re: [Kicad-developers] UTF-8 change please test on Windows/Mac

Le 17/10/2018 à 14:01, jp charras a écrit : > Le 17/10/2018 à 13:45, jp charras a écrit : >> Le 17/10/2018 à 01:51, Seth Hillbrand a écrit : >>> Hi All- >>> >>> Our UTF-8 routines are mildly fragile and didn't play nicely with >>> higher-order unicode sequences [1] causing a segfault for anything

Re: [Kicad-developers] [PATCH] Fuzzable PCB parsing test harness

Hey John, Close but no cigar. I'm still getting a single link error. C:/msys64/mingw32/bin/../lib/gcc/i686-w64-mingw32/7.3.0/../../../../i686-w64-mingw32/bin/ld.exe: ../../common/libcommon.a(marker_base.cpp.obj):marker_base.cpp:(.text+0xee9): undefined reference to

[Kicad-developers] KiCad 5 PPA does not have a kicad package for Ubuntu 18.10

Hey Jean-Samuel and people dealing with the KiCad PPA / linux packaging The "official" (at least it is the documented approach on how to install KiCad on Ubuntu ) KiCad PPA does not have the a kicad package for Ubuntu 18.10 (Cosmic Cuttlefish). This means

Re: [Kicad-developers] UTF-8 change please test on Windows/Mac

Le 17/10/2018 à 13:45, jp charras a écrit : > Le 17/10/2018 à 01:51, Seth Hillbrand a écrit : >> Hi All- >> >> Our UTF-8 routines are mildly fragile and didn't play nicely with >> higher-order unicode sequences [1] causing a segfault for anything >> larger than 16-bits. >> >> I've pushed a fix

Re: [Kicad-developers] UTF-8 change please test on Windows/Mac

Le 17/10/2018 à 01:51, Seth Hillbrand a écrit : > Hi All- > > Our UTF-8 routines are mildly fragile and didn't play nicely with > higher-order unicode sequences [1] causing a segfault for anything > larger than 16-bits. > > I've pushed a fix that changes how wchar_t* characters are assigned to >