On 10/22/19 1:08 AM, Carsten Schoenert wrote:
> Hi,
>
> Am 21.10.19 um 23:16 schrieb Ian McInerney:
>> We also seem to have assertions enabled in the Debian build (there have
>> been two reports from users [1], [2]). Is this something we control as
>> well, or is the the distribution packaging
I can look into doing this for release builds on macOS If I do this, I
will need to make a pre-release build for folks to test since by definition
this wouldn't be tested on nightlies, right?
Are there other dependencies that we want to build differently for release
vs nightly?
Adam
On Tue,
A man can dream xD
On Mon, 21 Oct 2019 at 23:15, Jon Evans wrote:
>
> On Mon, Oct 21, 2019 at 5:53 PM Diego Herranz <
> diegoherr...@diegoherranz.com> wrote:
>
>>
>> It looks like by the time 6.0 is out, Ubuntu 16.04 may still be
>> officially supported. Just something to have in mind.
>>
>
> I
I would prefer that stable release builds have assertions disabled in
KiCad and all of it's library dependencies. If we want to provide debug
builds for users who want to help with debugging, I'm fine with that.
Wayne
On 10/22/19 7:43 AM, Adam Wolf wrote:
> I can look into doing this for
On 2019-10-21 22:08, Carsten Schoenert wrote:
Hi,
Am 21.10.19 um 23:16 schrieb Ian McInerney:
We also seem to have assertions enabled in the Debian build (there
have
been two reports from users [1], [2]). Is this something we control as
well, or is the the distribution packaging forcing them
On 2019-10-22 16:06, Ian McInerney wrote:
> I dug into the website history and apparently the original intent should have
> been to support 16.04 LTS until its standard support ends in 2021
> (https://github.com/KiCad/kicad-website/commit/007fb582a316fa513778a393e2696d17c0031cea#r33487782).
>
I would probably personally prefer if we kept it at 1.59 instead of
dropping it back (I hope to improve the unit testing of the tool framework,
so having the better testing library would make that easier), but we need
to be consistent with the support lifetimes we use. If 16.04 is supported
I dug into the website history and apparently the original intent should
have been to support 16.04 LTS until its standard support ends in 2021 (
https://github.com/KiCad/kicad-website/commit/007fb582a316fa513778a393e2696d17c0031cea#r33487782).
Since we haven't actually used any code from the
It should also be noted that 20.04 will be the next LTS release of Ubuntu.
This means that there will be two post-16.04 LTS releases out there before
KiCad 6 will be released (I'm not *that* optimistic :) ). Is it really
worth it to actively support 3 different LTS releases? It doesn't sound
very
Hello Seth,
Am 22.10.19 um 18:10 schrieb Seth Hillbrand:
> Why do you have "hardening=+all" enabled?
mostly because this is the default for building binary packages with
enabled hardening.
https://wiki.debian.org/Hardening#Using_Hardening_Options
> This is likely where the assertions are
10 matches
Mail list logo
