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?
the Debian build configuration is
Wayne
Thanks for the additional information. I mentioned the compile warnings because
they appear to be different from the ones I got when I compiled 32 bit.
As for MSVC, I am a big fan and can see the benefits of moving to it. One
advantage was that you wouldn’t have to install MSYS2 and all
On Mon, Oct 21, 2019 at 5:53 PM Diego Herranz
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 love your optimism :)
___
Mailing list:
I understand and that'll mean I'll have to move on, which in my case, it's
not a big issue. I was waiting until 20.04 LTS, though :)
>> The stable version of KiCad will always build with 16.04.
It looks like by the time 6.0 is out, Ubuntu 16.04 may still be officially
supported. Just something
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?
-Ian
[1] https://bugs.launchpad.net/kicad/+bug/1847554
[2]
According to Ubuntu[1], 16.04 looks like it will continue to receive
maintenance updates until April 2021. It looks like we got that wrong.
The boost version in 16.04 is 1.58. There is no newer version of boost
in the back ports repo so we have a decision to make. Drop support for
Ubuntu 16.04
You can still run 5.1 on 16.04. If you want bleeding edge, don't lock
yourself down with a "stable" system.
On Mon, 21 Oct 2019 at 21:37, Diego Herranz
wrote:
>
> I see. Are those dates when the respective OS support finishes or when we
> stop supporting them?
> I was under the impression it is
I see. Are those dates when the respective OS support finishes or when we
stop supporting them?
I was under the impression it is the former (although it is not fully
clear) in which case that date is wrong.
Thanks,
Diego
On Mon, 21 Oct 2019 at 20:16, Ian McInerney
wrote:
> The listing I used
The listing I used when looking at whether our supported OS's had Boost
1.59 were the dates given here:
http://kicad-pcb.org/help/system-requirements/#_gnulinux. On that page, it
says that our support for 16.04 ended in April.
-Ian
On Mon, Oct 21, 2019 at 8:03 PM Diego Herranz
wrote:
> I
There were two bugs still on the 5.1.5 milestone [1], [2] that related to
the editing of H/V/45 constrained polygons. I have bumped those to 6.0 now.
Should we reopen and move [3] and [4] to 6.0 so that we actually fix the
issues there?
-Ian
[1] https://bugs.launchpad.net/kicad/+bug/1842055
[2]
I wasn't getting any nightly package update lately and checking [1] I've
just noticed this boost bump has left Ubuntu 16.04 (Xenial) out.
Ubuntu 16.04 will be supported until April 2021 [2].
Was this overlooked when checking distros? Or was it a deliberate decision?
Is there anything that can be
On 2019-10-21 10:52, Ian McInerney wrote:
Seth,
Just to clarify, for 5.1.5 (and future 5.1 releases), the H/V/45 is
only available during initial zone creation and is not going to be
active for editing the lines after creation? If this is the case, I
will push the bugs for this into the 6.0
I thought this might be the case. If you click cancel, the assertion
dialog will not be displayed again until you restart KiCad.
Would one of our macos devs please take a look at the config settings
use to build wxWidgets and see if we can turn the assertions off on
release builds? This might
Seth,
Just to clarify, for 5.1.5 (and future 5.1 releases), the H/V/45 is only
available during initial zone creation and is not going to be active for
editing the lines after creation? If this is the case, I will push the bugs
for this into the 6.0 milestone, so they can be addressed there.
It may be a false alarm--I am reviewing everything and it looks like
it is working for everyone so far. There may be some documentation we
have to add to the macOS specific things about allowing permissions
when a popup pops up on first run, but if I am understanding correctly
none of the issues
Hi Jonaton,
This is an assertion in wxWidgets being raised. This really shouldn't
happen on release builds. While assertions like this are annoying they
are not show stoppers unless clicking either the "No" or "Cancel"
buttons cause KiCad to crash. I'm guessing this is not the case but one
of
On 10/20/19 12:02 PM, Seth Hillbrand wrote:
> On 2019-10-20 08:40, Ian McInerney wrote:
>
>> There is also this H/V/45 issue [1]. It is more of a gray area though,
>> since it will probably involve touching the file format due to what is
>> happening (the H/V/45 is being saved as a global board
Do we know if this is a KiCad source bug issue or a macos packaging
issue? I was getting the distinct impression that it was the latter. I
agree that we do not want to release 5.1.5 without a functioning macos
package. I'm willing to hold off on the rc1 tag until we resolve this
issue. It may
Hi Seth,
On 10/20/19 1:48 PM, Seth Hillbrand wrote:
> Hi Wayne-
>
> These should be fixed. I've pushed the reload issue off to v6 as the
> setting isn't available in the current file format as Ian mentioned, so
> I've reset the associated bug with a new milestone.
Thanks. I appreciate the
Brian,
On 10/21/19 9:24 AM, Brian Piccioni wrote:
> I'm updating this email in case somebody else has a similar problem.
>
>
>
> I reinstalled Msys2 64 bit and rebuilt a 64 bit debug version of Kicad.
> It appear to run fine, except when I run PCBNew from a mingw64 terminal
> I get
>
>
>
I'm updating this email in case somebody else has a similar problem.
I reinstalled Msys2 64 bit and rebuilt a 64 bit debug version of Kicad. It
appear to run fine, except when I run PCBNew from a mingw64 terminal I get
$ pcbnew
21 matches
Mail list logo
