From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: kicad: update to 7.0.0
Date: Thu, 16 Feb 2023 02:27:47 +0100 [thread overview]
Message-ID: <20230216012747.b9T4_9j9tyWNAEh60mn150Y9-VWUWgrnvggqRHkTTkg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42264@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
There's a merged pull request on the void-packages repository
kicad: update to 7.0.0
https://github.com/void-linux/void-packages/pull/42264
Description:
#### Testing the changes
- I tested the changes in this PR: **YES**
Opened up some projects and exported gerbers without issues.
- I built this PR locally for my native architecture, (x86_64-glibc)
I am seeing a lot of warnings in the build, mostly coming from the comes-with-kicad pybind11. Since there is already a patch for the Warnings.cmake file, this could be silenced further, but i am not sure if this wanted.
New dependency on unixodbc, i hope i put it in the right places.
prev parent reply other threads:[~2023-02-16 1:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 19:18 [PR PATCH] kicad: update all kicad packages " mkalte666
2023-02-14 19:19 ` [PR REVIEW] " classabbyamp
2023-02-14 19:20 ` classabbyamp
2023-02-14 19:20 ` classabbyamp
2023-02-14 19:23 ` mkalte666
2023-02-14 19:39 ` classabbyamp
2023-02-14 21:10 ` [PR PATCH] [Updated] kicad: update " mkalte666
2023-02-14 21:17 ` classabbyamp
2023-02-15 21:22 ` classabbyamp
2023-02-15 21:22 ` [PR PATCH] [Updated] " classabbyamp
2023-02-16 1:27 ` classabbyamp [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230216012747.b9T4_9j9tyWNAEh60mn150Y9-VWUWgrnvggqRHkTTkg@z \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).