Re: [Kicad-developers] JetBrains

I don't think we have one. I pay for a personal one, but if we had one already set up I might look at the criteria again. I really like stuff from Jetbrains. Adam On Thu, Mar 22, 2018, 7:01 PM Jeff Young wrote: > Do we have a JetBrains CLion license yet, or should I apply for

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

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

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

[Kicad-developers] JetBrains

Do we have a JetBrains CLion license yet, or should I apply for one? (OpenSource projects can get their products for free if they meet some criteria.) I’m ready to give up on QTCreator. It’s too flaky about wanting to “own” the project. ___ Mailing

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

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

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

[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

Re: [Kicad-developers] [PATCH] Add/modify python APIs for querying available pcbnew footprints

resend, this time to the list and not just to Wayne. Keep forgetting that the replyto is the person I'm directly replying to and not the group. note that this is actually two mails I sent today. Miles On Thu, Mar 22, 2018 at 10:05 PM, miles mccoo wrote: > Attached is an

Re: [Kicad-developers] Lib maintainers request help for reviewing installation script changes

Hi everybody, Wayne Stambaugh writes: > If someone would pin down the exact version of cmake where this > available, I would appreciated it. My benchmark (Debian stable) is > currently shipping with 3.7.2 although that seems like a pretty current > version. I don't want

Re: [Kicad-developers] [PATCH] Fix for bug/1754049

No comments on the current discussion, it all makes sense. Just want to point out a couple things in case they were missed. The layers are being deleted (instead of disabled) to prevent DRC problems and prevent file cruft, according to comments in the code. kicad plugin is deleting layers from

Re: [Kicad-developers] Lib maintainers request help for reviewing installation script changes

Hello Rene, Am 22.03.18 um 15:13 schrieb Rene Pöschl: > Dear developers, > > we lib maintainers might be good at checking symbols and footprints > against datasheets, the KLC and industry standards but we are a bit lost > with the requirements of installation scripts. > > Could one of you

Re: [Kicad-developers] [PATCH] Fix for bug/1754049

Le 22/03/2018 à 18:48, Andrey Kuznetsov a écrit : > I thought we were talking about deleting layers, not disabling them? Both. The dialog disables layers. How to manage items living on disabled layers (considering they can live on more than one layer, like pads and keepout zones)? Currently, I

Re: [Kicad-developers] [PATCH] Fix for bug/1754049

Is there any good reason to allow "deleting" layers that are part of footprints? I could see deleting routing layers (inner copper, etc) but I think we should just get rid of the idea that you can "delete" the silkscreen etc., just make it "disable" so that it can be re-enabled without any fuss.

Re: [Kicad-developers] MeetUp of KiCad Developers, Librarians and Contributers on MiniDebConf in Hamburg?

Hi Wayne, Am 20.03.18 um 13:16 schrieb Wayne Stambaugh: > Hey Carsten, > > Thank you for organizing this! It sounds like it will be a lot of fun. > I wish I could make it but I doubt I will have the time. Although I > hope we have the stable release out before May 16. well, we can't have

Re: [Kicad-developers] [PATCH] Fix for bug/1754049

Le 21/03/2018 à 17:46, Wayne Stambaugh a écrit : > JP, > > Did you take a look at this patch? I know we have talked about this in > the past and that the fix would not be easy. Until we can define and > implement a complete solution, this could be a short term fix. When you > get a chance,

Re: [Kicad-developers] Lib maintainers request help for reviewing installation script changes

What do you mean with “Xcode to build KiCad” (or, what do you want to do)? Usually KiCad is built with clang from Xcode, so yes. Xcode itself is only an IDE. You definitely can use Xcode to edit source files or to debug KiCad built with usual cmake command line (just create an “empty" project

Re: [Kicad-developers] Lib maintainers request help for reviewing installation script changes

I Have a question for the OS X developers here. Are you using Xcode to build KiCAD? I would like to get started on building KiCAD with Xcode, so I am looking for some clues or advice if this is not possible/practical. Thanks to all of you for a great product. Jean-Paul N1JPL > On Mar 22,

Re: [Kicad-developers] Lib maintainers request help for reviewing installation script changes

If someone would pin down the exact version of cmake where this available, I would appreciated it. My benchmark (Debian stable) is currently shipping with 3.7.2 although that seems like a pretty current version. I don't want to bump the cmake version too high and drop a bunch of linux distros

Re: [Kicad-developers] Lib maintainers request help for reviewing installation script changes

This will break the nightlies for macOS, as the packaging scripts currently work around the fact that they didn't previously work on macOS with modifications. Is this something Nick or I can adjust the current nightlies to over the weekend, and then we make the cutover in the middle of next week?

Re: [Kicad-developers] Lib maintainers request help for reviewing installation script changes

​CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT​ is a relatively recent addition to cmake. Maybe 3.7 or so? I'd hesitate using that in the install script yet but maybe that's overly cautious. If you do use it, we need to bump the minimum version at the top as well. -S 2018-03-22 7:20 GMT-07:00

Re: [Kicad-developers] Lib maintainers request help for reviewing installation script changes

Looks fine to me but I would like one of our macos packagers to confirm the install path changes that are specific to macos before we merge them. On 3/22/2018 10:13 AM, Rene Pöschl wrote: > Dear developers, > > we lib maintainers might be good at checking symbols and footprints > against

[Kicad-developers] Lib maintainers request help for reviewing installation script changes

Dear developers, we lib maintainers might be good at checking symbols and footprints against datasheets, the KLC and industry standards but we are a bit lost with the requirements of installation scripts. Could one of you take a look at the changes in the following pull requests? -

Re: [Kicad-developers] Feedback on 6.0 work

That is the plan. On 3/21/2018 7:48 PM, Jeff Young wrote: > Good point.  I think that *is* the plan as far as I understand it. > >> On 21 Mar 2018, at 23:43, Jon Evans > > wrote: >> >> I actually thing that's a reasonable thing to think about