Re: [Kicad-developers] Stable release 4.0.6

[Adam Wolf]

Thanks!

I can't quite keep up with the list.  How are docs?

Adam Wolf

On Wed, Feb 22, 2017 at 5:44 PM, Wayne Stambaugh  wrote:
> Thank you Oliver for all of your hard work.
>
> Cheers,
>
> Wayne
>
> On 2/22/2017 6:18 PM, Oliver Walters wrote:
>> All libraries have now been tagged as 4.0.6
>>
>> On Wed, Feb 15, 2017 at 1:26 AM, Wayne Stambaugh > <mailto:stambau...@gmail.com>> wrote:
>>
>> Are there any outstanding issues to prevent rolling out a 4.0.6 stable
>> release?  If not, I will set the version string and tag that commit as
>> 4.0.6.  How much time do our source translators, doc devs, and library
>> devs need to have everything ready?
>>
>> Thanks,
>>
>> Wayne
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> <https://launchpad.net/~kicad-developers>
>> Post to : kicad-developers@lists.launchpad.net
>> <mailto:kicad-developers@lists.launchpad.net>
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> <https://launchpad.net/~kicad-developers>
>> More help   : https://help.launchpad.net/ListHelp
>> <https://help.launchpad.net/ListHelp>
>>
>>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Stable release 4.0.6

[Adam Wolf]

No problem, I am still contemplating how to generate a libcurl that runs on
OS X 10.7

Adam Wolf

On Feb 23, 2017 12:29 AM, "Nick Østergaard"  wrote:

The docs are not quite ready yet, there are some things that still needs to
be included.

Den 23/02/2017 01.56 skrev "Adam Wolf" :

> Thanks!
>
> I can't quite keep up with the list.  How are docs?
>
> Adam Wolf
>
> On Wed, Feb 22, 2017 at 5:44 PM, Wayne Stambaugh 
> wrote:
> > Thank you Oliver for all of your hard work.
> >
> > Cheers,
> >
> > Wayne
> >
> > On 2/22/2017 6:18 PM, Oliver Walters wrote:
> >> All libraries have now been tagged as 4.0.6
> >>
> >> On Wed, Feb 15, 2017 at 1:26 AM, Wayne Stambaugh  >> <mailto:stambau...@gmail.com>> wrote:
> >>
> >> Are there any outstanding issues to prevent rolling out a 4.0.6
> stable
> >> release?  If not, I will set the version string and tag that commit
> as
> >> 4.0.6.  How much time do our source translators, doc devs, and
> library
> >> devs need to have everything ready?
> >>
> >> Thanks,
> >>
> >> Wayne
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> <https://launchpad.net/~kicad-developers>
> >> Post to : kicad-developers@lists.launchpad.net
> >> <mailto:kicad-developers@lists.launchpad.net>
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> <https://launchpad.net/~kicad-developers>
> >> More help   : https://help.launchpad.net/ListHelp
> >> <https://help.launchpad.net/ListHelp>
> >>
> >>
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Stable release 4.0.6

[Adam Wolf]

I suspect I will be able to have a release candidate by the end of the
weekend, ie 4 days from now.

I don't have any way to test if it will work as far back as we claim
support for for the 4x line, but I am not certain that is a world-ending
problem at this point.  (I will be able to confirm it runs on more modern
OS X installs.) Apple hasn't even released security patches for those
systems for years and years, so if those users exist, they're already well
trained in being left behind by companies.

Adam Wolf

On Thu, Feb 23, 2017, 7:21 AM Wayne Stambaugh  wrote:

> Sounds like we might need another week before making the release
> announcement or am I misreading this?
>
> On 2/23/2017 8:06 AM, Adam Wolf wrote:
> > No problem, I am still contemplating how to generate a libcurl that runs
> > on OS X 10.7
> >
> > Adam Wolf
> >
> > On Feb 23, 2017 12:29 AM, "Nick Østergaard"  > <mailto:oe.n...@gmail.com>> wrote:
> >
> > The docs are not quite ready yet, there are some things that still
> > needs to be included.
> >
> > Den 23/02/2017 01.56 skrev "Adam Wolf"
> > mailto:adamw...@feelslikeburning.com
> >>:
> >
> > Thanks!
> >
> > I can't quite keep up with the list.  How are docs?
> >
> > Adam Wolf
> >
> > On Wed, Feb 22, 2017 at 5:44 PM, Wayne Stambaugh
> > mailto:stambau...@gmail.com>> wrote:
> > > Thank you Oliver for all of your hard work.
> > >
> > > Cheers,
> > >
> > > Wayne
> > >
> > > On 2/22/2017 6:18 PM, Oliver Walters wrote:
> > >> All libraries have now been tagged as 4.0.6
> > >>
> > >> On Wed, Feb 15, 2017 at 1:26 AM, Wayne Stambaugh
> > mailto:stambau...@gmail.com>
> > >> <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>>
> > wrote:
> > >>
> > >> Are there any outstanding issues to prevent rolling out a
> > 4.0.6 stable
> > >> release?  If not, I will set the version string and tag
> > that commit as
> > >> 4.0.6.  How much time do our source translators, doc
> > devs, and library
> > >> devs need to have everything ready?
> > >>
> > >> Thanks,
> > >>
> > >> Wayne
> > >>
> > >> ___
> > >> Mailing list: https://launchpad.net/~kicad-developers
> > <https://launchpad.net/~kicad-developers>
> > >> <https://launchpad.net/~kicad-developers
> > <https://launchpad.net/~kicad-developers>>
> > >> Post to : kicad-developers@lists.launchpad.net
> > <mailto:kicad-developers@lists.launchpad.net>
> > >> <mailto:kicad-developers@lists.launchpad.net
> > <mailto:kicad-developers@lists.launchpad.net>>
> > >> Unsubscribe : https://launchpad.net/~kicad-developers
> > <https://launchpad.net/~kicad-developers>
> > >> <https://launchpad.net/~kicad-developers
> > <https://launchpad.net/~kicad-developers>>
> > >> More help   : https://help.launchpad.net/ListHelp
> > <https://help.launchpad.net/ListHelp>
> > >> <https://help.launchpad.net/ListHelp
> > <https://help.launchpad.net/ListHelp>>
> > >>
> > >>
> > >
> > >
> > > ___
> > > Mailing list: https://launchpad.net/~kicad-developers
> > <https://launchpad.net/~kicad-developers>
> > > Post to : kicad-developers@lists.launchpad.net
> > <mailto:kicad-developers@lists.launchpad.net>
> > > Unsubscribe : https://launchpad.net/~kicad-developers
> > <https://launchpad.net/~kicad-developers>
> > > More help   : https://help.launchpad.net/ListHelp
> > <https://help.launchpad.net/ListHelp>
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > <https://launchpad.net/~kicad-developers>
> > Post to : kicad-developers@lists.launchpad.net
> > <mailto:kicad-developers@lists.launchpad.net>
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > <https://launchpad.net/~kicad-developers>
> > More help   : https://help.launchpad.net/ListHelp
> > <https://help.launchpad.net/ListHelp>
> >
> >
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Stable release 4.0.6

[Adam Wolf]

I had assumed it did not.  I will investigate before building it
myself though.  Thanks for the pointer.

Adam Wolf

On Thu, Feb 23, 2017 at 8:22 AM, Simon Wells  wrote:
> @adam why do you neeed a libcurl? does 10.7 not come with libcurl?
>
> On 24 February 2017 at 02:35, Wayne Stambaugh  wrote:
>> Does the ubuntu package even have the correct docs, translations, and
>> libraries?  AFAIK, some of this has not been committed and tagged yet.
>> In the future, please hold off making stable packages available until we
>> have packages for the three major platforms.  I'm ok if some of the more
>> obscure linux distros don't have packages but we should at least have
>> windows, osx, and linux (dpkg and rpm) packages ready to go rather than
>> release them as they are completed.  All this will do is frustrate users
>> of other platforms because there is no 4.0.6 package available and make
>> them feel like second class citizens.
>>
>> Cheers,
>>
>> Wayne
>>
>> On 2/23/2017 8:22 AM, Chris Pavlina wrote:
>>> In the future we should probably look into making our releases a bit
>>> more coordinated.
>>>
>>> https://forum.kicad.info/t/4-0-6-for-ubuntu-is-out/5441
>>>
>>> On Tue, Feb 14, 2017 at 09:26:21AM -0500, Wayne Stambaugh wrote:
>>>> Are there any outstanding issues to prevent rolling out a 4.0.6 stable
>>>> release?  If not, I will set the version string and tag that commit as
>>>> 4.0.6.  How much time do our source translators, doc devs, and library
>>>> devs need to have everything ready?
>>>>
>>>> Thanks,
>>>>
>>>> Wayne
>>>>
>>>> ___
>>>> Mailing list: https://launchpad.net/~kicad-developers
>>>> Post to : kicad-developers@lists.launchpad.net
>>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>>> More help   : https://help.launchpad.net/ListHelp
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Torrents for KiCad distribution

[Adam Wolf]

I know that Amazon provides torrent downloads for files in S3, so if
we uploaded our files to S3, we could also provide them via torrent.
I am not certain this gets us anything though.

Adam Wolf

On Thu, Feb 23, 2017 at 10:50 AM, Mark Roszko  wrote:
>>I have no issue with that but there is no way for KiCad to control what is 
>>uploaded to a torrent so I really don't want the project to be responsible 
>>for it
>
> The torrent could be autogenerated by the download server when the
> files are transferred over, the download server would act as the
> initial seed server. The torrent once created could be shared on the
> website and then thats it. The contents of the torrent cannot change
> without it being a completely different hash and thus invalid for the
> torrent.
>
>>Does our website not have enough bandwidth for downloading KiCad packages?
>
> Actually simultaneous downloads from multiple users do seem to slow it
> down quite a tad bit. It's not like the files are hosted on a CDN like
> other projects may have or even github.
>
> The theory with torrents is the download server would consume the
> same bandwidth during initial seed but then others could then "donate"
> their bandwidth afterwards to continue sharing (the initial seed is
> still there too).
>
>
> Not advocating for this but just throwing my two cents in
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [RFC] 3D models repository

[Adam Wolf]

For OS X packages, it would change a script, but shouldn't be a problem.

Adam Wolf

On Fri, Feb 24, 2017 at 2:45 AM, Oliver Walters
 wrote:
> Hi everyone,
>
> Recently I raised this issue:
>
> https://lists.launchpad.net/kicad-developers/msg27922.html
>
> There were some good responses, thanks for the input.
>
> First task is going to be moving the 3D models, as this will be
> significantly easier.
>
> e.g. something like GitHub.com/KiCad/packages3D
>
> To this end, I'd like some further information from those in the know:
>
> A) is there any impediment to having the KISYS3DMOD envvar point to
> somewhere different? e.g. ./KiCad/share/packages3D/
> B) To the package managers, how much effort to package 3D models from a
> separate repo?
> C) to the docs maintainers, would there be much to change if we redirected
> the 3D repo?
> D) Generally, what other considerations would be required?
>
> Essentially, if I made this change right now without telling anyone, what
> would I break?
>
> As a side note there have been some great recent contributions to the 3D
> data, with a fair bit of momentum over at the forums.
>
> Regards,
> Oliver
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [RFC] 3D models repository

[Adam Wolf]

Yeah, let me clarify--by "wouldn't be a problem" for OS X, I meant "if
you did it without saying where it's going and when it's changing", it
would break the OS X package, but the change would only take a minute
or two, and would be quickly testable.

On Fri, Feb 24, 2017 at 6:57 AM, Wayne Stambaugh  wrote:
> On 2/24/2017 3:45 AM, Oliver Walters wrote:
>> Hi everyone,
>>
>> Recently I raised this issue:
>>
>> https://lists.launchpad.net/kicad-developers/msg27922.html
>>
>> There were some good responses, thanks for the input.
>>
>> First task is going to be moving the 3D models, as this will be
>> significantly easier.
>>
>> e.g. something like GitHub.com/KiCad/packages3D
>>
>> To this end, I'd like some further information from those in the know:
>>
>> A) is there any impediment to having the KISYS3DMOD envvar point to
>> somewhere different? e.g. ./KiCad/share/packages3D/
>
> I believe you mean share/kicad/modules/packages3d.  Why would change the
> install path?  Irregardless of what repo the 3D models are in, they
> should always get installed in this location.  Where else would be
> appropriate to install them?  Changing this path would most likely break
> everyone's 3D viewing experience.
>
>> B) To the package managers, how much effort to package 3D models from a
>> separate repo?
>
> I'll leave this to our package devs.
>
>> C) to the docs maintainers, would there be much to change if we
>> redirected the 3D repo?
>> D) Generally, what other considerations would be required?
>>
>> Essentially, if I made this change right now without telling anyone,
>> what would I break?
>
> I'm sure all of the package builders.  You would need to coordinate this
> change with the package devs.
>
>>
>> As a side note there have been some great recent contributions to the 3D
>> data, with a fair bit of momentum over at the forums.
>>
>> Regards,
>> Oliver
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Torrents for KiCad distribution

[Adam Wolf]

Let's log what it looks like when the next stable comes out, and
analyze it then.  If we want to push our binaries to Amazon or Google
or some other CDN, I can almost certainly have W&L pay for it,
especially if someone else sets it up :).  I know Amazon can seed
torrents and provide https downloads with just a button click.

Adam Wolf
Cofounder and Engineer
W&L

On Fri, Feb 24, 2017 at 9:25 AM, Mark Roszko  wrote:
> https helps but isn't full proof. I have to deal with a stupid Cisco
> system called "ScanSafe" that companies use to MITM SSL connections,
> causing some of my users to generate tons of client error logs from
> the garbage that stuff injects into my web application pages. It goes
> as far to rewrite the CSP headers my server generates but they do it
> wrong so the browser still generates a CSP violation report for me.
> There's also those antivirus aka scareware programs that now MITM
> user's SSL connections en masse while being utter security hole filled
> garbage. And now the Cloudflare SSL leak that is also lol.
>
>
> One problem with torrents is for people on networks where they are
> either blocked or throttled to death (a problem for American
> university students at the very least). But that's why if you offer
> downloads you don't want to be just torrent only.
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Stable release 4.0.6

[Adam Wolf]

I can try this weekend.

Adam Wolf

On Feb 24, 2017 5:50 PM, "Simon Wells"  wrote:

> can we get an "official" python disabled build for osx of stable(all 3
> python options disabled)? you can hide it in some nightmare of subdirs
> or in testing it might just help diagnosing python/wxpython issues
>
> On 25 February 2017 at 11:39, Chris Pavlina 
> wrote:
> > Yeah - my general impression from a number of inconsistencies in the
> > file format vs. the spec is that KiCad's file format really should be
> > considered implementation-defined.
> >
> > In order to have a _proper_ file format spec, it seems to be that two
> > things need to be done:
> >
> > 1. Put the format spec _in the repository_
> > 2. Version it, and require anybody changing the format in the code to:
> > a. Update the MMDD version that gets written to the file
> >(technically we already require this, but I've seen a couple
> >changes go in without doing this...)
> > b. Make a new format spec version and document the change
> >
> > Until we do that, it's implementation-defined with a wannabe spec :P
> >
> > On Fri, Feb 24, 2017 at 11:23:42PM +0100, Nick Østergaard wrote:
> >> Normally when we speak of "the docs" we are not talking about the
> >> fileformat specs, but the stuff in https://github.com/KiCad/kicad-doc
> >>
> >> 2017-02-24 23:22 GMT+01:00 Kevin Cozens :
> >> > On 2017-02-23 01:29 AM, Nick Østergaard wrote:
> >> >>
> >> >> The docs are not quite ready yet,
> >> >
> >> >
> >> > Documentation is (almost) always the last thing to get written or
> updated. I
> >> > was making use of the file formats document while working on a
> project of
> >> > mine to convert schematics from another program in to one that can be
> read
> >> > by Kicad. I found a lot of issues with the docs.
> >> >
> >> > I was told Wayne maintains that document. I'll be emailing him to
> find out
> >> > what the procedure is for providing information about the changes
> needed.
> >> >
> >> > --
> >> > Cheers!
> >> >
> >> > Kevin.
> >> >
> >> > http://www.ve3syb.ca/   |"Nerds make the shiny things that
> distract
> >> > Owner of Elecraft K2 #2172  | the mouth-breathers, and that's why
> we're
> >> > | powerful!"
> >> > #include  | --Chris Hardwick
> >> >
> >> >
> >> > ___
> >> > Mailing list: https://launchpad.net/~kicad-developers
> >> > Post to : kicad-developers@lists.launchpad.net
> >> > Unsubscribe : https://launchpad.net/~kicad-developers
> >> > More help   : https://help.launchpad.net/ListHelp
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Stable release status update.

[Adam Wolf]

I'm in travel right now, I'll double-check on macOS when I arrive.

Adam Wolf

On Mar 3, 2017 2:18 PM, "Wayne Stambaugh"  wrote:

> I'm just checking to see where we stand on the 4.0.6 release.  I got a
> notice from the doc dev group that they need another day or two.  I
> think the translations are good to go.  How are our installers coming
> along?
>
> Cheers,
>
> Wayne
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Stable release status update.

[Adam Wolf]

Thanks everyone for your hard work.

The pokiness of the MacOS stable releases are due to some... lessons
learned that we'll fix for 5.x!

Adam Wolf

On Sun, Mar 5, 2017 at 12:16 PM, Nick Østergaard  wrote:
> Yes, the announcement for the website. Everything for building should now be
> ready Adam and js-reynaud.
>
> A windows rc2 is building and will be available on the download site. I may
> test it finally tomorrow.
>
> Den 05/03/2017 19.09 skrev "Wayne Stambaugh" :
>>
>> I'm assuming your are talking about the website announcement and not the
>> announcement on launchpad?  I'll see if I can get it done by the end of
>> the day.
>>
>> On 3/5/2017 11:15 AM, Nick Østergaard wrote:
>> > The docs have been tagged.
>> >
>> > @Wayne, could you upload the announcement as a draft? Just add draft =
>> > true in the document header.
>> >
>> > 2017-03-03 23:27 GMT+01:00 Jean-Samuel Reynaud :
>> >> PPA is ready since few days. Once doc will be tagged I will create doc
>> >> packages.
>> >>
>> >> Regards,
>> >>
>> >> Le 03/03/2017 à 21:18, Wayne Stambaugh a écrit :
>> >>>
>> >>> I'm just checking to see where we stand on the 4.0.6 release.  I got a
>> >>> notice from the doc dev group that they need another day or two.  I
>> >>> think the translations are good to go.  How are our installers coming
>> >>> along?
>> >>>
>> >>> Cheers,
>> >>>
>> >>> Wayne
>> >>>
>> >>> ___
>> >>> Mailing list: https://launchpad.net/~kicad-developers
>> >>> Post to : kicad-developers@lists.launchpad.net
>> >>> Unsubscribe : https://launchpad.net/~kicad-developers
>> >>> More help   : https://help.launchpad.net/ListHelp
>> >>
>> >>
>> >>
>> >>
>> >> ___
>> >> Mailing list: https://launchpad.net/~kicad-developers
>> >> Post to : kicad-developers@lists.launchpad.net
>> >> Unsubscribe : https://launchpad.net/~kicad-developers
>> >> More help   : https://help.launchpad.net/ListHelp
>>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Stable release status update.

[Adam Wolf]

I will be uploading the 4.0.6-rc1 for macOS shortly.  I opened up some
files with it, poked around, seemed ok.

Adam Wolf

On Sun, Mar 5, 2017 at 3:23 PM, Jean-Samuel Reynaud
 wrote:
> Hi all,
>
> Doc package are ready now on my side (ubuntu ppa).
>
> Regards,
> Le 05/03/2017 à 19:16, Nick Østergaard a écrit :
>> Yes, the announcement for the website. Everything for building should
>> now be ready Adam and js-reynaud.
>>
>> A windows rc2 is building and will be available on the download site. I
>> may test it finally tomorrow.
>>
>> Den 05/03/2017 19.09 skrev "Wayne Stambaugh" > <mailto:stambau...@gmail.com>>:
>>
>> I'm assuming your are talking about the website announcement and not the
>> announcement on launchpad?  I'll see if I can get it done by the end of
>> the day.
>>
>> On 3/5/2017 11:15 AM, Nick Østergaard wrote:
>> > The docs have been tagged.
>> >
>> > @Wayne, could you upload the announcement as a draft? Just add draft =
>> > true in the document header.
>> >
>> > 2017-03-03 23:27 GMT+01:00 Jean-Samuel Reynaud
>> mailto:js.reyn...@gmail.com>>:
>> >> PPA is ready since few days. Once doc will be tagged I will
>> create doc
>> >> packages.
>> >>
>> >> Regards,
>> >>
>> >> Le 03/03/2017 à 21:18, Wayne Stambaugh a écrit :
>> >>>
>> >>> I'm just checking to see where we stand on the 4.0.6 release.  I
>> got a
>> >>> notice from the doc dev group that they need another day or two.  I
>> >>> think the translations are good to go.  How are our installers
>> coming
>> >>> along?
>> >>>
>> >>> Cheers,
>> >>>
>> >>> Wayne
>> >>>
>> >>> ___
>> >>> Mailing list: https://launchpad.net/~kicad-developers
>> <https://launchpad.net/~kicad-developers>
>> >>> Post to : kicad-developers@lists.launchpad.net
>> <mailto:kicad-developers@lists.launchpad.net>
>> >>> Unsubscribe : https://launchpad.net/~kicad-developers
>> <https://launchpad.net/~kicad-developers>
>> >>> More help   : https://help.launchpad.net/ListHelp
>> <https://help.launchpad.net/ListHelp>
>> >>
>> >>
>> >>
>> >>
>> >> ___
>> >> Mailing list: https://launchpad.net/~kicad-developers
>> <https://launchpad.net/~kicad-developers>
>> >> Post to : kicad-developers@lists.launchpad.net
>> <mailto:kicad-developers@lists.launchpad.net>
>> >> Unsubscribe : https://launchpad.net/~kicad-developers
>> <https://launchpad.net/~kicad-developers>
>> >> More help   : https://help.launchpad.net/ListHelp
>> <https://help.launchpad.net/ListHelp>
>>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Stable release status update.

[Adam Wolf]

Hi folks,

The macOS rc is uploading.  Before we post the blog post, can we
confirm we're collecting download stats on the download server (so I
can make sure S3 makes sense for us and then sponsor that?)

Adam Wolf

On Sun, Mar 5, 2017 at 10:14 PM, Adam Wolf
 wrote:
> I will be uploading the 4.0.6-rc1 for macOS shortly.  I opened up some
> files with it, poked around, seemed ok.
>
> Adam Wolf
>
> On Sun, Mar 5, 2017 at 3:23 PM, Jean-Samuel Reynaud
>  wrote:
>> Hi all,
>>
>> Doc package are ready now on my side (ubuntu ppa).
>>
>> Regards,
>> Le 05/03/2017 à 19:16, Nick Østergaard a écrit :
>>> Yes, the announcement for the website. Everything for building should
>>> now be ready Adam and js-reynaud.
>>>
>>> A windows rc2 is building and will be available on the download site. I
>>> may test it finally tomorrow.
>>>
>>> Den 05/03/2017 19.09 skrev "Wayne Stambaugh" >> <mailto:stambau...@gmail.com>>:
>>>
>>> I'm assuming your are talking about the website announcement and not the
>>> announcement on launchpad?  I'll see if I can get it done by the end of
>>> the day.
>>>
>>> On 3/5/2017 11:15 AM, Nick Østergaard wrote:
>>> > The docs have been tagged.
>>> >
>>> > @Wayne, could you upload the announcement as a draft? Just add draft =
>>> > true in the document header.
>>> >
>>> > 2017-03-03 23:27 GMT+01:00 Jean-Samuel Reynaud
>>> mailto:js.reyn...@gmail.com>>:
>>> >> PPA is ready since few days. Once doc will be tagged I will
>>> create doc
>>> >> packages.
>>> >>
>>> >> Regards,
>>> >>
>>> >> Le 03/03/2017 à 21:18, Wayne Stambaugh a écrit :
>>> >>>
>>> >>> I'm just checking to see where we stand on the 4.0.6 release.  I
>>> got a
>>> >>> notice from the doc dev group that they need another day or two.  I
>>> >>> think the translations are good to go.  How are our installers
>>> coming
>>> >>> along?
>>> >>>
>>> >>> Cheers,
>>> >>>
>>> >>> Wayne
>>> >>>
>>> >>> ___
>>> >>> Mailing list: https://launchpad.net/~kicad-developers
>>> <https://launchpad.net/~kicad-developers>
>>> >>> Post to : kicad-developers@lists.launchpad.net
>>> <mailto:kicad-developers@lists.launchpad.net>
>>> >>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> <https://launchpad.net/~kicad-developers>
>>> >>> More help   : https://help.launchpad.net/ListHelp
>>> <https://help.launchpad.net/ListHelp>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> ___
>>> >> Mailing list: https://launchpad.net/~kicad-developers
>>> <https://launchpad.net/~kicad-developers>
>>> >> Post to : kicad-developers@lists.launchpad.net
>>> <mailto:kicad-developers@lists.launchpad.net>
>>> >> Unsubscribe : https://launchpad.net/~kicad-developers
>>> <https://launchpad.net/~kicad-developers>
>>> >> More help   : https://help.launchpad.net/ListHelp
>>> <https://help.launchpad.net/ListHelp>
>>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] [PATCH] Update macOS portion of compiling.md

[Adam Wolf]

Hi folks!

Just a minor docs tweak to compiling.md.  I updated OSX to macOS, in
most places, and I changed the wording around "supported versions 10.7
to 10.10" to "10.9 to 10.12".

Let me know if there are any issues.

Adam Wolf


0001-Update-macOS-portion-of-compiling.md.patch
Description: Binary data
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Patch to compile _pcbnew.kiface only once

[Adam Wolf]

I have some time to do testing on this now that the stable package is
finished.

Simon, please resend if possible and I'll take a look this weekend.

Adam Wolf

On Thu, Mar 16, 2017, 5:05 PM Simon Wells  wrote:

> the problem is most of the python bundling crap is in patches (and
> yeah it is a bit hackish) wwas passed off to adam for testing but he
> never came back. but its also reliant on the python build not being
> broken. It is also as unhackish as it will get due to how cmake works,
> althought we MAY be able to push something upstream to cmake to fix
> DUE to the python bundling guidelines released by apple but i don't
> know whether they give a damn about them. and whats required to follow
> apples guidelides re python bundling.
>
>
>
> On 17 March 2017 at 10:35, Bernhard Stegmaier 
> wrote:
> > As I said before, I plan to work on the whole python packaging stuff as
> discussed below if no one else volunteers to do before.
> > I had some look around on how to do this, but I didn’t find any
> out-of-the-box solution which could be integrated quickly.
> > Unfortunately, I am still busy with other (non KiCad) things and it will
> still take a few weeks until I can start working on it (I hope during
> easter holidays)…
> >
> >> On 16 Mar 2017, at 22:08, Chris Pavlina 
> wrote:
> >>
> >> I'm of two minds on this. On one hand, I'd like to disable scripting on
> >> the macOS nightlies until it's fixed, so macOS users still *have*
> >> nightlies. On the other hand, I worry that doing so will remove
> >> motivation to actually fix it.
> >>
> >> Is anyone actually _actively working on a fix_? I keep seeing chatter
> >> about this, but no actual attempts to fix it.
> >>
> >> Honestly I think the patch that broke the build should be reverted until
> >> a fix can be prepared, but considering who submitted it, I doubt I'll
> >> have any say there.
> >>
> >>
> >> On Thu, Mar 16, 2017 at 04:56:14PM -0400, Jean-Paul Louis wrote:
> >>> I agree 150% with Bernhard.
> >>>
> >>> A disabled Python is 150% better than no new build at all.
> >>>
> >>> I do not understand why OS X users are considered second class
> citizens.
> >>>
> >>> Just my $0.02,
> >>> Jean-Paul
> >>> N1JPL
> >>>
> >>>
> >>>
> >>>> On Mar 16, 2017, at 2:06 PM, Bernhard Stegmaier <
> stegma...@sw-systems.de> wrote:
> >>>>
> >>>> I have just seen people on the forum complaining that OSX nightlies
> still don’t build.
> >>>>
> >>>> @Simon:
> >>>> Do you intend to push your changes, no matter how hackish?
> >>>> Might at least be a start to work with.
> >>>>
> >>>> Or, just disable python scripting at all until the whole python
> bundling has been sorted out?
> >>>> Having no python scripting is better than having no build or a build
> where it doesn’t work right...
> >>>>
> >>>>
> >>>> Regards,
> >>>> Bernhard
> >>>>
> >>>>> On 21 Feb 2017, at 18:56, Simon Wells  wrote:
> >>>>>
> >>>>> I have previously sent a patch to adam for testing that bundled
> >>>>> python. but it was a bit hackish as since python is a system lib
> >>>>> bundleutilies doesn't copy it.
> >>>>>
> >>>>> On 21 February 2017 at 21:28, Bernhard Stegmaier
> >>>>>  wrote:
> >>>>>>
> >>>>>> On 21 Feb 2017, at 00:31, Wayne Stambaugh 
> wrote:
> >>>>>>
> >>>>>> On 2/20/2017 6:27 PM, Nick Østergaard wrote:
> >>>>>>
> >>>>>> 2017-02-20 23:48 GMT+01:00 Bernhard Stegmaier <
> stegma...@sw-systems.de>:
> >>>>>>
> >>>>>> How is this done on Windows?
> >>>>>> You also don’t have a global filesystem with one Python there where
> you just
> >>>>>> copy it into the right place… where does the Windows installer put
> those
> >>>>>> files and how do you use them from some installed Python? Are there
> issues
> >>>>>> with library paths of the library dependencies that come with KiCAD
> when
> >>>>>> used from an external Python?
> >>>>>>
> >>>>>>
> >>>>>> I am not a

Re: [Kicad-developers] v5 timeline

[Adam Wolf]

I have a suite of Mac packaging things I have in progress that I want
to get in before 5, based on some issues with how I set some things up
in 4.  I am working on an update to the list to get some discussion
going on this topic.

On Tue, Mar 28, 2017 at 10:07 AM, Chris Pavlina  wrote:
> Sounds good.
>
> I've collected all the things I want to work on for 5.0 properly on
> Launchpad now, assigned to myself. These are:
>
> - Fix remaining UI/UX issues with the component selector.
> - Investigate possible footprint preview panel locale issues
> - Implement footprint selection tags on history items
> - Document the new component selector.
> - Fix OpenGL compatibility test crash on startup [1]
> - Implement clean OpenGL/Cairo fallback [2]
>
> Plus a few more minor things (all assigned to me on Launchpad).
>
> I'd like to get all these done before 5.0, is that okay? I'm not sure
> how far off the geometry library and via stitching are so I don't know
> how much time that gives me.
>
> [1] https://bugs.launchpad.net/kicad/+bug/1676915
> [2] https://bugs.launchpad.net/kicad/+bug/1676916
>
>
> On Tue, Mar 28, 2017 at 10:47:19AM -0400, Wayne Stambaugh wrote:
>> Hey Chris,
>>
>> The following items are holding up the v5 branch:
>>
>> Symbol library table (me).
>> Unified geometry library (Tom).
>> Stitching via support (Tom & Orson).
>>
>> I was hoping I would be done with the symbol library table by now but
>> I'm really having trouble finding the time to finish it up.  I'm not
>> sure where Tom and Orson stand.  I just saw an email from Tom the other
>> day so it looks like there is still a bit of work to do on his end with
>> the stitching via support.
>>
>> Thanks,
>>
>> Wayne
>>
>> On 3/28/2017 10:45 AM, Chris Pavlina wrote:
>> > Hey Wayne,
>> >
>> > In the interest of prioritizing my own work - just curious if you have
>> > any idea how long it's going to be before declaring the v5 feature
>> > freeze, and what that's waiting on.
>> >
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Vacation.

[Adam Wolf]

Have a good holiday, Wayne.  Thanks for everything you do for the KiCad project!

Adam Wolf

On Thu, Jun 29, 2017 at 10:07 AM, Wayne Stambaugh  wrote:
> I just want to give everyone a quick heads up that I will be leaving for
> vacation this evening until July 9th.  I am *not* taking my laptop with
> me so if anything important that requires my approval comes up, please
> refrain from discussing it until I return.  I will already have enough
> emails in my inbox.  Since I'm only going to have my cell phone with me,
> my motivation to answer emails while on vacation will be near zero.
>
> Cheers,
>
> Wayne
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Stable release 4.0.7

[Adam Wolf]

I will run a build this week based on the stable branch and see.
Simon/Nick/anyone working on Mac packaging stuff, please let me know
if there are changes you want me to pull in, or if I should use the
same set of scripts as for 4.0.6.

(I think there might have been issues with where templates were stored
in 4.0.6 on the macOS packages... I need to check my notes.)

Feel free to take it off list or start a new thread if there's a bunch
of Mac packaging stuff to discuss.

Adam

On Wed, Jul 12, 2017 at 10:06 AM, Wayne Stambaugh  wrote:
> If there are no outstanding issues with the stable 4 branch, I'm going
> to tag it for the 4.0.7 release on Friday.  Please let me know if there
> are any source changes that need to be made be before I tag it.
>
> I would like to make the release announcement on July 30th.  Is this
> enough time for our doc devs, translators, and package devs to be ready
> for the release?  If not, please let me know and I will push back the
> announcement date.
>
> Thank you everyone for your continued support making KiCad possible.
>
> Cheers,
>
> Wayne
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ATTN: Package Maintainers - RFC: Library Reorganization

[Adam Wolf]

Thanks!  Regardless of how the migration happens, I really appreciate
having advance notice and I'm certain the rest of the packagers do
too! :)

Adam

On Thu, Jul 13, 2017 at 8:18 PM, Oliver Walters
 wrote:
> To the package maintainers:
>
> There has been a lot of movement of late by the library team, with a view to
> improve (vastly) the quality of the symbol libraries.
>
> The major change is our plan to reorganize the symbol libraries to bring
> some consistency - currently they are scattered and there is no real rhyme
> or reason to library convention.
>
> Reference - https://github.com/KiCad/kicad-library/issues/1402
>
> This is a big change - so much so that I would like to retain a separation
> between the current symbol libraries (for legacy compatibility). My
> suggestion is to enact the new symbols in a new repository:
>
> https://github.com/kicad/kicad-symbols
>
> We currently have a separate discussion underway as to how we manage
> migration to the new repository (or whether we simply make a block change to
> the current one) - https://github.com/KiCad/kicad-library/issues/1415
>
> A further very important note is that there is a new repository for 3d
> models, which is of far higher quality - https://github.com/kicad/packages3d
>
> This repository should supersede the 3d models currently located in the
> kicad-library repository. This also brings a functional separation between
> the symbol libraries and the 3d library, which is fantastic.
>
>
> My goal for release concurrent with KiCad v5 is thus:
>
> a) Mark kicad-library as legacy and don't package with v5
> b) Package kicad-symbols as the symbol libraries
> c) Package packages3d as the 3D model libraries
>
> I'm not 100% on top of how the packaging takes place so if there are any
> good reasons that this should not take place as I have laid out above,
> please let me know now.
>
> The footprint libraries will remain as they are for v5. I have some ideas
> there but they require a lot more work - this is the first step towards the
> KiCad Library Management Manifesto (evil laugh).
>
> Regards,
> Oliver
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 4.0.7 release update.

[Adam Wolf]

Did someone make the 4.0.7 docs zip yet?

Adam Wolf

On Sat, Jul 22, 2017 at 2:38 PM, Wayne Stambaugh  wrote:
> Does anyone need more time before I make the 4.0.7 stable release
> announcement?  If not I will push the announcement to the website Monday
> evening.  If so, I can push it back to next weekend.
>
> Cheers,
>
> Wayne
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 4.0.7 release update.

[Adam Wolf]

I generated a build with 4.0.7 sources and 4.0.6 docs as a test--it's
up in testing as 4.0.7-pre1
(http://downloads.kicad-pcb.org/osx/testing/)

I want to test that templates and things are in the right
places--there were some packaging bug reports from 4.0.6 I want to
check on this package.

My Mac is at the shop til the end of the week, but I can install on a
work computer and verify, but if someone else can, please let me know.

Adam Wolf

On Sun, Jul 23, 2017 at 4:24 PM, Adam Wolf
 wrote:
> Did someone make the 4.0.7 docs zip yet?
>
> Adam Wolf
>
> On Sat, Jul 22, 2017 at 2:38 PM, Wayne Stambaugh  wrote:
>> Does anyone need more time before I make the 4.0.7 stable release
>> announcement?  If not I will push the announcement to the website Monday
>> evening.  If so, I can push it back to next weekend.
>>
>> Cheers,
>>
>> Wayne
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] bugs in stable 4.07

[Adam Wolf]

This is not a problem for MacOS packaging.  The things that impact
MacOS packaging are when the dependencies change.  Remaking a 4.0.7
build after the tag moves isn't a problem.

Adam

On Mon, Jul 24, 2017 at 9:45 AM, Wayne Stambaugh  wrote:
> If we have known segfault bugs we should fix them.  I can remove the tag
> on the stable branch and move it to your bug fix commits.  Nice catch.
>
> I need some input from our package devs as to the impact on the stable
> release packaging.  I can push the release back another week or two to
> allow our package devs to create new packages.  Sorry about the extra
> work.  This is the first time I've had to do this.
>
> On 7/24/2017 10:37 AM, jp charras wrote:
>> Hi Wayne,
>>
>> I found 2 bugs in version 4.0.7
>>
>> The first is bug 1705941 (KiCad segfaults when creating project zip to dir 
>> with no write permission).
>> I fixed it (this is a minor change) in master (rev 
>> 622ba4f11bc788ec8690c51928061034045d3d18), and in
>> my local stable 4.0.7 working tree (I can commit it).
>>
>> the second is 
>> https://forum.kicad.info/t/edge-cuts-export-corrupted-using-python-interface/7173,
>> created by commit bfacf023608dfe192900576a60b204f63cd8.
>>
>> After this commit, default values are not compatible with gerber output.
>> It affects only the python scripts (both in master and stable 4.07 
>> versions), because incorrect plot
>> parameters are modified by the plot dialog.
>> However the plot code is not well designed and can create issues in any plot 
>> format.
>> The fix is not very hard, but needs a minimal work.
>>
>> But on Launchpad, the 4.0.7 is already tagged.
>> So is it possible now to fix these issues on Launchpad, or is it too late?
>>
>> Thanks.
>>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] 4.0.7 packaging (docs, macOS)

[Adam Wolf]

The 4.0.7 pre1 build I made last week with the 4.0.6 docs and libs works OK.

The help files launch, the various sub programs launch standalone as
well as through the project manager, the translations work.

There is at least one bug with the Template Selector--when you switch
between the User Templates, System Templates, and Portable Templates
tabs at the top, the path in the bottom doesn't match.  Sometimes when
you select User Templates, for example, it shows the System Template
path, othertimes Portable Templates, other times it actually shows
User Templates.  This is in launchpad, but the initial bug report
isn't quite right.  (https://bugs.launchpad.net/kicad/+bug/1492576)

I do not suspect this is a release blocker.

Before I can make the real 4.0.7 package, though, I need the docs for
4.0.7 generated.

Thanks everyone!

Adam Wolf

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 4.0.7 packaging (docs, macOS)

[Adam Wolf]

No problem.  I definitely agree with the libs, and now that I think
about it--unless we are adding new features, which we shouldn't be,
the docs should be fine too.

I will re-run the job without the -pre1 suffix and generate the release.

Adam Wolf

On Sat, Jul 29, 2017 at 3:42 PM, Wayne Stambaugh  wrote:
> On 7/28/2017 11:08 PM, Adam Wolf wrote:
>> The 4.0.7 pre1 build I made last week with the 4.0.6 docs and libs works OK.
>
> I'm guessing that we are keeping the libs and docs at 4.0.6.  I haven't
> seen or heard any move to tag 4.0.7.  I think it's important to keep the
> libs the same to prevent breaking schematics even though the new libs
> are far superior.  It may be wise to keep the docs at the same tag as
> well.  There may be documentation for features in the dev branch that do
> not exist in the stable 4 branch.
>
>>
>> The help files launch, the various sub programs launch standalone as
>> well as through the project manager, the translations work.
>>
>> There is at least one bug with the Template Selector--when you switch
>> between the User Templates, System Templates, and Portable Templates
>> tabs at the top, the path in the bottom doesn't match.  Sometimes when
>> you select User Templates, for example, it shows the System Template
>> path, othertimes Portable Templates, other times it actually shows
>> User Templates.  This is in launchpad, but the initial bug report
>> isn't quite right.  (https://bugs.launchpad.net/kicad/+bug/1492576)
>>
>> I do not suspect this is a release blocker.
>
> It is not a release blocker but it would be nice to get it fixed.  AFAIK
> the problem doesn't exist on windows or linux.
>
>>
>> Before I can make the real 4.0.7 package, though, I need the docs for
>> 4.0.7 generated.
>
> Unless there are no objections, I think using 4.0.6 tags are fine in
> this case unless someone with more knowledge of the lib and doc repos
> can tag a better 4.0.7 commit.
>
>>
>> Thanks everyone!
>>
>> Adam Wolf
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Python script offered as example for Action Plugin and wxFormBuilder integration

[Adam Wolf]

I think PEP8 is great for us.  Let's just add a line that says "We use
PEP8 as our Python style guide."

Adam Wolf

On Sat, Aug 12, 2017 at 10:27 AM, Strontium  wrote:
> Hello Wayne and Greg,
>
> Can I suggest just adopting PEP8 for Python code formatting.  Its clean,
> well documented, and there are plenty of linters to check conformance.  And
> if there is anything in PEP8 that is annoying for KiCad development (cant
> imagine what) just specify an exclusion or exception.
>
> Steven
>
> On 12/08/17 22:15, Wayne Stambaugh wrote:
>>
>> On 8/11/2017 10:08 PM, Greg Smith wrote:
>
> ...
>>>
>>> Suggestions on coding style, functionality, integration technique are
>>> welcome!
>>
>> We have not defined a Python coding style.  It's something that needs to
>> be done but no one has had the time to do it.  Please look at some of
>> the existing Python code in the KiCad source repo and follow what others
>> have done.  The last time I looked (which admittedly has been a while),
>> the formatting of our Python code was pretty consistent.
>
> ...
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Python script offered as example for Action Plugin and wxFormBuilder integration

[Adam Wolf]

Sure.  I was actually in the audience for that talk :)  IIRC, the
biggest takeaway is that sometimes there are exceptions, especially
for highly idiomatic code, and also that the 80 character original
line length limit is silly today and something like 120 is more
appropriate.

If you have particular changes you'd like to suggest to PEP8 for
Python style, let's discuss them.  On the other hand, we have no
automatic code rejection because of style--it's all human enforced at
this point, which means those exceptions for highly idiomatic code,
when commented and explained to the committer, already get through.

Adam Wolf

On Sat, Aug 12, 2017 at 11:30 AM, Kevin Cozens  wrote:
> On 2017-08-12 11:43 AM, Adam Wolf wrote:
>>
>> I think PEP8 is great for us.  Let's just add a line that says "We use
>> PEP8 as our Python style guide."
>
>
> Before you get too deep in to following PEP8 you might want to watch the
> video of a talk given by Raymond Hettinger (a core Python programmer) at
> PyCon 2015. The talk is called Beyond "PEP 8 -- Best practices for beautiful
> intelligible code" and can be seen at:
> https://www.youtube.com/watch?v=wf-BqAjZb8M
>
> --
> Cheers!
>
> Kevin.
>
> http://www.ve3syb.ca/   |"Nerds make the shiny things that distract
> Owner of Elecraft K2 #2172  | the mouth-breathers, and that's why we're
> | powerful!"
> #include  | --Chris Hardwick
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Stable release 4.0.7 status.

[Adam Wolf]

I have uploaded the macosx build from this morning into the staging
directory of the server.  If the release happens and I am on vacation,
someone with server access can move it over.

Adam Wolf

On Tue, Aug 15, 2017, 1:53 PM Wayne Stambaugh  wrote:

> Thanks Simon.
>
> We may have to wait for Nick to get back from holiday to fire the 4.0.7
> build.  I'm not sure exactly when he returns so we may have to push the
> release announcement back.  I do not believe that I have access to this
> or I would do it myself.
>
> On 8/15/2017 11:45 AM, Simon Richter wrote:
> > Hi,
> >
> > Took a while, but I have a Boost 1.60 package that builds, and I've run
> > the 4.0.6 stable build again to test it — looks good to me.
> >
> > Packages are at
> >
> > http://downloads.kicad-pcb.org/windows/testing/
> >
> > These were built with Nick's regular KiCad-Winbuilder project from
> > GitHub, so the 4.0.7 release can be triggered by adjusting the version
> > number in the PKGBUILD-stable file in that project, Jenkins will pick it
> > up automatically then.
> >
> > Not sure if that breaks OCE, because they also use Boost. I'm rebuilding
> > OCE, just to be sure, but that does not affect the stable release, only
> > the nightlies.
> >
> >Simon
> >
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Linux build environment

[Adam Wolf]

I test installing the dependencies from the package manager, and then
downloading the KiCad source and compiling it on a clean 16.04 machine
every day and have been for a few months.

If they start to fail, I'll poke the list.

Adam Wolf

On Wed, Aug 16, 2017 at 7:10 AM, Simon Richter  wrote:
> Hi,
>
> On 16.08.2017 09:16, Ingo Kletti wrote:
>
>> Is there a preferred Linux distro/build environment?
>
> No, it should work in any Linux distro where the requirements can be
> met. Requiring people to install a different distribution than they are
> used to would be a barrier to entry.
>
> If there is a problem on a particular setup we want to know about it, so
> we can investigate. If the build instructions don't cover a particular
> distribution, we want to know about it and improve the documentation.
>
> The only thing that may be problematic are really old releases, but
> 16.04 is certainly not too old.
>
>Simon
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Stable release 4.0.7 status.

[Adam Wolf]

So since we are updating libs now, are we updating the version number
in the docs?  Otherwise reusing the docs from the last release means
the 4.0.7 docs have a front page that says 4.0.6...

Adam

On Fri, Aug 25, 2017 at 8:10 AM, Nick Østergaard  wrote:
> I have got reports for people just sanity testing it that it seems to work.
> So I think we can move it to the stable folder.
>
> I don't know what the status is for the Macos and PPA builds.
>
> 2017-08-25 1:03 GMT+02:00 Simon Richter :
>>
>> Hi,
>>
>> On 25.08.2017 00:48, Wayne Stambaugh wrote:
>>
>> > Great work everyone!  Lets fire up those package builders.
>>
>> http://kiwi.hogyros.de:8080/job/windows-kicad-msys2-stable/11/console
>>
>> This will upload to
>>
>> http://downloads.kicad-pcb.org/windows/testing/
>>
>>Simon
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Stable release 4.0.7 status.

[Adam Wolf]

I'll run the builder today and hopefully we can do the release
announcement over the weekend!

Adam

On Fri, Aug 25, 2017 at 8:22 AM, Nick Østergaard  wrote:
> The docs are updated a bit, mostly translations I think. The tarball for it
> should be available.
>
> 2017-08-25 15:17 GMT+02:00 Adam Wolf :
>>
>> So since we are updating libs now, are we updating the version number
>> in the docs?  Otherwise reusing the docs from the last release means
>> the 4.0.7 docs have a front page that says 4.0.6...
>>
>> Adam
>>
>> On Fri, Aug 25, 2017 at 8:10 AM, Nick Østergaard 
>> wrote:
>> > I have got reports for people just sanity testing it that it seems to
>> > work.
>> > So I think we can move it to the stable folder.
>> >
>> > I don't know what the status is for the Macos and PPA builds.
>> >
>> > 2017-08-25 1:03 GMT+02:00 Simon Richter :
>> >>
>> >> Hi,
>> >>
>> >> On 25.08.2017 00:48, Wayne Stambaugh wrote:
>> >>
>> >> > Great work everyone!  Lets fire up those package builders.
>> >>
>> >> http://kiwi.hogyros.de:8080/job/windows-kicad-msys2-stable/11/console
>> >>
>> >> This will upload to
>> >>
>> >> http://downloads.kicad-pcb.org/windows/testing/
>> >>
>> >>Simon
>> >>
>> >>
>> >> ___
>> >> Mailing list: https://launchpad.net/~kicad-developers
>> >> Post to : kicad-developers@lists.launchpad.net
>> >> Unsubscribe : https://launchpad.net/~kicad-developers
>> >> More help   : https://help.launchpad.net/ListHelp
>> >>
>> >
>
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Stable release 4.0.7 status.

[Adam Wolf]

Hi folks,

Updated 4.0.7 packages are in osx-staging-stable on the server.  If
someone could test that they open up and seem to work OK they're ready
to go, otherwise I am unfortunately busy today and will not be able to
test them until tomorrow.

If someone else tests them and they seem OK they are OK to me.  (They
should work--the last 4 or 5 4.0.7 release candidates worked fine, I
just don't want to release them without testing the exact files.)

Adam

On Sat, Aug 26, 2017 at 8:16 AM, Jean-Samuel Reynaud
 wrote:
> Hi,
>
> Building is in progress for binaries in PPA. For documentation and i18n it
> is also in progress.
> A little more work is needed for libs and modules. But I'm working on it.
>
>
> Le 25/08/2017 à 15:10, Nick Østergaard a écrit :
>
> I have got reports for people just sanity testing it that it seems to work.
> So I think we can move it to the stable folder.
>
> I don't know what the status is for the Macos and PPA builds.
>
> 2017-08-25 1:03 GMT+02:00 Simon Richter :
>>
>> Hi,
>>
>> On 25.08.2017 00:48, Wayne Stambaugh wrote:
>>
>> > Great work everyone!  Lets fire up those package builders.
>>
>> http://kiwi.hogyros.de:8080/job/windows-kicad-msys2-stable/11/console
>>
>> This will upload to
>>
>> http://downloads.kicad-pcb.org/windows/testing/
>>
>>Simon
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Routing algorithm used in PCB

[Adam Wolf]

Hi Arun,

I helped OSHPark render KiCad PCBs to gerbers "in the cloud" so people
can upload KiCad PCB files and order them. Through the existing
scripting framework, you can put parts of KiCad in the cloud, but
there has been a massive amount of work in getting the UI stuff
working with wx, and I am skeptical we will see a non-wx KiCad anytime
soon.

You may be more interested in something like PCBmodE, which uses svg
and other technologies you may find more to your liking.

Adam Wolf

On Mon, Aug 28, 2017 at 1:47 PM, Arun Kumar  wrote:
>
> At least the non-resource intensive tasks like creating schematics, symbols
> and foot prints etc can be pushed on to the web.
>
> Resource intensive tasks can be done by a server side code (c++ or python
> code which you already developed can be used at the server side).
>
> Google is able to run services like sheets, docs and other resource
> intensive services on the cloud. Everything will eventually move to the
> cloud. It's better that we start a web based as early as possible.
>
> Today even the development environment like IDEs, SDK, workspaces have moved
> to cloud (example https://www.codenvy.com/)
>
> On Mon, Aug 28, 2017 at 10:26 PM, Bastian Neumannn
>  wrote:
>>
>> KiCad does come with a python interface.
>> Moving to python as native system and other web technologies are not a
>> good idea imho.
>>
>> Not every software is better with web and cloud stuff.
>>
>> 2017-08-28 18:04 GMT+02:00 Arun Kumar :
>>>
>>> Documentation of code or the usage of Kicad? I see that there is already
>>> documentation on the user guide.
>>>
>>> Would be happy if Kicad transitions to python or other web technologies.
>>>
>>> On Mon, Aug 28, 2017 at 8:56 PM, Fabrizio Tappero
>>>  wrote:
>>>>
>>>> Hi Arun,
>>>> if yu like you can contribute with the documentation.
>>>>
>>>> Regards
>>>> Fabrizio
>>>>
>>>>
>>>> On Mon, Aug 28, 2017 at 10:47 AM, Arun Kumar 
>>>> wrote:
>>>>>
>>>>> I don't know C++ so unable  to contribute and I want to build my own
>>>>> FOSS app with the languages I know. I always wanted to contribute to an
>>>>> existing project there  isn't a proper documentation about the source 
>>>>> code.
>>>>> Have to go through hundreds and thousands of lines of code to understand
>>>>> where they have implemented a specific functionality.
>>>>>
>>>>> I browsed the folders of the source code of Kicad but unable to
>>>>> understand what routing techniques are used and the code associated with 
>>>>> it.
>>>>> I  found  a folder with name algorithm but couldn't understand how they're
>>>>> working with the parts.
>>>>>
>>>>> Thanks,
>>>>> Arun
>>>>>
>>>>> On Mon, Aug 28, 2017 at 12:04 PM, José Ignacio 
>>>>> wrote:
>>>>>>
>>>>>> You already established that you want to extract techniques from kicad
>>>>>> for your own project instead of contributing. The code is all there in 
>>>>>> the
>>>>>> repo, free to use under the GPL.
>>>>>>
>>>>>> On Mon, Aug 28, 2017 at 12:41 AM, Arun Kumar 
>>>>>> wrote:
>>>>>>>
>>>>>>> Hi Team,
>>>>>>>
>>>>>>> Which PCB routing algorithm are used in PCB designing in Kicad?
>>>>>>>
>>>>>>> Thanks
>>>>>>> Arun
>>>>>>>
>>>>>>> ___
>>>>>>> Mailing list: https://launchpad.net/~kicad-developers
>>>>>>> Post to : kicad-developers@lists.launchpad.net
>>>>>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ___
>>>>> Mailing list: https://launchpad.net/~kicad-developers
>>>>> Post to : kicad-developers@lists.launchpad.net
>>>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>
>>>>
>>>
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Symbol library table remapping branch.

[Adam Wolf]

Hi Wayne,

Awesome news.  I know there are some changes the MacOS team wants to make
before stable-5 gets too solid, but I think most of those are packaging
related, except for some Python ones necessary to fix some gross bugs and
enable binary signing.

Adam Wolf

On Sep 1, 2017 4:10 PM, "Wayne Stambaugh"  wrote:

> On 9/1/2017 5:09 PM, Wayne Stambaugh wrote:
> > I finally found the time to finish the symbol library table remapping
> > implementation and I would like some help with testing before I merge
> > this into the master branch.  I would like to get as much testing as
> > possible.  I remember the issues when we switched from the same library
> > lookup format in Pcbnew so I would like to try to get as many of the
> > issues resolved before I merge the changes into the master branch.
> > Please back up your schematic files before you load them.  Otherwise you
> > will have a bunch of broken symbol library links in schematic since all
> > of the symbols names will now be in the new format
> > (LIB_NICKNAME:SYMBOL_NAME).  Also, please don't generate any external
> > files such as netlists with the remapped symbol names.  I haven't tested
> > any of that yet.  I am just trying to get the remapping as accurate as
> > possible.  The branch can be found in my dev repo at:
>
> git clone -b remap-symbols-to-sym-lib-table
> https://git.launchpad.net/~stambaughw/kicad/+git/kicad-dev
>
> >
> >
> > Before you test this, please perform the following tasks:
> >
> > 1. Delete the sym-lib-table file in your user configuration .kicad
> >folder if the table is empty.
> > 2. If you do not have a relatively recent install of the kicad-library
> >repo, install the latest libraries so you have the latest fully
> >populated symbol library table template file.
> > 3. Start Eeschema and allow the symbol library table config dialog copy
> >the default sym-lib-table file to your user config .kicad folder.  If
> >the default sym-lib-table file cannot be found, please point the
> >config dialog to the correct location.  Using the latest
> >sym-lib-table template file will give you the best remapping results.
> >
> > The first time you attempt to load a schematic that hasn't been
> > remapped, Eeschema will prompt you remap the symbol library links.  If
> > you choose not to remap, your schematic will most likely appear fine but
> > this is because all of the symbols will be linked to the cache library.
> > Here is what is happening during the remap process:
> >
> > 1. Backups of all of the schematic files are made.
> >
> > 2. The full library file name and path for each symbol is be compared to
> >the full library file name and path of every entry in the library
> >table.  If an exact match is found, the library nickname is added to
> >the LIB_ID object to create the fully qualified ID.
> >
> > 3. If the symbol library is not found in the global symbol library table
> >and the library file is valid and on your system, a project symbol
> >library is created with the symbol library added to it.  I could have
> >added an option to add these libraries to the global symbol library
> >table but I left that as an exercise for the user.
> >
> > 4. The symbol library table links in the schematic symbols are
> >refreshed.
> >
> > Obviously, the remapping depends on the availability of the symbol
> > libraries used in your project.  If you've inadvertently deleted a
> > symbol library and the cache library is being used then you are skating
> > on thin ice.  I don't see that as an issue since you were skating on
> > thin ice already.  I did change the message panel message when you click
> > on symbols in the schematic that are linked to the cache to display the
> > library information in red to warn the user that the cache library is
> > being used as the symbol link.  I am thinking it might be a better idea
> > to draw symbols that are linked to the cache library with a different
> > color to make it obvious to the user that they should fix their broken
> > links.
> >
> > I still have to convert the symbol chooser, the symbol library viewer,
> > the symbol library editor, some other minor bits and peices  over to
> > use the new symbol library table.  Once that is completed, I will make
> > a last call before I create the stable 5 branch so if you have anything
> > you want to see make it into the stable 5 release, now would be a good
> > time to get that ready to go.
> >
> >

Re: [Kicad-developers] KiCAD with MacOS Barely Usable

[Adam Wolf]

I don't have issues with rendering lag on my Retina display (not in
low-DPI mode) either, unless my board gets very complicated.

I do not run on an external display.

On Tue, Sep 5, 2017 at 11:16 AM, Jon Evans  wrote:
> I think the Retina display is just one piece of the puzzle re. Mac
> performance.  I have a Retina display and don't have any issues with
> rendering lag (and don't run in low-DPI mode either).  So, I suspect that
> there are some combinations of display + GPU + maybe drivers, library
> versions, etc? that can cause poor performance.
>
> -Jon
>
> On Tue, Sep 5, 2017 at 12:12 PM, Andrey Kuznetsov 
> wrote:
>>
>> Yes, I did.
>>
>> On Tue, Sep 5, 2017 at 9:11 AM Nick Østergaard  wrote:
>>>
>>> Did you try the tip mentioned on the webpage?
>>>
>>> http://kicad-pcb.org/help/known-system-related-issues/#_osx
>>>
>>> 2017-09-05 16:32 GMT+02:00 Jon Evans :

 Hi Andrey,

 I tried to reproduce this and couldn't.  I'm on 10.12.6, on a 2017 rMBP
 with internal display and 2K external display (don't have a 5K, but can't
 see how that would matter).  I also tried with an external mouse and didn't
 see any issue with the scroll wheel.

 Any other Mac developers have any ideas to help diagnose this?
 Andrey, it would probably be good to open a bug report so that this
 doesn't get lost in email.

 -Jon

 On Fri, Sep 1, 2017 at 7:58 PM, Andrey Kuznetsov 
 wrote:
>
> Here's an example video.
> I move the scroll wheel one at a time at first, and it zooms very slow,
> notice it jumps from like 7x to 22x in a single scroll.
> I tried PCBnew with OpenGL and it has additional problems, it zooms
> pretty fast compared to Eeschema but when it stops, there's 50:50 chance 
> it
> will jump 1 zoom level about a second after the zoom stops, which throws 
> you
> off badly in terms of where you are. It's not my scroll wheel behaving
> badly, scroll wheel is ratcheted, nothing like this happens on web pages,
> pdfs, etc.
> https://www.dropbox.com/s/rtlzeadfkkf3atn/KiCAD_20170801.mov?dl=0
>
> On Fri, Sep 1, 2017 at 4:31 PM, Andrey Kuznetsov 
> wrote:
>>
>> I'm using last night's nightly.
>>
>> Which mac do you have, retina display, external display?
>> My schematic operations are super laggy.
>>
>> To select a few parts, I have to click, wait a few seconds then drag,
>> if I don't wait and start dragging and release, the parts never get
>> selected.
>>
>> On Fri, Sep 1, 2017 at 4:27 PM, Jon Evans  wrote:
>>>
>>> Hi Andrey,
>>>
>>> Are you running the stable build or the nightlies?
>>> I'm also using 10.12 and while there are some issues, it is usable.
>>> I agree the zooming behavior is somewhat strange on Mac right now, but I
>>> don't have any issues with lag or the other things you describe (I'm 
>>> using
>>> nightly builds).
>>>
>>> -Jon
>>>
>>> On Fri, Sep 1, 2017 at 7:17 PM, Andrey Kuznetsov
>>>  wrote:

 Hi,

 Previously used KiCAD on Windows, everything worked well, even the
 nightlies.
 Just started using KiCAD on MAC OSX 10.12.6 on macbook pro 2016 with
 5K display, tried it without external display, no change, tried with 
 low
 resolution mode for the program, no change, tried reducing screen
 resolution, a little better, but still supper laggy and weird.

 Starting a new project and currently working in Eeschema.

 It takes 0.7s to rotate an LED symbol clockwise 90 degrees,
 everything is so laggy.
 Selecting parts, half the time doesn't select probably because I
 release too soon, the other half, very slow.

 Using the scroll wheel to zoom in and out causes horrendous lags.
 Not only that but somehow it ends up zooming to unpredictable levels 
 when
 only 1 mouse scroll is triggered and inertia disabled, because it keeps
 zooming and I move the mouse, it ends up zooming not where I was 
 originally
 pointing to zoom with 1 scroll wheel trig. For example, sometimes the 
 zoom
 doesn't stop right away so instead of zooming by 10 or 25% it goes 
 from 0.6x
 to 11x, like WTFF. So the zoom completely doesn't work, useless.
 Why is it that when I press CMD+scroll wheel it scrolls viewport
 horizontally?
 I have 2 scroll wheels, horiz and vert, both are scrolling
 horizontally.

 Button tool tips take a very long time to show up, I think 2
 seconds, 0.5s -1s should be used, when you're working and need a quick
 reminder, 2 seconds must as well be 10 seconds.

 Anyone else familiar with things I'm experiencing?

 Thanks

 --
 kandre...@gmail.c

Re: [Kicad-developers] A question about development environments for Kicad...

[Adam Wolf]

Many developers develop on Linux, some develop on Windows, and only a
few develop on MacOS.

Adam Wolf

On Thu, Sep 7, 2017 at 8:32 PM, Terry Gray  wrote:
> As a new addition to this group I have a question.  What are the prevalent
> dev. environments used by the primary Kicad developers. This might seem an
> inconsequential query, but I have a good reason for asking.  As far as I can
> discern (and I am hoping you guys can help clear this up for me) the current
> project structure doesn't seem to lend itself to the normal edit, build,
> debug cycle.  At least as far as I can tell.  The built executables won't
> execute in place with them in their corresponding project directories...that
> is to say, Kicad will execute but it can't instantiate eeschema because it
> can't find all the libraries.  I am currently performing a make install, to
> a local directory, to keep from corrupting my working installation, and I
> can debug from there but I can't edit interactively since the embedded .elf
> code isn't the original source.  Can someone clear this up for me?
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] A question about development environments for Kicad...

[Adam Wolf]

Terry,

If you like IDEs, clion works pretty great with KiCad in my
experience.  It requires cmake, so it has pretty great cmake support
:)

Adam Wolf

On Thu, Sep 7, 2017 at 8:48 PM, Terry Gray  wrote:
> Well, I think that is where the development environment comes in.  I am in
> Linux and use number of different IDE's: Code::Blocks, CodeLight, Eclipse
> CDT, etc.  In most of these, when the project is set up inside the IDE, when
> debugging you can edit the source in the same buffer as the debugger is
> displaying, and I can set a breakpoint at the error, stop debugging, make an
> edit, recompile and debug.  Code::Blocks is a pretty good lightweight IDE
> but has very poor cmake support and CodeLight is only a bit better.
>
> As a side note, I am finally biting the bullet and trying to learn Emacs.
> Is anyone using it on the Kicad tree?  Care to share a good cmake .init.el
> file?
>
>
> On 09/07/2017 08:38 PM, Jon Evans wrote:
>
> On Linux you can run the binaries from the project directory (or at least, I
> can).  So on my Linux machines I can build and debug individual parts .  On
> MacOS I do have to run make install like you say, but then can debug things
> from my temporary install directory.  What do you mean by edit
> interactively, though?
>
> -Jon
>
> On Thu, Sep 7, 2017 at 9:32 PM, Terry Gray  wrote:
>>
>> As a new addition to this group I have a question.  What are the prevalent
>> dev. environments used by the primary Kicad developers. This might seem an
>> inconsequential query, but I have a good reason for asking.  As far as I can
>> discern (and I am hoping you guys can help clear this up for me) the current
>> project structure doesn't seem to lend itself to the normal edit, build,
>> debug cycle.  At least as far as I can tell.  The built executables won't
>> execute in place with them in their corresponding project directories...that
>> is to say, Kicad will execute but it can't instantiate eeschema because it
>> can't find all the libraries.  I am currently performing a make install, to
>> a local directory, to keep from corrupting my working installation, and I
>> can debug from there but I can't edit interactively since the embedded .elf
>> code isn't the original source.  Can someone clear this up for me?
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [RFC] Changing default text size

[Adam Wolf]

Is there any chance we can solve this issue across our codebase across
all the filetypes before 5 comes out?  For any instance where we omit
the values if they're "default", can we explicitly set the default at
the beginning of the file?

I feel like we've been bit by this sort of thing in the past.

Adam Wolf

On Fri, Sep 8, 2017 at 7:55 AM, Wayne Stambaugh  wrote:
> Oliver,
>
> The new default text size will will be transparent (not written to the
> file) as long as users accept this change.  Should the user prefer the
> 60mil text size and change them from the new 50mil default to 60mils,
> they will now have a file change to keep the same schematic they had
> prior the change.  Conversely, users like me who change all of their
> text to 50mils will also have a file change because now 50mils is the
> default and will not be saved in the file.  If you use VCS, this kind of
> change is annoying.  I'm not saying I'm opposed to the change.  I'm just
> warning you that there are consequences for making this change.
> Personally, I prefer 50mils so it's a win for me.
>
> Cheers,
>
> Wayne
>
> On 9/7/2017 6:44 PM, Oliver Walters wrote:
>> Wayne,
>>
>> So are you saying that if a text item has a default text size
>> (hard-coded to 0.060") then this text size will *not* be written to the
>> file? i.e. an omitted text field size means "use default size"?
>>
>> Oliver
>>
>> On Fri, Sep 8, 2017 at 4:30 AM, Wayne Stambaugh > <mailto:stambau...@gmail.com>> wrote:
>>
>> If you change the default text size, then users schematics will appear
>> differently the next time they open their schematics and they will have
>> to go back an change them back to .060" which will change their file(s).
>>  Will users even notice?  I don't know but if they do, I'll bet they
>> wont be happy about it.
>>
>> On my todo list is a global text size dialog similar the the one in
>> Pcbnew for setting schematic object text sizes.  This may be a less
>> intrusive way to set schematic texts sizes rather than change the
>> default.
>>
>> On 9/7/2017 12:12 AM, Oliver Walters wrote:
>> > Currently the default text size in eeschema for labels is 60mils.
>> >
>> > The official libs and KLC require 50mils. Users can "easily"
>> change the
>> > default setting to 50mils but it seems an unnecessary step that
>> could be
>> > removed.
>> >
>> > Would changing the default label size from 60mils to 50mils break
>> > anything? For example are label size numbers omitted in a file
>> format if
>> > they are default?
>> >
>> > Cheers,
>> > Oliver
>> >
>> >
>> > ___
>> > Mailing list: https://launchpad.net/~kicad-developers
>> <https://launchpad.net/~kicad-developers>
>> > Post to : kicad-developers@lists.launchpad.net
>> <mailto:kicad-developers@lists.launchpad.net>
>> > Unsubscribe : https://launchpad.net/~kicad-developers
>> <https://launchpad.net/~kicad-developers>
>> > More help   : https://help.launchpad.net/ListHelp
>> <https://help.launchpad.net/ListHelp>
>> >
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> <https://launchpad.net/~kicad-developers>
>> Post to : kicad-developers@lists.launchpad.net
>> <mailto:kicad-developers@lists.launchpad.net>
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> <https://launchpad.net/~kicad-developers>
>> More help   : https://help.launchpad.net/ListHelp
>> <https://help.launchpad.net/ListHelp>
>>
>>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] KiCad Libraries (again)

[Adam Wolf]

I really, really like the idea of having the libraries page on the
KiCad website itself.

I have run into numerous people who do not understand that the github
libraries are "official".  Plus, this means that *for whatever reason*
if the libraries move from github, the pages explaining the libraries
stay in the same space.

Adam Wolf

On Thu, Sep 14, 2017 at 7:54 PM, Oliver Walters
 wrote:
> Ben,
>
> That's also an option, I hadn't considered that! Perhaps I was focused on
> the GitHub-side solution too closely.
>
> Wayne, do you want to weigh in here before I spend too much further effort
> developing this? Could the libraries page be developed on the KiCad website
> itself?
>
> The structure could remain largely the same but the formatting would need to
> change from Jekyll to Hugo.
>
> Cheers,
> Oliver
>
> On Fri, Sep 15, 2017 at 1:17 AM, Ben Hest  wrote:
>>
>> Does this method provide an advantage over doing a similar thing using
>> Hugo and putting the docs on the kicad-pcb.org website?
>> https://github.com/KiCad/kicad-website
>>
>>
>> - Ben
>>
>> On Thu, Sep 14, 2017 at 7:01 AM, Oliver Walters
>>  wrote:
>>>
>>> Hi everyone,
>>>
>>> The conversation of how best to manage and distribute KiCad libraries has
>>> been raging for a while now.
>>>
>>> Users looking to download or contribute to the libraries are currently
>>> presented with a github landing page and some bland wiki pages (e.g. for the
>>> KLC information).
>>>
>>> I have been working on a new-and-improved website system for the
>>> following:
>>>
>>> * Clear information about the libraries
>>> * A place to download the latest libraries
>>> * Information on what is *in* the libraries
>>> * Instructions on how to contribute to the libs
>>> * Better presentation of the KLC
>>>
>>> This website will need to be updated periodically to present the latest
>>> version of the libraries to the users. Also, if users are going to be
>>> downloading library files then it could potentially use a lot of bandwidth.
>>> Thirdly, the generated content should be scripted but statically hosted.
>>>
>>> The solution? GitHub pages! - https://pages.github.com/ -
>>>
>>> These are hosted from your github repository, and for e.g. ours would
>>> have the URL kicad.github.io - this could be easily redirected from
>>> kicad-lib.org/library (for example).
>>>
>>> GitHub pages use the jekyll toolset to generate static content.
>>>
>>> With a small amount of additional Python scripting I have created a
>>> bare-bones example of what this might look like (locally hosted on my laptop
>>> for now):
>>>
>>> Here are some screenshots! Ignore the colors and simple layout scheme,
>>> this is currently just a framework.
>>>
>>> https://imgur.com/a/0GELG
>>>
>>> The main objectives of this project are:
>>>
>>> a) Present a more professional landing page for the libraries
>>> b) Leverage GitHub Pages functionality
>>> c) Improve KLC
>>>
>>> And, eventually:
>>>
>>> Provide a standardised way to separate the KiCad libraries from the KiCad
>>> installer!
>>>
>>> Thoughts and comments appreciated!
>>>
>>> Cheers,
>>>
>>> Oliver
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>>
>>
>> --
>>
>> -Ben
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] KiCad Libraries (again)

[Adam Wolf]

This sounds awesome to me, and helps keep KiCad cohesive.  I remember
when basically every KiCad site was a fan site and it was pretty hard
to find anything, and we have done a great job lately and this is
going to help make it even better I think!

I do not think that this even technically requires to change the
static site engine, if you already have a lot of work or a reason to
stick with whatever you have already used.  It is pretty easy for the
site folks to host the static site out of a different directory, for
example.  (It's a bummer when you show something cool to a mailing
list and everyone is enthusiastic but then asks you do to more work or
to redo what you already did :) )

On Thu, Sep 14, 2017 at 9:14 PM, Oliver Walters
 wrote:
> Adam,
>
> Both are really good points.
>
> Here's what I propose:
>
> Short Term:
>
> Move the library information / license / KLC / contributing information to
> the website. This will also include links to download library releases (from
> github)
>
> Medium Term:
>
> Provide downloads of individual libraries, which will be hosted (??
> somewhere ?? )
>
> Long Term:
>
> Full description of library elements, including image previews / metadata /
> etc. This will be searchable.
>
> Actual library data remains on GitHub, obviously.
>
> On Fri, Sep 15, 2017 at 12:01 PM, Adam Wolf 
> wrote:
>>
>> I really, really like the idea of having the libraries page on the
>> KiCad website itself.
>>
>> I have run into numerous people who do not understand that the github
>> libraries are "official".  Plus, this means that *for whatever reason*
>> if the libraries move from github, the pages explaining the libraries
>> stay in the same space.
>>
>> Adam Wolf
>>
>> On Thu, Sep 14, 2017 at 7:54 PM, Oliver Walters
>>  wrote:
>> > Ben,
>> >
>> > That's also an option, I hadn't considered that! Perhaps I was focused
>> > on
>> > the GitHub-side solution too closely.
>> >
>> > Wayne, do you want to weigh in here before I spend too much further
>> > effort
>> > developing this? Could the libraries page be developed on the KiCad
>> > website
>> > itself?
>> >
>> > The structure could remain largely the same but the formatting would
>> > need to
>> > change from Jekyll to Hugo.
>> >
>> > Cheers,
>> > Oliver
>> >
>> > On Fri, Sep 15, 2017 at 1:17 AM, Ben Hest  wrote:
>> >>
>> >> Does this method provide an advantage over doing a similar thing using
>> >> Hugo and putting the docs on the kicad-pcb.org website?
>> >> https://github.com/KiCad/kicad-website
>> >>
>> >>
>> >> - Ben
>> >>
>> >> On Thu, Sep 14, 2017 at 7:01 AM, Oliver Walters
>> >>  wrote:
>> >>>
>> >>> Hi everyone,
>> >>>
>> >>> The conversation of how best to manage and distribute KiCad libraries
>> >>> has
>> >>> been raging for a while now.
>> >>>
>> >>> Users looking to download or contribute to the libraries are currently
>> >>> presented with a github landing page and some bland wiki pages (e.g.
>> >>> for the
>> >>> KLC information).
>> >>>
>> >>> I have been working on a new-and-improved website system for the
>> >>> following:
>> >>>
>> >>> * Clear information about the libraries
>> >>> * A place to download the latest libraries
>> >>> * Information on what is *in* the libraries
>> >>> * Instructions on how to contribute to the libs
>> >>> * Better presentation of the KLC
>> >>>
>> >>> This website will need to be updated periodically to present the
>> >>> latest
>> >>> version of the libraries to the users. Also, if users are going to be
>> >>> downloading library files then it could potentially use a lot of
>> >>> bandwidth.
>> >>> Thirdly, the generated content should be scripted but statically
>> >>> hosted.
>> >>>
>> >>> The solution? GitHub pages! - https://pages.github.com/ -
>> >>>
>> >>> These are hosted from your github repository, and for e.g. ours would
>> >>> have the URL kicad.github.io - this could be easily redirected from
>> >>> kicad-lib.org/library (for example).
>> >>>
>> >>> GitHub page

Re: [Kicad-developers] [PATCH] Improve template selector for macOS

[Adam Wolf]

Thanks Seppe.

This bug has been irritating, thanks for fixing it!

Adam Wolf

On Mon, Sep 18, 2017 at 9:58 AM, jp charras  wrote:
> Le 18/09/2017 à 16:11, Seppe Stas a écrit :
>> This fixes some issues with the template selector that cause it not to work 
>> properly on macOS.
>>
>> The main issue is a race condition where `OnPageChange` uses 
>> `m_notebook->GetSelection()` to get the
>> selected page number instead of `event.GetSelection()` as defined in the docs
>> <http://docs.wxwidgets.org/3.1/classwx_notebook.html#a24783577628b3da1537a9476629cc72b>.
>>
>> On macOS `m_notebook->GetSelection()` sometimes / typically returns the page 
>> number of the old page,
>> resulting in the template selector not working properly and issues as 
>> described in lp:1492577
>> <https://bugs.launchpad.net/kicad/+bug/1492577> and lp:1672116
>> <https://bugs.launchpad.net/kicad/+bug/1672116>.
>>
>> Another problem is the template pages not being rendered properly when 
>> initially added using the
>> `AddTemplatesPage` call. Only when the notebook page is active and shown it 
>> is possible to render
>> the template page, pointing in the direction of another race condition.
>>
>> I did not find a proper solution to this problem, but ignoring the template 
>> path not being updated
>> at least allows the "validate" and "browse" buttons to render the templates.
>>
>> On the long run, it's probably a good idea to completely redo the template 
>> system. It's riddled with
>> race conditions on macOS and render issues on Ubuntu, and it's one of the 
>> only parts of KiCad
>> heavily relying on wxFormBuilder projects.
>>
>> This is my first public contribution to the KiCad project and I plan to fix 
>> some more things. I'm
>> not sure if emails to this group or Launchpad PRs are prefered.
>
> Thanks Seppe.
>
> I committed your patch, because it looks good (and tested on W7).
>
> Sending patches to the dev. ML is the right way, especially for small 
> patches, from my point of view.
> They are easy to review and to apply.
>
> --
> Jean-Pierre CHARRAS
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] File format version increment

[Adam Wolf]

Strontium,

I assume you are talking about linux based on the word PPA, but mostly
for other people on the list, you can do this with the MacOS KiCad.

Adam

On Thu, Sep 21, 2017 at 8:59 PM, Strontium  wrote:
> This is a question for the distribution maintainers,
>
> Is it possible to change the distribution PPA's (etc) so that one can
> install the nightly and the stable version of kicad, simultaneously?
>
> When things like file format versions change then people have to make a
> choice, do I run nightly and lose backward compatibility OR do I run stable
> and lose newer features/the ability to test.   It would be handy to be able
> to have Stable installed to do real work, and nightly also installed for
> testing, or for boards where you really want access to a new feature early.
>
> Steven
>
>
>
> On 20/09/17 00:38, Maciej Sumiński wrote:
>
> For your information: support for long pad and pin names has been just
> merged. As the change affects both eeschema and pcbnew, and may result
> in files that are not loaded correctly with older versions - the file
> format versions had to be incremented.
>
> Regards,
> Orson
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Symbol library table input.

[Adam Wolf]

If it isn't backwards compatible, I vote for changing the version.

Adam Wolf

On Sun, Oct 22, 2017 at 3:49 PM, Wayne Stambaugh  wrote:
> I'm am almost ready to push the symbol library table code.  All I have
> left is to update the Eagle plugin, remove the current library
> management dialog, and clear the library entries from the project.  One
> thing that will change is that the schematic files will be incompatible
> with older versions of kicad due to the way symbol library links are
> mapped.  Technically the file format is not changing.  Only the library
> symbol link ( from SYMBOL_NAME to LIB_NICKNAME:SYMBOL_NAME ) is
> changing.  Older versions of KiCad will open the schematic but all of
> the symbol links will be broken.  I haven't bumped the schematic file
> version but I'm thinking I should.  Anyone else have any thoughts on this?
>
> Cheers,
>
> Wayne
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] [PATCH] wxWidgets macOS 10.13 Patch

[Adam Wolf]

Hi folks,

Attached is a patch that adds a patch that helps wxWidgets build on
the latest macOS 10.13 High Sierra.

Additionally, when folks build wxWidgets, they'll need to set the
CPPFLAG of D__ASSERT_MACROS_DEFINE_VERSIONS_WITHOUT_UNDERSCORES=1.

I'm working on updating the packaging scripts so folks can use those
as a reference.

Adam Wolf


0001-Added-patch-for-wxwidgets-for-macOS-High-Sierra-10.1.patch
Description: Binary data
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] wxWidgets macOS 10.13 Patch

[Adam Wolf]

No problem.  More details about the CPPFLAG are here:

https://trac.wxwidgets.org/ticket/17929

Once 3.0.4 is out, it'll be handled inside of wxwidgets, so it's just
a transitory thing for folks looking to build on High Sierra now.

Honestly, I'm not sure we need to to add it to any docs or anything,
but if people come knocking asking for help on building KiCad on 10.13
in the next few months, maybe they'll find this message.

Adam Wolf

On Tue, Nov 7, 2017 at 1:59 AM, Maciej Sumiński  wrote:
> Hi Adam,
>
> Thank you for the (meta)patch. Would you give some more details about
> the required CPPFLAG? Perhaps we could do something on our side? I would
> rather avoid adding one more requirement to the way wxWidgets building
> process, unless there is really no other method.
>
> Regards,
> Orson
>
> On 11/07/2017 03:25 AM, Adam Wolf wrote:
>> Hi folks,
>>
>> Attached is a patch that adds a patch that helps wxWidgets build on
>> the latest macOS 10.13 High Sierra.
>>
>> Additionally, when folks build wxWidgets, they'll need to set the
>> CPPFLAG of D__ASSERT_MACROS_DEFINE_VERSIONS_WITHOUT_UNDERSCORES=1.
>>
>> I'm working on updating the packaging scripts so folks can use those
>> as a reference.
>>
>> Adam Wolf
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] wxWidgets macOS 10.13 Patch

[Adam Wolf]

I'll prep a patch for the build doc in the next few days.

Adam

On Tue, Nov 7, 2017 at 7:06 AM, Wayne Stambaugh  wrote:
> My preference would be add it to the kicad build doc.  It would be
> easier to find this information in the kicad build document than the
> developers mailing list and easier to point someone to the build docs.
> It may be a while before wx 3.0.4 is available and I imagine even longer
> until folks stop creating osx builds with 10.13 and wx 3.0.3.
>
> Cheers,
>
> Wayne
>
> On 11/7/2017 7:50 AM, Adam Wolf wrote:
>> No problem.  More details about the CPPFLAG are here:
>>
>> https://trac.wxwidgets.org/ticket/17929
>>
>> Once 3.0.4 is out, it'll be handled inside of wxwidgets, so it's just
>> a transitory thing for folks looking to build on High Sierra now.
>>
>> Honestly, I'm not sure we need to to add it to any docs or anything,
>> but if people come knocking asking for help on building KiCad on 10.13
>> in the next few months, maybe they'll find this message.
>>
>> Adam Wolf
>>
>> On Tue, Nov 7, 2017 at 1:59 AM, Maciej Sumiński  
>> wrote:
>>> Hi Adam,
>>>
>>> Thank you for the (meta)patch. Would you give some more details about
>>> the required CPPFLAG? Perhaps we could do something on our side? I would
>>> rather avoid adding one more requirement to the way wxWidgets building
>>> process, unless there is really no other method.
>>>
>>> Regards,
>>> Orson
>>>
>>> On 11/07/2017 03:25 AM, Adam Wolf wrote:
>>>> Hi folks,
>>>>
>>>> Attached is a patch that adds a patch that helps wxWidgets build on
>>>> the latest macOS 10.13 High Sierra.
>>>>
>>>> Additionally, when folks build wxWidgets, they'll need to set the
>>>> CPPFLAG of D__ASSERT_MACROS_DEFINE_VERSIONS_WITHOUT_UNDERSCORES=1.
>>>>
>>>> I'm working on updating the packaging scripts so folks can use those
>>>> as a reference.
>>>>
>>>> Adam Wolf
>>>
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [REQUEST] Default library install location

[Adam Wolf]

This wouldn't be difficult on macOS.  It is already kinda set up like that
with the split installer already..

Adam Wolf

On Nov 8, 2017 1:02 AM, "Oliver Walters" 
wrote:

> To the package maintainers:
>
> For v5 release, can the default library install path be set to a user
> directory rather than program directory that may require administrator
> rights?
>
> e.g. instead of
>
> C:\Program Files\KiCad\share\...
> or
> /usr/share/kicad/...
>
> something like;
>
> C:\Users\Oliver\KiCad\...
>
> /home/Oliver/KiCad
>
> (Not necessarily those paths but something like that).
>
> A lot of users are reporting issues with being able to download or modify
> library files, due to user privileges.
>
> How attainable is such a change before v5 release?
>
> Thanks,
> Oliver
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Mac packaging plans for V5 and beyond

[Adam Wolf]

Hi folks!

I have some things I've been working on for KiCad for quite a long
time, and I'd like to wait to show them off once they're finished, but
I want to announce them before the feature freeze for v5 (and maybe
even get some help).

1) Reworking how python is included.  I'm now following the way Apple
suggests, and this seems to fix some long-standing bugs with people
who have already had things installed.  This is basically ready today,
and could be incorporated into our nightlies at almost any time (with
buy-in from Nick and everyone else who does those), but could also
wait until #4.

2) Signing.  I got an Apple key for my business so I can sign binaries
and they won't pop up that annoying warning.  I have this working on
my system, however, it cannot work with the symlink method that we're
using right now for macOS packaging.  Chris and I have been talking
about changing this on and off--it definitely won't happen before V5,
but I'd like to get it in the works so it's finished by V6.

The remaining work on this is to document the issues with the symlink
method, brainstorm ideas to see if there's an option Chris and I
missed, and get buy-in and schedule the work before the V6 freeze.

3) Builds!  A good friend of mine tried to get KiCad to build based on
our build page, and he spent nearly two weeks and was unable to get it
to build on macOS or Linux, and he does software development for a
living!  Based on that, I thought I could help out.  I wrote some
simple scripts, and now I am creating a new VM for a variety of OSes
from a clean template, telling them to patch themselves with all the
latest security patches, and then running an extremely minimal build
script that just tests to see if it builds.  I am currently doing this
for Ubuntu 16.04, 16.10, 17.04, 17.10, and macOS 10.12, everyday.  (I
will be adding macOS 10.13 and 10.9-10.11, as well as Fedora 25 and 26
shortly.)  This is not for packaging, this is just for developers to
see that "hey, if you follow this short list of instructions, you
should be able to get kicad building on your system".

I remember all the pain we had supporting builds on the developer list
in the past, and I do not want to bring that back, but this should
help warn us if the dependency names change, or if something breaks on
those systems.

The remaining work on this is mostly documentation.  I need to
document how other people can use these scripts, and also, if we have
buy-in, rework the builds page so that it's easier for new developers
to get started building KiCad.

4) Reworking the macOS build scripts.  I have been talking about this
for three years.  I am reworking the macOS build scripts, and actually
basing them on CMake :)  I have Python, wxwidgets, wxpython, and kicad
building already working.  Next I will be adding docs, packaging a
dmg, packaging the extras dmg.

Right now I'm using them with Clion to add a feature to KiCad, and
they're pretty slick!

The next steps here are for me to get it so this has the same output
as the current system, and then get buy-in to switch to it for
nightlies.  Once this has happened, I can use this to make stable
builds in a VM.  This is important, because the way the V4 stable
builds were made, using some tricks with homebrew, has been
discontinued and it will be trickier and trickier to make new stable
releases that way.

#4 is the actual top priority-I want to replace nightlies and stable
with that new packaging script before V5 comes out, and I'm working on
it every day.

I can do most of them on my own if it isn't interesting work to other
people, but if people want to help, let me know and I can set them up
on Github and set up some issues.  I have to say, most of these items
have been on my radar for awhile, and I'm glad I finally spent the
time and read the 100+ page docs from Apple and did a bunch of
experiments and finally made some breakthroughs!

Adam Wolf

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Mac packaging plans for V5 and beyond

[Adam Wolf]

Drats!  I forgot to include the link to the builds page (which is
definitely not ready for primetime):
https://builder.wayneandlayne.com/job/CompileKiCadOnCleanVM/

Adam Wolf

On Tue, Nov 14, 2017 at 4:02 PM, Adam Wolf
 wrote:
> Hi folks!
>
> I have some things I've been working on for KiCad for quite a long
> time, and I'd like to wait to show them off once they're finished, but
> I want to announce them before the feature freeze for v5 (and maybe
> even get some help).
>
> 1) Reworking how python is included.  I'm now following the way Apple
> suggests, and this seems to fix some long-standing bugs with people
> who have already had things installed.  This is basically ready today,
> and could be incorporated into our nightlies at almost any time (with
> buy-in from Nick and everyone else who does those), but could also
> wait until #4.
>
> 2) Signing.  I got an Apple key for my business so I can sign binaries
> and they won't pop up that annoying warning.  I have this working on
> my system, however, it cannot work with the symlink method that we're
> using right now for macOS packaging.  Chris and I have been talking
> about changing this on and off--it definitely won't happen before V5,
> but I'd like to get it in the works so it's finished by V6.
>
> The remaining work on this is to document the issues with the symlink
> method, brainstorm ideas to see if there's an option Chris and I
> missed, and get buy-in and schedule the work before the V6 freeze.
>
> 3) Builds!  A good friend of mine tried to get KiCad to build based on
> our build page, and he spent nearly two weeks and was unable to get it
> to build on macOS or Linux, and he does software development for a
> living!  Based on that, I thought I could help out.  I wrote some
> simple scripts, and now I am creating a new VM for a variety of OSes
> from a clean template, telling them to patch themselves with all the
> latest security patches, and then running an extremely minimal build
> script that just tests to see if it builds.  I am currently doing this
> for Ubuntu 16.04, 16.10, 17.04, 17.10, and macOS 10.12, everyday.  (I
> will be adding macOS 10.13 and 10.9-10.11, as well as Fedora 25 and 26
> shortly.)  This is not for packaging, this is just for developers to
> see that "hey, if you follow this short list of instructions, you
> should be able to get kicad building on your system".
>
> I remember all the pain we had supporting builds on the developer list
> in the past, and I do not want to bring that back, but this should
> help warn us if the dependency names change, or if something breaks on
> those systems.
>
> The remaining work on this is mostly documentation.  I need to
> document how other people can use these scripts, and also, if we have
> buy-in, rework the builds page so that it's easier for new developers
> to get started building KiCad.
>
> 4) Reworking the macOS build scripts.  I have been talking about this
> for three years.  I am reworking the macOS build scripts, and actually
> basing them on CMake :)  I have Python, wxwidgets, wxpython, and kicad
> building already working.  Next I will be adding docs, packaging a
> dmg, packaging the extras dmg.
>
> Right now I'm using them with Clion to add a feature to KiCad, and
> they're pretty slick!
>
> The next steps here are for me to get it so this has the same output
> as the current system, and then get buy-in to switch to it for
> nightlies.  Once this has happened, I can use this to make stable
> builds in a VM.  This is important, because the way the V4 stable
> builds were made, using some tricks with homebrew, has been
> discontinued and it will be trickier and trickier to make new stable
> releases that way.
>
> #4 is the actual top priority-I want to replace nightlies and stable
> with that new packaging script before V5 comes out, and I'm working on
> it every day.
>
> I can do most of them on my own if it isn't interesting work to other
> people, but if people want to help, let me know and I can set them up
> on Github and set up some issues.  I have to say, most of these items
> have been on my radar for awhile, and I'm glad I finally spent the
> time and read the 100+ page docs from Apple and did a bunch of
> experiments and finally made some breakthroughs!
>
> Adam Wolf

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Mac packaging plans for V5 and beyond

[Adam Wolf]

No problem.  I don't really care which option we go with. :)

Adam Wolf

On Nov 14, 2017 5:40 PM, "Simon Wells"  wrote:

> Assuming its just the symlinks that are the problem i see 2 work arounds
>
> 1) do an apple and make it so you can launch the seperate apps from the
> app menu (ala xcode)
> 2) just have people open the bundle and run the applications from the
> applications directory (ala xcode as well)
>
> It would be nice if you were able to change the app menu in the dock when
> kicad wasn't running and it would also be nice if there were options in the
> right click on the .app to choose alternate launchers, but unfortunately
> thats not possible.
>
> sorry for the double post adam, this was meant to go to the list not to you
>
>
>
>
> On 15/11/2017, at 12:24, Nick Østergaard  wrote:
>
> 2017-11-14 23:02 GMT+01.00, Adam Wolf :
>
> Drats!  I forgot to include the link to the builds page (which is
> definitely not ready for primetime):
> https://builder.wayneandlayne.com/job/CompileKiCadOnCleanVM/
>
> Adam Wolf
>
> On Tue, Nov 14, 2017 at 4:02 PM, Adam Wolf
>  wrote:
>
> Hi folks!
>
> I have some things I've been working on for KiCad for quite a long
> time, and I'd like to wait to show them off once they're finished, but
> I want to announce them before the feature freeze for v5 (and maybe
> even get some help).
>
>
> Nice, good to see that you can still twitch.
>
> 1) Reworking how python is included.  I'm now following the way Apple
> suggests, and this seems to fix some long-standing bugs with people
> who have already had things installed.  This is basically ready today,
> and could be incorporated into our nightlies at almost any time (with
> buy-in from Nick and everyone else who does those), but could also
> wait until #4.
>
>
> Well, where is your new work? IIRC we use your scripts from
> https://github.com/wayneandlayne/KiCadMacOSPackaging to do the
> nightlies...
>
> Getting the issue fixed where it break if you have installed wxpython
> from elsewhere would be great.
>
> 2) Signing.  I got an Apple key for my business so I can sign binaries
> and they won't pop up that annoying warning.  I have this working on
> my system, however, it cannot work with the symlink method that we're
> using right now for macOS packaging.  Chris and I have been talking
> about changing this on and off--it definitely won't happen before V5,
> but I'd like to get it in the works so it's finished by V6.
>
> The remaining work on this is to document the issues with the symlink
> method, brainstorm ideas to see if there's an option Chris and I
> missed, and get buy-in and schedule the work before the V6 freeze.
>
> 3) Builds!  A good friend of mine tried to get KiCad to build based on
> our build page, and he spent nearly two weeks and was unable to get it
> to build on macOS or Linux, and he does software development for a
> living!  Based on that, I thought I could help out.  I wrote some
> simple scripts, and now I am creating a new VM for a variety of OSes
> from a clean template, telling them to patch themselves with all the
> latest security patches, and then running an extremely minimal build
> script that just tests to see if it builds.  I am currently doing this
> for Ubuntu 16.04, 16.10, 17.04, 17.10, and macOS 10.12, everyday.  (I
> will be adding macOS 10.13 and 10.9-10.11, as well as Fedora 25 and 26
> shortly.)  This is not for packaging, this is just for developers to
> see that "hey, if you follow this short list of instructions, you
> should be able to get kicad building on your system".
>
> I remember all the pain we had supporting builds on the developer list
> in the past, and I do not want to bring that back, but this should
> help warn us if the dependency names change, or if something breaks on
> those systems.
>
> The remaining work on this is mostly documentation.  I need to
> document how other people can use these scripts, and also, if we have
> buy-in, rework the builds page so that it's easier for new developers
> to get started building KiCad.
>
> 4) Reworking the macOS build scripts.  I have been talking about this
> for three years.  I am reworking the macOS build scripts, and actually
> basing them on CMake :)  I have Python, wxwidgets, wxpython, and kicad
> building already working.  Next I will be adding docs, packaging a
> dmg, packaging the extras dmg.
>
> Right now I'm using them with Clion to add a feature to KiCad, and
> they're pretty slick!
>
> The next steps here are for me to get it so this has the same output
> as the current system, and then get buy-in to switch to it f

[Kicad-developers] recent macos build failures

[Adam Wolf]

Hi folks!

Anyone having issues like this recently?

*08:58:06* default:
/vagrant/build/kicad/src/kicad/qa/eeschema/eeschema_test_utils.cpp:28:23:
error: no member named 'getenv' in namespace 'std'; did you mean
simply 'getenv'?*08:58:06* default: const char* env =
std::getenv( "KICAD_TEST_EESCHEMA_DATA_DIR" );*08:58:06* default:
 ^~~*08:58:06* default:
   getenv


Adam Wolf
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] recent macos build failures

[Adam Wolf]

Thanks!  Amazing response time!

On Mon, Apr 8, 2019 at 2:34 PM Seth Hillbrand  wrote:

> Am 2019-04-08 14:57, schrieb Adam Wolf:
> > Hi folks!
> >
> > Anyone having issues like this recently?
> >
> > 08:58:06 default:
> > /vagrant/build/kicad/src/kicad/qa/eeschema/eeschema_test_utils.cpp:28:23:
> > error: no member named 'getenv' in namespace 'std'; did you mean
> > simply 'getenv'?
> > 08:58:06 default: const char* env = std::getenv(
> > "KICAD_TEST_EESCHEMA_DATA_DIR" );
> > 08:58:06     default:   ^~~
> > 08:58:06 default:   getenv
> >
> > Adam Wolf
>
> Should be fixed now.
>
> -S
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] macOS issue upstream

[Adam Wolf]

Hi folks!

If someone is looking for something to do (ha!) some of our macOS builds
are broken right now due to an issue between a recent boost update in
Homebrew and CMake.  It doesn't look like the community is making much
traction, but this may just be me being pessimistic:

https://discourse.brew.sh/t/boost-with-icu-uses-relative-library-paths/4047/2

https://github.com/Homebrew/homebrew-core/issues/36685

https://gitlab.kitware.com/cmake/cmake/issues/19035

If someone wants to take a look and run things down, that would be
awesome.  Let me know.

Adam Wolf
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] macOS issue upstream

[Adam Wolf]

We can probably pin it, but I like to keep at least one build running
unpinned versions of everything so that we can detect issues before our
users complain that nothing builds.

I'll test and make sure we are OK this week.

On Tue, Apr 9, 2019 at 3:06 PM Seth Hillbrand  wrote:

> Am 2019-04-09 14:56, schrieb Adam Wolf:
> > Hi folks!
> >
> > If someone is looking for something to do (ha!) some of our macOS
> > builds are broken right now due to an issue between a recent boost
> > update in Homebrew and CMake.  It doesn't look like the community is
> > making much traction, but this may just be me being pessimistic:
> >
> >
> https://discourse.brew.sh/t/boost-with-icu-uses-relative-library-paths/4047/2
> >
> > https://github.com/Homebrew/homebrew-core/issues/36685
> >
> > https://gitlab.kitware.com/cmake/cmake/issues/19035
> >
> > If someone wants to take a look and run things down, that would be
> > awesome.  Let me know.
> >
> > Adam Wolf
>
> Hi Adam-
>
> Is this needed for 5.1.1 or can we pin the previous brew version(s)?
>
> -S
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] new macos requirements, could use some help

[Adam Wolf]

Hi folks!

Some interesting news... I need to dig into it to figure out what it
means, but lemme know if anyone else wants to learn the ins and out of
Mac packaging.

I am not planning on quitting or anything, but I am at my limit of
time maintaining what we have and working towards Python 3 for v6 for
macOS.  I do not think I will be able to keep up in the near future.

Adam Wolf

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.1 release reminder.

[Adam Wolf]

I'll be working on this as soon as I can, for macOS, but I am a little
worried about being prompt for this release.  I don't want to hold up the
whole release, but I don't want it to be a surprise if I can't get a
package out until the middle or towards the end of this week.

Adam

On Fri, Apr 12, 2019, 3:23 PM Wayne Stambaugh  wrote:

> Just a reminder.  I will be tagging 5.1.1 Sunday afternoon so any last
> minute bug fixes should probably be in by tomorrow so I can do a build
> check and some quick testing to make sure nothing went sideways.  Also,
> please no translatable string changes until we start 5.1.2.  Hopefully
> the library, doc, and translation repos will get tagged on Sunday so we
> can get the back builders fired up.  Thanks again everyone for your
> tireless efforts.
>
> Cheers,
>
> Wayne
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] new macos requirements, could use some help

[Adam Wolf]

Oh, that's what I get for trying to post from my phone...

I forgot the link, and without it, my post seems super ominous!  Sorry
about that!

https://developer.apple.com/news/?id=04102019a

Adam

On Fri, Apr 12, 2019 at 8:25 AM Adam Wolf  wrote:
>
> Hi folks!
>
> Some interesting news... I need to dig into it to figure out what it
> means, but lemme know if anyone else wants to learn the ins and out of
> Mac packaging.
>
> I am not planning on quitting or anything, but I am at my limit of
> time maintaining what we have and working towards Python 3 for v6 for
> macOS.  I do not think I will be able to keep up in the near future.
>
> Adam Wolf

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] new macos requirements, could use some help

[Adam Wolf]

I'm really, really not pleased with the timing of it.  They announced
it 7 days ago, and it will be in effect as soon as 10.14.5 is
released, which is in *second beta* already.

I'm certain they'll have some special place you can say "whitelist
this software" but honestly there are 2 instructions users have to
follow already to install our software already, and we get a bug
report every few weeks from someone who didn't follow one of those.
I'm not excited to add to that list (until we can follow their
process, which may not be bad at all.

Combined with the Homebrew dependency change, this means that I gotta
pick between getting nightlies working again with the homebrew issue,
the next stable out the door, or getting ready for notarization.

(My current working order of priorities is stable release,
notarization, and then nightlies.)

Adam



On Mon, Apr 15, 2019 at 8:13 AM Mark Roszko  wrote:
>
> Yes.
>
> They basically require software submission which then results in a signature 
> when it passes an anti virus check. They aren't so far planning on enforcing 
> arbitrary approval rules like the app store but we'll see.
>
> But it's basically Apple avoiding the install of local antiviruses on 
> machines. That would hurt their marketing and brand image.
>
>
>
>
> On Mon, Apr 15, 2019 at 9:08 AM Tomasz Wlostowski  
> wrote:
>>
>> On 13/04/2019 22:57, Adam Wolf wrote:
>> > Oh, that's what I get for trying to post from my phone...
>> >
>> > I forgot the link, and without it, my post seems super ominous!  Sorry
>> > about that!
>> >
>> > https://developer.apple.com/news/?id=04102019a
>>
>> So does this mean we can't distribute our software anymore without
>> Apple's cryptographical blessing?
>>
>> Tom
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>
>
>
> --
> Mark

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.1 release reminder.

[Adam Wolf]

Are the rest of the parts tagged?  Is the docs tarball ready?

Thanks!

Adam

On Wed, Apr 17, 2019 at 6:34 AM Wayne Stambaugh  wrote:
>
> Nick,
>
> I have the release announcement ready to go but it's on my desktop
> computer at home.  If most of the packages are ready, I will push the
> release announcement this evening after I get home from work.
>
> Cheers,
>
> Wayne
>
>
> On 4/17/2019 7:18 AM, Nick Østergaard wrote:
> > The windows installers are uploading to the stable folder
> >
> > A quick sanity check says they work. Although that in the 32 bit version
> > the python console does not open from the toolbar, but I think that has
> > been an issue for a while. Works ok for 64 bit.
> >
> > And of couse we see the cannot write fp-lib-cache when opening demo
> > projects as usual.
> >
> > @Wayne Stambaugh  do you have a release
> > announcement ready? I don't see a draft pushed.
> >
> > On Mon, 15 Apr 2019 at 21:30, Jean-Samuel Reynaud  > > wrote:
> >
> > Hi all,
> >
> > Most of packages are ready now on PPA. Missing packages are i18n and
> > docs (not tag on the repo).
> >
> > Regards,
> > Le 14/04/2019 à 22:24, Wayne Stambaugh a écrit :
> >  > Hi Jean-Samuel,
> >  >
> >  > Sorry about, I just pushed the tag.
> >  >
> >  > Wayne
> >  >
> >  > On 4/14/19 4:21 PM, Jean-Samuel Reynaud wrote:
> >  >> Dear Wayne,
> >  >>
> >  >> I don't see the tag yet. Did you push it ?
> >  >> Once done I'll launch ppa builds...
> >  >>
> >  >> Regards,
> >  >> Le 14/04/2019 à 22:08, Wayne Stambaugh a écrit :
> >  >>> I just tagged the 5.1 source repo and uploaded the 5.1.1 source
> >  >>> archive[1].  Where do we stand with the doc and translation
> > repos?  As
> >  >>> soon as they are tagged, we can start the package builds.  Once
> > most of
> >  >>> the main packages are built, I will make the release announcement.
> >  >>>
> >  >>> Cheers,
> >  >>>
> >  >>> Wayne
> >  >>>
> >  >>> [1]:
> > https://launchpad.net/kicad/5.0/5.1.1/+download/kicad-5.1.1.tar.xz
> >  >>>
> >  >>> On 4/14/19 2:00 PM, Rene Pöschl wrote:
> >   Hi all,
> >  
> >   I just tagged the library.
> >  
> >   Some small design breaking changes are included in the symbol
> > libs.
> >   (There was a minor miscommunication as some maintainers
> > thought there
> >   will not be another version 5 release. I needed to revert one
> > change
> >   because of that the other 3 where ok in my mind.)
> >  
> >   Everything is detailed in the github issue
> >   https://github.com/KiCad/kicad-symbols/issues/1724
> >  
> >   On 12/04/19 22:23, Wayne Stambaugh wrote:
> >  > Just a reminder.  I will be tagging 5.1.1 Sunday afternoon so
> > any last
> >  > minute bug fixes should probably be in by tomorrow so I can
> > do a build
> >  > check and some quick testing to make sure nothing went
> > sideways.  Also,
> >  > please no translatable string changes until we start 5.1.2.
> > Hopefully
> >  > the library, doc, and translation repos will get tagged on
> > Sunday so we
> >  > can get the back builders fired up.  Thanks again everyone
> > for your
> >  > tireless efforts.
> >  >
> >  > Cheers,
> >  >
> >  > Wayne
> >  >
> >  > ___
> >  > Mailing list: https://launchpad.net/~kicad-developers
> >  > Post to : kicad-developers@lists.launchpad.net
> > 
> >  > Unsubscribe : https://launchpad.net/~kicad-developers
> >  > More help   : https://help.launchpad.net/ListHelp
> >  
> >  
> >  
> >   ___
> >   Mailing list: https://launchpad.net/~kicad-developers
> >   Post to : kicad-developers@lists.launchpad.net
> > 
> >   Unsubscribe : https://launchpad.net/~kicad-developers
> >   More help   : https://help.launchpad.net/ListHelp
> >  >>>
> >  >>> ___
> >  >>> Mailing list: https://launchpad.net/~kicad-developers
> >  >>> Post to : kicad-developers@lists.launchpad.net
> > 
> >  >>> Unsubscribe : https://launchpad.net/~kicad-developers
> >  >>> More help   : https://help.launchpad.net/ListHelp
> >  >>>
> >  >>
> >  >>
> >  >> ___
> >  >> Mailing list: https://launchpad.net/~kicad-developers
> >  >> Post to : kicad-developers@lists.launchpad.net
> > 

Re: [Kicad-developers] 5.1.1 release reminder.

[Adam Wolf]

I am running a set of builds with pinned Boosts that may fix the
problem with mac packaging. Right now, cmake and brew are pointing
fingers at each other and I don't see any upstream progress. :(

It may be a few days.

I apologize for holding up the releases!

Adam

On Fri, Apr 19, 2019 at 10:30 AM Wayne Stambaugh  wrote:
>
> Are we ready to make the release announcement?  I didn't see the macos
> 5.1.1 package but maybe I missed it?  As soon as that's ready, I'll make
> the announcement.
>
> Wayne
>
> On 4/19/2019 11:22 AM, Jean-Samuel Reynaud wrote:
> > Dear All,
> >
> > First sorry for HTML mail...
> >
> > PPA for 5.1.1 is ready since few days. Download stats indicate around
> > 2312 downloads since the beginning of this week.
> > Of course it's only for Ubuntu users... Anyway...
> > Graphic of distribution by date :
> >
> >
> >
> >
> > Le 17/04/2019 à 16:43, Nick Østergaard a écrit :
> >> @adam, yes, all tagged and doc tarball also uploaded
> >>
> >> ons. 17. apr. 2019 15.32 skrev Adam Wolf
> >> mailto:adamw...@feelslikeburning.com>>:
> >>
> >> Are the rest of the parts tagged?  Is the docs tarball ready?
> >>
> >> Thanks!
> >>
> >> Adam
> >>
> >> On Wed, Apr 17, 2019 at 6:34 AM Wayne Stambaugh
> >> mailto:stambau...@gmail.com>> wrote:
> >> >
> >> > Nick,
> >> >
> >> > I have the release announcement ready to go but it's on my desktop
> >> > computer at home.  If most of the packages are ready, I will
> >> push the
> >> > release announcement this evening after I get home from work.
> >> >
> >> > Cheers,
> >> >
> >> > Wayne
> >> >
> >> >
> >> > On 4/17/2019 7:18 AM, Nick Østergaard wrote:
> >> > > The windows installers are uploading to the stable folder
> >> > >
> >> > > A quick sanity check says they work. Although that in the 32
> >> bit version
> >> > > the python console does not open from the toolbar, but I think
> >> that has
> >> > > been an issue for a while. Works ok for 64 bit.
> >> > >
> >> > > And of couse we see the cannot write fp-lib-cache when opening
> >> demo
> >> > > projects as usual.
> >> > >
> >> > > @Wayne Stambaugh <mailto:stambau...@gmail.com
> >> <mailto:stambau...@gmail.com>> do you have a release
> >> > > announcement ready? I don't see a draft pushed.
> >> > >
> >> > > On Mon, 15 Apr 2019 at 21:30, Jean-Samuel Reynaud
> >> mailto:js.reyn...@gmail.com>
> >> > > <mailto:js.reyn...@gmail.com <mailto:js.reyn...@gmail.com>>>
> >> wrote:
> >> > >
> >> > > Hi all,
> >> > >
> >> > > Most of packages are ready now on PPA. Missing packages
> >> are i18n and
> >> > > docs (not tag on the repo).
> >> > >
> >> > > Regards,
> >> > > Le 14/04/2019 à 22:24, Wayne Stambaugh a écrit :
> >> > >  > Hi Jean-Samuel,
> >> > >  >
> >> > >  > Sorry about, I just pushed the tag.
> >> > >  >
> >> > >  > Wayne
> >> > >  >
> >> > >  > On 4/14/19 4:21 PM, Jean-Samuel Reynaud wrote:
> >> > >  >> Dear Wayne,
> >> > >  >>
> >> > >  >> I don't see the tag yet. Did you push it ?
> >> > >  >> Once done I'll launch ppa builds...
> >> > >  >>
> >> > >  >> Regards,
> >> > >  >> Le 14/04/2019 à 22:08, Wayne Stambaugh a écrit :
> >> > >  >>> I just tagged the 5.1 source repo and uploaded the
> >> 5.1.1 source
> >> > >  >>> archive[1].  Where do we stand with the doc and
> >> translation
> >> > > repos?  As
> >> > >  >>> soon as they are tagged, we can start the package
> >> builds.  Once
> >> > > m

Re: [Kicad-developers] 5.1.1 issue

[Adam Wolf]

Hi folks!

I was able to pin Boost to the previous homebrew build and things seem
to build for macOS again.  I generated 5.1.1 packages, and I can even
upload them, but it will be mere single-digit minutes of extra effort
to spin a 5.1.2 once things are tagged again.

I have a 5.0 branch nightly.  I can setup a 5.1 branch as well--or is
5.0 done and should I just switch that over?

Adam


On Sun, Apr 21, 2019 at 5:51 PM Wayne Stambaugh  wrote:
>
> Hey Frank,
>
> On 4/21/19 6:33 PM, Frank Severinsen wrote:
> > a non-dev-lead +1 ;)
>
> LOL!
>
> >
> > As a small side note there is a discussion on the forum to get a V5.1
> > branch "nightly" going.
> > https://forum.kicad.info/t/does-it-make-sense-to-have-development-snapshots-for-the-v5-1-branch-going-forward/15723/37
> > This would hopefully help avoiding bugfix enduced bugs making it to stable.
> > I can imagine alot of people (including myself) who wants to help
> > testing, but can't use nightlies due to the file fomat changes.
>
> I think this is a great idea.  This would give us more testing of the
> current stable release branch between releases.  It most likely would
> have prevented the current situation.
>
> Cheers,
>
> Wayne
>
> >
> >
> >
> > Den 21. april 2019 kl. 23.18.53 +02.00, skrev Wayne Stambaugh
> > :
> >> It's looks like 5.1.1 has a serious issue which was fixed and will be
> >> released in 5.1.2. Since folks have already started downloading 5.1.1,
> >> I don't think changing the 5.1.1 tag is a good idea. How much trouble
> >> would it be to spin 5.1.2 and skip formally releasing 5.1.1? I'm fine
> >> if we use the 5.1.1 libraries, documentation, and translations as
> >> nothing has change since 5.1.1 that would effect anything. I figure
> >> this will give Adam some more time to get the macos release out. I
> >> apologize in advance for dropping the ball on this.
> >>
> >> Cheers,
> >>
> >> Wayne
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> 
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] upload issues to cern s3cmd?

[Adam Wolf]

Hi folks!

Apologies if I should send this to someone else rather than the whole
list, but I have been getting this error for the past few days:

s3cmd put kicad-extras-20190422-020027.dmg
kicad-nightly-20190422-014543-53437fe36.dmg
kicad-unified-20190422-022513-3c0012449.dmg
s3://kicad-downloads/osx/nightly/
ERROR: Error parsing xml: syntax error: line 1, column 0
ERROR: b'Error 400: Bad Request\nClient sent malformed request'


Invoked as: /usr/local/Cellar/s3cmd/2.0.2_1/libexec/bin/s3cmd put
kicad-extras-20190422-020027.dmg
kicad-nightly-20190422-014543-53437fe36.dmg
kicad-unified-20190422-022513-3c0012449.dmg
s3://kicad-downloads/osx/nightly/
Problem: ParseError: syntax error: line 1, column 0
S3cmd:   2.0.2
python:   3.7.2 (default, Jan 13 2019, 12:51:54)
[Clang 9.0.0 (clang-900.0.39.2)]
Traceback (most recent call last):
File "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/bin/s3cmd", line 3092, in 
 rc = main()
   File "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/bin/s3cmd", line 3001, in main
 rc = cmd_func(args)
   File "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/bin/s3cmd", line 421,
in cmd_object_put
 response = s3.object_put(full_name, uri_final, extra_headers,
extra_label = seq_label)
   File 
"/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/S3.py",
line 677, in object_put
 return self.send_file_multipart(src_stream, headers, uri, size,
extra_label)
   File 
"/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/S3.py",
line 1603, in send_file_multipart
 upload.upload_all_parts(extra_label)
   File 
"/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/MultiPart.py",
line 119, in upload_all_parts
 self.upload_part(seq, offset, current_chunk_size, labels,
remote_status = remote_statuses.get(seq))
   File 
"/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/MultiPart.py",
line 176, in upload_part
 response = self.s3.send_file(request, self.file_stream, labels,
buffer, offset = offset, chunk_size = chunk_size)
   File 
"/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/S3.py",
line 1531, in send_file
 self.send_file, request, stream, labels, buffer, offset = offset,
chunk_size = chunk_size, use_expect_continue = use_expect_continue)
   File 
"/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/S3.py",
line 1181, in _http_400_handler
 failureCode = getTextFromXml(response['data'], 'Code')
   File 
"/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/Utils.py",
line 142, in getTextFromXml
 tree = getTreeFromXml(xml)
   File 
"/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/Utils.py",
line 106, in getTreeFromXml
 tree = ET.fromstring(xml)
   File 
"/usr/local/Cellar/python/3.7.2_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/xml/etree/ElementTree.py",
line 1315, in XML
 parser.feed(text)
 xml.etree.ElementTree.ParseError: syntax error: line 1, column 0

I have tried a few times over a few days. It used to work for me.  Any thoughts?

Adam

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] 5.1.0 nightlies?

[Adam Wolf]

Hi folks,

Do we want more nightlies?  Macos already makes master nightlies and 5.0
nightlies.  Do we want 5.1 nightlies?  Is there a better place to put them
rather than in testing? Does nightlies/master nightlies/5.0 and
nightlies/5.1 make more sense for users?

Adam
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] upload issues to cern s3cmd?

[Adam Wolf]

Interesting.  I didn't change anything that I know of on my side...
definitely didn't change anything related to syntax.

I wonder if a brew update broke s3cmd.

I may just upload a few of these nightlies by hand in order to get
people new stuff before KiCon.

Adam

On Mon, Apr 22, 2019 at 8:38 AM Nick Østergaard  wrote:
>
> But it seems like you can also use the aws-cli as follows:
>
> aws s3 cp your.dmg s3://kicad-downloads/osx/nightly/ --endpoint-url 
> https://s3.cern.ch
>
> After you configured the access and secrect key with aws configure.
>
> On Mon, 22 Apr 2019 at 15:30, Nick Østergaard  wrote:
>>
>> I guess s3cmd does not work with python3.
>>
>> Then I took at look at https://s3tools.org/s3cmd and it says that version 2 
>> do work with python3 and it looks like are using verison 2...
>>
>> Does it work if you put just one file?
>>
>> On Mon, 22 Apr 2019 at 15:19, Adam Wolf  
>> wrote:
>>>
>>> Hi folks!
>>>
>>> Apologies if I should send this to someone else rather than the whole
>>> list, but I have been getting this error for the past few days:
>>>
>>> s3cmd put kicad-extras-20190422-020027.dmg
>>> kicad-nightly-20190422-014543-53437fe36.dmg
>>> kicad-unified-20190422-022513-3c0012449.dmg
>>> s3://kicad-downloads/osx/nightly/
>>> ERROR: Error parsing xml: syntax error: line 1, column 0
>>> ERROR: b'Error 400: Bad Request\nClient sent malformed request'
>>>
>>>
>>> Invoked as: /usr/local/Cellar/s3cmd/2.0.2_1/libexec/bin/s3cmd put
>>> kicad-extras-20190422-020027.dmg
>>> kicad-nightly-20190422-014543-53437fe36.dmg
>>> kicad-unified-20190422-022513-3c0012449.dmg
>>> s3://kicad-downloads/osx/nightly/
>>> Problem: ParseError: syntax error: line 1, column 0
>>> S3cmd:   2.0.2
>>> python:   3.7.2 (default, Jan 13 2019, 12:51:54)
>>> [Clang 9.0.0 (clang-900.0.39.2)]
>>> Traceback (most recent call last):
>>> File "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/bin/s3cmd", line 3092, in 
>>> 
>>>  rc = main()
>>>File "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/bin/s3cmd", line 3001, in 
>>> main
>>>  rc = cmd_func(args)
>>>File "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/bin/s3cmd", line 421,
>>> in cmd_object_put
>>>  response = s3.object_put(full_name, uri_final, extra_headers,
>>> extra_label = seq_label)
>>>File 
>>> "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/S3.py",
>>> line 677, in object_put
>>>  return self.send_file_multipart(src_stream, headers, uri, size,
>>> extra_label)
>>>File 
>>> "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/S3.py",
>>> line 1603, in send_file_multipart
>>>  upload.upload_all_parts(extra_label)
>>>File 
>>> "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/MultiPart.py",
>>> line 119, in upload_all_parts
>>>  self.upload_part(seq, offset, current_chunk_size, labels,
>>> remote_status = remote_statuses.get(seq))
>>>File 
>>> "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/MultiPart.py",
>>> line 176, in upload_part
>>>  response = self.s3.send_file(request, self.file_stream, labels,
>>> buffer, offset = offset, chunk_size = chunk_size)
>>>File 
>>> "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/S3.py",
>>> line 1531, in send_file
>>>  self.send_file, request, stream, labels, buffer, offset = offset,
>>> chunk_size = chunk_size, use_expect_continue = use_expect_continue)
>>>File 
>>> "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/S3.py",
>>> line 1181, in _http_400_handler
>>>  failureCode = getTextFromXml(response['data'], 'Code')
>>>File 
>>> "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/Utils.py",
>>> line 142, in getTextFromXml
>>>  tree = getTreeFromXml(xml)
>>>File 
>>> "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/Utils.py",
>>> line 106, in getTreeFromXml
>>>  tree = ET.fromstring(xml)
>>>File 
>>> "/usr/local/Cellar/python/3.7.2_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/xml/etree/ElementTree.py",
>>> line 1315, in XML
>>>  parser.feed(text)
>>>  xml.etree.ElementTree.ParseError: syntax error: line 1, column 0
>>>
>>> I have tried a few times over a few days. It used to work for me.  Any 
>>> thoughts?
>>>
>>> Adam
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : kicad-developers@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.0 nightlies?

[Adam Wolf]

I set them up.  They'll upload to testing/5.1 for now.

Do we want to move the regular nightlies to nightlies/master and put
these in nightlies/5.1?

Adam

On Mon, Apr 22, 2019 at 9:35 AM Wayne Stambaugh  wrote:
>
> Adam,
>
> Nightly 5.1 builds would be really helpful.  We have discussed doing
> this so hopefully we can provide them for most platforms.  Given that
> the 5.0 branch is no longer supported, I cannot think of a reason to
> continue nightly 5.0 builds.  I'm guessing having testing branch folders
> is a good idea given that the master branch tag still shows 5.1.0 which
> can be confusing for users.
>
> Wayne
>
> On 4/22/2019 10:26 AM, Adam Wolf wrote:
> > Hi folks,
> >
> > Do we want more nightlies?  Macos already makes master nightlies and 5.0
> > nightlies.  Do we want 5.1 nightlies?  Is there a better place to put
> > them rather than in testing? Does nightlies/master nightlies/5.0 and
> > nightlies/5.1 make more sense for users?
> >
> > Adam
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.0 nightlies?

[Adam Wolf]

I think the way Nick describes is how macos is, so it's probably fine as it
is.

On Mon, Apr 22, 2019, 4:11 PM Wayne Stambaugh  wrote:

> I think makes sense for macos as well.  Although /master may be a bit
> more descriptive than nightlies.  Regardless of which way we choose to
> do this, it should be consistent across platforms.
>
> On 4/22/19 5:08 PM, Nick Østergaard wrote:
> > Previously I have been running with /testing/ for
> > windows, and /nightlies for master.
> >
> > On Mon, 22 Apr 2019 at 23:05, Adam Wolf  > <mailto:adamw...@feelslikeburning.com>> wrote:
> >
> > I set them up.  They'll upload to testing/5.1 for now.
> >
> > Do we want to move the regular nightlies to nightlies/master and put
> > these in nightlies/5.1?
> >
> > Adam
> >
> > On Mon, Apr 22, 2019 at 9:35 AM Wayne Stambaugh
> > mailto:stambau...@gmail.com>> wrote:
> > >
> > > Adam,
> > >
> > > Nightly 5.1 builds would be really helpful.  We have discussed
> doing
> > > this so hopefully we can provide them for most platforms.  Given
> that
> > > the 5.0 branch is no longer supported, I cannot think of a reason
> to
> > > continue nightly 5.0 builds.  I'm guessing having testing branch
> > folders
> > > is a good idea given that the master branch tag still shows 5.1.0
> > which
> > > can be confusing for users.
> > >
> > > Wayne
> > >
> > > On 4/22/2019 10:26 AM, Adam Wolf wrote:
> > > > Hi folks,
> > > >
> > > > Do we want more nightlies?  Macos already makes master nightlies
> > and 5.0
> > > > nightlies.  Do we want 5.1 nightlies?  Is there a better place
> > to put
> > > > them rather than in testing? Does nightlies/master nightlies/5.0
> and
> > > > nightlies/5.1 make more sense for users?
> > > >
> > > > Adam
> > > >
> > > > ___
> > > > Mailing list: https://launchpad.net/~kicad-developers
> > > > Post to : kicad-developers@lists.launchpad.net
> > <mailto:kicad-developers@lists.launchpad.net>
> > > > Unsubscribe : https://launchpad.net/~kicad-developers
> > > > More help   : https://help.launchpad.net/ListHelp
> > > >
> > >
> > > ___
> > > Mailing list: https://launchpad.net/~kicad-developers
> > > Post to : kicad-developers@lists.launchpad.net
> > <mailto:kicad-developers@lists.launchpad.net>
> > > Unsubscribe : https://launchpad.net/~kicad-developers
> > > More help   : https://help.launchpad.net/ListHelp
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > <mailto:kicad-developers@lists.launchpad.net>
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] recent macos build failures

[Adam Wolf]

I am seeing this again when I am trying to build 5.1.2 for macOSes
older than 10.14.  Does that make any sense?

Adam

On Mon, Apr 8, 2019 at 10:12 PM Adam Wolf  wrote:
>
> Thanks!  Amazing response time!
>
> On Mon, Apr 8, 2019 at 2:34 PM Seth Hillbrand  wrote:
>>
>> Am 2019-04-08 14:57, schrieb Adam Wolf:
>> > Hi folks!
>> >
>> > Anyone having issues like this recently?
>> >
>> > 08:58:06 default:
>> > /vagrant/build/kicad/src/kicad/qa/eeschema/eeschema_test_utils.cpp:28:23:
>> > error: no member named 'getenv' in namespace 'std'; did you mean
>> > simply 'getenv'?
>> > 08:58:06 default: const char* env = std::getenv(
>> > "KICAD_TEST_EESCHEMA_DATA_DIR" );
>> > 08:58:06 default:   ^~~
>> > 08:58:06 default:   getenv
>> >
>> > Adam Wolf
>>
>> Should be fixed now.
>>
>> -S

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] upload issues to cern s3cmd?

[Adam Wolf]

Hi folks!

Interesting observation.  When I send a single file, I get a few
errors and those chunks are retried and things are fine.  When I send
multiple files in one s3cmd, s3cmd appears to die on the first error.
This does not really explain why I'm getting "bad response" errors
relatively often, but it does not appear to be a blocking issue for me
anymore.

I have converted my scripts over.

Adam


On Mon, Apr 22, 2019 at 9:52 AM Adam Wolf  wrote:
>
> Interesting.  I didn't change anything that I know of on my side...
> definitely didn't change anything related to syntax.
>
> I wonder if a brew update broke s3cmd.
>
> I may just upload a few of these nightlies by hand in order to get
> people new stuff before KiCon.
>
> Adam
>
> On Mon, Apr 22, 2019 at 8:38 AM Nick Østergaard  wrote:
> >
> > But it seems like you can also use the aws-cli as follows:
> >
> > aws s3 cp your.dmg s3://kicad-downloads/osx/nightly/ --endpoint-url 
> > https://s3.cern.ch
> >
> > After you configured the access and secrect key with aws configure.
> >
> > On Mon, 22 Apr 2019 at 15:30, Nick Østergaard  wrote:
> >>
> >> I guess s3cmd does not work with python3.
> >>
> >> Then I took at look at https://s3tools.org/s3cmd and it says that version 
> >> 2 do work with python3 and it looks like are using verison 2...
> >>
> >> Does it work if you put just one file?
> >>
> >> On Mon, 22 Apr 2019 at 15:19, Adam Wolf  
> >> wrote:
> >>>
> >>> Hi folks!
> >>>
> >>> Apologies if I should send this to someone else rather than the whole
> >>> list, but I have been getting this error for the past few days:
> >>>
> >>> s3cmd put kicad-extras-20190422-020027.dmg
> >>> kicad-nightly-20190422-014543-53437fe36.dmg
> >>> kicad-unified-20190422-022513-3c0012449.dmg
> >>> s3://kicad-downloads/osx/nightly/
> >>> ERROR: Error parsing xml: syntax error: line 1, column 0
> >>> ERROR: b'Error 400: Bad Request\nClient sent malformed request'
> >>>
> >>>
> >>> Invoked as: /usr/local/Cellar/s3cmd/2.0.2_1/libexec/bin/s3cmd put
> >>> kicad-extras-20190422-020027.dmg
> >>> kicad-nightly-20190422-014543-53437fe36.dmg
> >>> kicad-unified-20190422-022513-3c0012449.dmg
> >>> s3://kicad-downloads/osx/nightly/
> >>> Problem: ParseError: syntax error: line 1, column 0
> >>> S3cmd:   2.0.2
> >>> python:   3.7.2 (default, Jan 13 2019, 12:51:54)
> >>> [Clang 9.0.0 (clang-900.0.39.2)]
> >>> Traceback (most recent call last):
> >>> File "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/bin/s3cmd", line 3092, in 
> >>> 
> >>>  rc = main()
> >>>File "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/bin/s3cmd", line 3001, 
> >>> in main
> >>>  rc = cmd_func(args)
> >>>File "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/bin/s3cmd", line 421,
> >>> in cmd_object_put
> >>>  response = s3.object_put(full_name, uri_final, extra_headers,
> >>> extra_label = seq_label)
> >>>File 
> >>> "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/S3.py",
> >>> line 677, in object_put
> >>>  return self.send_file_multipart(src_stream, headers, uri, size,
> >>> extra_label)
> >>>File 
> >>> "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/S3.py",
> >>> line 1603, in send_file_multipart
> >>>  upload.upload_all_parts(extra_label)
> >>>File 
> >>> "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/MultiPart.py",
> >>> line 119, in upload_all_parts
> >>>  self.upload_part(seq, offset, current_chunk_size, labels,
> >>> remote_status = remote_statuses.get(seq))
> >>>File 
> >>> "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/MultiPart.py",
> >>> line 176, in upload_part
> >>>  response = self.s3.send_file(request, self.file_stream, labels,
> >>> buffer, offset = offset, chunk_size = chunk_size)
> >>>File 
> >>> "/usr/local/Cellar/s3cmd/2.0.2_1/libexec/lib/python3.7/site-packages/S3/S3.py",
> >>> line 1531, in send_file
> >>>  self.send_file, request, stream, labels, buffer, offset = offset,
> >&g

Re: [Kicad-developers] recent macos build failures

[Adam Wolf]

I already have a way to handle this, actually, and will release 5.1.2-1.

This is already handled in my scripts because of a messup of mine from the
V4 days.

If I keep messing up eventually our system will handle everything :p

Adam

On Wed, Apr 24, 2019, 9:17 AM Wayne Stambaugh  wrote:

> I guess this means that on macos we will have to package
> 5.1.2-2-gb6c9d4a8 as stable instead of 5.1.2 for older versions of
> macos.  Sigh!
>
> Cheers,
>
> Wayne
>
> On 4/24/2019 9:34 AM, John Beard wrote:
> > Hi Adam,
> >
> > The fix was only made on master. I have pushed it to 5.1 as commit
> > b6c9d4a88c279c4269cb22995765640de294a16e
> >
> > Cheers,
> >
> > John
> >
> > On Wed, Apr 24, 2019 at 2:24 PM Adam Wolf 
> wrote:
> >>
> >> I am seeing this again when I am trying to build 5.1.2 for macOSes
> >> older than 10.14.  Does that make any sense?
> >>
> >> Adam
> >>
> >> On Mon, Apr 8, 2019 at 10:12 PM Adam Wolf <
> adamw...@feelslikeburning.com> wrote:
> >>>
> >>> Thanks!  Amazing response time!
> >>>
> >>> On Mon, Apr 8, 2019 at 2:34 PM Seth Hillbrand 
> wrote:
> >>>>
> >>>> Am 2019-04-08 14:57, schrieb Adam Wolf:
> >>>>> Hi folks!
> >>>>>
> >>>>> Anyone having issues like this recently?
> >>>>>
> >>>>> 08:58:06 default:
> >>>>>
> /vagrant/build/kicad/src/kicad/qa/eeschema/eeschema_test_utils.cpp:28:23:
> >>>>> error: no member named 'getenv' in namespace 'std'; did you mean
> >>>>> simply 'getenv'?
> >>>>> 08:58:06 default: const char* env = std::getenv(
> >>>>> "KICAD_TEST_EESCHEMA_DATA_DIR" );
> >>>>> 08:58:06 default:   ^~~
> >>>>> 08:58:06 default:   getenv
> >>>>>
> >>>>> Adam Wolf
> >>>>
> >>>> Should be fixed now.
> >>>>
> >>>> -S
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] CI builds

[Adam Wolf]

I will set up a new view for the macbuilder that should be all green, and I
can also set it up to push build failures to a list.

Does it make sense to have all the builders email a new list that
committers and packages can watch?

Adam

On Wed, Apr 24, 2019, 11:38 AM John Beard  wrote:

> On Wed, Apr 24, 2019 at 4:51 PM Steven A. Falco 
> wrote:
> >
> > It is not quite a CI builder, but there is also the Fedora nightly that
> happens on Copr:
> > https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/
>
> That's useful to know, thanks
>
> > I see some failures there on kicad2step.  Here is a representative
> sample from the Rawhide build:
>
> Should be fixed now (static vs shared libs). Issue only exists on master.
>
> Cheers,
>
> John
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] CI builds

[Adam Wolf]

I do not have a job like that for macOS at this point, so things like
"brew broke an upstream thing" would also show up.

These are not super common, but I could also put a special word in all
of the build emails so people can easily filter them out.

Or, I can wait on doing anything and create a job that just builds.

Adam

On Wed, Apr 24, 2019 at 12:48 PM Wayne Stambaugh  wrote:
>
> I wouldn't have an issue with forwarding build errors to the dev mailing
> list as long as the build failure messages were limited to compile/link
> errors due to broken source repo commits.  I don't think it's necessary
> for devs to see all of the other unrelated build issues.  I don't know
> if it would be possible to segregate out the compile/link errors.  I
> don't know that a separate mailing list is warranted.  I'm already on
> too many mailing lists ;)
>
> Wayne
>
> On 4/24/2019 1:07 PM, Adam Wolf wrote:
> > I will set up a new view for the macbuilder that should be all green,
> > and I can also set it up to push build failures to a list.
> >
> > Does it make sense to have all the builders email a new list that
> > committers and packages can watch?
> >
> > Adam
> >
> > On Wed, Apr 24, 2019, 11:38 AM John Beard  > <mailto:john.j.be...@gmail.com>> wrote:
> >
> > On Wed, Apr 24, 2019 at 4:51 PM Steven A. Falco
> > mailto:stevenfa...@gmail.com>> wrote:
> >  >
> >  > It is not quite a CI builder, but there is also the Fedora
> > nightly that happens on Copr:
> >  > https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/
> >
> > That's useful to know, thanks
> >
> >  > I see some failures there on kicad2step.  Here is a
> > representative sample from the Rawhide build:
> >
> > Should be fixed now (static vs shared libs). Issue only exists on
> > master.
> >
> > Cheers,
> >
> > John
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > <mailto:kicad-developers@lists.launchpad.net>
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.2 release announcement initial draft

[Adam Wolf]

MacOS builds are cranking away.  I really want to get them up tonight or at
least before I leave tomorrow at 2 CST.

Adam

On Wed, Apr 24, 2019, 5:04 PM Wayne Stambaugh  wrote:

> I just pushed the 5.1.2 release announcement initial draft to the
> website repo.  As soon as we have macos builds ready, I will remove the
> draft tag unless there is something else holding up the release.  Please
> let me know.
>
> Cheers,
>
> Wayne
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.2 release announcement initial draft

[Adam Wolf]

5.1.2-1 for macOS is uploading on the slow Airbnb wifi.  It may be a
few hours yet, but it should be up soon!

Adam

On Wed, Apr 24, 2019 at 11:24 PM Wayne Stambaugh  wrote:
>
> I believe they are in testing and ready to go.
>
> On 4/24/19 6:21 PM, Andrew Lutsenko wrote:
> > Windows 5.1.2 builds are still not available in stable folder
> > https://kicad-downloads.s3.cern.ch/index.html?prefix=windows/stable/
> >
> > On Wed, Apr 24, 2019 at 3:04 PM Wayne Stambaugh  > > wrote:
> >
> > I just pushed the 5.1.2 release announcement initial draft to the
> > website repo.  As soon as we have macos builds ready, I will remove the
> > draft tag unless there is something else holding up the release.  Please
> > let me know.
> >
> > Cheers,
> >
> > Wayne
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > 
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] macOS build errors, swig?

[Adam Wolf]

Hi folks!

I'm seeing broken builds, reporting

06:14:03 default: Error: the swig import helper was not fixed, check
/vagrant/build/kicad/src/kicad-build/pcbnew/pcbnew.py

06:14:03 default:and fix this script: fix_swig_imports.py
06:14:03 default: make[6]: *** [pcbnew/pcbnew_wrap.cxx] Error 2

across the board on my macOS builds, both 10.11 and 10.14.

This appears to be new since 9741b43da.

Adam

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] ERC / DRC user survey

[Adam Wolf]

Do you mind if we share this to other KiCad users?

Adam

On Thu, May 2, 2019 at 11:55 AM Jon Evans  wrote:
>
> Hi all,
>
> The development team would like feedback from users on the ERC and DRC 
> functionality of KiCad.  We'd like to know what KiCad gets right, and what 
> features are missing that you need.
>
> The data from this anonymous survey will help us prioritize development 
> efforts related to ERC and DRC.  While we make no promises about whether or 
> when any particular feature will be implemented, we will make our best effort 
> to include user feedback in our specifications for the ERC and DRC upgrades 
> that are planned for KiCad 6.0
>
> Here's the survey link:
> https://forms.gle/RgrSwvgfGZGr2zJH9
>
> Thanks for your help,
> Jon
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 6.0 string proposal

[Adam Wolf]

Yes, we build wxwidgets ourselves!  Let me know what settings I should
set, and we can get test builds out shortly!

https://github.com/KiCad/kicad-mac-builder/blob/master/kicad-mac-builder/wxpython.cmake

Adam

On Fri, May 3, 2019 at 11:52 AM Wayne Stambaugh  wrote:
>
> It seems like this is macos specific.  Don't we have our own custom
> wxwidgets builds for macos?  Maybe we should change the build flags.
>
> On 5/3/2019 12:34 PM, Jeff Young wrote:
> > This is the only bug I could find in the database: 
> > https://bugs.launchpad.net/kicad/+bug/1822678.  Note that the Michaels 
> > (both Geselbracht and Kavanagh) are on OSX.
> >
> > There’s also the two I fixed (neither of which was logged as I couldn’t 
> > figure out how to reproduce them).  Once again, OSX.
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] macOS build errors, swig?

[Adam Wolf]

Hi folks!

I'm still not able to get anything to build on macOS, either 10.14 or
10.11.  I keep getting:

Error: the swig import helper was not fixed, check
/vagrant/build/kicad/src/kicad-build/pcbnew/pcbnew.py
and fix this script: fix_swig_imports.py

Does anyone know anything more about this?  Is anyone else able to
make a Mac build?

Adam

On Wed, May 1, 2019 at 9:36 AM Adam Wolf  wrote:
>
> Hi folks!
>
> I'm seeing broken builds, reporting
>
> 06:14:03 default: Error: the swig import helper was not fixed, check
> /vagrant/build/kicad/src/kicad-build/pcbnew/pcbnew.py
>
> 06:14:03 default:and fix this script: fix_swig_imports.py
> 06:14:03 default: make[6]: *** [pcbnew/pcbnew_wrap.cxx] Error 2
>
> across the board on my macOS builds, both 10.11 and 10.14.
>
> This appears to be new since 9741b43da.
>
> Adam

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] macOS build errors, swig?

[Adam Wolf]

Sorry for the noise.

It appears that we need to adjust that script for when new versions of
swig come out.  Homebrew recently updated to swig 4.0.0.  I will see
if I can version pin swig for the moment and come up with the patch to
get swig 4.0.0 working.

Adam

On Mon, May 6, 2019 at 12:25 PM Adam Wolf  wrote:
>
> Hi folks!
>
> I'm still not able to get anything to build on macOS, either 10.14 or
> 10.11.  I keep getting:
>
> Error: the swig import helper was not fixed, check
> /vagrant/build/kicad/src/kicad-build/pcbnew/pcbnew.py
> and fix this script: fix_swig_imports.py
>
> Does anyone know anything more about this?  Is anyone else able to
> make a Mac build?
>
> Adam
>
> On Wed, May 1, 2019 at 9:36 AM Adam Wolf  
> wrote:
> >
> > Hi folks!
> >
> > I'm seeing broken builds, reporting
> >
> > 06:14:03 default: Error: the swig import helper was not fixed, check
> > /vagrant/build/kicad/src/kicad-build/pcbnew/pcbnew.py
> >
> > 06:14:03 default:and fix this script: fix_swig_imports.py
> > 06:14:03 default: make[6]: *** [pcbnew/pcbnew_wrap.cxx] Error 2
> >
> > across the board on my macOS builds, both 10.11 and 10.14.
> >
> > This appears to be new since 9741b43da.
> >
> > Adam

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] IMPORTANT build change for OSX users

[Adam Wolf]

Thanks!  This is on my short list.  I hope early next week unless someone
makes a PR to kicad-mac-builder :)

Adam

On Wed, May 8, 2019, 4:03 PM Jeff Young  wrote:

> I’ve added a check in the headers that will *fail* a compile if
> wxUSE_UNICODE_UTF8 is set.  This will allow us to remove a bunch of our
> mutex hacks.  (It turns out that it’s only on for OSX; the other platforms
> *already* have it off.)
>
> You’ll need to do 3 things in your wxWidgets tree:
>
> 1) git fetch (your origin should be set to g...@github.com
> :KiCad/wxWidgets.git and you should be on branch kicad/macos-wx-3.0)
> 2) run your configure command *without* the --enable-UTF8 option [1]
> 3) make install (in wxWidgets/build)
>
> (You’ll probably need to do a clean and a re-build of Kicad after this.)
>
> Cheers,
> Jeff.
>
> [1] This is the configure I used:
>
> ../configure \
> --prefix=`pwd`/../wx-bin \
> --with-opengl \
> --enable-aui \
> --enable-html \
> --enable-stl \
> --enable-debug \
> --enable-debug-gdb \
> --with-libjpeg=builtin \
> --with-libpng=builtin \
> --with-regex=builtin \
> --with-libtiff=builtin \
> --with-zlib=builtin \
> --with-expat=builtin \
> --without-liblzma \
> --with-macosx-version-min=10.13 \
> --enable-universal-binary=x86_64 \
> CC=clang \
> CXX=clang++
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Release Checklist

[Adam Wolf]

Great idea! I have a lightweight test procedure for macOS packaging of
major releases here,  under Test Procedure:
https://github.com/KiCad/kicad-mac-builder/blob/master/README.md


On Sat, May 25, 2019 at 11:27 AM Seth Hillbrand  wrote:
>
> Hi Devs-
>
> I've committed a proposed checklist format to my branch[1] on launchpad.
>   This is the outline of a proposed checklist for KiCad releases that we
> can use to verify consistent (i.e. fewer regressions) behavior before
> tagging new versions.  This currently documents just the main window.
> If people like the idea, I'll work on expanding the list to cover the
> full suite.
>
> The proposed release workflow would then look like:
> 1) Wayne tags an RC and copies the current template into a new file
> called release_checklist_v#.#RC#
> 2) Everyone begins testing the items on the list, marking them as
> working or reporting/fixing bugs
>a. All tests happen against the tag.  If a test fails, it can be
> marked **fixed** after a fix is committed
> 3) Once all tests are marked either **complete** or **fixed**, and no
> new issues arise, we start again with a fresh RC
> 4) Once an RC has all tests marked **complete** instead of **fixed**, we
> are ready for release.
>
> Let me know if people have suggestions for how this process might be
> improved/modified.
>
> Best-
> Seth
>
>
> [1]
> https://git.launchpad.net/~sethh/kicad/commit/?id=8c2d0b6957d4b1da47741947850a959602564ba4&context=3&ignorews=0&ss=1
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Wrong dependencies in build

[Adam Wolf]

Thanks for chasing this down.  It couldn't have been easy.

On Thu, May 30, 2019 at 3:38 PM Simon Richter  wrote:
>
> Hi,
>
> we have some intermittent build failures that I've tried to debug today. As
> parallelism is involved, I now want to set everything on fire.
>
> Symptom: if we have enough CPUs, the lexer generation is started multiple
> times in parallel for the same outputs. The first platform where we saw
> this was MSVC, but I can also get it on Linux, although the timing is a bit
> tighter there. As a result, the generated header file is broken in various
> ways -- on MSVC, every second token in the enumeration swaps place with its
> comma, on Linux we get two copies of the file interleaved.
>
> According to the fine folks on the #cmake IRC channel, what we're doing
> since b7f890adb "Fix parallel build bugs." is illegal, because output files
> from a custom command are consumed by two different projects -- i.e. rather
> than the intention that the files are built in the custom target, now the
> custom target causes another avenue where a parallel build needs to prepare
> the files.
>
> I have no immediate idea how to write this so it is safe for any number of
> CPUs and portable everywhere, so if anyone does, it'd be nice if they'd fix
> it, because I probably won't get around to it for a while.
>
>Simon
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] macOS updates

[Adam Wolf]

Hi folks,

I am still digesting a lot of the macOS news from today, but have no
fear about Python!  Lots of folks are freaking out online about future
versions of macOS not coming with Python or Ruby or other
interpreters, but Apple told us this years ago, and that's why we
package Python and bundle it into KiCad.app. (It was a huge pain and
took like 6 months, but I feel pretty smug about doing it now :) )

I have to I gotta get back to getting Python 3 working!

Adam

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] New package for macOS 5.1.2 stable including ngspice-30 ?

[Adam Wolf]

How about making 5.1.2-1 or -2 or whatever.  I don't like replacing
packages that have been released.

I just updated the package so nightlies tonight should be from the
upstream ngspice-30-2 tag. If they build, and if someone can commit to
trying it out, I can regenerate 5.1.2-x this week!

Thanks folks!

Adam

On Sun, Jun 9, 2019 at 11:28 AM Carsten Schoenert
 wrote:
>
> Hi
>
> Am 09.06.19 um 09:03 schrieb Holger Vogt:
> > Hi Adam,
> >
> > would you mind creating a new package for macOS 5.1.2 stable replacing
> > the outdated libngspice 26 by the recent libngspice version 30?
> >
> > And then use libngspice 30 also for the nightlies?
> >
> > Nick has done this successfully for Windows. All tests have been o.k..
> >
> > The users may benefit from the ngspice patches since version 26 (see
> > https://bugs.launchpad.net/kicad/+bug/1821520) towards better usage
> > during pcb design.
>
> it should be possible to check the version of the ngspice library while
> the cmake configure run and error out if the version is lower than 30.
> I'm not an CMake expert but some version check should be possible here too.
>
> --
> Regards
> Carsten Schoenert
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Set KiCad version in MacOS apps

[Adam Wolf]

I will review today.

Thanks for your help, Seppe!

On Tue, Jun 11, 2019, 10:11 AM Wayne Stambaugh  wrote:

> Seppe,
>
> Your patch looks good to me.  Any MacOS devs care to comment?
>
> Cheers,
>
> Wayne
>
> On 6/11/19 10:46 AM, Seppe Stas wrote:
> > Hey Wayne
> >
> > I attached my patch (generated with `git format-patch --attach
> > origin/master`) to my last email as
> > per http://www.kicad-pcb.org/contribute/developers/#_submitting_patches.
> > I have a feeling Gmail might not like the mail headers in the patch.
> >
> > I created a new patch without the --attach option and added it to this
> > email (I am more used to this patch format and I believe it worked in
> > the past).
> >
> > Greetings
> > Seppe
> >
> > On Tue, Jun 11, 2019 at 4:27 PM Wayne Stambaugh  > > wrote:
> >
> > Seppe,
> >
> > I don't understand why your emails keep ending up on the moderated
> list
> > but something strange is going on.  I had to moderate this one as
> well.
> >  Please attach your patch (created using `git format-patch`) so it
> can
> > be reviewed and commented on.
> >
> > Cheers,
> >
> > Wayne
> >
> > On 6/11/19 10:17 AM, Seppe Stas wrote:
> > > Hey
> > >
> > > I closed the merge request on Launchpad and re-attached the patch
> and
> > > before and after screenshots (the after being built from a dirty
> > master
> > > branch) to this mail:
> > >
> > > Before:
> > > [image: Screenshot 2019-06-05 at 22.46.43.png]
> > > After:
> > > [image: Screenshot 2019-06-05 at 22.46.54.png]
> > >
> > > As you can see, having this version information displayed in
> Spotlight
> > > makes choosing the correct KiCad version a lot easier. It works
> > for the
> > > other apps (EEschema, PCBNew, ...) as well.
> > >
> > > Greetings
> > > Seppe
> > >
> > > On Tue, Jun 11, 2019 at 2:50 PM Seth Hillbrand  > > wrote:
> > >
> > >> Hi Seppe-
> > >>
> > >> I see this e-mail.  Perhaps it was a launchpad hiccup.
> > >>
> > >> I've added Adam to the code review at [1].  Would you mind
> re-sending
> > >> the images to the list?
> > >>
> > >> Thanks-
> > >> Seth
> > >>
> > >> [1]
> > https://code.launchpad.net/~seppestas/kicad/+git/kicad/+merge/368644
> > >>
> > >> On 2019-06-11 05:23, Seppe Stas wrote:
> > >>> Hey
> > >>>
> > >>> I'm not sure if this email got ignored or if it got rejected by
> some
> > >>> mailing system, but it does not seem to show up in the mailing
> list
> > >>> archive
> > >>> .
> > >>>
> > >>> Maybe now it works?
> > >>>
> > >>> Seppe
> > >>>
> > >>> On Wed, Jun 5, 2019 at 10:55 PM Seppe Stas  > > wrote:
> > >>>
> >  Hey guys and girls (probably mostly Adam in particular)
> > 
> >  Attached is a patch that sets the version in all MacOS apps to
> the
> >  value
> >  of KICAD_VERSION, i.e the value of git describe. See commit
> message
> >  for
> >  more technical details. This version show up when e.g launching
> the
> >  app
> >  using spotlight, and during the migration period from KiCad 4
> > to KiCad
> >  5
> >  (that is still going on) I really miss(ed) this feature, since
> > I have
> >  3
> >  different versions of KiCad on my system (4, 5 and master).
> > 
> >  See attached screenshots:
> >  [image: Screenshot 2019-06-05 at 22.46.54.png]
> >  [image: Screenshot 2019-06-05 at 22.46.43.png]
> > 
> >  I tested this patch on both the latest master (6f8a0a4ee) and
> > the 5.1
> >  branch (cd6da987c). I hope you consider adding it to a KiCad 5
> > release
> >  so I
> >  can use it when KiCad 6 comes out. (I hope I finished migrating
> to
> >  KiCad 5
> >  by then).
> > 
> >  Note that in order to update this value, CMake has to be
> > re-run, but I
> >  would not expect this to be a big problem since I assume the
> > releases
> >  are
> >  always built from scratch.
> > 
> >  Greeting
> >  Seppe Stas
> > 
> > >>>
> > >>> ___
> > >>> Mailing list: https://launchpad.net/~kicad-developers
> > >>> Post to : kicad-developers@lists.launchpad.net
> > 
> > >>> Unsubscribe : https://launchpad.net/~kicad-developers
> > >>> More help   : https://help.launchpad.net/ListHelp
> > >>
> > >
> > >
> > > ___
> > > Mailing list: https://launchpad.net/~kicad-developers
> > > Post to : kicad-developer

Re: [Kicad-developers] [PATCH] Set KiCad version in MacOS apps

[Adam Wolf]

I did not test it, but reading over it, it looks great.  Thanks!

Adam

On Tue, Jun 11, 2019 at 1:41 PM Adam Wolf  wrote:
>
> I will review today.
>
> Thanks for your help, Seppe!
>
> On Tue, Jun 11, 2019, 10:11 AM Wayne Stambaugh  wrote:
>>
>> Seppe,
>>
>> Your patch looks good to me.  Any MacOS devs care to comment?
>>
>> Cheers,
>>
>> Wayne
>>
>> On 6/11/19 10:46 AM, Seppe Stas wrote:
>> > Hey Wayne
>> >
>> > I attached my patch (generated with `git format-patch --attach
>> > origin/master`) to my last email as
>> > per http://www.kicad-pcb.org/contribute/developers/#_submitting_patches.
>> > I have a feeling Gmail might not like the mail headers in the patch.
>> >
>> > I created a new patch without the --attach option and added it to this
>> > email (I am more used to this patch format and I believe it worked in
>> > the past).
>> >
>> > Greetings
>> > Seppe
>> >
>> > On Tue, Jun 11, 2019 at 4:27 PM Wayne Stambaugh > > <mailto:stambau...@gmail.com>> wrote:
>> >
>> > Seppe,
>> >
>> > I don't understand why your emails keep ending up on the moderated list
>> > but something strange is going on.  I had to moderate this one as well.
>> >  Please attach your patch (created using `git format-patch`) so it can
>> > be reviewed and commented on.
>> >
>> > Cheers,
>> >
>> > Wayne
>> >
>> > On 6/11/19 10:17 AM, Seppe Stas wrote:
>> > > Hey
>> > >
>> > > I closed the merge request on Launchpad and re-attached the patch and
>> > > before and after screenshots (the after being built from a dirty
>> > master
>> > > branch) to this mail:
>> > >
>> > > Before:
>> > > [image: Screenshot 2019-06-05 at 22.46.43.png]
>> > > After:
>> > > [image: Screenshot 2019-06-05 at 22.46.54.png]
>> > >
>> > > As you can see, having this version information displayed in 
>> > Spotlight
>> > > makes choosing the correct KiCad version a lot easier. It works
>> > for the
>> > > other apps (EEschema, PCBNew, ...) as well.
>> > >
>> > > Greetings
>> > > Seppe
>> > >
>> > > On Tue, Jun 11, 2019 at 2:50 PM Seth Hillbrand > > <mailto:s...@hillbrand.org>> wrote:
>> > >
>> > >> Hi Seppe-
>> > >>
>> > >> I see this e-mail.  Perhaps it was a launchpad hiccup.
>> > >>
>> > >> I've added Adam to the code review at [1].  Would you mind 
>> > re-sending
>> > >> the images to the list?
>> > >>
>> > >> Thanks-
>> > >> Seth
>> > >>
>> > >> [1]
>> > https://code.launchpad.net/~seppestas/kicad/+git/kicad/+merge/368644
>> > >>
>> > >> On 2019-06-11 05:23, Seppe Stas wrote:
>> > >>> Hey
>> > >>>
>> > >>> I'm not sure if this email got ignored or if it got rejected by 
>> > some
>> > >>> mailing system, but it does not seem to show up in the mailing list
>> > >>> archive
>> > >>> <https://lists.launchpad.net/kicad-developers/date.html>.
>> > >>>
>> > >>> Maybe now it works?
>> > >>>
>> > >>> Seppe
>> > >>>
>> > >>> On Wed, Jun 5, 2019 at 10:55 PM Seppe Stas > > <mailto:seppes...@gmail.com>> wrote:
>> > >>>
>> > >>>> Hey guys and girls (probably mostly Adam in particular)
>> > >>>>
>> > >>>> Attached is a patch that sets the version in all MacOS apps to the
>> > >>>> value
>> > >>>> of KICAD_VERSION, i.e the value of git describe. See commit 
>> > message
>> > >>>> for
>> > >>>> more technical details. This version show up when e.g launching 
>> > the
>> > >>>> app
>> > >>>> using spotlight, and during the migration period from KiCad 4
>> > to KiCad
>> >  

[Kicad-developers] running multiple versions of KiCad on macOS

[Adam Wolf]

Seeing Seppe's patch made me think of something I tried to do last
time, but ended up running out of time.

What do folks think about changing the data directory for macOS to
have the major version, to make it a little easier to run KiCad 5 and
6 on the same computer?  Am I opening a can of worms?

Adam Wolf

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] running multiple versions of KiCad on macOS

[Adam Wolf]

Environment variables are tricky for users to set for graphical apps
in macOS, unfortunately.

I wonder if we can think through this and find something that is
unequivocably better than what we have today without requiring us to
invent a bunch of new things.

I know I get scared every release that someone has set themselves up
with an impossible-to-reproduce environment--I always test and
emphasize the "backup everything kicaddy" scripts then.

Adam

On Wed, Jun 12, 2019 at 7:12 PM Seppe Stas  wrote:
>
> Andy, I don’t think Adam is talking about the library folders, those can 
> already be easily set using environmental arguments.
>
> On that note though, being able to have those environmental variables be 
> updated depending on the KiCad version would also be a nice to have, since 
> for some reason KiCad does not seem to pick up on env vars set by launchctl 
> on MacOS, making easy switching only available when launching KiCAD from the 
> command line (which also seems to come with a bunch of bugs seemingly related 
> to OpenGL).
>
> Right now I have some custom scripts that set up the correct env vars and 
> symlinks the library table files, it works okish.
>
> I also noted KiCad 4 currently complains on launh because it doesn’t 
> understand some settings set by KiCAD 5. Everything still works fine though.
>
> Seppe
>
> On Thu, 13 Jun 2019 at 00:20, Andy Peters  wrote:
>>
>>
>> > On Jun 12, 2019, at 2:38 PM, Adam Wolf  
>> > wrote:
>> >
>> > Seeing Seppe's patch made me think of something I tried to do last
>> > time, but ended up running out of time.
>> >
>> > What do folks think about changing the data directory for macOS to
>> > have the major version, to make it a little easier to run KiCad 5 and
>> > 6 on the same computer?  Am I opening a can of worms?
>>
>> “data directory” as in where the libraries etc are stored?
>>
>> Currently in ~/Library/Application Support/kicad or /Library/Application 
>> Support/kicad ??
>>
>> Possibly changed to ~/Library/Application Support/kicad 5/ and 
>> ~/Library/Application Support/kicad 6/ for example?
>>
>> I don’t have a problem with it, but the question is how to manage it. Assume 
>> that everyone who already has Kicad installed is using the “default” 
>> location. When the user upgrades to a new major version, perhaps on first 
>> run it should ask about the library locations.
>>
>> But there’s a complication … do those locations exist?
>>
>> As part of that first run, should the new version offer to upgrade existing 
>> libraries and store them in the new location?
>>
>> (And what does that do to users who keep libraries in source-code control 
>> and the libraries on the computers live in working copies?)
>>
>> I mean, I agree that if the intent is to be able to run Kicad 5 and Kicad 6 
>> on the same machine and those versions have incompatible libraries then yes, 
>> we need to be able to tell those two installs where their libraries live.
>>
>> Of course, if Kicad 6 can use Kicad 5’s libraries as is, then there is no 
>> need for the distinction.
>>
>> Yes, can of worms indeed.
>>
>> -a
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] KiCad keycaps (KiCaps?)

[Adam Wolf]

I wonder if there are any places that'll do a Macbook Pro keycover
oneoff, like https://www.decalgirl.com/make/app/?t=1606 or something?

On Fri, Jun 28, 2019 at 8:35 AM Bob Gustafson  wrote:
>
> Cool !
>
> On 6/28/19 3:50 AM, metacollin wrote:
>
> Recently, I discovered that there are a number of places online that will 
> make custom keycap sets relatively inexpensively, so I made a custom keycap 
> layout using KiCad's iconography (amongst other things).  Nothing fancy, some 
> macOS specific keys, but I thought a few people might want to see this :).  
> I've attached the layout template in .ai and .svg formats as well in case 
> anyone wants to make their own version/adapt to a different layout/whatever.
>
> Of course, we all have shortcuts burned into our muscle memory already, but 
> don't let that stop you ;)
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Bug 1833851 - Massively Parallel Builds

[Adam Wolf]

For what it's worth, I have already essentially made python an unofficial
packaging requirement on macos.

Adam

On Sun, Jun 30, 2019, 9:45 AM Seth Hillbrand  wrote:

> Hi Devs-
>
> I'm stuck at a decision on this bug and would like some opinions from
> others.
>
> The background is the GNU make is not intelligent about parallel builds
> and doesn't merge generated targets.  So we need to serialize the
> dependencies but this breaks everytime we include the lexer header file
> in a different object or use the generated DSO for more than one target.
>   Eventually, we have sufficient parallel processes that the header gets
> generated twice.  If this happens at the same time, the build breaks.
>
> The two (ok, three) options I see are as follows:
>
> 1) Build the header file into a target directory instead of the source
> directory.  Then everyone gets to build their own with no conflict.  We
> end up building lots and lots of header/lexer files.  Developers won't
> see the files in the usual location.
>
> 2) We build the files like bitmap pngs.  That is, they are re-built by a
> different CMAKE flag and their header/cpp files are checked into the
> repository.  When we add tags to the parser, we need to explicitly
> regenerate the lexer files and check them in.
>
> 3) External scripting.  We could utilize an external python script to
> force one build at a time using lockfiles.  This would add python as a
> build dependency.  We could alternatively use flock in a shell script
> but I'm not sure that exists on all platforms.
>
> Does anyone have preference for which option we take?
>
> -Seth
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] New package for macOS 5.1.2 stable including ngspice-30 ?

[Adam Wolf]

I do not personally use ngspice.  I have filed an issue if someone has a
quick one to add.

https://github.com/KiCad/kicad-mac-builder/issues/90

Adam

On Mon, Jul 1, 2019, 9:43 PM Nick Østergaard  wrote:

> Good news, it seems like we managed to make the kicad-mac-packaging
> scripts happy.
>
> After upgrading to ngspice 30 we had to update the include path for
> some unknown reason. But it seems like it should work now. The first
> build has been pushed to the nightly download location. It is not been
> repackaged for stable. I guess Adam will handle that if we don't
> release a 5.1.3 before.
>
> But I don't think it is ready for primetime yet, first user of the build
> says:
>
> <{HD}> haha so hitting the play button crashed all of kicad
> <{HD}> yep, just tried again. The whole thing crashes.
> <{HD}> This is fun and all but I am going out for dinner. I will be
> back in a few hours.
>
> So if anyone else on mac could try it out? Maybe you Jeff can try it out?
> I think he tested the unified version:
>
> https://kicad-downloads.s3.cern.ch/osx/nightly/kicad-unified-20190701-113048-53e18489e-10_14.dmg
>
> Cheers.
>
> On Fri, 21 Jun 2019 at 11:16, Nick Østergaard  wrote:
> >
> > I see no reason to make ngspice 30 a strict minimum requirement.
> >
> > Lets just help packagers update to the latest ngspice and we are good.
> >
> > tor. 13. jun. 2019 18.33 skrev Wayne Stambaugh :
> >>
> >> On 6/10/19 4:01 PM, Carsten Schoenert wrote:
> >> > Hello Wayne,
> >> >
> >> > Am 10.06.19 um 20:15 schrieb Wayne Stambaugh:
> >> >> We cannot make ngspice 30 the minimum version.  There are far too
> many
> >> >> linux distros where 30 is not available yet.  Please keep in mind,
> >> >> Debian stable and the latest Ubuntu LTS version are the benchmarks
> for
> >> >> dependency package versions.  I'm fine with packaging macos and
> windows
> >> >> with 30.
> >> >
> >> > current Debian stable (Stretch) has KiCad version 4.0.5+dfsg1-4 in the
> >> > archive and no package libngspice0 at all (not even in non-free) so
> >> > there is nothing to take care on here.
> >> >
> >> > The current Ubuntu LTS release 18.04 (Bionic Beaver) has KiCad version
> >> > 4.0.7+dfsg1-1ubuntu2 and libngspice0 version 27-1.
> >> > At least the KiCad version is long long outdated. So also not really
> >> > relevant too.
> >> >
> >> > But all relevant current Debian releases are providing a recent KiCad
> >> > version and also libngspice0 in version 30.2-1 (from unstable to
> >> > stretch-backports). This is also available in all Downstream of Debian
> >> > means also in Ubuntu >= 'Cosmic Cuttlefish' are providing KiCad
> >> > 5.0.0+dfsg1-2, but also libngspice0 in version 27. Updates wont
> happen.
> >> >
> >> > But Jean-Samuel Reynaud is providing actual versions of KiCad and also
> >> > the depending libngspice0 package and they even work in the always
> >> > outdated Linux Mint distro. So for me your requirements you like to
> set
> >> > are fulfilled.
> >> >
> >> > And normally the application is defining the requirements. Simulations
> >> > seems to be for some users an critical option. So if the maintainers
> of
> >> > ngspice hardly suggesting to use the most recent version of ngspice in
> >> > recent KiCad version I would strongly consider to increase this build
> >> > dependency.
> >> >
> >> > In the end it's up to the KiCad maintainers to define the requirements
> >> > for KiCad. It was a long road to get ngspice into Debian main but in
> the
> >> > end it happened, big thanks to Holger again btw! So Debian has no
> >> > problem to provide KiCad with a depending libngspice0 library >= 30.2.
> >> >
> >>
> >> Is this a problem for any of the other package devs?  If not, I have no
> >> issue with bumping the minimum version to 30.  If this prevents any
> >> other platforms from being built, then it will have to wait.
> >>
> >> Cheers,
> >>
> >> Wayne
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] New package for macOS 5.1.2 stable including ngspice-30 ?

[Adam Wolf]

I have not yet been able to get 10.11 to build with ngspice 30.  I
will only look for a little bit.  Our policy would have us upgrade to
10.12 as a minimum requirement anyway, since 10.11 no longer gets
security updates.

Adam

On Mon, Jul 1, 2019 at 10:03 PM Adam Wolf  wrote:
>
> I do not personally use ngspice.  I have filed an issue if someone has a 
> quick one to add.
>
> https://github.com/KiCad/kicad-mac-builder/issues/90
>
> Adam
>
> On Mon, Jul 1, 2019, 9:43 PM Nick Østergaard  wrote:
>>
>> Good news, it seems like we managed to make the kicad-mac-packaging
>> scripts happy.
>>
>> After upgrading to ngspice 30 we had to update the include path for
>> some unknown reason. But it seems like it should work now. The first
>> build has been pushed to the nightly download location. It is not been
>> repackaged for stable. I guess Adam will handle that if we don't
>> release a 5.1.3 before.
>>
>> But I don't think it is ready for primetime yet, first user of the build 
>> says:
>>
>> <{HD}> haha so hitting the play button crashed all of kicad
>> <{HD}> yep, just tried again. The whole thing crashes.
>> <{HD}> This is fun and all but I am going out for dinner. I will be
>> back in a few hours.
>>
>> So if anyone else on mac could try it out? Maybe you Jeff can try it out?
>> I think he tested the unified version:
>> https://kicad-downloads.s3.cern.ch/osx/nightly/kicad-unified-20190701-113048-53e18489e-10_14.dmg
>>
>> Cheers.
>>
>> On Fri, 21 Jun 2019 at 11:16, Nick Østergaard  wrote:
>> >
>> > I see no reason to make ngspice 30 a strict minimum requirement.
>> >
>> > Lets just help packagers update to the latest ngspice and we are good.
>> >
>> > tor. 13. jun. 2019 18.33 skrev Wayne Stambaugh :
>> >>
>> >> On 6/10/19 4:01 PM, Carsten Schoenert wrote:
>> >> > Hello Wayne,
>> >> >
>> >> > Am 10.06.19 um 20:15 schrieb Wayne Stambaugh:
>> >> >> We cannot make ngspice 30 the minimum version.  There are far too many
>> >> >> linux distros where 30 is not available yet.  Please keep in mind,
>> >> >> Debian stable and the latest Ubuntu LTS version are the benchmarks for
>> >> >> dependency package versions.  I'm fine with packaging macos and windows
>> >> >> with 30.
>> >> >
>> >> > current Debian stable (Stretch) has KiCad version 4.0.5+dfsg1-4 in the
>> >> > archive and no package libngspice0 at all (not even in non-free) so
>> >> > there is nothing to take care on here.
>> >> >
>> >> > The current Ubuntu LTS release 18.04 (Bionic Beaver) has KiCad version
>> >> > 4.0.7+dfsg1-1ubuntu2 and libngspice0 version 27-1.
>> >> > At least the KiCad version is long long outdated. So also not really
>> >> > relevant too.
>> >> >
>> >> > But all relevant current Debian releases are providing a recent KiCad
>> >> > version and also libngspice0 in version 30.2-1 (from unstable to
>> >> > stretch-backports). This is also available in all Downstream of Debian
>> >> > means also in Ubuntu >= 'Cosmic Cuttlefish' are providing KiCad
>> >> > 5.0.0+dfsg1-2, but also libngspice0 in version 27. Updates wont happen.
>> >> >
>> >> > But Jean-Samuel Reynaud is providing actual versions of KiCad and also
>> >> > the depending libngspice0 package and they even work in the always
>> >> > outdated Linux Mint distro. So for me your requirements you like to set
>> >> > are fulfilled.
>> >> >
>> >> > And normally the application is defining the requirements. Simulations
>> >> > seems to be for some users an critical option. So if the maintainers of
>> >> > ngspice hardly suggesting to use the most recent version of ngspice in
>> >> > recent KiCad version I would strongly consider to increase this build
>> >> > dependency.
>> >> >
>> >> > In the end it's up to the KiCad maintainers to define the requirements
>> >> > for KiCad. It was a long road to get ngspice into Debian main but in the
>> >> > end it happened, big thanks to Holger again btw! So Debian has no
>> >> > problem to provide KiCad with a depending libngspice0 library >= 30.2.
>> >> >
>> >>
>> >> Is this a problem for any of the other packa

Re: [Kicad-developers] New package for macOS 5.1.2 stable including ngspice-30 ?

[Adam Wolf]

Based upon a bug in the tracker, it may be working or not working depending
upon external files, rather than exactly which nightly build it is.

On Wed, Jul 3, 2019, 8:16 AM Nick Østergaard  wrote:

> Cool, thank you for verifying.
>
> ons. 3. jul. 2019 14.54 skrev Seth Hillbrand :
>
>> On 2019-07-03 02:12, Nick Østergaard wrote:
>> > On Wed, 3 Jul 2019 at 06:39, Seth Hillbrand  wrote:
>> >> Hi Nick-
>> >>
>> >> Tested with latest nightly and it works nicely on 10.14.3.  I used the
>> >> simulations in the demos folder.
>> >>
>> >> Best-
>> >> Seth
>> >
>> > Cool, thank your for verifying. Did you check that it was actually
>> > running ngspice 30 with the control commands?
>>
>> Just checked now.
>>
>> .control
>> op
>> print allv
>> .enc
>>
>> Works correctly
>>
>> -Seth
>>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] macOS nightly builds no longer supporting 10.11

[Adam Wolf]

Hi folks!

I've been unable to keep 10.11 builds going. I'm certain it's
possible, but 10.11 is out of security updates and has been for a bit,
so I don't feel too bad about bumping the lower version to 10.12.  I
should be be spending more time getting 10.15 working, not keeping
10.11 working. :)

If this is a problem for anyone here, or predicted to be a problem
with users, please let me know.

I'll be migrating the nightly builds this week, and then adjusting the
kicad-mac-builder README accordingly.

Thanks!

Adam

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] build error on macos on 5.1 branch

[Adam Wolf]

Hi folks!

Running into a build error on my macOS jobs for 5.1:

I'm adding what I think is the appropriate message...


05:46:01 default: [ 69%] Building CXX object
pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/import_gfx/graphics_import_mgr.cpp.o
05:46:04 default: In file included from
/vagrant/build/kicad/src/kicad/pcbnew/import_gfx/graphics_import_mgr.cpp:27:
05:46:04 default:
/vagrant/build/kicad/src/kicad/pcbnew/import_gfx/dxf_import_plugin.h:
05:46:04 default: 151:16:
05:46:04 default: error: no matching constructor for
initialization of 'wxArrayString'
05:46:04 default: return wxArrayString( 1,
formatWildcardExt( "dxf" ) );
05:46:04 default:^
~
05:46:04 default:
/vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h:54:
05:46:04 default: 5: note: candidate constructor not viable: no
known conversion from 'wxString' to 'const char **' for 2nd argument
05:46:04 default:
05:46:04 default: wxArrayString(size_t sz, const char** a);
05:46:04 default: ^
05:46:04 default:
/vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h:55:5:
05:46:04 default: note: candidate constructor not viable: no known
conversion from 'wxString' to 'const wchar_t **' for 2nd argument
05:46:04 default: wxArrayString(size_t sz, const wchar_t** a);
05:46:04 default: ^
05:46:04 default:
/vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h:56
05:46:04 default: :
05:46:04 default: 5: note: candidate constructor not viable: no
known conversion from 'wxString' to 'const wxString *' for 2nd
argument
05:46:04 default: wxArrayString(size_t sz, const wxString* a);
05:46:04 default: ^
05:46:04 default:
/vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h:53:5:
05:46:04 default: note: candidate constructor not viable: requires
single argument 'a', but 2 arguments were provided
05:46:04 default: wxArrayString(const wxArrayString& a) :
wxArrayStringBase(a) { }
05:46:04 default: ^
05:46:04 default:
/vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h:52:5: note
05:46:04 default: : candidate constructor not viable: requires 0
arguments, but 2 were provided
05:46:04 default: wxArrayString() { }
05:46:04 default: ^
05:46:04 default: In file included from
/vagrant/build/kicad/src/kicad/pcbnew/import_gfx/graphics_import_mgr.cpp:28:
05:46:04 default:
/vagrant/build/kicad/src/kicad/pcbnew/import_gfx/svg_import_plugin.h:49:16:
error: no matching constructor for initialization of 'wxArrayString'
05:46:04 default: return wxArrayString( 1,
formatWildcardExt( "svg" ) );
05:46:04 default:^
~
05:46:04 default:
/vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h:54:5: note:
candidate constructor not viable: no known conversion from 'wxString'
to 'const char **' for 2nd argument
05:46:04 default: wxArrayString(size_t sz, const char** a);
05:46:04 default:
05:46:04 default: ^
05:46:04 default:
/vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h:55:5:
05:46:04 default: note: candidate constructor not viable: no known
conversion from 'wxString' to 'const wchar_t **' for 2nd argument
05:46:04 default: wxArrayString(size_t sz, const wchar_t** a);
05:46:04 default: ^
05:46:04 default:
/vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h:56:
05:46:04 default: 5: note:
05:46:04 default: candidate constructor not viable: no known
conversion from 'wxString' to 'const wxString *' for 2nd argument
05:46:04 default: wxArrayString(size_t sz, const wxString* a);
05:46:04 default:
05:46:04 default: ^
05:46:04 default: /vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h
05:46:04 default: :53:5:
05:46:04 default:  note: candidate constructor not viable:
requires single argument 'a', but 2 arguments were provided
05:46:04 default: wxArrayString(const wxArrayString& a) :
wxArrayStringBase(a) { }
05:46:04 default: ^
05:46:04 default: /vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h:
05:46:04 default: 52:5
05:46:04 default: : note
05:46:04 default: : candidate constructor not viable: requires 0
arguments, but 2 were provided
05:46:04 default: wxArrayString() { }
05:46:04 default: ^
05:46:05 default: 2 errors generated.
05:46:05 default: make[6]: ***
[pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/import_gfx/graphics_import_mgr.cpp.o]
Error 1
05:46:05 default: make[5]: ***
[pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/all] Error 2
05:46:05 default: make[4]: *** [all] Error 2

Thanks folks!

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.la

Re: [Kicad-developers] build error on macos on 5.1 branch

[Adam Wolf]

Thanks!

On Thu, Jul 11, 2019, 2:36 PM Seth Hillbrand  wrote:

> Ah, I see Jeff fixed up my commit for OSX in the master branch.  I've
> cherry-picked his fix for 5.1.  Let me know if it doesn't fix it.
>
> Best-
> Seth
>
> On 2019-07-11 13:59, Adam Wolf wrote:
> > Builds at at 044b4a6d4 on master went through fine.
> >
> > Adam
> >
> > On Thu, Jul 11, 2019 at 11:04 AM Seth Hillbrand 
> > wrote:
> >>
> >> Hi Adam-
> >>
> >> This looks like the result of a cherry-pick I did the other day.  Do
> >> you
> >> get this error in the master branch as well?
> >>
> >> -S
> >>
> >> On 2019-07-11 11:55, Adam Wolf wrote:
> >> > Hi folks!
> >> >
> >> > Running into a build error on my macOS jobs for 5.1:
> >> >
> >> > I'm adding what I think is the appropriate message...
> >> >
> >> >
> >> > 05:46:01 default: [ 69%] Building CXX object
> >> >
> pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/import_gfx/graphics_import_mgr.cpp.o
> >> > 05:46:04 default: In file included from
> >> >
> /vagrant/build/kicad/src/kicad/pcbnew/import_gfx/graphics_import_mgr.cpp:27:
> >> > 05:46:04 default:
> >> > /vagrant/build/kicad/src/kicad/pcbnew/import_gfx/dxf_import_plugin.h:
> >> > 05:46:04 default: 151:16:
> >> > 05:46:04 default: error: no matching constructor for
> >> > initialization of 'wxArrayString'
> >> > 05:46:04 default: return wxArrayString( 1,
> >> > formatWildcardExt( "dxf" ) );
> >> > 05:46:04 default:^
> >> > ~
> >> > 05:46:04 default:
> >> > /vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h:54:
> >> > 05:46:04 default: 5: note: candidate constructor not viable: no
> >> > known conversion from 'wxString' to 'const char **' for 2nd argument
> >> > 05:46:04 default:
> >> > 05:46:04 default: wxArrayString(size_t sz, const char** a);
> >> > 05:46:04 default: ^
> >> > 05:46:04 default:
> >> > /vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h:55:5:
> >> > 05:46:04 default: note: candidate constructor not viable: no known
> >> > conversion from 'wxString' to 'const wchar_t **' for 2nd argument
> >> > 05:46:04 default: wxArrayString(size_t sz, const wchar_t** a);
> >> > 05:46:04 default: ^
> >> > 05:46:04 default:
> >> > /vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h:56
> >> > 05:46:04 default: :
> >> > 05:46:04 default: 5: note: candidate constructor not viable: no
> >> > known conversion from 'wxString' to 'const wxString *' for 2nd
> >> > argument
> >> > 05:46:04 default: wxArrayString(size_t sz, const wxString* a);
> >> > 05:46:04 default: ^
> >> > 05:46:04 default:
> >> > /vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h:53:5:
> >> > 05:46:04 default: note: candidate constructor not viable: requires
> >> > single argument 'a', but 2 arguments were provided
> >> > 05:46:04 default: wxArrayString(const wxArrayString& a) :
> >> > wxArrayStringBase(a) { }
> >> > 05:46:04 default: ^
> >> > 05:46:04 default:
> >> > /vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h:52:5: note
> >> > 05:46:04 default: : candidate constructor not viable: requires 0
> >> > arguments, but 2 were provided
> >> > 05:46:04 default: wxArrayString() { }
> >> > 05:46:04 default: ^
> >> > 05:46:04 default: In file included from
> >> >
> /vagrant/build/kicad/src/kicad/pcbnew/import_gfx/graphics_import_mgr.cpp:28:
> >> > 05:46:04 default:
> >> >
> /vagrant/build/kicad/src/kicad/pcbnew/import_gfx/svg_import_plugin.h:49:16:
> >> > error: no matching constructor for initialization of 'wxArrayString'
> >> > 05:46:04 default: return wxArrayString( 1,
> >> > formatWildcardExt( "svg" ) );
> >> > 05:46:04 default:^
> >> > ~
> >> > 05:46:04 default:
> >> > /vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h:

Re: [Kicad-developers] build error on macos on 5.1 branch

[Adam Wolf]

It's all fixed.  Thanks!

On Thu, Jul 11, 2019 at 5:32 PM Adam Wolf  wrote:
>
> Thanks!
>
> On Thu, Jul 11, 2019, 2:36 PM Seth Hillbrand  wrote:
>>
>> Ah, I see Jeff fixed up my commit for OSX in the master branch.  I've
>> cherry-picked his fix for 5.1.  Let me know if it doesn't fix it.
>>
>> Best-
>> Seth
>>
>> On 2019-07-11 13:59, Adam Wolf wrote:
>> > Builds at at 044b4a6d4 on master went through fine.
>> >
>> > Adam
>> >
>> > On Thu, Jul 11, 2019 at 11:04 AM Seth Hillbrand 
>> > wrote:
>> >>
>> >> Hi Adam-
>> >>
>> >> This looks like the result of a cherry-pick I did the other day.  Do
>> >> you
>> >> get this error in the master branch as well?
>> >>
>> >> -S
>> >>
>> >> On 2019-07-11 11:55, Adam Wolf wrote:
>> >> > Hi folks!
>> >> >
>> >> > Running into a build error on my macOS jobs for 5.1:
>> >> >
>> >> > I'm adding what I think is the appropriate message...
>> >> >
>> >> >
>> >> > 05:46:01 default: [ 69%] Building CXX object
>> >> > pcbnew/CMakeFiles/pcbnew_kiface_objects.dir/import_gfx/graphics_import_mgr.cpp.o
>> >> > 05:46:04 default: In file included from
>> >> > /vagrant/build/kicad/src/kicad/pcbnew/import_gfx/graphics_import_mgr.cpp:27:
>> >> > 05:46:04 default:
>> >> > /vagrant/build/kicad/src/kicad/pcbnew/import_gfx/dxf_import_plugin.h:
>> >> > 05:46:04 default: 151:16:
>> >> > 05:46:04 default: error: no matching constructor for
>> >> > initialization of 'wxArrayString'
>> >> > 05:46:04 default: return wxArrayString( 1,
>> >> > formatWildcardExt( "dxf" ) );
>> >> > 05:46:04 default:^
>> >> > ~
>> >> > 05:46:04 default:
>> >> > /vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h:54:
>> >> > 05:46:04 default: 5: note: candidate constructor not viable: no
>> >> > known conversion from 'wxString' to 'const char **' for 2nd argument
>> >> > 05:46:04 default:
>> >> > 05:46:04 default: wxArrayString(size_t sz, const char** a);
>> >> > 05:46:04 default: ^
>> >> > 05:46:04 default:
>> >> > /vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h:55:5:
>> >> > 05:46:04 default: note: candidate constructor not viable: no known
>> >> > conversion from 'wxString' to 'const wchar_t **' for 2nd argument
>> >> > 05:46:04 default: wxArrayString(size_t sz, const wchar_t** a);
>> >> > 05:46:04 default: ^
>> >> > 05:46:04 default:
>> >> > /vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h:56
>> >> > 05:46:04 default: :
>> >> > 05:46:04 default: 5: note: candidate constructor not viable: no
>> >> > known conversion from 'wxString' to 'const wxString *' for 2nd
>> >> > argument
>> >> > 05:46:04 default: wxArrayString(size_t sz, const wxString* a);
>> >> > 05:46:04 default: ^
>> >> > 05:46:04 default:
>> >> > /vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h:53:5:
>> >> > 05:46:04 default: note: candidate constructor not viable: requires
>> >> > single argument 'a', but 2 arguments were provided
>> >> > 05:46:04 default: wxArrayString(const wxArrayString& a) :
>> >> > wxArrayStringBase(a) { }
>> >> > 05:46:04 default: ^
>> >> > 05:46:04 default:
>> >> > /vagrant/build/wxwidgets-dest/include/wx-3.0/wx/arrstr.h:52:5: note
>> >> > 05:46:04 default: : candidate constructor not viable: requires 0
>> >> > arguments, but 2 were provided
>> >> > 05:46:04 default: wxArrayString() { }
>> >> > 05:46:04 default: ^
>> >> > 05:46:04 default: In file included from
>> >> > /vagrant/build/kicad/src/kicad/pcbnew/import_gfx/graphics_import_mgr.cpp:28:
>> >> > 05:46:04 default:
>> >> > /vagrant/build/kicad/src/kicad/pcbnew/import_gfx/svg_import_plugin.h:49:16:
>> >> > error: no matchin

Re: [Kicad-developers] 5.1.3 release

[Adam Wolf]

MacOS would be ready today.  I'll upload packages and prep a PR (not to
merge until everything is loaded).

On Fri, Aug 2, 2019, 10:36 AM Wayne Stambaugh  wrote:

> Seeing that Fedora is one of the major distros, I will push the release
> announcement to a week from today.  Thanks for the update.
>
> Cheers,
>
> Wayne
>
>
> On 8/2/2019 11:13 AM, Steven A. Falco wrote:
> > The Fedora build of 5.1.3 is waiting for Karma.  It will be available in
> about 6 days.  I have another build in the pipeline owing to bug 1838448,
> which should become available a few days later.
> >
> >   Steve
> >
> > On 8/2/19 11:07 AM, Wayne Stambaugh wrote:
> >> Where do we stand on packaging for the 5.1.3 stable release?  We should
> >> be close but I didn't see the updates to the website download links.  I
> >> would like to make the release announcement tomorrow or Sunday if
> >> possible.  Please let me know if this and issue.
> >>
> >> Cheers,
> >>
> >> Wayne
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> >>
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.4 release - release announcement/blog entry?

[Adam Wolf]

MacOS is building.  I am out of town and return tomorrow.  If there are no
issues I should be able to get them uploaded tonight, if not, Sunday.

On Fri, Aug 9, 2019, 1:21 PM Wayne Stambaugh  wrote:

> I fine with adding the release announcement to the changelog.  I'm
> guessing this will be final blog post url.  The release announcement is
> already updated and ready to go as soon as the macos and windows
> packages are built, uploaded to the server, and the website download
> links are updated.  As soon as that it done, I will remove the draft tag
> from the release announcement.  Hopefully I wont be more than a few more
> days.
>
> Cheers,
>
> Wayne
>
> On 8/9/19 3:50 PM, Stefan Brüns wrote:
> > On Freitag, 9. August 2019 16:45:37 CEST Nick Østergaard wrote:
> >> kicad-doc 5.1.4 has been tagged
> >
> > Hi,
> >
> > the packages for openSUSE (Tumbleweed and Leap) are ready and waiting
> for
> > submission to the repos, but I would like to include the release
> announcement
> > URL in the changelog.
> >
> > Extrapolating past releases, it will likely show up as:
> > http://kicad-pcb.org/blog/2019/08/KiCad-5.1.4-Release/
> >
> > Any reservations for including this URL in the Changelog?
> >
> > Kind regards,
> >
> > Stefan
> >
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.4 release - release announcement/blog entry?

[Adam Wolf]

Working on this this morning.  Thanks for your patience all.

Adam

On Mon, Aug 12, 2019 at 7:56 AM Wayne Stambaugh  wrote:
>
> Ian,
>
> Nice catch.  I just pushed the fix.
>
> Thanks,
>
> Wayne
>
> On 8/12/2019 8:47 AM, Ian McInerney wrote:
> > Wayne,
> >
> > There seems to be a typo in the release announcement (line 23), it
> > references the 5.1.3 milestone page twice instead of 5.1.3 and 5.1.4.
> >
> > -Ian
> >
> > On Mon, Aug 12, 2019 at 2:39 PM Wayne Stambaugh  > <mailto:stambau...@gmail.com>> wrote:
> >
> > I just installed 5.1.4_1 on windows 10 and everything seems to be
> > working as expected.  I did not see the 5.1.4 macos package.  I will
> > hold off updating the website download page and the release announcement
> > until that is ready.  Thank you everyone for your efforts.  Hopefully
> > the next stable release will go a bit more smoothly.
> >
> > Cheers,
> >
> > Wayne
> >
> > On 8/9/2019 6:01 PM, Nick Østergaard wrote:
> > > Please sanity test the windows build and make pr for the website, I
> > > won't make commits until sunday. I am travelling.
> > >
> > > fre. 9. aug. 2019 23.50 skrev Adam Wolf
> > mailto:adamw...@feelslikeburning.com>
> > > <mailto:adamw...@feelslikeburning.com
> > <mailto:adamw...@feelslikeburning.com>>>:
> > >
> > > MacOS is building.  I am out of town and return tomorrow.  If
> > there
> > > are no issues I should be able to get them uploaded tonight,
> > if not,
> > > Sunday.
> > >
> > > On Fri, Aug 9, 2019, 1:21 PM Wayne Stambaugh
> > mailto:stambau...@gmail.com>
> > > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>>
> > wrote:
> > >
> > > I fine with adding the release announcement to the
> > changelog.  I'm
> > > guessing this will be final blog post url.  The release
> > > announcement is
> > > already updated and ready to go as soon as the macos and
> > windows
> > > packages are built, uploaded to the server, and the
> > website download
> > > links are updated.  As soon as that it done, I will remove the
> > > draft tag
> > > from the release announcement.  Hopefully I wont be more
> > than a
> > > few more
> > > days.
> > >
> > > Cheers,
> > >
> > > Wayne
> > >
> > > On 8/9/19 3:50 PM, Stefan Brüns wrote:
> > > > On Freitag, 9. August 2019 16:45:37 CEST Nick Østergaard
> > wrote:
> > > >> kicad-doc 5.1.4 has been tagged
> > > >
> > > > Hi,
> > > >
> > > > the packages for openSUSE (Tumbleweed and Leap) are
> > ready and
> > > waiting for
> > > > submission to the repos, but I would like to include the
> > > release announcement
> > > > URL in the changelog.
> > > >
> > > > Extrapolating past releases, it will likely show up as:
> > > > http://kicad-pcb.org/blog/2019/08/KiCad-5.1.4-Release/
> > > >
> > > > Any reservations for including this URL in the Changelog?
> > > >
> > > > Kind regards,
> > > >
> > > > Stefan
> > > >
> > > >
> > > > ___
> > > > Mailing list: https://launchpad.net/~kicad-developers
> > > > Post to : kicad-developers@lists.launchpad.net
> > <mailto:kicad-developers@lists.launchpad.net>
> > > <mailto:kicad-developers@lists.launchpad.net
> > <mailto:kicad-developers@lists.launchpad.net>>
> > > > Unsubscribe : https://launchpad.net/~kicad-developers
> > > > More help   : https://help.launchpad.net/ListHelp
> > > >
> > >
> > > ___
> > > Mailing lis

Re: [Kicad-developers] 5.1.4 release - release announcement/blog entry?

[Adam Wolf]

Hi folks!

5.1.4 is up for macOS.  It's in two versions, like last time.  10.12
and 10.13 use 
https://kicad-downloads.s3.cern.ch/osx/stable/kicad-unified-5.1.4-0.dmg,
and 10.14 uses 
https://kicad-downloads.s3.cern.ch/osx/stable/kicad-unified-5.1.4-0-10_14.dmg

The second file is not yet uploaded but should be within an hour or
two... it's uploading, slowly but surely.

Thanks for everyone's patience.  I'll work on getting package uploads
from the build machine for releases--I have to do an extra
download/upload step and that makes it take a lot longer if I'm on
travel--unlike nightlies which upload automatically.

Adam

On Mon, Aug 12, 2019 at 10:29 AM Wayne Stambaugh  wrote:
>
> Adam,
>
> Please ping the mailing list once you get this uploaded so I can get
> everything released.
>
> Thanks,
>
> Wayne
>
> On 8/12/2019 10:04 AM, Adam Wolf wrote:
> > Working on this this morning.  Thanks for your patience all.
> >
> > Adam
> >
> > On Mon, Aug 12, 2019 at 7:56 AM Wayne Stambaugh  
> > wrote:
> >>
> >> Ian,
> >>
> >> Nice catch.  I just pushed the fix.
> >>
> >> Thanks,
> >>
> >> Wayne
> >>
> >> On 8/12/2019 8:47 AM, Ian McInerney wrote:
> >>> Wayne,
> >>>
> >>> There seems to be a typo in the release announcement (line 23), it
> >>> references the 5.1.3 milestone page twice instead of 5.1.3 and 5.1.4.
> >>>
> >>> -Ian
> >>>
> >>> On Mon, Aug 12, 2019 at 2:39 PM Wayne Stambaugh  >>> <mailto:stambau...@gmail.com>> wrote:
> >>>
> >>> I just installed 5.1.4_1 on windows 10 and everything seems to be
> >>> working as expected.  I did not see the 5.1.4 macos package.  I will
> >>> hold off updating the website download page and the release 
> >>> announcement
> >>> until that is ready.  Thank you everyone for your efforts.  Hopefully
> >>> the next stable release will go a bit more smoothly.
> >>>
> >>> Cheers,
> >>>
> >>> Wayne
> >>>
> >>> On 8/9/2019 6:01 PM, Nick Østergaard wrote:
> >>> > Please sanity test the windows build and make pr for the website, I
> >>> > won't make commits until sunday. I am travelling.
> >>> >
> >>> > fre. 9. aug. 2019 23.50 skrev Adam Wolf
> >>> mailto:adamw...@feelslikeburning.com>
> >>> > <mailto:adamw...@feelslikeburning.com
> >>> <mailto:adamw...@feelslikeburning.com>>>:
> >>> >
> >>> > MacOS is building.  I am out of town and return tomorrow.  If
> >>> there
> >>> > are no issues I should be able to get them uploaded tonight,
> >>> if not,
> >>> > Sunday.
> >>> >
> >>> > On Fri, Aug 9, 2019, 1:21 PM Wayne Stambaugh
> >>> mailto:stambau...@gmail.com>
> >>> > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>>
> >>> wrote:
> >>> >
> >>> > I fine with adding the release announcement to the
> >>> changelog.  I'm
> >>> > guessing this will be final blog post url.  The release
> >>> > announcement is
> >>> > already updated and ready to go as soon as the macos and
> >>> windows
> >>> > packages are built, uploaded to the server, and the
> >>> website download
> >>> > links are updated.  As soon as that it done, I will remove 
> >>> the
> >>> > draft tag
> >>> > from the release announcement.  Hopefully I wont be more
> >>> than a
> >>> > few more
> >>> > days.
> >>> >
> >>> > Cheers,
> >>> >
> >>> > Wayne
> >>> >
> >>> > On 8/9/19 3:50 PM, Stefan Brüns wrote:
> >>> > > On Freitag, 9. August 2019 16:45:37 CEST Nick Østergaard
> >>> wrote:
> >>> > >> kicad-doc 5.1.4 has been tagged
> >>> > >
> >>> > > Hi,
> >>> > >
> >>> 

Re: [Kicad-developers] 5.1.4 release - release announcement/blog entry?

[Adam Wolf]

macOS is ready!

Adam

On Mon, Aug 12, 2019 at 10:43 PM Adam Wolf
 wrote:
>
> Hi folks!
>
> 5.1.4 is up for macOS.  It's in two versions, like last time.  10.12
> and 10.13 use 
> https://kicad-downloads.s3.cern.ch/osx/stable/kicad-unified-5.1.4-0.dmg,
> and 10.14 uses 
> https://kicad-downloads.s3.cern.ch/osx/stable/kicad-unified-5.1.4-0-10_14.dmg
>
> The second file is not yet uploaded but should be within an hour or
> two... it's uploading, slowly but surely.
>
> Thanks for everyone's patience.  I'll work on getting package uploads
> from the build machine for releases--I have to do an extra
> download/upload step and that makes it take a lot longer if I'm on
> travel--unlike nightlies which upload automatically.
>
> Adam
>
> On Mon, Aug 12, 2019 at 10:29 AM Wayne Stambaugh  wrote:
> >
> > Adam,
> >
> > Please ping the mailing list once you get this uploaded so I can get
> > everything released.
> >
> > Thanks,
> >
> > Wayne
> >
> > On 8/12/2019 10:04 AM, Adam Wolf wrote:
> > > Working on this this morning.  Thanks for your patience all.
> > >
> > > Adam
> > >
> > > On Mon, Aug 12, 2019 at 7:56 AM Wayne Stambaugh  
> > > wrote:
> > >>
> > >> Ian,
> > >>
> > >> Nice catch.  I just pushed the fix.
> > >>
> > >> Thanks,
> > >>
> > >> Wayne
> > >>
> > >> On 8/12/2019 8:47 AM, Ian McInerney wrote:
> > >>> Wayne,
> > >>>
> > >>> There seems to be a typo in the release announcement (line 23), it
> > >>> references the 5.1.3 milestone page twice instead of 5.1.3 and 5.1.4.
> > >>>
> > >>> -Ian
> > >>>
> > >>> On Mon, Aug 12, 2019 at 2:39 PM Wayne Stambaugh  > >>> <mailto:stambau...@gmail.com>> wrote:
> > >>>
> > >>> I just installed 5.1.4_1 on windows 10 and everything seems to be
> > >>> working as expected.  I did not see the 5.1.4 macos package.  I will
> > >>> hold off updating the website download page and the release 
> > >>> announcement
> > >>> until that is ready.  Thank you everyone for your efforts.  
> > >>> Hopefully
> > >>> the next stable release will go a bit more smoothly.
> > >>>
> > >>> Cheers,
> > >>>
> > >>> Wayne
> > >>>
> > >>> On 8/9/2019 6:01 PM, Nick Østergaard wrote:
> > >>> > Please sanity test the windows build and make pr for the website, 
> > >>> I
> > >>> > won't make commits until sunday. I am travelling.
> > >>> >
> > >>> > fre. 9. aug. 2019 23.50 skrev Adam Wolf
> > >>>  > >>> <mailto:adamw...@feelslikeburning.com>
> > >>> > <mailto:adamw...@feelslikeburning.com
> > >>> <mailto:adamw...@feelslikeburning.com>>>:
> > >>> >
> > >>> > MacOS is building.  I am out of town and return tomorrow.  If
> > >>> there
> > >>> > are no issues I should be able to get them uploaded tonight,
> > >>> if not,
> > >>> > Sunday.
> > >>> >
> > >>> > On Fri, Aug 9, 2019, 1:21 PM Wayne Stambaugh
> > >>> mailto:stambau...@gmail.com>
> > >>> > <mailto:stambau...@gmail.com <mailto:stambau...@gmail.com>>>
> > >>> wrote:
> > >>> >
> > >>> > I fine with adding the release announcement to the
> > >>> changelog.  I'm
> > >>> > guessing this will be final blog post url.  The release
> > >>> > announcement is
> > >>> > already updated and ready to go as soon as the macos and
> > >>> windows
> > >>> > packages are built, uploaded to the server, and the
> > >>> website download
> > >>> > links are updated.  As soon as that it done, I will 
> > >>> remove the
> > >>> > draft tag
> > >>> > from the release announcement.  Hopefully I wont be more
> > >>> than a
> > >>> >