Hi Mariusz,
On 5/2/24 1:50 PM, Mariusz Plucinski wrote:
Hi,
Am 01.05.24 um 20:50 schrieb Wayne Stambaugh:
Hello Mariusz,
On 5/1/24 9:42 AM, Mariusz Plucinski wrote:
Hi all,
I'm new here, and to KiCad in general. Trying to come up with a
workflow that'd suit me best, I encountered some
Hello Mariusz,
On 5/1/24 9:42 AM, Mariusz Plucinski wrote:
Hi all,
I'm new here, and to KiCad in general. Trying to come up with a workflow
that'd suit me best, I encountered some limitations. So here I am,
looking for advices on how to lift them, and how to convert my ideas
into
The KiCad project is proud to announce the latest version 8 bug fix
release. See the blog post[1] on the KiCad website for more information
about this release. Thank you to everyone who made this release possible.
Wayne
[1]: https://www.kicad.org/blog/2024/03/KiCad-8.0.1-Release/
--
You
If you are not aware, 7.0.11 was release yesterday. This will most
likely be the last 7.0 branch bug fix release. We will continue to back
port fixes to this branch if they are trivial to back port so users who
continue to run the 7.0 branch will be able to run testing builds.
Stable
Hi Jan,
The feature and string freeze policy applies to features hidden behind
and advanced configuration settings. Developer only features (such as
the PNS router developer tools) and unit tests are exempt from the
freeze policy.
Cheers,
Wayne
On 2/20/24 5:41 AM, Jan Wichmann wrote:
The development branch of KiCad is officially in string freeze as we
prepare for the release of 8.0.0. Please do not make any string changes
except for spelling and grammar errors so we can give our translators
adequate time before we release. Thank you for your cooperation.
Kind Regards,
The stable version 7.0.9 of KiCad has been released. More information
about this release can be found in the release announcement[1]. Thank
you to everyone who made this release possible.
Cheers,
Wayne
[1]: https://www.kicad.org/blog/2023/11/KiCad-7.0.9-Release/
--
You received this
We will be releasing 7.0.9 on Tuesday, October 31st barring any show
stoppers.
Cheers,
Wayne
--
You received this message because you are subscribed to the Google Groups "KiCad
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Hi Javier,
As the KiCad project leader and as a developer who was with the project
when CERN initially made it's decision to support KiCad, I would like to
extend my sincerest thanks to all of the help that CERN has provided.
From handling donations to paying for developer time, CERN has
(https://launchpad.net/~kicad/+archive/ubuntu/kicad-7.0-nightly) I
only see:
7.0.6-rc3-2-testing~172+202307051204~9d5f85634c~ubuntu22.04.1
Which seems to be quite old. Any ideas?
Regards, SET
On 2/8/23 08:21, Wayne Stambaugh wrote:
> We are planning to release
-7.0-nightly) I only
see:
7.0.6-rc3-2-testing~172+202307051204~9d5f85634c~ubuntu22.04.1
Which seems to be quite old. Any ideas?
Regards, SET
On 2/8/23 08:21, Wayne Stambaugh wrote:
We are planning to release version 7.0.7 on August 15th. This means
that we will tag the repos on the 13th
We are planning to release version 7.0.7 on August 15th. This means
that we will tag the repos on the 13th. If you have any remaining tasks
to complete for the next bug fix release, please have them done by this
date or they will have to wait until 7.0.8. Thank you for your cooperation.
Hi Marco
On 7/5/23 12:33 PM, Marco Ciampa wrote:
On Wed, Jul 05, 2023 at 11:52:36AM -0400, Wayne Stambaugh wrote:
The 7.0 branch has been tagged for 7.0.6. The plan is to announce the
release tomorrow. Getting 7.0.6 out was a bit of a challenge. Hopefully
7.0.7 will go smoothly. Thank you
The 7.0 branch has been tagged for 7.0.6. The plan is to announce the
release tomorrow. Getting 7.0.6 out was a bit of a challenge.
Hopefully 7.0.7 will go smoothly. Thank you to everyone who contributed
to releasing 7.0.6.
Cheers,
Wayne
--
You received this message because you are
Hi John,
You may want to consider creating a DXFLIB_PLOTTER object along with the
logic to use it rather than risking breaking the existing DXF_PLOTTER.
I don't know that anyone on the development team has any experience with
using dxflib to write to DXF. Once the DXFLIB_PLOTTER object is
This latest bug fix version of KiCad has been released[1]. Due to some
unfortunate regressions, 7.0.3 and 7.0.4 had to be pulled. Thank you to
everyone who made this release possible.
Cheers,
Wayne
[1]: https://www.kicad.org/blog/2023/05/KiCad-7.0.5-Release/
--
You received this message
Due to an unexpected critical bug in the 7.0.3 packages, there will be
no official 7.0.3 release. We will be releasing 7.0.4 on Tuesday, May
23rd barring anything unexpected.
Cheers,
Wayne
--
You received this message because you are subscribed to the Google Groups "KiCad
Developers"
Unfortunately, it 7.0.3 is not going to be officially released. A
serious bug was found in the PNS router in the release packages so we
are going to push a 7.0.4 release after some additional testing to make
sure the issue is fixed. Sorry for the inconvenience.
Cheers,
Wayne
--
You
This is a friendly reminder that we are planning on releasing 7.0.3 on
May 14th barring anything unexpected. If you have any issues with this
date, please let me know so we can adjust accordingly.
Cheers,
Wayne
--
You received this message because you are subscribed to the Google Groups
I am the KiCad lead developer but the final decision for adding a
feature of this magnitude would require buy in from the lead development
team. If you interested in contributing to KiCad, we can discuss how to
move forward. I suspect that integrating chip design features into
KiCad will be
Hi Sagar,
There is definitely interest in including chip design capability in
KiCad, when that happens really depends on a lot of factors. I'm not
familiar with the code listed below, but a good start to getting a
feature like this into KiCad would be to ensure all of the code in the
list
Hello Chistoph,
I apologize for not announcing the 7.0.2 release was pending a few weeks
ago like I normally do. It just fell through the cracks this time. I
will try to be more mindful in the future for making sure folks who are
not on the Zulip developer list are kept in the loop of new
We also have lots of opportunities for
sponsorships, booths and community projects.
If you would like to speak at KiCon, now is your opportunity to submit
a talk proposal <https://kicon.kicad.org>. Expect to see talks by
Wayne Stambaugh and the KiCad lead development team as well as a
1 Mar 2023 at 02:56, Wayne Stambaugh wrote:
Hi Liang,
I would be surprised if the this was all the files that needed to
be updated in order to add more copper layers. Without actually
seeing your changes, it's impossible for me to know for sure. I
don't see any DRC source fi
KiCAD.
Could you please kindly check if those files are enough?
image.png
Sincerely
Liang
On Fri, 24 Feb 2023 at 00:45, Wayne Stambaugh
wrote:
Hi Liang,
The LSET object is merely where it's possible to add new layers
but doing so will not be helpful and possibly harmful if yo
Hi Liang,
The LSET object is merely where it's possible to add new layers but
doing so will not be helpful and possibly harmful if you don't
understand how layers work internally. Virtually every object on boards
and footprints has to understand what the layers mean in order for them
to
The KiCad project is excited to announce that Fabien Corona has accepted
an invitation to become the latest member of the KiCad lead development
team. Please join me in welcoming Fabien to the team.
Cheers,
Wayne
--
You received this message because you are subscribed to the Google Groups
The latest major version of KiCad has been released. The website should
be updated shortly and most of the major platform packages are already
available for download. Thank you to everyone who contributed to
version 7 of KiCad.
Enjoy,
Wayne
--
You received this message because you are
2023 at 1:55 PM Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote:
James,
In order to do this correctly, you will have to use SCH_SHEET_PATH
objects using the complete schematic hierarchy to differentiate ERC
issues in shared SCH_SCREEN objects. I'm not sure this is
James,
In order to do this correctly, you will have to use SCH_SHEET_PATH
objects using the complete schematic hierarchy to differentiate ERC
issues in shared SCH_SCREEN objects. I'm not sure this is really that
important to fix. When an ERC issue is fixed in a SCH_SCREEN object, it
gets
Unfortunately it looks like we are going to miss our planned 7.0.0
release date of January 31st. Packaging wxPython for our Ubuntu PPA is
proving more difficult than expected. As soon as we have this issue
resolved, we intent to release one week later. Hopefully we will get
this issue
The latest and hopefully last stable release of the 6.0 branch has been
release[1]. Thank you to everyone who made the this release possible.
Hopefully everything goes well and 7.0.0 will be release on January 31st.
Cheers,
Wayne
[1]: https://www.kicad.org/blog/2023/01/KiCad-6.0.11-Release/
Hi Prasad,
We are planning on implementing pad stacks during version 8 development.
We currently are not planning back drill support for the initial pad
stack implementation but it's certainly something we would like to
implement.
That being said, pad stacks will require massive internal
On 12/13/22 9:25 AM, Steven A. Falco wrote:
On 12/12/22 07:19 PM, Wayne Stambaugh wrote:
The 6.0.10 stable release of KiCad is planned for Monday, December
19th. If you have any last minute changes to get into any of the
repos, now is the time. I plan on tagging the 6.0 branch on Saturday
The 6.0.10 stable release of KiCad is planned for Monday, December 19th.
If you have any last minute changes to get into any of the repos, now
is the time. I plan on tagging the 6.0 branch on Saturday to allow time
for our builders to complete and upload to the KiCad download sites.
Cheers,
The version 7 string freeze will begin December 7th which means the last
day to submit string changes is December 6th. I know the original date
was December 1st but we still have too many string changes to get
committed. After the freeze, only spelling errors, gross grammatical
errors, and
I am happy to announce that Carsten Presser is our new library team
lead developer. During our discussions at CERN, he agreed to take over
the lead library developer role which has been doing for some time now.
Please join me in congratulating Carsten on his new "official" role.
Cheers,
The latest stable version of KiCad has been release. You should upgrade
to get the latest bug fixes. For more information about this release,
please see the blog post on the KiCad website[1]. Thank you to everyone
who made this release possible.
Cheers,
Wayne
[1]:
We are planning on tagging all of the repos for stable release 6.0.9 on
Saturday, October 29th and the release announcement on October 31st. If
you have commits that need cherry-picked from master or any other
changes, now is the time. Thank you everyone for your contributions to
the KiCad
Sorry for the late announcement but as of October 1st, we were
officially in feature freeze for version 7. That means no new features
can be pushed to the development branch of KiCad. Any merge requests
that contain new features will be deferred until the version 8
development window opens
I am happy to announce that Aleksandr Shvartzkop (das-t on GitLab) has
agreed to accept an invitation to the KiCad lead development team.
Aleksandr has been contributing some nice optimization improvements and
other improvements to KiCad for some time and the lead development team
decided it
We now have a pretty good number of bug fixes in the stable branch so
it's time to start thinking about the next stable release. I plan on
tagging 6.0.8 on Tuesday, September 27th and making the release
announcement on Thursday the 29th. Please let me know if anyone has any
issues with this
Just a quick heads up to everyone working on version 7 of KiCad, the
feature freeze is scheduled for the end of the month (September 30th).
If you have any new feature development in progress, it must be pushed
to the main repo by then or it will have to wait until after the stable
release. I
On 8/9/22 7:27 PM, Steven A. Falco wrote:
On 8/9/22 06:42 PM, 'Ian McInerney' via KiCad Developers wrote:
On Tue, Aug 9, 2022 at 8:50 PM Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote:
On 8/9/2022 3:13 PM, Steven A. Falco wrote:
> On 8/9/22 03:08 PM, Wayne Sta
On 8/9/2022 3:13 PM, Steven A. Falco wrote:
On 8/9/22 03:08 PM, Wayne Stambaugh wrote:
Hi Steve,
On 8/9/2022 2:37 PM, Steven A. Falco wrote:
For those who don't follow the Fedora development list, i.e. most
everyone :-), I've attached two emails related to wxWidgets and
wxPython. It looks
Hi Steve,
On 8/9/2022 2:37 PM, Steven A. Falco wrote:
For those who don't follow the Fedora development list, i.e. most
everyone :-), I've attached two emails related to wxWidgets and
wxPython. It looks like we will soon have wxWidgets/wxPython 3.2.0 in
Rawhide.
This change won't apply to
t. It may
be a setting in GitLab. When I have some time to look at it I will.
I'm not terribly thrilled with the current solution but it resolved most
of our issues so we could get 6.0.7 released.
Niki
On Thu, 2022-07-28 at 07:55 -0400, Wayne Stambaugh wrote:
Hi Nikki,
Unfortunately
126 is beyound the 6.0.7
release point I guess.
This is the version string that CMake writes out:
Writing
/home/niki/Sync/Kicad/Software/kicad-6.0-build_Release/kicad_build_version.h
file with version: (6.0.6-126-g39dd51490d)
Best regards
Niki
On Wed, 2022-07-27 at 15:43 -0400, Wayne Stambaugh
Version 6.0.7 of KiCad has officially been released[1]. Thank you
everyone for your efforts in making this release possible.
Cheers,
Wayne
[1]: https://www.kicad.org/blog/2022/07/KiCad-6.0.7-Release/
--
You received this message because you are subscribed to the Google Groups "KiCad
The latest stable version six branch of KiCad has been released[1].
Thank you to everyone who contributed there time and talent to make this
stable release of KiCad possible.
Cheers,
Wayne
[1]: https://www.kicad.org/blog/2022/06/KiCad-6.0.6-Release/
One other thing that I forgot, it would be nice if we could get some
extra eyes on the recent router changes to make sure there are no
regressions. Please download the latest testing build and help with the
testing if possible.
On 6/11/22 11:32, Wayne Stambaugh wrote:
> We now have a suffici
We now have a sufficient number of bug fixes in the 6.0 branch to start
thinking about a 6.0.6 stable release. The goal is to tag 6.0.6 Friday,
June 17th and make the release announcement on the 19th. If anyone has
any last minute commits to make to the documentation and/or libraries,
now is the
hpad.net/kicad-developers/msg43255.html
> <https://lists.launchpad.net/kicad-developers/msg43255.html>
> [2]
> https://launchpad.net/~mhier/+archive/ubuntu/libboost-latest/+packages
> <https://launchpad.net/~mhier/+archive/ubuntu/libboost-latest/+packages>
>
> On Mon,
It looks like someone back ported some random number generator fixes
from master that are not available in boost 1.56 which is the minimum
version in the 6.0 branch. We should address this since 18.04 LTS is a
supported system[1].
[1]:https://www.kicad.org/help/system-requirements/
On 5/9/22
Stable version 6.0.5 has officially been release. See the release
announcement[1] for more information. Thanks to everyone who made this
release possible.
Cheers,
Wayne
[1]:https://www.kicad.org/blog/2022/05/KiCad-6.0.5-Release/
___
Mailing list:
Yet another last minute critical issue was fixed yesterday so I'm
pushing tagging back another week. I will tag 6.0.5 on Monday, May 2nd.
Wayne
On 4/25/22 12:02 PM, Wayne Stambaugh wrote:
> Sending this again because apparently some folks on the mailing list
> didn't get it.
Sending this again because apparently some folks on the mailing list
didn't get it. Sorry for the noise.
Wayne
On 4/22/22 7:39 AM, Wayne Stambaugh wrote:
> Due to another crash bug being fixed, the new freeze date started on
> April 19th. To allow a full week of testing, I will be t
Due to another crash bug being fixed, the new freeze date started on
April 19th. To allow a full week of testing, I will be tagging 6.0.5 on
Wednesday, April 27th.
Cheers,
Wayne
On 4/15/22 6:30 PM, Wayne Stambaugh wrote:
> The 6.0 source branch repo has been frozen for the upcoming 6.
The 6.0 source branch repo has been frozen for the upcoming 6.0.5 stable
release. I plan on tagging the source branch on April 22nd and release
on the 24th. If you have any last minute library or documentation
changes that you would like to make before we have to tag those repos,
now is the
Thanks Mark!
On 3/31/22 11:37 AM, Jon Evans wrote:
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
Hi Markus,
The KiCad version 7 feature freeze date is September 30th so your MR
would have to be merged by that date to make it in V7. Given that the
Pcbnew and 3D viewer SpaceMouse code was a rather large change set, you
should probably submit the MR by the end of August to allow time for
The stable version 6.0.4 of KiCad has been released. The packages for
most major platforms should be available. The reason there was no 6.0.3
release is that we found an issue with 6.0.3 before the official release
announcement was made and had to fix it. The KiCad development team
would
The source repo has been tagged so we need to get the remaining repos
tagged so we can get the package builders fired up.
Cheers,
Wayne
On 3/15/22 9:41 AM, Wayne Stambaugh wrote:
I am planning on tagging 6.0.3 this evening around 8PM EDT. Please let
me know if you need more time. All
I am planning on tagging 6.0.3 this evening around 8PM EDT. Please let
me know if you need more time. All of the other repos will need tagged
as well so we can packages built and uploaded. The goal is release on
Thursday, March 17th.
Cheers,
Wayne
On 3/8/22 7:32 AM, Wayne Stambaugh wrote
We are planning on releasing 6.0.3 on March 15th which means that we
will have to have all of the repos tagged by March 13th. Please let me
know if you have any issues with this time line. Thanks in advance for
the help.
Cheers,
Wayne
___
All of the repos have been tagged for 6.0.2 and the documentation
archive can be download from
https://kicad-downloads.s3.cern.ch/docs/kicad-doc-6.0.2.tar.gz. Let's
get those package builders fired up for the 6.0.2 release.
Cheers,
Wayne
___
Mailing
On 2/10/22 10:06 AM, Steven A. Falco wrote:
On 2/7/22 04:46 PM, Wayne Stambaugh wrote:
On 2/7/2022 4:39 PM, Steven A. Falco wrote:
On 2/7/22 03:39 PM, Wayne Stambaugh wrote:
The goal is to release 6.0.2 on Friday, February 11th. If this is an
issue for anyone please let me know. I apologize
On 2/7/2022 4:39 PM, Steven A. Falco wrote:
On 2/7/22 03:39 PM, Wayne Stambaugh wrote:
The goal is to release 6.0.2 on Friday, February 11th. If this is an
issue for anyone please let me know. I apologize that it's this late
due to the Launch mailing list issue.
To confirm, do you mean
The goal is to release 6.0.2 on Friday, February 11th. If this is an
issue for anyone please let me know. I apologize that it's this late
due to the Launch mailing list issue.
Cheers,
Wayne
___
Mailing list:
In case you didn't know, the KiCad developer's mailing list was down for
a few days so no one was getting the messages. If you sent anything
over the last few days and didn't get a response, your going to have to
resend it. I don't think anyone should be expected to go through the
mailing
Just a friendly reminder to developers to please update the copyright
date to 2022 as you make changes to the KiCad source files.
Cheers,
Wayne
___
Mailing list: https://launchpad.net/~kicad-developers
Post to :
t;CompactedFamily" [01,02]_[02..64]_[H,V]_2.54mm )
Same for footprints
Franck
Le 06/01/2022 à 23:43, Wayne Stambaugh a écrit :
Just a quick heads up to all library, package, documentation, and
translation developers, barring any unexpected critical bugs I will be
tagging stable release version
Just a quick heads up to all library, package, documentation, and
translation developers, barring any unexpected critical bugs I will be
tagging stable release version 6.0.1 late on Tuesday, January 11 (EST)
for official release on January 15th. If you have anything you want to
push before
The build error is fixed. Thanks.
On 12/26/21 11:55 AM, jeff wrote:
More bits committed...
On 26 Dec 2021, at 15:48, Wayne Stambaugh wrote:
Now I'm seeing this:
/home/foo/src/kicad-trunk/qa/pns/pns_log_viewer.cpp: In constructor
‘PNS_LOG_VIEWER_FRAME::PNS_LOG_VIEWER_FRAME(wxFrame
Now I'm seeing this:
/home/foo/src/kicad-trunk/qa/pns/pns_log_viewer.cpp: In constructor
‘PNS_LOG_VIEWER_FRAME::PNS_LOG_VIEWER_FRAME(wxFrame*)’:
/home/foo/src/kicad-trunk/qa/pns/pns_log_viewer.cpp:294:14: error:
request for member ‘m_ZoneDisplayMode’ in ‘settings’, which is of
pointer type
I'm seeing the following build failure this morning:
/home/foo/src/kicad-trunk/qa/qa_utils/mocks.cpp:622:28: error: no
declaration matches ‘const PCB_DISPLAY_OPTIONS&
PCB_TOOL_BASE::displayOptions() const’
622 | const PCB_DISPLAY_OPTIONS& PCB_TOOL_BASE::displayOptions() const
|
Due to the recent churn, the KiCad lead development team has decide to
tag a release candidate 2 for version 6. If testing goes well over the
weekend, the goal is to tag 6.0.0 on Monday.
Until version 6 is tagged, no new commits can be pushed directly to the
master branch. All commits until
Check to make sure the KICAD_BUILD_I18N and KICAD_I18N_UNIX_STRICT_PATH
build options are set properly. They default to OFF.
On 11/19/21 8:47 AM, Marco Ciampa wrote:
Hi devs!
In order to check the coherence of the translation I often compile and install
KiCad from source (from git).
Using
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 to the KiCad project and I look forward
to his contributions as lead developer. Please join me in
congratulating
Hi Lorenzo,
Welcome back.
It sounds to me like you are describing a variant system to allow for
different populations of the same board layout from a single schematic
design. This is already planned for version 7 so you wont have to use
any hacks like you are suggesting below to create a
Hi Steven,
I don't remember the 3D model or documentation licensing changing. The
source license did change from AGPLv3+ to GPLv3+.
Cheers,
Wayne
On 11/16/21 11:17 AM, Steven A. Falco wrote:
As we get close to releasing 6.x builds, I'd like to make sure our
packages specify the correct
Release candidate 1 of version 6 has been tagged and pushed. Package
builds should be available in the next few days for most systems. There
are still a few minor issues which should get fixed by stable release
6.0.0. If all goes well, the stable release should be ready by the end
of the
Unfortunately we found a locale issue with 5.1.11. Some of the packages
were ready and uploaded to website which resulted in a few users
downloading them which exposed the issue. We have fixed the issue but
given that users have already downloaded 5.1.11 packages, we will not be
officially
Hi Stefan,
There is not a formal release notes per se but you can see the list of
closed issues at https://gitlab.com/groups/kicad/-/milestones/6.
Cheers,
Wayne
On 10/30/2021 11:03 AM, Stefan Brüns wrote:
Hi,
I am currently preparing packages for openSUSE, and was wondering if the
release
The lead development team has agreed on a version 6 release schedule as
follows:
- String freeze November 1.
- Tag RC1 on November 15.
- All repos frozen on December 14.
- Tag all repos with 6.0.0 on December 15.
- 6.0.0 release announcement December 31 (maybe the day before Christmas
just
I had to re-tag the 5.1 branch due to removal of the old domain name and
a last minute bug fix. Please update any previous package builds to the
latest commit. I apologize for any inconvenience.
Cheers,
Wayne
___
Mailing list:
On 10/26/21 4:31 PM, Carsten Schoenert wrote:
Hello Wayne,
Am 26.10.21 um 20:38 schrieb Wayne Stambaugh:
Hi Carsten,
Do we still we still build and deploy the old 5.1 developer docs
anywhere? I guess I should remove them just in case someone else does.
I should be able to get
I purged the old domain from the 5.1 branch developer docs and pushed
everything to the 5.1 branch so we should be good to go.
- Wayne
On 10/26/21 2:40 PM, Wayne Stambaugh wrote:
Please hold off building the 5.1.11 packages until I get this fixed even
though the resulting code wont be any
Please hold off building the 5.1.11 packages until I get this fixed even
though the resulting code wont be any different, the commit hash will
be. Sorry for the headaches.
Cheers,
Wayne
On 10/26/21 2:38 PM, Wayne Stambaugh wrote:
Hi Carsten,
Do we still we still build and deploy the old
schrieb Wayne Stambaugh:
I just pushed the 5.1.11 tag to the 5.1 branch so please tag all of the
other repos so we can start the packaging process. Please let me know
if there are any issues that would delay the tagging.
I guess the loss of kicad-pcb.org isn't incorporated yet into this tag
I just pushed the 5.1.11 tag to the 5.1 branch so please tag all of the
other repos so we can start the packaging process. Please let me know
if there are any issues that would delay the tagging.
Thank you everyone for continued contributions to KiCad.
Cheers,
Wayne
On 10/21/21 9:03 AM, Dick Hollenbeck wrote:
On 10/19/21 3:29 PM, Seth Hillbrand wrote:
we attempted to secure the rights to the original domain name from Dick without
success.
This is untrue. *No* offer was ever made, neither to re-imburse nor any offer
to purchase was ever made.
"we
On 9/14/21 10:05 AM, Steven A. Falco wrote:
> Thanks, Jeff. It looks like "make clean" does the right thing - it
> removes "include/page_layout_reader_lexer.h", among others.
>
> I was used to just blowing away the build directory to clean up, but now
> I know that that is not sufficient for
Hi Johannes,
I'm curious where you got wxWidgets 3.1.6 from. The last tag I see in
the wxWidgets repo is 3.1.5 and I'm pretty sure KiCad builds fine with
wxWidgets 3.1.5. AFAIK, the version of wxWidgets packaged for Ubuntu
20.04 is 3.0.4.
Cheers,
Wayne
On 9/8/21 12:55 AM,
I am happy to announce that Roberto Fernandez Bautista has accepted an
invitation to the KiCad lead development team. Roberto has made some
significant contributions to the KiCad project and I look forward to his
contributions as lead developer. Please join me in congratulating
Roberto in
Add -DPYTHON_INCLUDE_DIR=/mingw64/include/python3.8 to the CMake command
line. You have msys2 python installed which for some reason,
FindPythonLibs.cmake detects instead of the mingw64 path.
On 7/2/2021 11:55 PM, pradeepa.kck wrote:
I am using MINGW64.
Sent on the go with Vodafone
comment about what it
would take to do that. I've been using 3.1 on Debian testing for quite
a long time now and it seems to be stable and it also fixes a lot of issues.
Ruth
On 28/06/2021 16:53, Wayne Stambaugh wrote:
Which version of KiCad are you talking about, 5.1 or master? Where
Which version of KiCad are you talking about, 5.1 or master? Where are
you getting your Kubuntu KiCad package, Kubuntu or the KiCad PPA? The
decision to build against wxWidgets 3.1 is up to the disto package
developer if you are using the disto's package.
On 6/28/21 11:38 AM, Ruth Ivimey-Cook
Piccioni wrote:
> Ah.
>
> Perhaps it would be useful to throw up a dialog to the effect that that
> the schematic should be updated?
>
> It still says
>
> PCB and schematic successfully reannotated
>
> In the dialog.
>
>
> On 2021-06-28 11:29 a.m., Way
The reannotation dialog update schematic option because it was removed
because it could leave schematics in an undefined state under certain
conditions. See commit 54e18f6b1f4c2199f8748fff82198f86522bef83 and the
related issue for details.
Wayne
On 6/28/21 9:51 AM, Brian Piccioni wrote:
> Hello
1 - 100 of 5523 matches
Mail list logo
