Re: [Kicad-developers] [PATCH] Fixes for Visual Studio / vcpkg build

Jon Thanks so much! I am busy working with Alexander on renumbering so it may take me a few days to see if I can get it to work. Brian From: Jon EvansSent: November 29, 2019 9:19 PMTo: Brian PiccioniCc: KiCad DevelopersSubject: Re: [Kicad-developers] [PATCH] Fixes for Visual Studio / vcpkg build 

Re: [Kicad-developers] [PATCH] Fixes for Visual Studio / vcpkg build

Hi Brian, I will try to write a better guide, especially if I can get a full (all options) KiCad build going rather than a minimal one. In the meantime, I'm attaching my CMakeSettings.json from VS2019 in case it's helpful. It has a hard-coded toolchain path that you'll have to check/update. I

Re: [Kicad-developers] v6 roadmap and schedule (was Re: 5.1.5 released.)

pe 29. marrask. 2019 klo 20.28 Ruth Ivimey-Cook (r...@ivimey.org) kirjoitti: > I would be interested to know why it is not possible/good to use "normal" > outline fonts (ttf, otf et al) on a PCB what are the issues? > That's an easy one to answer, at least partially. PCB needs graphics which

Re: [Kicad-developers] Linux Packagers: Resource File Updates

Hi Ian, Am 29.11.19 um 12:16 schrieb Ian McInerney: > Carsten, thanks for pointing those changes out. I will update the file > with them as well. Redoing the screenshots is also on my todo list > (since they still show a v4 release currently). Do you know what the > guidelines are for sizing of

Re: [Kicad-developers] GitLab migration

On 2019-11-29 10:15, Wayne Stambaugh wrote: Hi Simon, On 11/29/2019 1:09 PM, Simon Richter wrote: Hi Wayne, On Fri, Nov 29, 2019 at 12:49:30PM -0500, Wayne Stambaugh wrote: I will also be disabling the Launchpad blueprint and answers pages as well. We not going to migrate the blueprints to

[Kicad-developers] v6 roadmap and schedule (was Re: 5.1.5 released.)

Hi, On 29/11/2019 13:56, Wayne Stambaugh wrote: It's not as up to date as it should be but it's pretty close https://docs.kicad-pcb.org/doxygen/v6_road_map.html I'm hoping some feedback on these goals would be welcomed: User Interface Modernization *Goal:* Give KiCad a more modern

Re: [Kicad-developers] GitLab migration

We will have to figure this out as we go. What ever platform we use, it will not be the free for all that we currently have. On 11/29/2019 1:19 PM, Jon Evans wrote: > As far as I know, there is not fine-grained access control on Wiki > pages.  The only way to do something like this to create a

Re: [Kicad-developers] GitLab migration

As far as I know, there is not fine-grained access control on Wiki pages. The only way to do something like this to create a separate project just for a public wiki. Then a limited set of people would have permissions to copy things from the public wiki to the main KiCad project wiki. To be

Re: [Kicad-developers] GitLab migration

Hi Simon, On 11/29/2019 1:09 PM, Simon Richter wrote: > Hi Wayne, > > On Fri, Nov 29, 2019 at 12:49:30PM -0500, Wayne Stambaugh wrote: > >> I will also be disabling the Launchpad blueprint and answers pages as >> well. We not going to migrate the blueprints to GitLab because the >> entire

Re: [Kicad-developers] GitLab migration

Hi Wayne, On Fri, Nov 29, 2019 at 12:49:30PM -0500, Wayne Stambaugh wrote: > I will also be disabling the Launchpad blueprint and answers pages as > well. We not going to migrate the blueprints to GitLab because the > entire blueprint system is a mess due to the lack of sane permissions. > We

[Kicad-developers] GitLab migration

In case you haven't been paying attention, KiCad is in the process of migrating to GitLab. This process will happen slowly starting with the source repo and eventually culminating in all of the repos that KiCad directly and indirectly depend on being migrated as well. The first thing to migrate

Re: [Kicad-developers] v6 roadmap and schedule (was: Re: 5.1.5 released.)

pe 29. marrask. 2019 klo 16.41 Wayne Stambaugh (stambau...@gmail.com) kirjoitti: > > There is no way I would attempt to determine or mandate the order which > features get merged. They will get merged based on their readiness to > be merged. > I thought there might be something else, like

Re: [Kicad-developers] v6 roadmap and schedule (was: Re: 5.1.5 released.)

On 11/29/2019 9:32 AM, Eeli Kaikkonen wrote: > > > pe 29. marrask. 2019 klo 15.56 Wayne Stambaugh (stambau...@gmail.com > ) kirjoitti: >> >> It's not as up to date as it should be but it's pretty close >> >> https://docs.kicad-pcb.org/doxygen/v6_road_map.html > > >

[Kicad-developers] v6 roadmap and schedule (was: Re: 5.1.5 released.)

pe 29. marrask. 2019 klo 15.56 Wayne Stambaugh (stambau...@gmail.com) kirjoitti: > > It's not as up to date as it should be but it's pretty close > > https://docs.kicad-pcb.org/doxygen/v6_road_map.html As you surely know, everybody is very interested about not only the features but also the

Re: [Kicad-developers] Linux Packagers: Resource File Updates

Am 29.11.19 um 13:01 schrieb Nick Østergaard: > I have not seen any packaging scripts depend on it, if it does I think it > is fair for the package to be updated, but isn't it alreade handled by the > make install step? That's correct, so far I know all distros build the package and install the

Re: [Kicad-developers] 5.1.5 released.

It's not as up to date as it should be but it's pretty close https://docs.kicad-pcb.org/doxygen/v6_road_map.html On 11/27/2019 9:13 PM, Tim Hawkins wrote: > Is there a roadmap and timeline for 6.0 publicaly available? > > On Thu, Nov 28, 2019, 9:30 AM Steven A. Falco,

Re: [Kicad-developers] Linux Packagers: Resource File Updates

I have not seen any packaging scripts depend on it, if it does I think it is fair for the package to be updated, but isn't it alreade handled by the make install step? fre. 29. nov. 2019 12.59 skrev Ian McInerney : > Thanks for the feedback. > > Steve, I won't be changing anything about how the

Re: [Kicad-developers] Linux Packagers: Resource File Updates

Thanks for the feedback. Steve, I won't be changing anything about how the version information is generated, only adding a tag to the appdata file to contain the full version (this will be the same as the version that gets displayed in the help window, so it contains the distro-specific extra

Re: [Kicad-developers] Space used on server

Hi Nick, I'm not asking for anything. Just, I'm using a hacky way to mirror the downloads to Sourceforge, involving storing a complete copy locally. I'm definitely going to architect a solution that doesn't require that if it becomes a problem for me, but I thought I'd let the list know just in

Re: [Kicad-developers] Space used on server

What are you asking? On Fri, 29 Nov 2019 at 10:44, tedd.t...@gmail.com wrote: > > Hi all, > > Just a quick note in case no-one's aware. I remember before the move > to CERN's infrastructure, the server hosting all the builds had a > script to delete old testing builds, presumably to keep space

[Kicad-developers] Space used on server

Hi all, Just a quick note in case no-one's aware. I remember before the move to CERN's infrastructure, the server hosting all the builds had a script to delete old testing builds, presumably to keep space used in check. Since the move, there hasn't been any deletions of testing builds, and as of

Re: [Kicad-developers] 5.1.5 released.

For those on fedora, i just got 5.1.5 through dnf update On Thu, Nov 28, 2019, 7:47 AM Wayne Stambaugh, wrote: > KiCad 5.1.5 has officially been released[1]. Thank you to everyone who > contributed your time and talent to make this release possible. > > Cheers, > > Wayne > > [1]: