Re: [kicad] Re: Improvements to the http library

> What is your view on caching? I agree with Seth that HTTP standards should be used where possible. I also think it would be ideal if there is no need for a "version 2" HTTP library, and instead we can make incremental improvements that are backwards-compatible. > However, this would mean that

Re: [kicad] Re: Improvements to the http library

> My idea, which has not yet been thought of, is that the LIB_SYMBOL has a separate list of volatile fields that are only for the symbol chooser and may also be displayed differently, for example with italics or something like that. If volatile data is implemented, it should be supported in more

Re: [kicad] Re: Improvements to the http library

> In particular, with the idea of including volatile fields such as stock count, price or similar in the future. As discussed on previous gitlab MRs, volatile data should not be mixed up with part fields. Fields are specifically non-volatile. If you want to make a proposal for some system to

Re: [kicad] Cannot compile Kicad (branches: master, 8.0, 7.0) due to the gal library

What happens when you pass KICAD_USE_EGL=ON to cmake? On Fri, Apr 26, 2024 at 3:26 PM Sven Wehrend wrote: > > > I get the following error log: > > [ 7%] Built target pcm_settings > [ 7%] Building CXX object > common/gal/CMakeFiles/gal.dir/__/draw_panel_gal.cpp.o > In file included from >

Re: [kicad] Cannot compile Kicad (branches: master, 8.0, 7.0) due to the gal library

Your CMake output does not show any errors. It ends successfully. What error do you get when you try to build? On Fri, Apr 26, 2024 at 2:44 PM 'Sven Wehrend' via KiCad Developers wrote: > > Hello, I am new to the Kicad project but would like to contribute to give > back to the community. But

Re: [kicad] Re: Improvements to the http library

Hi Rosy, > I would be happy to invest time in revising the http library so that the > various problems can be solved, but I would like to know who I should talk to > so that the work is not in vain but is then accepted? This list is a good place, please say more about what you propose to do

Re: [kicad] .step export for all copper layers

> should we simply add an option "export any copper"? or would it be better to > make a layer-list to specify what should be exported? I think it would catch most use cases to just have a single toggle between outer layers and all layers. > how the export-dialog is made. is there a

Re: [kicad] Some questions to the roadmap for next time

b.com/kicad/code/kicad/-/issues/> - you can > >>>>> > search for related issues there, or start a new one. > >>>>> > > >>>>> > Hope this helps > >>>>> > > >>

Re: [kicad] Returning to contributing - high speed design tools

h runs these checks. My question is can we do > this before we start routing the board (i.e. query the DRC data structures > for some human-readable list of length / skew rules)? We could then only > run these constraints against the board during routing to potentially > reduce the O(N*M) burde

Re: [kicad] Returning to contributing - high speed design tools

Hi James, I think there are a number of people working on things in this area so it will be important to coordinate. I don't think working on time-based tuning should be started until some other overhauls to the existing length-based system are farther along. I would suggest that if you are

Re: [kicad] Some questions to the roadmap for next time

; Am 26.02.2024 um 20:08 schrieb 'Rafał Pietrak' via KiCad Developers: > > Hi Oliver, > > > > You've asked for snippet source - it came from this email by Jon. > > > > -R > > > > W dniu 26.02.2024 o 15:47, Jon Evans pisze: > >> Hello

Re: [kicad] Some questions to the roadmap for next time

Hello Oliver, On Mon, Feb 26, 2024 at 9:34 AM 'White Fox' via KiCad Developers < devlist@kicad.org> wrote: > > As far I know, KiCAD has no support for multiboard projects. I looked > out for something like a road map and found something on gitlab, but > maybe outdated. Last edit was 2020. >

Re: [kicad] Code formatting question

Yes, this is a norm. KiCad's code style is not 100% representable in clang-format, and we also have a policy of not doing bulk-reformatting of files. Make sure to configure your editor to not reformat lines that you didn't edit, and you should be OK. Personally I turn off auto-reformatting, and

Re: [kicad] dev platform suggestions.

Hi Glen, Debian or Ubuntu are both fine choices. The one thing to be aware of is that modern Ubuntu turns on Wayland by default, and Wayland has issues that cause KiCad bugs / certain features to not work properly. In both cases, you will need to use a newer version of wxWidgets (3.2, the newer

Re: [kicad] Unable to build

Hi, KiCad is not supported on this platform, so I doubt anyone can provide step-by-step build instructions. It sounds like you are getting stuck at the building wxWidgets stage? If so, you probably will need to step through that cmake and see where it is getting hung up. > P.S. Is it possible

Re: [kicad] Fully custom DRC rules using python

> I assume for most requirements this would be possible. I will have to do some proper analysis of the requirements to answer that fully though. I will try and deconstruct each requirement into a minimum set of constraints and conditions and try to find commonalities. Unfortunately the ECSS is not

Re: [kicad] Fully custom DRC rules using python

> implementing all (or most) rules from the ECSS-Q-ST-70-12C specification would result in quite a specialised rule set not really that applicable for non-space related projects. I'm not sure how practical this line of thought would be, but my first thought is: can we implement enough rule

[kicad] Re: new open-source electromagnetic field solver available (OpenWME)

Hello Steffen, Thanks for sharing this! Fabien Corona started working on KiCad integration with FEM solvers but the work is still in early stages. Perhaps there is some overlap in possible use cases. It is not immediately clear to me: is your library meant to work from "real" geometry (i.e. a

Re: [kicad] Re: Multiple track dragging development

thm and what is needed at least. >>> >>> Appreciate the pointer to looking at component dragger. >>> >>> Hi Stuart, >> >> I encourage you to have a look at this branch: >> https://gitlab.com/twlostow/kicad/-/commits/tom-multidrag-demo

Re: [kicad] bezier track developement

I suggest the first place to start is implementing Bezier shape creation (don't worry about tracks right now). KiCad already has some level of internal support for Beziers, it just isn't fully-supported by the UI. In the current nightlies, graphic shapes can take on nets. -Jon On Fri, Aug 25,

Re: [kicad] Building on Mac

The makefiles are generated by CMake, you run make in the build root (whatever directory you ran the cmake command in). On Mon, Jul 31, 2023 at 6:43 PM Jeff Berkowitz wrote: > Hello. I'm using KiCad Mac Builder on Mac and trying to follow > https://dev-docs.kicad.org/en/build/macos/. I got the

Re: [kicad] Re: Multiple track dragging development

Hi Stuart, Some general comments on this project: 1) This functionality should be built into the router, not into the edit routines outside the router IMO. So this should be implemented as part of DRAGGER probably. If you look at how the rest of the router works, you should be able to re-use

Re: [kicad] odcb connector development and usage

Hi Rico, On Thu, Jul 13, 2023 at 11:19 AM Rico Schmitt wrote: > Hi there, > > TLDR: Is the odbc connector here to stay? Of course > Are there any development > plans for it? Yes, can you be more specific? > I tried it and found some issues using it, I have > implemented a draft of my

Re: [kicad] eeschema: allow Kicad to talk to a database using EXTERNAL plugins (dll, so etc)

key. >>>>> >>>>> >>>>> Please let me know what you think. >>>>> >>>>> Cheers, >>>>> Andre >>>>> >>>>> On Tuesday, 19 July 2022 at 11:47:45 pm UTC+10 se...@kipro-pcb.com >>>>>

Re: [kicad] Coroutine stack cleanups

I'm not clear on how all platforms can take the same codepath since there is some fundamentally platform-specific code in here? Anyway, my own personal thoughts are that anyone looking to work on this area: 1) should be prepared to do their own testing on at least Windows + arm64 Mac + amd64

Re: [kicad] Stable nightly version still 7.0.5

Testing builds have a version string that includes the most recent tag along with further version info. So it is expected and correct that testing builds after 7.0.5 include the string 7.0.5 as *part* of the version info. The testing build version string is platform/package-dependent. The

Re: [kicad] Changes in KiCad nightly coordinates and plot

I'm guessing this is https://gitlab.com/kicad/code/kicad/-/commit/c31b5eb7d8b89cc3e7630fa0550e3a911b1204a5 which was an intentional change. The old numbers were more rounding errors than the new ones. On Fri, Jun 2, 2023 at 9:59 AM Salvador E. Tropea wrote: > Hi All! > > The last nightly run

Re: [kicad] 7.0.3 stable release update

before the release. I don't know what you mean by "major problems" so I can't comment on them without more details. On Tue, May 16, 2023 at 1:16 PM Christoph Moench-Tegeder wrote: > ## Jon Evans (j...@craftyjon.com): > > > We would appreciate further user testing of 7.0 testi

Re: [kicad] 7.0.3 stable release update

We would appreciate further user testing of 7.0 testing builds so that we can be confident in a 7.0.4 release soon. In addition to the Ubuntu PPA that Ian linked, you can grab the latest builds for Windows/Mac here: Windows:

Re: [kicad] GetCharExcludes

I updated the cmake requirements so that this will get caught at configuration time now (for 7.99 only; we'll still support older wxWidgets on the 7.0 branch) -Jon On Sun, Mar 5, 2023 at 9:40 AM Steven A. Falco wrote: > Thanks, Ian. I've turned off the F36 COPR builds. > > Steve > >

Re: [kicad] Any thoughts on Fedora bug 2169876?

We can start by asking the user to type "bt" in the gdb prompt after they get the crash, which will give us a clue (assuming the Fedora packages are compiled with debug symbols) Your other suggestions are good ones. -Jon On Wed, Feb 15, 2023 at 11:52 AM Steven A. Falco wrote: > A user has

[kicad] Packager recommendation: require installation of symbols and footprints with KiCad

Hi all, It recently got brought up that on some platforms it is currently easy to install KiCad without also installing the symbols and footprints. This causes issues for unexpecting users, because KiCad doesn't currently do a good job of allowing users to recover from this situation after

Re: [kicad] IDE for KiCad development

I assume you are talking about Qt Creator? It's a perfectly fine IDE but I don't use it for KiCad so I have no advice on what settings to tweak. I think most developers are using Visual Studio on Windows and CLion or XCode on macOS. On Linux I use CLion, but have also used VSCode and Sublime

Re: [kicad] Verify macOS implementation of the SpaceMouse integration.

OK, thank you for looking into this. Best, Jon On Wed, Dec 21, 2022 at 3:08 AM Markus Bonk wrote: > We have tried with a clean install as well as with a drifting device and > cannot reproduce the reported issue. > > > > -Markus > > > > *From:* Jon Evans > *S

Re: [kicad] Verify macOS implementation of the SpaceMouse integration.

(are they created on first use?) -Jon On Mon, Dec 19, 2022 at 9:59 AM Jon Evans wrote: > Hello Markus, > > Thanks for the info, it sounds like there is something particular going on > with that one user. > Does the backtrace below indicate that the user has the 3DxWare software > i

Re: [kicad] Verify macOS implementation of the SpaceMouse integration.

ocationg parts) > and viewing in the 3D Viewer, nor on exit. > > No crash logs were generated either. > > > > > > --Markus > > > > *From:* devlist@kicad.org *On Behalf Of *Markus Bonk > *Sent:* Monday, December 19, 2022 7:04 AM > *To:* Jon Evans >

Re: [kicad] Verify macOS implementation of the SpaceMouse integration.

b6083f4.dmg has 3D Mouse support. > > > > Markus > > > > *From:* Jon Evans > *Sent:* Wednesday, September 21, 2022 2:46 PM > *To:* Markus Bonk > *Cc:* devlist@kicad.org > *Subject:* Re: [kicad] Verify macOS implementation of the SpaceMouse > integration. > >

Re: [kicad] KiCad 4.0.7 does not have a release file error

> you won't have access to the footprints you had previously used. You can make a project-local library and export the old footprints to it if desired. I think that is a reasonable workflow. On Thu, Nov 3, 2022 at 1:40 PM Steven A. Falco wrote: > On 11/3/22 12:11 PM, Jon Evans

Re: [kicad] KiCad 4.0.7 does not have a release file error

KiCad 6.x should still be able to open these files even if they used old symbols and footprints. I'm not sure they would need "porting" other than saving in the updated format. New schematics can be made with new symbols/footprints as desired. On Thu, Nov 3, 2022 at 12:10 PM Steven A. Falco

Re: [kicad] KiCad 4.0.7 does not have a release file error

See also https://gitlab.com/kicad/code/kicad/-/issues/12820 If those users want to keep using 4.0.7 they need to host it themselves. -Jon On Thu, Nov 3, 2022 at 11:38 AM Marco Ciampa wrote: > Can somebody address this request or at least point to the right > direction of how to solve it in

Re: [kicad] Verify macOS implementation of the SpaceMouse integration.

ib > > [...] > > > > and the build works out of the box with 3D Mouse support. > > > > Can we have a copy of your build log so that we can compare what the > differences are? > > > > Markus > > > > *From:* Jon Evans > *Sent:* Mo

Re: [kicad] Verify macOS implementation of the SpaceMouse integration.

9/2016 and all > applicable local data protection laws and regulations of the countries > where the company operates. To revoke your consent or exercise all your > rights with regards to personal data, please contact us at > priv...@3dconnexion.com. > > *From:* Jon Evans >

Re: [kicad] Verify macOS implementation of the SpaceMouse integration.

Hi Markus, I think the build at https://kicad-downloads.s3.cern.ch/osx/nightly/kicad-unified-20220914-003354-f304e2d4f6.dmg should have this enabled. Let me know if you find it does not. -Jon On Thu, Sep 15, 2022 at 11:16 AM Jon Evans wrote: > I've enabled this for the next build, I

Re: [kicad] Verify macOS implementation of the SpaceMouse integration.

I've enabled this for the next build, I'll report back if it has any troubles (I'm currently unable to test locally). But, in any case, the upcoming code freeze is for new features only. Since 3Dconnexion driver support has already been merged, any bugfixes for it on macOS would not be

Re: [kicad] What's your idea about a new skin

KiCad supports custom color themes. There is an (unofficial) repository containing a number of options here: https://github.com/pointhi/kicad-color-schemes I'm sure an Altium-inspired theme would be accepted here. On Wed, Sep 14, 2022 at 11:36 AM Seyed Keyarash Ghiasi wrote: > Dear all devs,

[kicad] Packager alert: unixodbc dependency

Hi all, The initial work to support database libraries will be merged this week, which will introduce a dependency on unixodbc for non-Windows platforms. We've been testing this on Ubuntu, Fedora, and macOS with no issues so far. Please let me know if anyone has any concerns. Thanks, Jon --

Re: [kicad] wxWidgets 3.2.0 for Fedora

. On Fri, Aug 12, 2022 at 11:50 AM Steven A. Falco wrote: > On 8/12/22 11:36 AM, Jon Evans wrote: > > The surface area of wxPython on KiCad critical functionality is fairly > low. I would recommend moving forward and seeing what happens. > > > > How long do we ha

Re: [kicad] wxWidgets 3.2.0 for Fedora

The surface area of wxPython on KiCad critical functionality is fairly low. I would recommend moving forward and seeing what happens. How long do we have to make this decision/recommendation? It seems easy enough to spot-check the most popular KiCad plugins that make use of wxPython to see if

Re: [kicad] Verify macOS implementation of the SpaceMouse integration.

I will defer to @Adam Wolf for details, but my guess would be it is not enabled, because: 1) KICAD_USE_3DCONNEXION defaults to off, so must be turned on per-platform. 2) It is not referenced in kicad-mac-builder , so there is nothing

Re: [kicad] eeschema: allow Kicad to talk to a database using EXTERNAL plugins (dll, so etc)

sed >>>> in KiCad, then this needs to be done in a scripting language. >>>> >>>> There are a couple reasons for this. The big one is that MacOS cannot >>>> load a binary plugin from outside the signed application without triggering >>>> Gate

Re: [kicad] eeschema: allow Kicad to talk to a database using EXTERNAL plugins (dll, so etc)

these get signed with the rest of the >> application. So, if the target is to allow ODBC interaction, we can >> probably support a binary plugin interface that explicitly does that. I >> think that this is (#7436 >> <https://gitlab.com/kicad/code/kicad/-/issues/7436>) &

Re: [kicad] eeschema: allow Kicad to talk to a database using EXTERNAL plugins (dll, so etc)

Hi Andre, I think it would be best to have two different discussions here, first about the idea and concept, and second about your proposed implementation. I wanted to lead with this because I think there is a tendency in discussions to mix the two together unnecessarily. This is a real need and

Re: [Kicad-doc-devs] current version and master branch

KiCad uses semver "approximately". I am not quite sure if I understand the question correctly, but the docs branch names *are* synchronized with the code at the moment. The 6.0 docs branch is the stable one, and master is the nightly (6.99) one. -Jon On Mon, May 2, 2022 at 8:47 AM Marco Ciampa

Re: [Kicad-developers] Icon for 3D Mouse center of rotation

Hi Markus, Adding a new icon is certainly possible. There are some guidelines here: https://dev-docs.kicad.org/en/rules-guidelines/icon-design/ In particular, the icon must be added with an appropriate SVG source file authored in Inkscape and with the appropriate (CC-BY-SA) license attribute

Re: [Kicad-developers] Introduction of sentry application monitoring and error tracking

Thanks for putting in the work to get this integrated, Mark! Having automated crash dumps will be invaluable to improving KiCad stability. On Wed, Mar 30, 2022 at 8:32 PM Mark Roszko wrote: > > Hey folks, > > We are planning to introduce the use of the Sentry platform into KiCad. > Sentry

Re: [Kicad-doc-devs] to whom it may concern (Graham Keeth?) - kicad manual

The English screenshot is out of date; we removed the option to import old library configurations as it resulted in broken library configurations for too many users. On Sat, Mar 19, 2022 at 10:49 AM Marco Ciampa wrote: > > Hello devs, > in these days I was forced to stay home for a few days for

Re: [Kicad-developers] 6.0.2 tagged.

@seth - I think the docs need to be re-packed in the manner Christoph says, IIRC that is a requirement for the Mac packaging. On Fri, Feb 11, 2022 at 10:09 AM Christoph Moench-Tegeder < c...@burggraben.net> wrote: > Hi, > > ## Wayne Stambaugh (stambau...@gmail.com): > > > All of the repos have

Re: [Kicad-developers] V6 documentation

> THE MAIN PROBLEM ARE THE OUTDATED DOCUMENTS! > NOT THE WAY THEY ARE DISTRIBUTED. One reason the documents are outdated is that they are hard to contribute to. They are hard to contribute to in part because they use a toolchain that only works well on Linux, and many of our users who might feel

Re: [Kicad-developers] V6 documentation

age and then install it via a USB stick or whatever (but probably not in a secure environment), but you could also download the docs website. -Jon On Wed, Jan 19, 2022 at 5:03 PM Eeli Kaikkonen wrote: > On Wed, Jan 19, 2022 at 6:38 PM Jon Evans wrote: > > > > What I would propose to imp

Re: [Kicad-developers] V6 documentation

On Wed, Jan 19, 2022 at 2:12 PM Steven A. Falco wrote: > > Not to put words in your mouth, but it sounds like the code will be > changed so that when someone clicks on the Help menu, they will get the > on-line version, if possible. > And only if the on-line version cannot be accessed, the code

[Kicad-developers] V6 documentation

On Wed, Jan 19, 2022 at 1:05 PM Carsten Schoenert wrote: > [ I'm on this list, no need to address me dedicated. ] > My email client does this automatically, but if it bothers you I removed it manually :) > > Am 19.01.22 um 18:45 schrieb Jon Evans: > > > I think you misunde

Re: [Kicad-developers] V6 documentation

On Wed, Jan 19, 2022 at 12:37 PM Carsten Schoenert wrote: > Hello Jon, > > Am 19.01.22 um 17:38 schrieb Jon Evans: > > Carsten, > > > > There is no reason to remove the ability to package docs offline, I just > > don't think it should be a focus of the pr

Re: [Kicad-developers] V6 documentation

not saying we should remove any way for people in high-security offline environments to get documentation, but just that it shouldn't be the default option. -Jon On Wed, Jan 19, 2022 at 12:12 PM Steven A. Falco wrote: > On 1/19/22 12:00 PM, Jon Evans wrote: > > That just doesn't seem th

Re: [Kicad-developers] V6 documentation

;. I.e., Fedora builds are not a "rolling release" - they are > tied to tags. > > Steve > > On 1/19/22 11:38 AM, Jon Evans wrote: > > Carsten, > > > > There is no reason to remove the ability to package docs offline, I just > don't think

Re: [Kicad-developers] V6 documentation

Carsten, There is no reason to remove the ability to package docs offline, I just don't think it should be a focus of the project. The majority of users will be served better by keeping a "rolling release" online at docs.kicad.org (with a download button, ideally). > It absolutely doesn't hurt

Re: [Kicad-developers] V6 documentation

e documentation site easily downloadable to be viewed in a browser when > offline. > > > Thanks! > > Gabriel Staples > > (sent from my Android) > > Le mar. 18 janv. 2022, 11:12 AM, Jon Evans a écrit : > >> We have decided to update the online documentation

Re: [Kicad-developers] V6 documentation

The documentation lives in this git repo: https://gitlab.com/kicad/services/kicad-doc The same sources build the version on the website (docs.kicad.org) and the offline docs. If keeping the offline docs is important, I think the next best thing is to insert some extra text in the offline build

Re: [Kicad-developers] V6 documentation

ou can access online version > from the software, so why to include old (probably no more relevant) > documentation? > > Regards, > Tomas > > On Tue, 18 Jan 2022, 17:17 Jon Evans, wrote: > >> I don't personally see the point of spamming the list with back and forth >> abo

Re: [Kicad-developers] V6 documentation

I don't personally see the point of spamming the list with back and forth about setting up Git/Gitlab, installing dependencies, etc. But, I am not opposed to it if others don't care. -Jon On Tue, Jan 18, 2022 at 12:02 PM Marco Ciampa wrote: > On Tue, Jan 18, 2022 at 09:10:22AM -0500,

Re: [Kicad-developers] V6 documentation

Hi Tomas, I've been loosely coordinating documentation updates for V6. There are not very many other people working on it. We'd be happy to have your help. If you contact me off-list I can help you get set up to make changes and we can figure out where you'd like to start. Best, Jon On Tue,

Re: [Kicad-developers] Was the initial graphics mode screen removed?

we try to make KiCad applicable to more high-end designers, it could become an issue for more people. -Jon On Tue, Jan 11, 2022 at 4:46 PM pmx wrote: > > > Le 11/01/2022 à 21:59, Jon Evans a écrit : > > The current offerings (e.g. bgfx) are generally multi-platform but without > the

Re: [Kicad-developers] Was the initial graphics mode screen removed?

higher than 2.1. On Tue, Jan 11, 2022 at 3:57 PM pmx wrote: > > > Le 11/01/2022 à 21:10, Jon Evans a écrit : > > > IMHO, we shouldn't remove anything that helps to deal gracefully > > with the diversity of situations (like a virtual machine), graphics > &

Re: [Kicad-developers] Was the initial graphics mode screen removed?

> IMHO, we shouldn't remove anything that helps to deal gracefully with the diversity of situations (like a virtual machine), graphics hardware and video drivers... and their possible bugs ! (as stated about X11/Mesa). The fallback engine we use today does not have feature-parity with the

Re: [Kicad-developers] help compliling kicad

It looks like your source directory is dirty (not the build dir) Try "git clean -fx" or similar. -Jon On Fri, Dec 31, 2021 at 1:30 PM Marco Ciampa wrote: > Hello devs! > I need some help. > > Sometimes my cmake configuration goes wrong and I get stuck with this > kind of error: > > Built

Re: [Kicad-developers] 6.0.0 build flags

I agree, KICAD_PCM can be removed now. On Sat, Dec 25, 2021 at 7:27 AM Nick Østergaard wrote: > Having the unused parameters is no harm, it will only generate a > warning at configure time. > > The KICAD_PCM flag already defaults to ON, but I guess it should just > be removed as an option? Are

Re: [Kicad-doc-devs] The future of the Getting Started chapter

On Sat, Nov 27, 2021 at 05:38:54PM -0500, Jon Evans wrote: > > As you might know, there is a chapter in the documentation called Getting > > Started in KiCad [1] which is at this point entirely out of date and does > > not really cover the modern KiCad workflow. I have seen man

[Kicad-doc-devs] The future of the Getting Started chapter

As you might know, there is a chapter in the documentation called Getting Started in KiCad [1] which is at this point entirely out of date and does not really cover the modern KiCad workflow. I have seen many people point new users at various video series or posts on the user forum as more

Re: [Kicad-developers] New lead developer announcement

Welcome Mikolaj! Happy to have you in this role :) -Jon On Fri, Nov 19, 2021 at 9:15 AM Wayne Stambaugh wrote: > I am happy to announce that Mikolaj Wielgus has accepted an invitation > to become a member of the KiCad lead development team. Mikolaj has made > some significant contributions

Re: [Kicad-developers] Version 6 release candidate 1

2021 um 14:58 -0500 schrieb Jon Evans: > >> When do you need it by? The docs are nowhere near ready for the > >> final release, so if this isn't a hard requirement, I would suggest > >> not bothering to package the docs for now. > > > > I hope to get 6.0.0-

Re: [Kicad-developers] Version 6 release candidate 1

Well, the new docs are not translated yet either, so there's that :) On Thu, Nov 18, 2021 at 3:04 PM Johannes Maibaum wrote: > Am Donnerstag, dem 18.11.2021 um 14:58 -0500 schrieb Jon Evans: > > When do you need it by? The docs are nowhere near ready for the > > final release, s

Re: [Kicad-developers] Version 6 release candidate 1

When do you need it by? The docs are nowhere near ready for the final release, so if this isn't a hard requirement, I would suggest not bothering to package the docs for now. On Thu, Nov 18, 2021 at 2:52 PM Johannes Maibaum wrote: > Hi Seth & list, > > Am Dienstag, dem 16.11.2021 um 12:52

[Kicad-developers] Calling all Python devs - KiCad 6 and plugin repository information

Hi all, If you develop Python plugins for KiCad, this message is for you! First of all, as you have probably seen, the new Python API won't be included in KiCad 6.0. We still want to support the existing SWIG API that allows the creation of action plugins in the PCB editor and external scripts,

Re: [Kicad-developers] Stability drive? [was Re: Version 6 release schedule]

). However, if we at least know that a problem exists upstream, than we can track it and volunteer devs who may have time to work on it can find it. -Jon On Mon, Nov 8, 2021 at 11:49 AM Jon Evans wrote: > I certainly agree with a stability drive, I would just caution to not > assume that th

Re: [Kicad-developers] Stability drive? [was Re: Version 6 release schedule]

t to > fix them (if possible) anyway because they could be hiding other issues, > either in a wood-trees way or because of side effects. The same applies to > warnings from the compiler, etc. > > Regards, > > Ruth > > > On 08/11/2021 16:38, Jon Evans wrote: > > Hi

Re: [Kicad-developers] Stability drive? [was Re: Version 6 release schedule]

Hi Ruth, Thanks for the notes. There is a lot of content in your email, and I worry it will get lost if it doesn't get split up into multiple issues on the issue tracker. Some of the issues you mention (GTK warnings, ASan issues related to Python, etc) are known issues and we don't plan to fix

Re: [Kicad-developers] Version 6 release schedule

Hi Jan and José, Unfortunately I don't have a status update for you on the pybind11 API. I'm going to investigate fixing the regressions in the SWIG API so that your plugins can access the board design settings again. Best, Jon On Mon, Nov 1, 2021 at 6:04 AM Jan Mrázek wrote: > Hello Wayne

Re: [Kicad-developers] Note to packagers: new data dependency for KiCad PCM

Hi Carsten, Sorry I was not clear, yes this is a dependency for the main binaries so it should go in the main package if you have multiple packages. Best, Jon On Mon, Nov 8, 2021 at 2:53 AM Carsten Schoenert wrote: > Hello Jon, > > Am 08.11.21 um 03:30 schrieb Jon Evans: &

[Kicad-developers] Note to packagers: new data dependency for KiCad PCM

Hi all, We just turned the plugin and content manager (PCM) feature on for all users. To work properly, this feature needs an additional directory packaged: $KICAD_DATA/schemas If your packaging scripts already grab everything inside $KICAD_DATA, you should not need to do anything. If you

[Kicad-developers] Ending support for macOS 10.14

Hi all, As described in more detail in a forum thread[1], Homebrew no longer packages opencascade for macOS 10.14. As opencascade is a requirement for KiCad, this means that we can no longer build on 10.14 and therefore cannot support 10.14 for the 5.99 nightly builds or the upcoming 6.0 stable

Re: [Kicad-developers] ngspice-35

Thanks Holger, I tested a fix and it works now (6b48825a) Updated https://gitlab.com/kicad/packaging/kicad-mac-builder/-/merge_requests/344 to bump to ngspice-35. I guess Mark can do the same in vcpkg for the Windows build. -Jon On Mon, Aug 9, 2021 at 1:50 PM Holger Vogt wrote: > Hi Jon, > >

Re: [Kicad-developers] ngspice-35

Hi Holger, Thanks for the notice. I tested this on macOS and had no trouble compiling or running, although KiCad does not properly display the ngspice version anymore (probably a KiCad bug) -Jon On Sun, Aug 8, 2021 at 4:14 PM Holger Vogt wrote: > ngspice-35 is available. > > Please see

Re: [Kicad-developers] old ngspice in 599 macOS nightly

Hi Holger, Last time Adam and I looked at this, I could not build ngspice-34 and kicad-nightly on macOS because of the issue with config.h changing. I have not tried recently; Adam, have you? -Jon On Wed, Jul 21, 2021 at 11:14 AM Holger Vogt wrote: > The nightly for macOS from July 20th is

Re: [Kicad-developers] Any pointers to speed up the build

I think from your screenshots in the issue you're working on that you're on Windows -- I can second that using Visual Studio / MSVC is significantly faster than mingw. Also, if you are testing something over and over in eeschema or pcbnew, just building that one target and running from the build

Re: [Kicad-developers] Help needed to configure gdb

gdb ./kicad/kicad is starting KiCad from the build directory. This isn't a fully-supported way of debugging KiCad, but if you want to do this, you must set the environment variable KICAD_RUN_FROM_BUILD_DIR=1 Alternatively, since you are running `make install` above, you can use gdb to debug

Re: [Kicad-developers] For those wondering about KiCad version 5.99.0 in Debian unstable...

Hi Carsten, I was reminded of this thread because of this forum post: https://forum.kicad.info/t/how-install-kicad-6-x-on-debian/30034/4 Is the fact that there is a 6.0.0 tag on experimental also related to this issue with versioning? Best, Jon On Sun, Apr 11, 2021 at 2:25 AM Carsten Schoenert

Re: [Kicad-developers] Coding style Policy (https://dev-docs.kicad.org/en/rules-guidelines/code-style/)

https://dev-docs.kicad.org/en/rules-guidelines/code-style/ has been updated to clarify this point. -Jon On Mon, Jul 5, 2021 at 12:32 PM Jon Evans wrote: > Lines which only contain braces do count as a blank line in this context. > We should clarify this in the style guide. > >

Re: [Kicad-developers] Coding style Policy (https://dev-docs.kicad.org/en/rules-guidelines/code-style/)

Lines which only contain braces do count as a blank line in this context. We should clarify this in the style guide. Best, Jon On Mon, Jul 5, 2021 at 2:20 AM Markus Bonk wrote: > Hi, > > > > In my opinion there may be issues with the examples in the KiCAD coding > style doc relating to 4.2.3

Re: [Kicad-developers] Experience compiling latest HEAD

Hi Ruth, You can build the nightly flatpak (with wx 3.1) by grabbing this repository and following the instructions in the readme: https://gitlab.com/kicad/packaging/kicad-flatpak/kicad-nightly-flatpaks/kicad-nightly-flatpak Johannes can probably answer any detailed questions better than I, but

Re: [Kicad-developers] Fatal Python error: failed to get the Python codec of the filesystem encoding

Please see https://dev-docs.kicad.org/en/build/windows-msvc/ at the bottom, the "running and debugging" section. Now that Python is required, you must tell KiCad how to find Python when running from Visual Studio. The options are to set the environment variables as explained on that page, or

Re: [Kicad-doc-devs] Thai translation

Hi BK and welcome! Starting with Weblate sounds like a good plan. Right now the user manual (English sources) is being (slowly) re-written to prepare for 6.0 RC (expected hopefully in the next few months). So, it might be good to only translate the updated parts (mostly just the "kicad" and

  1   2   3   4   5   6   7   8   9   10   >