Re: [Kicad-developers] Unable to build on Ubuntu 18.04 for 6.0 branch

[Jean-Samuel Reynaud]

Hi,

> Jean-Samuel, you may be able to use the mhier PPA[2] as the source
> for newer Boost versions that will allow KiCad on older Ubuntus.

Ok, I'll try that to see if it's possible.

Anyway what is the minimum version number required for boost ? Because
as I see on kicad/INSTALL.txt it's 1.59 (in master and 6.0 branches),
but not sure that is still true. At least with 1.65 it's not building
anymore (as in Ubuntu 18.04)  and with 1.71 it's ok (as in Ubuntu
20.04).

___
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] Unable to build on Ubuntu 18.04 for 6.0 branch

[Jean-Samuel Reynaud]

Hi,

As I see, since one of those commits:
891c919c239223ef601284a8f166d0f229f6b030
0ea7dabc1271dbc77b8d5764e4eecbeba85903d6
e1cd74dd78031b002737a79ddffcf3489d74105c
4d8297a1f6f18d59cb38361b88a959d7af062480

KiCad is unable to build on Ubuntu 18.04. I guess it's a boost version
issue (Boost is 1.65.1 on Ubuntu 18.04).
The build error:
kicad/common/kiid.cpp:50:73:   required from here
/usr/include/boost/random/detail/seed_impl.hpp:269:9: error: ‘class
boost::uuids::detail::seed_rng’ has no member named ‘generate’
 seq.generate([0], [0] + ((w+31)/32) * n);
 ^~~~


You can take a look as the build output at
https://launchpadlibrarian.net/600354670/buildlog_ubuntu-bionic-amd64.kicad_6.0.0+nightly-202205081117+43b8adad1a~116~ubuntu18.04.1_BUILDING.txt.gz
(large log, error message near the end ;)


Is this version of Ubuntu is still supported for 6.0 branch ? (for me
yes since the Ubuntu support is up to April 2023)...
Note that it affect version 6.0.5 (6.0.4 was built correctly)

Regards,

___
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] Introduction of sentry application monitoring and error tracking

[Jean-Samuel Reynaud]

Hi Mark,

Should I enable yet this on ubuntu nightly build (PPA) ?

Regards,
Le mercredi 30 mars 2022 à 20:31 -0400, Mark Roszko a écrit :
> Hey folks,
> 
> We are planning to introduce the use of the Sentry platform into
> KiCad.
> Sentry https://sentry.io/ is open source platform to capture
> application events, crash dumps, and other random analytics.
> Both their hosted platform (https://github.com/getsentry/sentry) is
> open source and the integrated SDK to handle crash handling in C++ is
> also open source on github under MIT license (
> https://github.com/getsentry/sentry-native)
> Sentry has given KiCad a sponsored account to use their SaaS platform
> as the KiCad team does not have the manpower to maintain a self-
> hosted instance.
> 
> The plan going forward is:
> - The primary use in KiCad will be to capture crash reports, but in
> the future it could also let us gather things like performance
> metrics of algorithms across the wider user base.
> - The implementation will be and will remain entirely opt-in with a
> one time prompt on startup, and the ability to turn it off in
> preferences. This is to maintain privacy regulation compliance and
> just good manners.
> - No PII is captured, we have no need or desire for it. Only a random
> GUID generated for your install is used to connect crash reports.
> This GUID can be reset at any time by the user.
> - To aid in avoiding PII capture, all sentry reports go to a "sentry-
> relay" server run on KiCad owned infrastructure, 
> this relay serves as a proxy to communicate to the main sentry.io
> platform, this aids in hiding originating IP addresses but we have
> also turned off the storage of IP addresses in sentry
> - Additionally, the cmake variable KICAD_USE_SENTRY is being added
> where a value of false will disable the inclusion of the sentry sdk
> entirely. The current default will be off as only Windows support is
> tested.
> - Sentry will only store at most 1 raw crash dump (though we can turn
> it off entirely) for analysis. Sentry will parse out only the
> relevant crash details such as call stack, and stack frame and
> discard the rest of the crash dump.
> - This will be deployed for Windows nightly builds first
> - Data in sentry is retained for at max 90 days before it is deleted
> automatically.
> 
> 
> This solves a many years long desire of the KiCad team to capture
> crash dumps without user involvement and sentry offers us a very easy
> solution to do it and help make KiCad better for everyone.
> 
> ___
> 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 Status and a way forward

[Jean-Samuel Reynaud]

Dear Seth,

First thanks for all your (and all team) efforts for making KiCad a
great EDA software.
About Python, I'm really interested to take a look at discussions on
that point. As I understand, swig will not be used anymore and pybind11
become the future (but not sure of my interpretation of commits ;).
As you know I maintain a Via stitching tool in python since few years
and as I know there are some users. So following discussion and
developments is interesting for me...

Regards,
Le 16/11/2021 à 19:24, Seth Hillbrand a écrit :
> Hi Folks-
> 
> Unfortunately, we were not able to get the Python revisions into version
> 6.  As such, we'll be using the legacy SWIG implementation for pcbnew
> during v6 and will introduce the updated API early in the v7 development
> process.
> 
> ## What happened?
> 
> Our goals for the Python API were to make a stable set of calls that
> plugin developers could rely on to work over multiple KiCad versions and
> to expand python scripting to eeschema.  This required abstracting a
> number of underlying concepts and re-writing a set of core
> applications.  And it didn't get done in time.
> 
> We decided that it was more important to get v6 out to our userbase with
> the status quo python scripting than for an indefinite delay to get the
> first API out.
> 
> ## What's the plan going forward?
> 
> Following the release of v6, the KiCad core dev team will be meeting to
> plan out our work for v7.  One of the items on our agenda will be to
> review where things went well and poorly in the v6 development.  We do
> this with the intention of improving both our development work and our
> communication with the community during upcoming releases.
> 
> We're also going to be reaching out to some of our plugin developers to
> get their input on things that they'd like to use the API for and ways
> that we might be able to facilitate that in v7.  If you have interest in
> being a part of that discussion (and you have published a couple plugins
> for KiCad or other projects), please reach out.  We're happy to include you.
> 
> I deeply regret that we won't have a shiny new python interface in v6. 
> I know that this will be a disappointment to a number of people. 
> Hopefully, the major advancements that we have built into v6 will
> assuage that somewhat.
> 
> ---
> Seth
> 
> -- 
> KiCad Services Corporation Logo
> Seth Hillbrand
> *Lead Developer*
> +1-530-302-5483‬
> Long Beach, CA
> www.kipro-pcb.com     i...@kipro-pcb.com
> 
> 
> 
> ___
> 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] Experience compiling latest HEAD

[Jean-Samuel Reynaud]

>> And the kicad built nightly v5.99 from
>> http://ppa.launchpad.net/kicad/kicad-dev-nightly/ubuntu/
>>
>> And it's v5.99 I was asking to include wx 3.1.
> 
> I though we had changed our nightly Ubuntu builds over to 3.1 but
> apparently not.  Maybe our PPA package dev can comment about what it
> would take to do that.  I've been using 3.1 on Debian testing for quite
> a long time now and it seems to be stable and it also fixes a lot of
> issues.
> 
Currently only wx 3.0 is available in ubuntu (as far as I see up to
21.04). So nightly build use 3.0. As Carsten say, 3.1 is the dev version
of WX and is not yet included in debian (so in ubuntu).


___
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] How many users does KiCAD have?

[Jean-Samuel Reynaud]

Dear Avishay,


For PPA I have some statistic (available at
https://jsreynaud.github.io/). But it include only download for packages
of KiCad via PPA (ubuntu).


Le 18/05/2021 à 12:19, Avishay Orpaz a écrit :
> I understand it's a tricky question to answer, especially when it comes
> to open source software, but is there any estimation about the number of
> active KiCAD users? How many (commercial) companies use KiCAD? How many
> people downloaded each version of KiCAD?
> 
> Avishay
> 
> ___
> 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.10 stable release tagged

[Jean-Samuel Reynaud]

On my side PPA (ubuntu) is ready with 5.1.10.

Le 27/04/2021 à 22:14, Christoph Moench-Tegeder a écrit :
> ## Seth Hillbrand (s...@kipro-pcb.com):
> 
>> Docs and i18n have been tagged.
> 
> And there they are, thanks.
> I'll give it a spin (testing, so important) and push later this week.
> 
> Regards,
> Christoph
> 


___
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.10 stable release tagged

[Jean-Samuel Reynaud]

Hi,

Same with kicad-i18n...


Le 27/04/2021 à 14:35, Christoph Moench-Tegeder a écrit :
> Hi,
> 
> ## Wayne Stambaugh (stambau...@gmail.com):
> 
>> I just pushed the stable release tag to GitLab.  Please update any repo 
>> tags as required so we can get the packages build.
> 
> Any chance to get kicad-doc tagged before the release? I'd rather
> push kicad, all the libraries and docs at once instead of piecemeal.
> 
> Regards,
> Christoph
> 


___
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] ngspice-34

[Jean-Samuel Reynaud]

FYI:
As I see the PATH for the file ngspice/config.h is changed on
ngspice-34. And on debian package this file is no more distributed on
this version (as I see on last updated package).

So there is an impact on some KiCad code:

common/build_version.cpp:161:#include 



Le 02/02/2021 à 09:16, Holger Vogt a écrit :
> We don't install cmpp and dlmain.c any more.
> 
> We also don't install the headers any more, except for sharedspice.h.
> 
> Holger
> 
> ___
> 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] Translation building changes in master

[Jean-Samuel Reynaud]

Ok thanks for this update. It will complete actions on my side ;)
As explained in zulip: On my side I have added a package during build
(kicad-its-files) that containt the missing ITS files.

 Since package shared-mime-info contain the right ITS file after version
2.0, this package is useful only on previous version of
shared-mime-info. So build dependency handle this for KiCad and package
kicad-its-files conflict automaticaly with newer version of
share-mime-info. It should be future proof ;)


Le 28/01/2021 à 01:29, Ian McInerney a écrit :
> Ok, I have updated the linux translation framework so that it will now
> gracefully handle errors in the file translation. If it detects an error
> when translating the metadata it will instead copy the raw metadata file
> over and throw a warning into the build log but let the build continue.
> 
> -Ian
> 
> On Thu, Jan 21, 2021 at 5:25 PM Ian McInerney  <mailto:ian.s.mciner...@ieee.org>> wrote:
> 
> Yes, Steve made me aware of the lack of that file on older distros -
> and I am working on a solution. I am currently building out the
> CMake files so that they try to do the translation and then check
> the return code and fallback to a simple file copy if the
> translation fails (and display the failure as a warning, so it is
> visible but doesn't stop the build process).
> 
> -Ian
> 
> On Thu, Jan 21, 2021 at 5:12 PM Steven A. Falco
> mailto:stevenfa...@gmail.com>> wrote:
> 
> We have the same problem with Fedora 32 because it also doesn't
> have the needed ITS file.
> 
> I believe Ian is looking into a solution.
> 
>         Steve
> 
> On 1/21/21 11:40 AM, Jean-Samuel Reynaud wrote:
> > Dear Ian,
> >
> > Since this update some build fail on ubuntu. In fact there is
> > translation of some XML files (for example mime types
> > resources/linux/mime/kicad-gerbers.xml.in
> <http://kicad-gerbers.xml.in>) but gettext is unable to find
> > rules to translate that kind of file without the appropriate
> ITS file.
> > On Ubuntu 18.04, shared-mime-info is too old and don't ship
> > shared-mime-info.loc and shared-mime-info.its. So building is
> failing.
> >
> > So what is your proposal for that ? Perhaps there is already
> an answer
> > about this point ? I think I can fix that by coping missing
> ITS files on
> > the appropriate directory but it's a dirty solution...
> >
> >
> >
> >
> > Le 18/01/2021 à 18:54, Ian McInerney a écrit :
> >> The changes to the i18n build system have now been merged
> into the
> >> master branch - with the change that KICAD_BUILD_I18N will
> default to
> >> OFF now, so it must be enabled when you want to build the
> translations
> >> libraries.
> >>
> >> At this point, all nightly builds of the master branch that
> include
> >> translations need to be updated to use the
> KICAD_BUILD_I18N=ON flag and
> >> no longer reference the i18n repository.
> >>
> >> -Ian
> >>
> >> On Sat, Jan 16, 2021 at 7:41 PM Ian McInerney
> mailto:ian.s.mciner...@ieee.org>
> >> <mailto:ian.s.mciner...@ieee.org
> <mailto:ian.s.mciner...@ieee.org>>> wrote:
> >>
> >>      Since we now host the v6 translations inside the main code
> >>      repository, I have consolidated the CMake scripts for
> building the
> >>      translation files into the main build process inside this MR
> >>     
> (https://gitlab.com/kicad/code/kicad/-/merge_requests/628). That
> >>      exposes a new CMake option `KICAD_BUILD_I18N`, which
> defaults to on,
> >>      that controls if the translations are built. When that
> option is ON,
> >>      gettext is a required dependency and when it is off it
> is not
> >>      needed. This change will require some people to modify
> their current
> >>      build setup to disable the translations if they do not
> wish to build
> >>      with gettext.
> >>
> >>      In that MR I have also added the linux metadata files to the
> >>      translation framework to allow 

Re: [Kicad-developers] Translation building changes in master

[Jean-Samuel Reynaud]

Dear Ian,

Since this update some build fail on ubuntu. In fact there is
translation of some XML files (for example mime types
resources/linux/mime/kicad-gerbers.xml.in) but gettext is unable to find
rules to translate that kind of file without the appropriate ITS file.
On Ubuntu 18.04, shared-mime-info is too old and don't ship
shared-mime-info.loc and shared-mime-info.its. So building is failing.

So what is your proposal for that ? Perhaps there is already an answer
about this point ? I think I can fix that by coping missing ITS files on
the appropriate directory but it's a dirty solution...




Le 18/01/2021 à 18:54, Ian McInerney a écrit :
> The changes to the i18n build system have now been merged into the
> master branch - with the change that KICAD_BUILD_I18N will default to
> OFF now, so it must be enabled when you want to build the translations
> libraries.
> 
> At this point, all nightly builds of the master branch that include
> translations need to be updated to use the KICAD_BUILD_I18N=ON flag and
> no longer reference the i18n repository.
> 
> -Ian
> 
> On Sat, Jan 16, 2021 at 7:41 PM Ian McInerney  > wrote:
> 
> Since we now host the v6 translations inside the main code
> repository, I have consolidated the CMake scripts for building the
> translation files into the main build process inside this MR
> (https://gitlab.com/kicad/code/kicad/-/merge_requests/628). That
> exposes a new CMake option `KICAD_BUILD_I18N`, which defaults to on,
> that controls if the translations are built. When that option is ON,
> gettext is a required dependency and when it is off it is not
> needed. This change will require some people to modify their current
> build setup to disable the translations if they do not wish to build
> with gettext.
> 
> In that MR I have also added the linux metadata files to the
> translation framework to allow for the strings contained inside them
> to be internationalized (so that the user sees translated strings on
> desktop icons/tooltips in their display manager). That should be a
> transparent change to the packagers of nightly builds, but a welcome
> change for users.
> 
> -Ian
> 
> 
> ___
> 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 Packaging heads up

[Jean-Samuel Reynaud]

On my side (ppa Ubuntu) I see an impact on the nightly builds package since
I produce renamed desktop files. I'll check that point as soon as possible.

Le mer. 20 janv. 2021 à 18:35, Seth Hillbrand  a écrit :

> This is a heads up for our Linux packagers that the launcher locations
> have changed in the master branch.
>
> You will now find the .desktop launcher files in the build directory,
> under `resources/linux/launchers/`
>
> -Seth
>
> --
> [image: KiCad Services Corporation Logo]
> Seth Hillbrand
> *Lead Developer*
> +1-530-302-5483‬
> Long Beach, CA
> www.kipro-pcb.comi...@kipro-pcb.com
> ___
> 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.9 tagged for release

[Jean-Samuel Reynaud]

PPA is currently building. Should be ok in 1 or 2 hours.

Le 22/12/2020 à 23:01, Nick Østergaard a écrit :
> I don't think we need that long. Everything seems to be tagged. I have
> triggered the windows build and it should just be a simple pkgver bump
> for macos and ubuntu ppa as well.
> 
> 
> On Tue, 22 Dec 2020 at 21:14, Wayne Stambaugh  wrote:
>>
>> 5.1.9 has been tagged for release. Please tag the library, doc, and
>> translation repos for release. I don't think we have much in the way of
>> changes there so is a week to get these repos tagged and another week to
>> get packages built for a January 5th release work for everyone?  Please
>> let me know an I will adjust the release schedule accordingly.  As
>> always, thank you to everyone who made this 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
> 


___
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.7 tagged.

[Jean-Samuel Reynaud]

FYI Ubuntu builds (PPA) are ready.

Le 25/09/2020 à 22:10, Wayne Stambaugh a écrit :
> I just pushed the 5.1.7 tagged commit to GitLab.  How are we doing on
> tagging the libraries, docs, and translations.  I would like to make the
> release announcement either 9/30 or 10/1 if possible.  Thank you to all
> of our developers who made this 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] 5.1.6 Release Update

[Jean-Samuel Reynaud]

KiCad 5.1.6 is now available on Ubuntu PPA since 2 days.

And some statistics on May 2020:

By Ubuntu version (only for 5.1 download):
Focal (20.04)  499.00 ( 8%)
Eoan (19.10)   389.00 ( 6%)
Bionic (18.04)4753.00 (76%)
Xenial (16.04) 582.00 ( 9%)
Totals6223.00





Le 15/05/2020 à 04:56, Adam Wolf a écrit :
> Mac builds have been uploaded, just the same as all the other 5.1
> releases.  Have a good weekend, everyone!
> 
> On Wed, May 13, 2020 at 3:48 PM Kevin Cozens  wrote:
>>
>> On 2020-05-13 4:11 p.m., Rene Pöschl wrote:
>>> You must pull the tagged commit otherwise you get whatever got merged last.
>>
>> Ok, thank you. With the v6 libraries no longer compatible with v5 I was
>> expecting to see a branch, not just a tag. Does this mean the v5 libraries
>> are no longer being maintained or will they be branched later if a change is
>> required to a v5 library?
>>
>> --
>> Cheers!
>>
>> Kevin.
>>
>> http://www.ve3syb.ca/   | "Nerds make the shiny things that
>> https://www.patreon.com/KevinCozens | distract the mouth-breathers, and
>>  | that's why we're powerful"
>> Owner of Elecraft K2 #2172  |
>> #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

Re: [Kicad-developers] 5.1.5 release tag

[Jean-Samuel Reynaud]

And there is already 1200 downloads since yesterday...

Le 20/11/2019 à 17:17, Jean-Samuel Reynaud a écrit :
> Hi All,
> 
> Version 5.1.5 are now available on the PPA (ubuntu).
> 
> 
> Le 18/11/2019 à 12:06, Nick Østergaard a écrit :
>> Everything is tagged.
>>
>> @adam, you should be able to bump the macos releases as well.
>>
>> søn. 17. nov. 2019 17.57 skrev Rene Pöschl > <mailto:poesc...@gmail.com>>:
>>
>> Libraries have been tagged.
>>
>> On 14/11/2019 18:36, Wayne Stambaugh wrote:
>> > The 5.1 branch has been tagged for 5.1.5 and the source archive has be
>> > uploaded to launchpad.  Please tag the library, doc, and translation
>> > repos so we can fire up those packages builders.
>> >
>> > Thanks,
>> >
>> > Wayne
>> >
>> > On 11/13/19 3:55 PM, Wayne Stambaugh wrote:
>> >> It's been a couple of weeks since 5.1.5-rc1 was tagged and everything
>> >> seems to have stabilized nicely.  I'm going to tag 5.1.5 tomorrow
>> around
>> >> noon EST unless something comes up.  I'm assuming the libraries,
>> >> documentation, and translations are ready to go and that it shouldn't
>> >> take too long to get most of the installer packages build and
>> uploaded
>> >> to the KiCad website.  I would like to make the release
>> announcement on
>> >> Wednesday, November 27th.  It would be something to be thankful for
>> >> leading into the US Thanksgiving Holiday.  If there are any
>> issues with
>> >> this date, please let me know.  Thank you everyone for your continued
>> >> support of the KiCad project.
>> >>
>> >> Cheers,
>> >>
>> >> Wayne
>> >>
>> > ___
>> > 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
>>
> 


___
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.5 release tag

[Jean-Samuel Reynaud]

Hi All,

Version 5.1.5 are now available on the PPA (ubuntu).


Le 18/11/2019 à 12:06, Nick Østergaard a écrit :
> Everything is tagged.
> 
> @adam, you should be able to bump the macos releases as well.
> 
> søn. 17. nov. 2019 17.57 skrev Rene Pöschl  >:
> 
> Libraries have been tagged.
> 
> On 14/11/2019 18:36, Wayne Stambaugh wrote:
> > The 5.1 branch has been tagged for 5.1.5 and the source archive has be
> > uploaded to launchpad.  Please tag the library, doc, and translation
> > repos so we can fire up those packages builders.
> >
> > Thanks,
> >
> > Wayne
> >
> > On 11/13/19 3:55 PM, Wayne Stambaugh wrote:
> >> It's been a couple of weeks since 5.1.5-rc1 was tagged and everything
> >> seems to have stabilized nicely.  I'm going to tag 5.1.5 tomorrow
> around
> >> noon EST unless something comes up.  I'm assuming the libraries,
> >> documentation, and translations are ready to go and that it shouldn't
> >> take too long to get most of the installer packages build and
> uploaded
> >> to the KiCad website.  I would like to make the release
> announcement on
> >> Wednesday, November 27th.  It would be something to be thankful for
> >> leading into the US Thanksgiving Holiday.  If there are any
> issues with
> >> this date, please let me know.  Thank you everyone for your continued
> >> support of the KiCad project.
> >>
> >> 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] Kicad support for Linux on PPC

[Jean-Samuel Reynaud]

Hi,

Best way it step 0 (backup) then step 2 (adding ppa and install kicad
5.1 over v4). Normaly there is no complicts. By using "apt full-upgrade"
once ppa is added, kicad should be upgraded.

Tell me.

For next reply, no need to put developers list in copy ;) I'll help you
directly..

Thanks,
Le 29/08/2019 à 13:32, Gianluca Renzi a écrit :
> Ok, thanks!
> I will give it a try on my PPC64 machine!
> 
> I have a question: at the moment I have on PPC64 ubuntu 16.04 and Kicad
> 4 installed from ubuntu packages. In the same machine I have compiled
> from sources (as the patches of mine) Kicad 5 and installed in a
> different path /opt/kicad-5 . Which is the best option?
> 
> 0- backup of my projects made with Kicad 4
> 
> 1- Remove Kicad 4 as Ubuntu package (apt remove ...)
>     Add your ppa
>     Install kicad-5.1 from your repo
>     Hope for the best for converting from 4 to 5.
> 
> 2- Add your ppa
>    Install kicad-5.1 over the version 4
>    Hope for the best for converting from 4 to 5
> 
> 3- Compile 5.1 from sources and install it in another path /opt/kicad-5.1
> 
> What do you think?
> 
> Best regards,
> Gianluca
> 
> On Thu, Aug 29, 2019 at 10:15 AM Jean-Samuel Reynaud
> mailto:js.reyn...@gmail.com>> wrote:
> 
> On Ubuntu 19.04, this is version 5.0.2 by default (but not available for
> PPC). Instead of recompiling, you can also use ppa
> (ppa:js-reynaud/kicad-5.1) but only for PPC64.
> 
> Regards,
> 
> Le 29/08/2019 à 09:49, Gianluca Renzi a écrit :
> > Ok, I will do that.
> > This evening I will have a look on what is installed by default on
>     > Ubuntu 19.04. Otherwise I will compile V5.1 from scratch.
> >
> > Regards,
> >
> > On Thu, Aug 29, 2019 at 9:43 AM Jean-Samuel Reynaud
> > mailto:js.reyn...@gmail.com>
> <mailto:js.reyn...@gmail.com <mailto:js.reyn...@gmail.com>>> wrote:
> >
> >     Dear Gianluca,
> >
> >     KiCad V4 is really old. For me it's not a good idea to provide
> packages
> >     on new distributions (not even sure that it will compile without
> >     patches...). Normaly, you can convert your work (keep a backup
> >     somewhere..) to V5 or better V5.1.
> >     As far as I remember, KiCad V5.1 is able to open V4 project, then
> >     convert it.
> >
> >     Regards,
> >     Le 28/08/2019 à 20:26, Gianluca Renzi a écrit :
> >     > Hello guys!
> >     > I hope everything is going well.
> >     > I have a request for Jean: I see you have the kicad 4
> package up to
> >     > ubuntu 18.04. Great work indeed!
> >     > In those days I got a new laptop running ubuntu 19.04 and it
> is a
> >     x86_64
> >     > based.
> >     > I was wondering if you can have kicad 4 for this ubuntu 19.04.
> >     Yesterday
> >     > I tried to compile from sources but it fails due to:
> >     > Make Error at CMakeModules/CheckCXXSymbolExists.cmake:41
> >     > (_CHECK_SYMBOL_EXISTS):
> >     >   Unknown CMake command "_CHECK_SYMBOL_EXISTS".
> >     > Call Stack (most recent call first):
> >     >   CMakeModules/PerformFeatureChecks.cmake:86
> (check_cxx_symbol_exists)
> >     >   CMakeLists.txt:141 (perform_feature_checks)
> >     >
> >     >
> >     > -- Configuring incomplete, errors occurred!
> >     > See also
> >     >
> >   
>  
> "/home/debian/packages/kicad-source-mirror-4.0/build/CMakeFiles/CMakeOutput.log".
> >     >
> >     > The biggest issue here I want to got all my work done in kicad 4
> >     > (installed in $HOME) then download the official ubuntu
> package then
> >     > convert everything to kicad 5.
> >     > Is it possible?
> >     >
> >     > Regards,
> >     > Gianluca
> >     >
> >     > On Mon, Feb 18, 2019 at 2:41 PM Gianluca Renzi
> mailto:icj...@gmail.com>
> >     <mailto:icj...@gmail.com <mailto:icj...@gmail.com>>
> >     > <mailto:icj...@gmail.com <mailto:icj...@gmail.com>
> <mailto:icj...@gmail.com <mailto:icj...@gmail.com>>>> wrote:
> >     >
> >     >     Great, thanks!
> >     >
> >     >     On Mon, Feb 18, 2019 at 2:40 PM Seth Hillbrand
> >     mailto:s...@hillbrand.org>
> <mailto:s...

Re: [Kicad-developers] Kicad support for Linux on PPC

[Jean-Samuel Reynaud]

On Ubuntu 19.04, this is version 5.0.2 by default (but not available for
PPC). Instead of recompiling, you can also use ppa
(ppa:js-reynaud/kicad-5.1) but only for PPC64.

Regards,

Le 29/08/2019 à 09:49, Gianluca Renzi a écrit :
> Ok, I will do that.
> This evening I will have a look on what is installed by default on
> Ubuntu 19.04. Otherwise I will compile V5.1 from scratch.
> 
> Regards,
> 
> On Thu, Aug 29, 2019 at 9:43 AM Jean-Samuel Reynaud
> mailto:js.reyn...@gmail.com>> wrote:
> 
> Dear Gianluca,
> 
> KiCad V4 is really old. For me it's not a good idea to provide packages
> on new distributions (not even sure that it will compile without
> patches...). Normaly, you can convert your work (keep a backup
> somewhere..) to V5 or better V5.1.
> As far as I remember, KiCad V5.1 is able to open V4 project, then
> convert it.
> 
> Regards,
> Le 28/08/2019 à 20:26, Gianluca Renzi a écrit :
> > Hello guys!
> > I hope everything is going well.
> > I have a request for Jean: I see you have the kicad 4 package up to
> > ubuntu 18.04. Great work indeed!
> > In those days I got a new laptop running ubuntu 19.04 and it is a
> x86_64
> > based.
> > I was wondering if you can have kicad 4 for this ubuntu 19.04.
> Yesterday
> > I tried to compile from sources but it fails due to:
> > Make Error at CMakeModules/CheckCXXSymbolExists.cmake:41
> > (_CHECK_SYMBOL_EXISTS):
> >   Unknown CMake command "_CHECK_SYMBOL_EXISTS".
> > Call Stack (most recent call first):
> >   CMakeModules/PerformFeatureChecks.cmake:86 (check_cxx_symbol_exists)
> >   CMakeLists.txt:141 (perform_feature_checks)
> >
> >
> > -- Configuring incomplete, errors occurred!
> > See also
> >
> 
> "/home/debian/packages/kicad-source-mirror-4.0/build/CMakeFiles/CMakeOutput.log".
> >
> > The biggest issue here I want to got all my work done in kicad 4
> > (installed in $HOME) then download the official ubuntu package then
> > convert everything to kicad 5.
> > Is it possible?
> >
> > Regards,
> > Gianluca
> >
> > On Mon, Feb 18, 2019 at 2:41 PM Gianluca Renzi  <mailto:icj...@gmail.com>
> > <mailto:icj...@gmail.com <mailto:icj...@gmail.com>>> wrote:
> >
> >     Great, thanks!
> >
> >     On Mon, Feb 18, 2019 at 2:40 PM Seth Hillbrand
> mailto:s...@hillbrand.org>
> >     <mailto:s...@hillbrand.org <mailto:s...@hillbrand.org>>> wrote:
> >
> >         Am 2019-02-11 10:39, schrieb Jean-Samuel Reynaud:
> >         > Dear all,
> >         >
> >         >  Please find attached a patch to adding missing support
> for Linux
> >         > platform on arch PPC and PPC64.
> >         >  It's proposed by an external user who need that...
> >         >
> >         >
> >         > Regards,
> >
> >         This patch has been pushed to the KiCad source tree. 
> Thank you
> >         Jean-Samuel and Gianluca!
> >
> >         -S
> >
> >
> >
> >     --
> >     Ciao e buona giornata.
> >
> >     "GP! In mezzo al campo stai proprio schifoso!"
> >     Coach M.Russo
> >
> >
> >
> > --
> > Ciao e buona giornata.
> >
> > "GP! In mezzo al campo stai proprio schifoso!"
> > Coach M.Russo
> 
> 
> 
> -- 
> Ciao e buona giornata.
> 
> "GP! In mezzo al campo stai proprio schifoso!"
> Coach M.Russo


___
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 support for Linux on PPC

[Jean-Samuel Reynaud]

Dear Gianluca,

KiCad V4 is really old. For me it's not a good idea to provide packages
on new distributions (not even sure that it will compile without
patches...). Normaly, you can convert your work (keep a backup
somewhere..) to V5 or better V5.1.
As far as I remember, KiCad V5.1 is able to open V4 project, then
convert it.

Regards,
Le 28/08/2019 à 20:26, Gianluca Renzi a écrit :
> Hello guys!
> I hope everything is going well.
> I have a request for Jean: I see you have the kicad 4 package up to
> ubuntu 18.04. Great work indeed!
> In those days I got a new laptop running ubuntu 19.04 and it is a x86_64
> based.
> I was wondering if you can have kicad 4 for this ubuntu 19.04. Yesterday
> I tried to compile from sources but it fails due to:
> Make Error at CMakeModules/CheckCXXSymbolExists.cmake:41
> (_CHECK_SYMBOL_EXISTS):
>   Unknown CMake command "_CHECK_SYMBOL_EXISTS".
> Call Stack (most recent call first):
>   CMakeModules/PerformFeatureChecks.cmake:86 (check_cxx_symbol_exists)
>   CMakeLists.txt:141 (perform_feature_checks)
> 
> 
> -- Configuring incomplete, errors occurred!
> See also
> "/home/debian/packages/kicad-source-mirror-4.0/build/CMakeFiles/CMakeOutput.log".
> 
> The biggest issue here I want to got all my work done in kicad 4
> (installed in $HOME) then download the official ubuntu package then
> convert everything to kicad 5.
> Is it possible?
> 
> Regards,
> Gianluca
> 
> On Mon, Feb 18, 2019 at 2:41 PM Gianluca Renzi  <mailto:icj...@gmail.com>> wrote:
> 
> Great, thanks!
> 
> On Mon, Feb 18, 2019 at 2:40 PM Seth Hillbrand  <mailto:s...@hillbrand.org>> wrote:
> 
> Am 2019-02-11 10:39, schrieb Jean-Samuel Reynaud:
> > Dear all,
> >
> >  Please find attached a patch to adding missing support for Linux
> > platform on arch PPC and PPC64.
> >  It's proposed by an external user who need that...
> >
> >
> > Regards,
> 
> This patch has been pushed to the KiCad source tree.  Thank you
> Jean-Samuel and Gianluca!
> 
> -S
> 
> 
> 
> -- 
> Ciao e buona giornata.
> 
> "GP! In mezzo al campo stai proprio schifoso!"
> Coach M.Russo
> 
> 
> 
> -- 
> Ciao e buona giornata.
> 
> "GP! In mezzo al campo stai proprio schifoso!"
> Coach M.Russo


___
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.3 release

[Jean-Samuel Reynaud]

For Ubuntu packages (ppa) it's ok everything is built since few days.

Regards

Le ven. 2 août 2019 à 17:08, Wayne Stambaugh  a
écrit :

> 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

Re: [Kicad-developers] 5.1.3 tagged

[Jean-Samuel Reynaud]

PPA is in progress:

kicad him self is ready (binary package)

Libraries are building (should be ready in few hours).

Waiting for tag of doc and i18n.

Regards,
Le 23/07/2019 à 18:37, Rene Pöschl a écrit :
> Libraries are tagged.
> 
> On 23/07/19 14:32, Wayne Stambaugh wrote:
>> I just tagged 5.1.3 and uploaded the source archive to launchpad.
>> Please tag the doc, translation, and library repos so we can get the
>> package builders going.  Thank you everyone for your continued support
>> of the KiCad project.
>>
>> 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] 5.1.1 release reminder.

[Jean-Samuel Reynaud]

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
> > >     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:

Re: [Kicad-developers] 5.1.1 release reminder.

[Jean-Samuel Reynaud]

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
>> 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.1 release reminder.

[Jean-Samuel Reynaud]

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
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.0 tag

[Jean-Samuel Reynaud]

Hi Pedro,

According to your version info you use Ubuntu version 14.04.
Based on this version py3 is not available because wx is not available
on py3 for this version.
You have to upgrade to 18.04 for that...

Regards,
Le 12/03/2019 à 20:21, Pedro Martin a écrit :
> Hi Jean-Samuel and All,
> 
> I have successfully installed v5.1.0 from ppa. Thanks for your fast
> support!
> 
> One of the new features is Pcbnew scripting support for Python 3  but in
> the version info KICAD_SCRIPTING_PYTHON3 is off.
> 
> Is this compilation alright?
> 
> Regards,
> Pedro.
> 
> 
> Application: kicad
> Version: 5.1.0-060a0da~80~ubuntu14.04.1, release build
> Libraries:
>     wxWidgets 3.0.2
>     libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3
> Platform: Linux 3.16.0-77-generic x86_64, 64 bit, Little endian, wxGTK
> Build Info:
>     wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
>     Boost: 1.54.0
>     Curl: 7.35.0
>     Compiler: GCC 4.8.4 with C++ ABI 1002
> 
> Build settings:
>     USE_WX_GRAPHICS_CONTEXT=OFF
>     USE_WX_OVERLAY=OFF
>     KICAD_SCRIPTING=ON
>     KICAD_SCRIPTING_MODULES=ON
>     KICAD_SCRIPTING_PYTHON3=OFF
>     KICAD_SCRIPTING_WXPYTHON=ON
>     KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
>     KICAD_SCRIPTING_ACTION_MENU=ON
>     BUILD_GITHUB_PLUGIN=ON
>     KICAD_USE_OCE=OFF
>     KICAD_USE_OCC=OFF
>     KICAD_SPICE=ON
> 
> 
> El 12/3/19 a las 15:41, Jean-Samuel Reynaud escribió:
>> You are true. It's missing. I have added packages. Copy is in progress...
>>
>> Le mar. 12 mars 2019 à 13:20, jack ma > <mailto:assang...@gmail.com>> a écrit :
>>
>>     There is no libngspice-kicad in
>>     https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-5.1 ?
>>
>>     Jean-Samuel Reynaud >     <mailto:js.reyn...@gmail.com>> 于2019年3月12日周二 下午7:08写道：
>>
>>     Just to confirm that packages on ppa dedicated to this new
>>     version (for
>>     Linux ubuntu) are now ready.
>>     I have a pending PR on the web site with instructions to use
>>     this new
>>     ppa for KiCad 5.1.
>>
>>     FYI I have an issue on building doc on version "Disco" (next
>>     release of
>>     ubuntu ie 19.04). I'm working on it to find a workarround (and
>>     propose a
>>     correction if needed).
>>
>>     Regards,
>>     Le 05/03/2019 à 01:20, Wayne Stambaugh a écrit :
>>  > Now that all of the confirmed high priority bugs have been
>>     addressed, we
>>  > should push all low priority bugs fixes to 5.1.1 unless there
>>     is no
>>  > possibility of breaking anything.  If nothing serious shows
>>     up in the
>>  > next few days, I'll tag 5.1.0 on Friday.  All of library,
>>     doc, and
>>  > translation devs should be ready to tag on Friday if possible
>>     so we can
>>  > get the packages built and uploaded to the website.  If you
>>     cannot make
>>  > this happen, please let me know.
>>  >
>>  > Cheers,
>>  >
>>  > Wayne
>>  >
>>  > ___
>>  > 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
>>


___
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 tag

[Jean-Samuel Reynaud]

You are true. It's missing. I have added packages. Copy is in progress...

Le mar. 12 mars 2019 à 13:20, jack ma  a écrit :

> There is no libngspice-kicad in
> https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-5.1 ?
>
> Jean-Samuel Reynaud  于2019年3月12日周二 下午7:08写道：
>
>> Just to confirm that packages on ppa dedicated to this new version (for
>> Linux ubuntu) are now ready.
>> I have a pending PR on the web site with instructions to use this new
>> ppa for KiCad 5.1.
>>
>> FYI I have an issue on building doc on version "Disco" (next release of
>> ubuntu ie 19.04). I'm working on it to find a workarround (and propose a
>> correction if needed).
>>
>> Regards,
>> Le 05/03/2019 à 01:20, Wayne Stambaugh a écrit :
>> > Now that all of the confirmed high priority bugs have been addressed, we
>> > should push all low priority bugs fixes to 5.1.1 unless there is no
>> > possibility of breaking anything.  If nothing serious shows up in the
>> > next few days, I'll tag 5.1.0 on Friday.  All of library, doc, and
>> > translation devs should be ready to tag on Friday if possible so we can
>> > get the packages built and uploaded to the website.  If you cannot make
>> > this happen, 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

Re: [Kicad-developers] 5.1.0 tag

[Jean-Samuel Reynaud]

Just to confirm that packages on ppa dedicated to this new version (for
Linux ubuntu) are now ready.
I have a pending PR on the web site with instructions to use this new
ppa for KiCad 5.1.

FYI I have an issue on building doc on version "Disco" (next release of
ubuntu ie 19.04). I'm working on it to find a workarround (and propose a
correction if needed).

Regards,
Le 05/03/2019 à 01:20, Wayne Stambaugh a écrit :
> Now that all of the confirmed high priority bugs have been addressed, we
> should push all low priority bugs fixes to 5.1.1 unless there is no
> possibility of breaking anything.  If nothing serious shows up in the
> next few days, I'll tag 5.1.0 on Friday.  All of library, doc, and
> translation devs should be ready to tag on Friday if possible so we can
> get the packages built and uploaded to the website.  If you cannot make
> this happen, 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] Kicad support for Linux on PPC

[Jean-Samuel Reynaud]

Hi all,

Please find attached a last (I hope) patch for PPC64 compilation issues...

Regards,
Le 20/02/2019 à 16:00, Wayne Stambaugh a écrit :
> Hi Jean-Samuel,
> 
> I merged your patch into the dev branch.  Thank you for your
> contribution to KiCad.
> 
> Cheers,
> 
> Wayne
> 
> On 2/20/2019 8:18 AM, Jean-Samuel Reynaud wrote:
>> Dear All,
>>
>> Following this patch application, please find attached a small patch to
>> fix compilation issue on PPC64 (PPC32 was ok).
>>
>> Regards,
>>
>> Le 18/02/2019 à 14:40, Seth Hillbrand a écrit :
>>> Am 2019-02-11 10:39, schrieb Jean-Samuel Reynaud:
>>>> Dear all,
>>>>
>>>>  Please find attached a patch to adding missing support for Linux
>>>> platform on arch PPC and PPC64.
>>>>  It's proposed by an external user who need that...
>>>>
>>>>
>>>> Regards,
>>>
>>> This patch has been pushed to the KiCad source tree.  Thank you
>>> Jean-Samuel and Gianluca!
>>>
>>> -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
> 

>From b4afe381e5bc5730bda1804cd1b0c0e8d0b52478 Mon Sep 17 00:00:00 2001
From: Jean-Samuel Reynaud 
Date: Wed, 27 Feb 2019 13:41:02 +0100
Subject: [PATCH] Fix another compilation issue on PPC64
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2.7.4"

This is a multi-part message in MIME format.
--2.7.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit

---
 include/system/libcontext.h | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)


--2.7.4
Content-Type: text/x-patch; name="0001-Fix-another-compilation-issue-on-PPC64.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0001-Fix-another-compilation-issue-on-PPC64.patch"

diff --git a/include/system/libcontext.h b/include/system/libcontext.h
index 2cd0482..8045fa2 100644
--- a/include/system/libcontext.h
+++ b/include/system/libcontext.h
@@ -46,8 +46,7 @@
 #ifdef _ARCH_PPC64
 #define LIBCONTEXT_PLATFORM_linux_ppc64
 #define LIBCONTEXT_CALL_CONVENTION
-#endif
-#ifdef _ARCH_PPC
+#elif defined _ARCH_PPC
 #define LIBCONTEXT_PLATFORM_linux_ppc32
 #define LIBCONTEXT_CALL_CONVENTION
 #endif

--2.7.4--


___
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 support for Linux on PPC

[Jean-Samuel Reynaud]

Dear All,

Following this patch application, please find attached a small patch to
fix compilation issue on PPC64 (PPC32 was ok).

Regards,

Le 18/02/2019 à 14:40, Seth Hillbrand a écrit :
> Am 2019-02-11 10:39, schrieb Jean-Samuel Reynaud:
>> Dear all,
>>
>>  Please find attached a patch to adding missing support for Linux
>> platform on arch PPC and PPC64.
>>  It's proposed by an external user who need that...
>>
>>
>> Regards,
> 
> This patch has been pushed to the KiCad source tree.  Thank you
> Jean-Samuel and Gianluca!
> 
> -S

>From 4ce597bd0a1cfe36eae92f7abac1ca23bf0b0b22 Mon Sep 17 00:00:00 2001
From: Jean-Samuel Reynaud 
Date: Wed, 20 Feb 2019 14:15:26 +0100
Subject: [PATCH] Fix compilation issue on PPC64
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2.7.4"

This is a multi-part message in MIME format.
--2.7.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit

---
 common/system/libcontext.cpp | 62 ++--
 1 file changed, 31 insertions(+), 31 deletions(-)


--2.7.4
Content-Type: text/x-patch; name="0001-Fix-compilation-issue-on-PPC64.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0001-Fix-compilation-issue-on-PPC64.patch"

diff --git a/common/system/libcontext.cpp b/common/system/libcontext.cpp
index 17f656e..f6f83ce 100644
--- a/common/system/libcontext.cpp
+++ b/common/system/libcontext.cpp
@@ -1011,24 +1011,24 @@ __asm (
 #if defined(LIBCONTEXT_PLATFORM_linux_ppc64) && defined(LIBCONTEXT_COMPILER_gcc)
 __asm (
 ".globl jump_fcontext\n"
-"#if _CALL_ELF == 2\n"
+#if _CALL_ELF == 2
 "  .text\n"
 "  .align 2\n"
 "jump_fcontext:\n"
 "addis   %r2, %r12, .TOC.-jump_fcontext@ha\n"
 "addi%r2, %r2, .TOC.-jump_fcontext@l\n"
 ".localentry jump_fcontext, . - jump_fcontext\n"
-"#else\n"
+#else
 "  .section \".opd\",\"aw\"\n"
 "  .align 3\n"
 "jump_fcontext:\n"
-"# ifdef _CALL_LINUX\n"
+# ifdef _CALL_LINUX
 ".quad   .L.jump_fcontext,.TOC.@tocbase,0\n"
 ".type   jump_fcontext,@function\n"
 ".text\n"
 ".align 2\n"
 ".L.jump_fcontext:\n"
-"# else\n"
+# else
 ".hidden .jump_fcontext\n"
 ".globl  .jump_fcontext\n"
 ".quad   .jump_fcontext,.TOC.@tocbase,0\n"
@@ -1037,13 +1037,13 @@ __asm (
 ".text\n"
 ".align 2\n"
 ".jump_fcontext:\n"
-"# endif\n"
-"#endif\n"
+# endif
+#endif
 "# reserve space on stack\n"
 "subi  %r1, %r1, 328\n"
-"#if _CALL_ELF != 2\n"
+#if _CALL_ELF != 2
 "std  %r2,  152(%r1)  # save TOC\n"
-"#endif\n"
+#endif
 "std  %r14, 160(%r1)  # save R14\n"
 "std  %r15, 168(%r1)  # save R15\n"
 "std  %r16, 176(%r1)  # save R16\n"
@@ -1122,9 +1122,9 @@ __asm (
 "lfd  %f0,  144(%r1)  # load FPSCR\n"
 "mtfsf  0xff, %f0  # restore FPSCR\n"
 "2:\n"
-"#if _CALL_ELF != 2\n"
+#if _CALL_ELF != 2
 "ld  %r2,  152(%r1)  # restore TOC\n"
-"#endif\n"
+#endif
 "ld  %r14, 160(%r1)  # restore R14\n"
 "ld  %r15, 168(%r1)  # restore R15\n"
 "ld  %r16, 176(%r1)  # restore R16\n"
@@ -1160,15 +1160,15 @@ __asm (
 "mr  %r3, %r5\n"
 "# jump to context\n"
 "bctr\n"
-"#if _CALL_ELF == 2\n"
+#if _CALL_ELF == 2
 "  .size jump_fcontext, .-jump_fcontext\n"
-"#else\n"
-"# ifdef _CALL_LINUX\n"
+#else
+# ifdef _CALL_LINUX
 "  .size .jump_fcontext, .-.L.jump_fcontext\n"
-"# else\n"
+# else
 "  .size .jump_fcontext, .-.jump_fcontext\n"
-"# endif\n"
-"#endif\n"
+# endif
+#endif
 ".section .note.GNU-stack,\"\",%progbits\n"
 );
 
@@ -1177,24 +1177,24 @@ __asm (
 #if defined(LIBCONTEXT_PLATFORM_linux_ppc64) && defined(LIBCONTEXT_COMPILER_gcc)
 __asm (
 ".globl make_fcontext\n"
-"#if _CALL_ELF == 2\n"
+#if _CALL_ELF == 2
 "  .text\n"
 "  .align 2\n"
 "make_fcontext:\n"
 "  addis   %r2, %r12, .TOC.-make_fcontext@ha\n"
 "  addi%r2, %r2, .TOC.-make_fcontext@l\n"
 "  .localentry make_fcontext, . - make_fcontext\n"
-"#else\n"
+#else
 "  .section \".opd\",\"aw\"\n"
 "  .align 3\n"
 "make_fcontext:\n"
-"# ifdef _CALL_LINUX\n"
+# ifdef _CALL_LINUX
 "  .quad   .L.make_fcontext,.TO

Re: [Kicad-developers] Kicad support for Linux on PPC

[Jean-Samuel Reynaud]

Hi,

According to the user that push to me that patch (Gianluca Renzi, a user
of the https://www.powerpc-notebook.org/ project), It's working
correctly and 3D look to be fast. So I assume that it's correct in term
of OpenGL configuration...

Regards,

Le 18/02/2019 à 10:23, Tomasz Wlostowski a écrit :
> On 17/02/2019 20:47, Wayne Stambaugh wrote:
>> Yes but I haven't heard back from Tom.  Since this is primarily his
>> code, I would like his input before I merge the PPC64 patch.
> 
> As I said in a similar thread about MIPS support, I'm not opposed to
> merge this, I'm just wondering if this PPC64 platform at least supports
> OpenGL 2.1, which is practically a must to use kicad 5.1.
> 
> 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

Re: [Kicad-developers] Kicad support for Linux on PPC

[Jean-Samuel Reynaud]

Is it possible to integrate that patch on rc2?

Thanks.

Le lun. 11 févr. 2019 à 18:18, Wayne Stambaugh  a
écrit :

> Nevermind.  I see you are just merging the PPC assembly code into
> libcontext.cpp which already has the Boost license.
>
> On 2/11/2019 11:14 AM, Jean-Samuel Reynaud wrote:
> > Hi
> >
> > As other arch on those files it was generated using :
> > https://github.com/twlostow/libcontext
> >
> > So for me it's exactly same copyright statement.
> >
> > Le 11/02/2019 à 17:00, Simon Richter a écrit :
> >> Hi,
> >>
> >> On 11.02.19 16:39, Jean-Samuel Reynaud wrote:
> >>
> >>>  Please find attached a patch to adding missing support for Linux
> >>> platform on arch PPC and PPC64.
> >>>  It's proposed by an external user who need that...
> >>
> >> Looks promising, but needs a copyright statement.
> >>
> >> If it is from Boost, we can include and relicence it like the other
> >> code, the Boost licence is permissive enough for that, but the author
> >> information needs to remain there; if it's new code (there aren't that
> >> many ways to do context switches anyway), this still needs attribution.
> >>
> >>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
>
___
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-rc1

[Jean-Samuel Reynaud]

Yes I'm preparing an announce on the forum to get more coverage ...


Le 11/02/2019 à 17:14, Wayne Stambaugh a écrit :
> Hi Jean-Samuel,
> 
> Thanks for providing packages with python3 and wxpython4 enabled.  This
> will help improve our test coverage.
> 
> Cheers,
> 
> Wayne
> 
> On 2/11/2019 11:11 AM, Jean-Samuel Reynaud wrote:
>> Dear All,
>>
>> PPA for KiCad 5.1 is now ready.
>> When it's possible (for example on Ubuntu Bionic) GTK 3 is used, python3
>> is enabled and WX4.0 too...
>>
>> Don't hesitate to report any issues on ppa.
>>
>> To use it:
>> sudo add-apt-repository ppa:js-reynaud/kicad-5.1
>> sudo apt-get update
>> sudo apt install kicad
>>
>> For the moment, as I see, no doc/templates/lib/footprint repo were tag
>> 5.1.0-rc1 yet...
>>
>> Note that for python plugins some refactoring can be needed when
>> migrating to python3. According to https://pythonclock.org/ perhaps it's
>> time to switch any plugins to python 3 ;)
>>
>>
>>
>>
>>
>> Le 08/02/2019 à 21:53, Marcos Chaparro a écrit :
>>> You are using GTK2 in this build.  Are you building yourself?  If so,
>>> you need to delete the existing build directory, create a new one and
>>> specify -DwxWidgets_CONFIG_OPTIONS="--toolkit=gtk3" in the cmake
>>> options.
>>>
>>>
>>> Its a nightly build
>>> from http://ppa.launchpad.net/js-reynaud/kicad-dev-nightly/ubuntu bionic
>>> main
>>>
>>> Will start a build now and see if it fixes it. Shouldn't the packaged
>>> deb for ubuntu bionic beaver (18.04) come with that cmake option set?
>>>
>>> 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
>>
> 
> ___
> 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 support for Linux on PPC

[Jean-Samuel Reynaud]

Hi

As other arch on those files it was generated using :
https://github.com/twlostow/libcontext

So for me it's exactly same copyright statement.

Le 11/02/2019 à 17:00, Simon Richter a écrit :
> Hi,
> 
> On 11.02.19 16:39, Jean-Samuel Reynaud wrote:
> 
>>  Please find attached a patch to adding missing support for Linux
>> platform on arch PPC and PPC64.
>>  It's proposed by an external user who need that...
> 
> Looks promising, but needs a copyright statement.
> 
> If it is from Boost, we can include and relicence it like the other
> code, the Boost licence is permissive enough for that, but the author
> information needs to remain there; if it's new code (there aren't that
> many ways to do context switches anyway), this still needs attribution.
> 
>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
> 




signature.asc
Description: OpenPGP digital signature
___
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-rc1

[Jean-Samuel Reynaud]

Dear All,

PPA for KiCad 5.1 is now ready.
When it's possible (for example on Ubuntu Bionic) GTK 3 is used, python3
is enabled and WX4.0 too...

Don't hesitate to report any issues on ppa.

To use it:
sudo add-apt-repository ppa:js-reynaud/kicad-5.1
sudo apt-get update
sudo apt install kicad

For the moment, as I see, no doc/templates/lib/footprint repo were tag
5.1.0-rc1 yet...

Note that for python plugins some refactoring can be needed when
migrating to python3. According to https://pythonclock.org/ perhaps it's
time to switch any plugins to python 3 ;)





Le 08/02/2019 à 21:53, Marcos Chaparro a écrit :
> You are using GTK2 in this build.  Are you building yourself?  If so,
> you need to delete the existing build directory, create a new one and
> specify -DwxWidgets_CONFIG_OPTIONS="--toolkit=gtk3" in the cmake
> options.
> 
> 
> Its a nightly build
> from http://ppa.launchpad.net/js-reynaud/kicad-dev-nightly/ubuntu bionic
> main
> 
> Will start a build now and see if it fixes it. Shouldn't the packaged
> deb for ubuntu bionic beaver (18.04) come with that cmake option set?
> 
> 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] Kicad support for Linux on PPC

[Jean-Samuel Reynaud]

Dear all,

 Please find attached a patch to adding missing support for Linux
platform on arch PPC and PPC64.
 It's proposed by an external user who need that...


Regards,

 Message transféré 
Sujet : Re: Kicad 5 PPA
Date :  Mon, 4 Feb 2019 13:18:24 +0100
De :Gianluca Renzi 
Pour :  Jean-Samuel Reynaud 



Thanks, I'll check it out.

On Mon, Feb 4, 2019 at 1:17 PM Jean-Samuel Reynaud mailto:js.reyn...@gmail.com>> wrote:

You have to follow the guideline there :

http://kicad-pcb.org/contribute/developers/

to propose your patch.

Regards,
Le 04/02/2019 à 12:13, Gianluca Renzi a écrit :
> Ok, thanks!
> I have already commited my changes to my local repo, but
git-send-email
> gives me NO OUTPUT. I followed the instructions to send the patch as
> email using git, but it does not work.
> Now???
>
> On Mon, Feb 4, 2019 at 12:04 PM Jean-Samuel Reynaud
> mailto:js.reyn...@gmail.com>
<mailto:js.reyn...@gmail.com <mailto:js.reyn...@gmail.com>>> wrote:
>
>     Hi,
>
>     Best way, now is to publish your KiCad modification to mailing
list.
>     Once done and accepted, PPA will automaticaly build it. It's
ready but
>     waiting for KiCad source ready for ppc...
>
>     Le 04/02/2019 à 10:01, Gianluca Renzi a écrit :
>     > Got it, thanks! 
>     > I solved removing all previous installation of wxpython and
>     wxwidget and
>     > re installing them with gtk2 and the correct stuff. The only
thing is
>     > the python installer put the wrong permission bits in a
subfolder of
>     > wxpython and simply it does not work.
>     > The slowness on 3d was due to the bad OpenGL library it uses
from
>     > ldconfig. Now it has an amazing speed!
>     > Kicad 5 & kicad 6 too!!!
>     >
>     > Shame on PPC users they lack PPA!
>     > Actually I do not know how to setup a PPA for them. Maybe it
should be
>     > great if someone help me out on creating the Deb package and the
>     > dependencies...
>     >
>     > Anyway thanks,
>     >
>     > Il giorno lun 4 feb 2019 09:25 Jean-Samuel Reynaud
>     mailto:js.reyn...@gmail.com>
<mailto:js.reyn...@gmail.com <mailto:js.reyn...@gmail.com>>
>     > <mailto:js.reyn...@gmail.com <mailto:js.reyn...@gmail.com>
<mailto:js.reyn...@gmail.com <mailto:js.reyn...@gmail.com>>>> ha
>     scritto:
>     >
>     >     Hi,
>     >
>     >     On my side, I install the following packages for dev
(extract from
>     >     debian/control):
>     >     debhelper (>= 6), cmake (>= 2.6.0), doxygen, libbz2-dev,
>     libcairo2-dev,
>     >     libglu1-mesa-dev, libgl1-mesa-dev, libglew-dev, libx11-dev,
>     >     libwxbase3.0-dev, libwxgtk3.0-dev, mesa-common-dev,
pkg-config,
>     >     libssl-dev, build-essential, cmake-curses-gui,
debhelper, grep,
>     >     python-wxgtk3.0, python-dev, swig3.0, python-wxgtk3.0-dev,
>     dblatex,
>     >     po4a, asciidoc, source-highlight, libboost-all-dev,
libglm-dev,
>     >     libcurl4-openssl-dev, libngspice-kicad,
liboce-foundation-dev,
>     >     liboce-modeling-dev, liboce-ocaf-lite-dev, liboce-ocaf-dev,
>     >     liboce-visualization-dev
>     >
>     >     It should miss something.
>     >
>     >
>     >     Le 03/02/2019 à 15:16, Gianluca Renzi a écrit :
>     >     > Hello Jean-Samuel,
>     >     > I was trying to build Kicad 5 from github sources, but I
>     messed up
>     >     > something with wxPython/wxWidget.
>     >     > I think I did the wrong commands like sudo python
setup blah
>     blah
>     >     install.
>     >     > Now kicad 5 configure cmake is not able to find
wxPython 3.1
>     anymore
>     >     > Even the kicad 6 configure cmake has the same issue.
>     >     > As I do not know python at all, maybe I am missing
something.
>     >     > The problem seems to be some access (staff group) or an
>     unknown module
>     >     > named wx:
>     >     >
>     >     > $ python
>     >     > Python 2.7.12 (default, Nov 12 2018, 14:36:49)
>     >     > [GCC 5.4.0 20160609] on linux2
>     >     > Type "help", "copyright", "credits" or "licen

Re: [Kicad-developers] 5.1.0-rc1

[Jean-Samuel Reynaud]

Just for information. I'm working on fixing ppa building issues for rc1.


Le ven. 8 févr. 2019 à 21:54, Marcos Chaparro  a
écrit :

> You are using GTK2 in this build.  Are you building yourself?  If so,
>> you need to delete the existing build directory, create a new one and
>> specify -DwxWidgets_CONFIG_OPTIONS="--toolkit=gtk3" in the cmake
>> options.
>>
>
> Its a nightly build from
> http://ppa.launchpad.net/js-reynaud/kicad-dev-nightly/ubuntu bionic main
>
> Will start a build now and see if it fixes it. Shouldn't the packaged deb
> for ubuntu bionic beaver (18.04) come with that cmake option set?
>
> 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

Re: [Kicad-developers] 5.1.0-rc1

[Jean-Samuel Reynaud]

Hi,

I have to take a look at that point ;) To try to use GTK3...

Le 06/02/2019 à 18:19, Seth Hillbrand a écrit :
> Am 2019-02-06 04:26, schrieb Jean-Samuel Reynaud:
>> Great news. By this way I created a dedicated PPA (Linux Ubuntu) for
>> this release:
>>
>> ppa:js-reynaud/kicad-5.1
> 
> Hi Jean-Samuel-
> 
> Will the 5.1 PPA build with GTK3?  I noticed that your PPA for 18.04 [1]
> is still building with GTK2 and wxpython off.
> 
> -Seth
> 
> [1]
> https://launchpadlibrarian.net/40162/buildlog_ubuntu-bionic-amd64.kicad_201902061447+5072298~84~ubuntu18.04.1_BUILDING.txt.gz
> 


___
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-rc1

[Jean-Samuel Reynaud]

Great news. By this way I created a dedicated PPA (Linux Ubuntu) for
this release:

ppa:js-reynaud/kicad-5.1


Le 05/02/2019 à 19:51, Wayne Stambaugh a écrit :
> I'm going to tag 5.1.0-rc1 this evening after I get home from work.
> There are still two low priority bugs against the 5.1.0-rc1 milestone
> left which I'm going to let slide and try to get them fixed by the
> stable release.  Hopefully we wont need an -rc2.
> 
> Unfortunately, this will break all of the linux distro package manager
> version handling because of our previous policy of tagging ahead for the
> next version.  I apologize up front for the issues this is going to
> cause.  This decision falls squarely on my shoulders.
> 
> The clock is ticking for the library, doc, and translation devs.  I
> would really like to get 5.1.0 released by the end of February.  This
> means the libraries, documentation, and translations would have to be
> tagged for 5.1.0 around 2/23 to give our package devs some time to get
> the packages built and uploaded to the website.  Please let me know if
> you cannot meet this date.
> 
> ___
> 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-pcb.org not reachable

[Jean-Samuel Reynaud]

On my side:
http://kicad-pcb.org is NOT working
but
http://www.kicad-pcb.org IS working...

They don't have the same address according to DNS:
$ host kicad-pcb.org
kicad-pcb.org has address 188.185.118.209
kicad-pcb.org has address 188.184.85.202
kicad-pcb.org has address 188.185.68.106
kicad-pcb.org mail is handled by 0 kicad-pcb.org.

$ host www.kicad-pcb.org
www.kicad-pcb.org is an alias for oonodelb.cern.ch.
oonodelb.cern.ch has address 188.185.82.144
oonodelb.cern.ch has address 188.184.28.138
oonodelb.cern.ch has address 188.184.93.89
oonodelb.cern.ch has IPv6 address 2001:1458:d00:e::100:8a
oonodelb.cern.ch has IPv6 address 2001:1458:201:e4::100:553
oonodelb.cern.ch has IPv6 address 2001:1458:d00:2e::100:34

Perhaps a configuration missing...

Le 05/02/2019 à 17:18, Rene Pöschl a écrit :
> It seems the kicad website is currently down.
> 
> 
> ___
> 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-dev-nightly PPA builds for artful outdated?

[Jean-Samuel Reynaud]

Dear Matthijs,

Launchpad doesn't support anymore build for artful. So it will no more
available.
Have you try Xenial PPA ? (not sure if it's working...)


Regards,
Le 11/12/2018 à 16:05, Matthijs Kooijman a écrit :
> Hey folks,
> 
> I've been trying to update to the latest nightly build, but it seems
> that the PPA has stopped building version for artful (17.10). The latest
> version is:
> 
> kicad  201807190649+829ba27~83~ubuntu17.10.1  js-reynaud (2018-07-19)
> 
> (from https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-dev-nightly)
> 
> The other distributions in the PPA have today's build available.
> 
> Was support for artful intentionally dropped, or is something wrong somewhere?
> I'm not quite how the process behind a PPA works, apparently.
> 
> I also looked at the build logs around the time of the last succesful
> build, and it seems there have been no (failing) attempts after that, so
> it looks like artful builds were just switched off?
> 
> I'm interested in the Artful build, since I'm running Debian/stable and artful
> seems to match stable best (installing bionic replaces libcurl3 with libcurl4,
> require an upgrade of half my system to testing...)
> 
> Any chance to get the artful builds up-to-date again? Anything I can do to 
> help?
> 
> Gr.
> 
> Matthijs
> 




signature.asc
Description: OpenPGP digital signature
___
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] Download stats?

[Jean-Samuel Reynaud]

Hi all,

I pick that old thread to give the following information:
I had put some download stats online. Those stats are ONLY for PPA (I
don't have any other sources). I'll try to keep those stats up-to-date...:
https://jsreynaud.github.io/

Initially I manually extract that data but now I have a daily cron ;)
Basically I use pivottable.js tools. No big code ...


Le 22/08/2018 à 00:22, Nick Østergaard a écrit :
> No we do not currently log downloads actively.
> Den man. 23. jul. 2018 kl. 05.03 skrev Adam Wolf
> :
>>
>> Do we capture download statistics on the file server at all?  It would
>> be really fun to see how many folks are downloading things.  I know it
>> is not an accurate representation of userbase, but I think it would
>> still be fun to see.
>>
>> If we do not, can someone turn up logging on it quickly so we can see
>> what downloads for for V5 look like?
>>
>> 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] KiCad 5 PPA does not have a kicad package for Ubuntu 18.10

[Jean-Samuel Reynaud]

Hi Seppe,

I'm currently working on that point... Should be ok soon...

Regards,
Le 17/10/2018 à 14:12, Seppe Stas a écrit :
> Hey Jean-Samuel and people dealing with the KiCad PPA / linux packaging
> 
> The "official" (at least it is the documented approach on how to install
> KiCad on Ubuntu <http://kicad-pcb.org/download/ubuntu/>) KiCad PPA does
> not have the a kicad package for Ubuntu 18.10 (Cosmic Cuttlefish). This
> means that installing KiCad on Ubuntu 18.10 will result in the kicad
> package from the mainline apt repository
> <https://packages.ubuntu.com/cosmic/kicad> to be installed, even if
> the js-reynaud/kicad-5 PPA was added to the repository list.
> 
> I wanted to report a bug for this
> on https://bugs.launchpad.net/~js-reynaud
> <https://bugs.launchpad.net/%7Ejs-reynaud> but this does not seem to be
> possible. Is this mailing list (and/or direct emails to Jean-Samuel
> Reynaud) the correct way to report issues with the PPA?
> 
> Geetings
> Seppe


___
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.0.1 release status.

[Jean-Samuel Reynaud]

Hi Wayne,

Yes the bug #1785377 affect also this release. Did I need to plan a
workarround to allow this build ?

Regards,
Le 15/10/2018 à 23:37, John Beard a écrit :
> Hi Wayne,
> 
> There was a commit on master made for this purpose: 9a3cfb857. The
> function is to remove a failing test and thereby avoid having to
> exclude it from the CTest harness, which doesn't work on old Boosts. I
> thought it was in v5, but it is evidently not (and git branch
> --contains concurs).
> 
> A simple cherry-pick should work.
> 
> Cheers,
> 
> John
> On Mon, Oct 15, 2018 at 7:03 PM Wayne Stambaugh  wrote:
>>
>> JS is on the mailing list.  I suspect he will reply soon.
>>
>> On 10/15/2018 1:59 PM, Ronnie Gaensli wrote:
>>> Hi all!
>>>
>>> I've been awaiting the 5.0.1 release to be officially available via the
>>> ppa of js-reynaud. Though unfortunatley there's an issue with the
>>> build: 
>>> https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-5/+build/15533528
>>> Actually it's the tests that cause the
>>> issue: 
>>> https://launchpadlibrarian.net/392947878/buildlog_ubuntu-trusty-amd64.kicad_5.0.1-stable-201810121506+33cea8e~66~ubuntu14.04.1_BUILDING.txt.gz
>>> at the very bottom
>>>
>>> I'm not yet in the position to tell the cause, but I would like raise
>>> awareness of this. Does Js-Reynaud read this here?, shall I contact him
>>> directly via launchpad, ? What best to do?
>>>
>>> Cheers
>>> Ronnie
>>>
>>>
>>> Am So., 14. Okt. 2018 um 19:43 Uhr schrieb Wayne Stambaugh
>>> mailto:stambau...@gmail.com>>:
>>>
>>> We will have to do the usual tagging of all of the repos with 5.0.2
>>> so I
>>> will have to wait to see if there any issues.  I shouldn't take very
>>> long so 5.0.1 may be a very short lived release.
>>>
>>> On 10/14/2018 01:13 PM, Adam Wolf wrote:
>>> > I think there are some 5.0.1s already up for download... Any issue
>>> just
>>> > going to 5.0.2?
>>> >
>>> > Adam
>>> >
>>> > On Sun, Oct 14, 2018, 11:05 AM Wayne Stambaugh
>>> mailto:stambau...@gmail.com>
>>> > >> wrote:
>>> >
>>> > I'm fine with pushing the release back another week.  I would
>>> rather not
>>> > release 5.0.1 with this bug.  We have a lot of ex-Eagle users and
>>> > breaking Eagle import is not good.  I see one of two options here.
>>> > Retag 5.0.1 with the current changes or release 5.0.2
>>> immediately.  I
>>> > don't know which is more work for our packagers so I am open
>>> to either
>>> > option.  Please let me know what works best for you and I will
>>> go with
>>> > that option.
>>> >
>>> > Cheers,
>>> >
>>> > Wayne
>>> >
>>> > On 10/14/2018 10:02 AM, Seth Hillbrand wrote:
>>> >  > Hi Wayne, et al-
>>> >  >
>>> >  > There is a critical bug that I introduced
>>> >  > with a5bdee747a59f80cf46f5aad5593aa4e1617b7c3  in 5.0.1.
>>> It affects
>>> >  > certain Eagle files imports and causes a crash.
>>> >  >
>>> >  > I've fixed this in the 5.0.2 tree.  I'm sorry for the extra
>>> problems.
>>> >  >
>>> >  > Between this and the footprint wizard, we may wish to
>>> announce a
>>> > 5.0.2
>>> >  > sooner rather than later.  Or packagers may wish to pull in the
>>> >  > post-5.0.2 tagged commits as patches to their builds before
>>> > announcement.
>>> >  >
>>> >  > -S
>>> >  >
>>> >  > Am Fr., 12. Okt. 2018 um 05:39 Uhr schrieb Wayne Stambaugh
>>> >  > mailto:stambau...@gmail.com>
>>> >
>>> > 
>>> >> >  >
>>> >  > Does anyone need more time to get packages built for the
>>> > 5.0.1 release?
>>> >  > I am hoping to release on Sunday if possible.  Please
>>> let me
>>> > know if you
>>> >  > need any additional time.
>>> >  >
>>> >  > Cheers,
>>> >  >
>>> >  > Wayne
>>> >  >
>>> >  > ___
>>> >  > Mailing list: https://launchpad.net/~kicad-developers
>>> > 
>>> >  > 
>>> >  > Post to : kicad-developers@lists.launchpad.net
>>> 
>>> > >> >
>>> >  > >> 
>>> > >> 

Re: [Kicad-developers] 5.0.1 release status.

[Jean-Samuel Reynaud]

PPA (Linux ubuntu). Should be ready tomorrow.

Le 12/10/2018 à 14:38, Wayne Stambaugh a écrit :
> Does anyone need more time to get packages built for the 5.0.1 release?
> I am hoping to release on Sunday if possible.  Please let me know if you
> need any additional time.
> 
> 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] Ubuntu PPA for Kicad 5: unmet dependencies

[Jean-Samuel Reynaud]

Yes for trusty there is an an update for WX to do since default WX
version is outdated in trusty. I copied those missing package on ppa for
kicad 4 but I forgot for 5.0. Im' gona to fix this now...


Le 12/09/2018 à 20:25, Kevin Cozens a écrit :
> On 2018-09-12 12:18 PM, Kaspar Emanuel wrote:
>> Looks like the issue might be that libwxgtk3 is at 3.0.0 in 14.04
>>  and KiCad wants 3.0.2
> 
> Yes, that would be the problem. You will either need a PPA for a newer
> version of wx or you will have to build and install a newer version.
> 


___
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] Nightly builds

[Jean-Samuel Reynaud]

Hi,

For Ubuntu I had added a ppa for dev versions (based on 5.0 branch):
https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-5-nightly

It should do the first build during next night...


Le 10/09/2018 à 15:49, Adam Wolf a écrit :
> I am setting up a macos one the same way.
> On Mon, Sep 10, 2018 at 7:30 AM Nick Østergaard  wrote:
>>
>> In addition to that I can note; that it follows the 5.0 branch for the
>> kicad source and the kicad-i18n, but is using the 5.0.0 tag for
>> everything else.
>> On Mon, 10 Sep 2018 at 14:29, Nick Østergaard  wrote:
>>>
>>> Hi Seth
>>>
>>> I have created them now, they are currently located in
>>> http://downloads.kicad-pcb.org/windows/testing/5.0/
>>>
>>> The installer naming is kicad-5.0-jenkins-${BUILD_ID}-x86_64.exe
>>>
>>> And the version string inside kicad is something like:
>>> Version: (5.0.1-dev-86-g7e8c5b957), release build
>>>
>>> It is not ideal, but should be good enough.
>>>
>>> Nick
>>> On Mon, 10 Sep 2018 at 11:11, Nick Østergaard  wrote:

 I will add it for the windows builds soon.

 I don't think there is a nightly PPA for the 5.0 branch yet, there was
 for the 4.0 branch for a period at least.
 On Sun, 9 Sep 2018 at 16:22, Seth Hillbrand  wrote:
>
> Hi All-
>
> Can we update the packaging scripts that produce nightly packages to also 
> make nightly builds of the 5.0 branch in addition to the master branch?  
> I worry that we may be getting close to 0 testing on this outside of the 
> few users who build their own.
>
> Thanks-
> 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
> 
> ___
> 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] Able to install KiCad stable and "daily build" in same computer

[Jean-Samuel Reynaud]

Perhaps this name should be configurable ("overridable" ?) by an env
variable ?


Le 12/04/2018 à 15:29, Strontium a écrit :
> kicad5
> kicad6
> etc etc works for me.  I am not wedded to my suggestion, it was
> illustrative only.
> 
> For backward compatibility, "kicad" would be for kicad4 because that's
> what it uses now, so there would be no "kicad4".
> 
> I agree that a user selectable configuration directory would be useful
> for some people.  It should not be difficult to do either, once there
> was a consensus on the how of it. However, being cognizant of how late
> in the release stage for V5 it is, this proposal to only change the base
> directory is to allow kicad4 and 5 to coexist (and nightlies) in the
> absolutely simplest possible way, without creeping the scope, or
> creating untested code paths or boundary cases.  I also don't feel that
> it creates a burden going forward, or precludes the development team
> expanding on this or any other changes to this area that are felt
> desirable.  I think we should push anything more exotic than just using
> a new base configuration directory to version 6.
> 
> Steven
> 
> On 12/04/18 18:39, Clemens Koller wrote:
>> I would pretty much vote to use the IMO more common naming scheme for
>> major package versions:
>>
>> kicad (the current one installed from the repository of your choice)
>> kicad4 (currently: 4.0.7)
>> kicad5 (currently: 5.0.0-rc2-dev...)
>> kicad6 (tbd.)
>>
>> ...avoiding the ".v5" i've seen lately.
>>
>> I believe there is less demand for different minor versions installed
>> next to each other, however it would be a nice-to-have.
>> (So... a user-selectable configuration might help: $ kicad -c
>> projectconfig.cfg)
>>
>> Regards,
>>
>> Clemens
>>
>> On 2018-04-12 09:33, Strontium wrote:
>>> After considering my patch, what about the following proposal:
>>>
>>> Just change the hard coded string in common.cpp (at around line 243)
>>> from:
>>>
>>> cfgpath.AppendDir( wxT( "kicad" ) );
>>>
>>> to
>>>
>>> cfgpath.AppendDir( wxT( "kicad.v5" ) );
>>>
>>> (or some other string)
>>>
>>> Thats it.  Then Kicad Version 5 will have a unique configuration
>>> directory that will not conflict with version 4.
>>>
>>> If an end user wants to bring their kicad V4 configuration over to v5,
>>> they just copy it themselves.  Otherwise it starts with a brand new
>>> blank configuration.  Alternatively packaging might be able to copy it
>>> over.  But i don't see any real need to do it for the user at that
>>> stage.  Its just a complication.
>>>
>>> Then when the development branch is forked, just rename this again to
>>> something like:
>>> cfgpath.AppendDir( wxT( "kicad.v6dev" ) );
>>>
>>> (or whatever).
>>>
>>> Then an end user can have V4, V5 and a Nightly all on the same machine
>>> and configurations won't conflict.
>>>
>>> Anything more exotic can be deferred to V6 development.
>>>
>>> Steven
>>>
>>>
>>>
>>>
>>> On 08/04/18 13:33, Carsten Schoenert wrote:
 Am 07.04.18 um 17:34 schrieb Strontium:
> Attached is a patch for discussion only.
>
> Its the minimum change I could come up with to implement a unique
> version specific config directory.
>
> Nick mentioned changing XDG_CONFIG_HOME, that will not work on Windows
> or Mac.
> And on Linux, etc it will change from "~/.config/kicad" to
> "~/somethingelse/kicad" which would work, but isn't a very friendly
> naming scheme.
 Changing XDG_CONFIG_HOME itself wouldn't be correct. XDG_CONFIG_HOME is
 pointing to '$HOME/.config' and XDG_DATA_HOME is referencing to
 $HOME/.local/share.

 I'm sure Windows and Mac have similar variables for the folders that
 should contain the logical same content.

 The path to the KiCad user config must based on such variables plus the
 preferred name for the config folder, so like kicad-5 (for KiCad5) and
 kicad-6 (for future version KiCad6) and kicad-nightly (for devel
 version). GTK is doing this for a long time.

> $ find  ~/.config -type d -name gtk*
> /home/carsten/.config/gtk-3.0
> /home/carsten/.config/gtk-2.0
 If KiCad will introduce some version specific user config and data
 folders (which I appreciate to see) it will be needed to configured by
 the build environment and not hard-coded in the binaries. The variables
 can be overwritten with some additional value given while starting the
 applications.

 e.g.
 take the default folders
 $ kicad

 override the setting for the default config etc.
 $ KICAD_XDG_CONFIG_HOME=/my/special/folder kicad

>>>
>>> ___
>>> 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: 

Re: [Kicad-developers] wxPython-gtk3 woes

[Jean-Samuel Reynaud]

Hi all,

First: for PPA, I disable for the moment WXPYTHON when needed (for
bionis...). So it fixing temporary this issue
(https://bugs.launchpad.net/kicad/+bug/1762432)

Second: I'm one of the user(s ?) who use wxpython for GUI in plugins.
I'm sure is not a major feature (yet). Anyway the possibility to create
plugins to KiCad in python with a minimal UI (simple dialog boxes...) is
really useful to add features that require input parameters...

Last point: Is there a list of issue detected with GTK3 ? Some bugs are
tagged with that ?

Regards,
Le 10/04/2018 à 13:35, Maciej Sumiński a écrit :
> It seems the easy solution to me too. I just wonder how many people rely
> on the Python shell or GUIs done with wxPython.
> 
> On 04/10/2018 01:32 PM, Jeff Young wrote:
>> I never got KICAD_SCRIPTING_WXPYTHON to work on my Mac, and I can’t say I’ve 
>> missed it.
>>
>>> On 10 Apr 2018, at 12:26, Maciej Sumiński  wrote:
>>>
>>> Apparently mixing wxWidgets-gtk2 and wxPython-gtk3 [1] is not only an
>>> Arch issue anymore, as the upcoming Ubuntu release (bionic) also
>>> provides wxPython package built against gtk3 [package: 2, bug report: 3].
>>>
>>> There are two things we can do to fix the problem for v5:
>>> - Backport python-wxgtk3.0 package built against gtk2. This way
>>> everything works as it used to be, but only for the nightlies. For the
>>> official release the users would be forced to add a PPA providing the
>>> backported package and it sounds troublesome.
>>>
>>> - Disable KICAD_SCRIPTING_WXPYTHON, as there is still available
>>> libwxgtk3.0 package [4] build against gtk2. The drawbacks are that the
>>> Python shell in pcbnew and scripts taking advantage of wxPython to
>>> display a GUI will not work anymore.
>>>
>>> In other news: Ubuntu bionic also ships wxPhoenix [5].
>>>
>>> Cheers,
>>> Orson
>>>
>>> 1. https://bugs.launchpad.net/kicad/+bug/1747677
>>> 2. https://packages.ubuntu.com/bionic/python-wxgtk3.0
>>> 3. https://bugs.launchpad.net/kicad/+bug/1762432
>>> 4. https://packages.ubuntu.com/bionic/libwxgtk3.0-0v5
>>> 5. https://packages.ubuntu.com/bionic/python3-wxgtk4.0
>>>
>>>
>>>
>>> ___
>>> 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
> 




signature.asc
Description: OpenPGP digital signature
___
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] Able to install KiCad stable and "daily build" in same computer

[Jean-Samuel Reynaud]

> 
> If you think the package is ready to be tested by a wider group, how
> about announcing it on the kicad.info forum [1]? If you do not have an
> account there, I can post a notice there for you.

Thanks. I think I will post a message in few days if I collect more
comments. As Nick say, I think I will change the name of he ppa to
"something nightly"




signature.asc
Description: OpenPGP digital signature
___
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] Able to install KiCad stable and "daily build" in same computer

[Jean-Samuel Reynaud]

> 
> No, but I may personally prefer the term nightly over daily to be
> consistent with the terminology we have been using for quite some time.
>  
Ok, I will change that before communicating...

> 
> - If you test it, are you able to find some limitations/bugs ?
> 
> 
> I am not sure how you implemented this. I assume you have scripting
> enabled in both builds. You need to make sure that you are using the
> correct pcbnew python module that matches the version of kicad that you
> like to run such that it won't explode.
Yes, it's based on script helpers.

> 
> What error message? The generic, you are already running another
> instance of kicad or whatever it says? I think that can be ignored safely.
Yes, this is this error I speak. I don't know if there are side effects.

___
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] [RFC] Able to install KiCad stable and "daily build" in same computer

[Jean-Samuel Reynaud]

Dear All,


Since I provide PPA (daily build for Ubuntu) for KiCad, I receive some
requests about installing daily build packages in parallel with stable
version.
With next version (V5) I think it can be useful...
FreeCad provide this kind of feature and you are able to run both
version in parallel.

For testing that I had created a dedicated PPA:
ppa:js-reynaud/kicad-dev-daily
(to add with sudo add-apt-repository ppa:js-reynaud/kicad-dev-daily)

Once added, you are able to install a new package "kicad-daily" that
won't conflict with existing "kicad" packages.
All files are installed on a separate folder and commands became
"something-daily". For example kicad-daily or pcbnew-daily...

So my questions are:
- Is it usefull ?
- Is it a bad idea/stupid :( ?
- If you test it, are you able to find some limitations/bugs ?
- Perhaps to have is plainly functional some modifications are needed.
What modifications ?


For the moment, you can't run in same time two versions (or there are
some error messages...) anyway both are installed and easily "runnable"...


Please give your comments, feedbacks...

___
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] PPA: KiCad 5.0

[Jean-Samuel Reynaud]

So now every repositories are tagged and all packages are built. PPA for
KiCad 5 is ready now...

Le 26/02/2018 à 16:00, Carsten Schoenert a écrit :
> Am 26.02.2018 um 12:10 schrieb Rene Pöschl:
>> The library repos have been tagged with 5.0.0-rc1
>>
>> (As requested yesterday in a similar mailing list thread. [1])
> 
> Excellent! Thanks.
> 
>> This will not be the last tag for 5.0.0. We will make more bugfixes. If 
>> time permits we might also do some larger changes as well.
>>
>> After the v5 release we will limit the lib to bugfixes and new 
>> additions. If a larger change is proposed we might create separate 
>> branches for v5 and v6
> 
> Sounds also correct, also thanks for this!
> 


___
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] PPA: KiCad 5.0

[Jean-Samuel Reynaud]

Thanks,

It's currently building doc and i18n. Should be ready in few minutes.

Le 26/02/2018 à 11:13, Nick Østergaard a écrit :
> kicad-doc and kicad-i18n has been tagged
> 
> 2018-02-26 10:53 GMT+01:00 Jean-Samuel Reynaud <js.reyn...@gmail.com
> <mailto:js.reyn...@gmail.com>>:
> 
> Dear All,
> 
>  Following KiCad 5.0 tagging, I had create a dedicated PPA for next
> release (5.0). For the moment, only RC1 of kicad is built. When other
> repositories will be tagger (i18n, docs and all libs), I will also
> provide them on this PPA.
> 
> It's available at:
> https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-5
> <https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-5>
> 
> Daily build are still active and still building "master" branch of KiCad
> as usual.
> 
> Regards,
> 
> ___
> 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

[Kicad-developers] PPA: KiCad 5.0

[Jean-Samuel Reynaud]

Dear All,

 Following KiCad 5.0 tagging, I had create a dedicated PPA for next
release (5.0). For the moment, only RC1 of kicad is built. When other
repositories will be tagger (i18n, docs and all libs), I will also
provide them on this PPA.

It's available at:
https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-5

Daily build are still active and still building "master" branch of KiCad
as usual.

Regards,

___
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] PPA: library packages modifications

[Jean-Samuel Reynaud]

Dear All,

Libraries packages on PPA follow now the same schema as future debian's
package for KiCad.

So packages are renamed as:
kicad-library => kicad-libraries
kicad-library-footprints => kicad-footprints
kicad-library-packages3d => kicad-packages3d
kicad-library-symbols => kicad-symbols
kicad-library-templates => kicad-templates

 Future update/downgrade from/to between ppa and Ubuntu official KiCad's
package should be easier in the future.
 Ubuntu official Kicad's packages are not yet on new shema (work is in
progress on Carsten side, big thanks to him) but will be ok on the a
near future.


Regards,
Le 17/02/2018 à 15:22, Nick Østergaard a écrit :
> Thank you very much, both of you.
> 
> Den 17. feb. 2018 8.44 AM skrev "Jean-Samuel Reynaud"
> <js.reyn...@gmail.com <mailto:js.reyn...@gmail.com>>:
> 
> Hi
> 
> Package naming will change in ppa to follow exactly the same schema
> as debian's packages. 
> 
> I will process those change as soon as possible. 
> 
> Regards.
> 
> Le 16 févr. 2018 23:46, "Nick Østergaard" <oe.n...@gmail.com
> <mailto:oe.n...@gmail.com>> a écrit :
> 
> 2018-01-15 11:55 GMT+01:00 Carsten Schoenert
> <c.schoen...@t-online.de <mailto:c.schoen...@t-online.de>>:
> 
> Hi,
> 
> adding some notes here for the planned Debian packaging.
> Jean-Samuel emailed my some days ago already about his
> planes and we
> have tried to stay in contact about a consistent packaging
>     schema
>     between Ubuntu and Debian which makes absolutely sense in my
> eyes.
> 
> Am 15.01.2018 um 09:40 schrieb Jean-Samuel Reynaud:
> ...
> > *New package situation:*
> >
> > So I have reshaped packages:
> >
> > kicad-library
> > kicad-library-footprints
> > kicad-library-packages3d
> > kicad-library-symbols
> > kicad-library-templates
> 
> I've agree on those new needed binary packages, which will also
> introduce the depending new source packages.
> 
> 
> So what did the final naming become?
> 
> According to the PPA it looks like:
> 
> https://code.launchpad.net/~js-reynaud/+archive/ubuntu/ppa-kicad/+packages?field.name_filter=_filter=published_filter=artful
> 
> <https://code.launchpad.net/~js-reynaud/+archive/ubuntu/ppa-kicad/+packages?field.name_filter=_filter=published_filter=artful>
> 
> kicad-library (not sure what this does)
> kicad-library-all (date of this is older than the packages, but
> I guess this is a meta package)
> kicad-library-footprints
> kicad-library-packages3d
> kicad-library-symbols
> kicad-library-templates
> 
> While on the figure on your page I see:
> https://wiki.debian.org/KiCad
> kicad-libraries (meta package for footprint, symbols and templates)
> kicad-footprint
> kicad-packages3d
> kicad-symbols
> kicad-templates
>  
> 
> 
> > kicad-library is a meta package. It had a dependency 
> (recommend, not
> > strong) to each others.
> 
> In terms of Debian and Ubuntu there is only Recommends and
> Suggests
> available. The difference between both is simple that a
> Suggests will
> never be installed automatically, a Recommends will be
> installed unless
> the user is turning this globally off (default in on) or
> while calling
> 'apt install' by the option '--no-install-recommends'.
> There is no strong or soft recommending.
> 
> I suggested to use 'kicad-libraries' as the package name and
> make
> 'kicad-library' a transitional package.
> 
> > The version of this package will be prefixed with a "1:" to put 
> it on
> > the front of older version of kicad-library.
> 
> This is not needed in my eyes. The sense of a epoch version
> is something
> different [1]. As long as the new version number for
> 'kicad-libra[y|ies]' is greater than the previous one the
> update will
> work as wanted, the new version is overwriting the old package.
> But I haven't looked at the existing PPA packages from
> Jean-Samuel in
&g

Re: [Kicad-developers] PPA: library packages modifications

[Jean-Samuel Reynaud]

Hi

Package naming will change in ppa to follow exactly the same schema as
debian's packages.

I will process those change as soon as possible.

Regards.

Le 16 févr. 2018 23:46, "Nick Østergaard" <oe.n...@gmail.com> a écrit :

2018-01-15 11:55 GMT+01:00 Carsten Schoenert <c.schoen...@t-online.de>:

> Hi,
>
> adding some notes here for the planned Debian packaging.
> Jean-Samuel emailed my some days ago already about his planes and we
> have tried to stay in contact about a consistent packaging schema
> between Ubuntu and Debian which makes absolutely sense in my eyes.
>
> Am 15.01.2018 um 09:40 schrieb Jean-Samuel Reynaud:
> ...
> > *New package situation:*
> >
> > So I have reshaped packages:
> >
> > kicad-library
> > kicad-library-footprints
> > kicad-library-packages3d
> > kicad-library-symbols
> > kicad-library-templates
>
> I've agree on those new needed binary packages, which will also
> introduce the depending new source packages.
>

So what did the final naming become?

According to the PPA it looks like:
https://code.launchpad.net/~js-reynaud/+archive/ubuntu/
ppa-kicad/+packages?field.name_filter=_
filter=published_filter=artful

kicad-library (not sure what this does)
kicad-library-all (date of this is older than the packages, but I guess
this is a meta package)
kicad-library-footprints
kicad-library-packages3d
kicad-library-symbols
kicad-library-templates

While on the figure on your page I see:
https://wiki.debian.org/KiCad
kicad-libraries (meta package for footprint, symbols and templates)
kicad-footprint
kicad-packages3d
kicad-symbols
kicad-templates


>
> > kicad-library is a meta package. It had a dependency (recommend, not
> > strong) to each others.
>
> In terms of Debian and Ubuntu there is only Recommends and Suggests
> available. The difference between both is simple that a Suggests will
> never be installed automatically, a Recommends will be installed unless
> the user is turning this globally off (default in on) or while calling
> 'apt install' by the option '--no-install-recommends'.
> There is no strong or soft recommending.
>
> I suggested to use 'kicad-libraries' as the package name and make
> 'kicad-library' a transitional package.
>
> > The version of this package will be prefixed with a "1:" to put it on
> > the front of older version of kicad-library.
>
> This is not needed in my eyes. The sense of a epoch version is something
> different [1]. As long as the new version number for
> 'kicad-libra[y|ies]' is greater than the previous one the update will
> work as wanted, the new version is overwriting the old package.
> But I haven't looked at the existing PPA packages from Jean-Samuel in
> detail until now.
>
> > kicad-library-packages3d own all 3D. This package have a large size (~
> > 330M, 4G on disk) . It will have a recommended dependency to
> > kicad-library-footprint
> >
> > kicad-library-footprints own all footprints
> > kicad-library-symbols same with symbols
> > kicad-library-templates same with ... templates ;)
> >
> > All kicad-library-* packages have a conflict constraint to
> > kicad-library << 1:0.1 and kicad-common (as before).
> > There is also a recommended dependency to kicad-library >= 1:0.1.
> >
> > This last point will avoid cross installation between kicad-library
> > version since those packages are be incompatible (shared files...).
>
> As written, not needed as long the new version is greater than the old
> one, and this is a hard requirement. If you use epoch you allow some
> smaller version explicitly.
>
> > *Migration*
> >
> > No specific action are required. Update will do his jobs automatically.
> > Anyway you can now install only one package if you want limit disk
> > space/download time...
> >
> > If you experience any errors, please let me know ! Main error that can
> > be found is one file in two packages (file conflict)...
>
> Ubuntu has no piuparts testing? In Debian there exists piuparts which is
> testing several constellations of possible upgrading a package.
>
> I hope I can start in the next weeks to modify the existing KiCad
> package in Debian to adopt Jean-Samuel package suggestions and uploading
> the new packages to NEW.
> My work on NGspice is no hard dependency foe KiCad but Want to get this
> out of the door before starting new things. If someone want to jump on
> to the packaging just ping me. Some experience with the Debian packaging
> would be appreciated!
> I will also travel to FOSDEM, so if someone want to do some face 2 face
> talking also just ping me. ;)
>
>
> [1] https://www.debian.org/doc/debian-policy/#

Re: [Kicad-developers] Kicad Build Issue on Ubuntu

[Jean-Samuel Reynaud]

Hi Babar,

As far as I know, on ubuntu 14.04, those packages version are not
available. You can install manually backports from adam's ppa:

https://launchpad.net/~adamwolf/+archive/ubuntu/kicad-trusty-backports

or from KiCad's PPA:
https://launchpad.net/~js-reynaud/+archive/ubuntu/ppa-kicad
But this last PPA include also KiCad himself...

Regards,
Le 29/01/2018 à 08:35, Babar Malik a écrit :
> HI,
> its sill the same error which can be seen below
> "*E: Unable to locate package python-wxgtk3.0-dev*
> *E: Couldn't find any package by regex 'python-wxgtk3.0-dev'"*
> *
> *
> *Regards,*
> *Babar Malik.*
> 
> Best Regards,
> Muhammad Babar Malik
> Namal College Mianwali
> An Associate College of University of Bradford
> 
> On 29 January 2018 at 12:26, jp charras  > wrote:
> 
> Le 29/01/2018 à 08:08, Babar Malik a écrit :
> > Thank you so much Carsten,
> > I have installed all the other packages but the only problem is with 
> "python-wxgtk3.0-dev" when i
> > try to install this the terminal shows me the following error message
> > "*E: Unable to locate package pythton-wxgtk3.0-dev*
> > *E: Couldn't find any package by regex 'pythton-wxgtk3.0-dev*"
> >
> > Please help me to solve this issue. 
> > Regards, 
> > Babar Malik. 
> >
> 
> "python-wxgtk3.0-dev", not "pythton-wxgtk3.0-dev"
> 
> > Best Regards,
> > Muhammad Babar Malik
> > Namal College Mianwali
> > An Associate College of University of Bradford
> >
> > On 29 January 2018 at 11:19, Carsten Schoenert  
> > >> 
> wrote:
> >
> >     Hello Babar,
> >
> >     Am 29.01.2018 um 05:12 schrieb Babar Malik:
> >     > I have tried a lot to install wxPython 3.0 but none of the 
> solution is
> >     > working. Can you please suggest any solution?
> >
> >     but you have not installed the package Maciej has suggested? If you 
> ask
> >     for help please give us all information what you have done (or 
> tried to
> >     do) and also the error messages you see.
> >
> >     You will need all of the following packages have installed on your
> >     system to get a recent version of KiCad nightly/development built 
> on a
> >     recent Ubuntu or Debian stretch or testing system.
> >
> >     > $ sudo apt install cmake doxygen libboost-context-dev 
> libboost-dev \
> >     > libboost-system-dev libboost-test-dev libcairo2-dev 
> libcurl4-openssl-dev \
> >     > libgl1-mesa-dev libglew-dev libglm-dev liboce-foundation-dev 
> liboce-ocaf-dev \
> >     > libssl-dev libwxbase3.0-dev libwxgtk3.0-dev python-dev 
> python-wxgtk3.0-dev \
> >     > swig wx-common
> >
> >     --
> >     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
> 
> >
> 
> 
> --
> 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: 

Re: [Kicad-developers] PPA: library packages modifications

[Jean-Samuel Reynaud]

Hi,

> In terms of Debian and Ubuntu there is only Recommends and Suggests
> available. The difference between both is simple that a Suggests will
> never be installed automatically, a Recommends will be installed unless
> the user is turning this globally off (default in on) or while calling
> 'apt install' by the option '--no-install-recommends'.
> There is no strong or soft recommending.
Yes, "strong" is my own comment to explain the difference between
Recommends and Suggests. The dependency I put is "Recommends" of course.


> 
> I suggested to use 'kicad-libraries' as the package name and make
> 'kicad-library' a transitional package
Originally I prefer to keep the same package name. But changing the
package name could be a good option also. If you use "kicad-libraries"
in debian I will follow you, no problem.

> 
>> The version of this package will be prefixed with a "1:" to put it on
>> the front of older version of kicad-library.
> 
> This is not needed in my eyes. The sense of a epoch version is something
> different [1]. As long as the new version number for
> 'kicad-libra[y|ies]' is greater than the previous one the update will
> work as wanted, the new version is overwriting the old package.
> But I haven't looked at the existing PPA packages from Jean-Samuel in
> detail until now.
I use "epoch notation" (1:) because I want to avoid files conflict. If I
change page name (to kicad-libraries), I can discard this (and mark
kicad-library as "Conflicts" instead of "kicad-library << 1:0.1")


> 
>> kicad-library-packages3d own all 3D. This package have a large size (~
>> 330M, 4G on disk) . It will have a recommended dependency to
>> kicad-library-footprint
>>
>> kicad-library-footprints own all footprints
>> kicad-library-symbols same with symbols
>> kicad-library-templates same with ... templates ;)
>>
>> All kicad-library-* packages have a conflict constraint to
>> kicad-library << 1:0.1 and kicad-common (as before).
>> There is also a recommended dependency to kicad-library >= 1:0.1.
>>
>> This last point will avoid cross installation between kicad-library
>> version since those packages are be incompatible (shared files...).
> 
> As written, not needed as long the new version is greater than the old
> one, and this is a hard requirement. If you use epoch you allow some
> smaller version explicitly.
>
In my case, I use epoch to avoid renaming. But as you suggest, using
"kicad-libraries" as package name can avoid this.

> 
>> *Migration*
>>
>> No specific action are required. Update will do his jobs automatically.
>> Anyway you can now install only one package if you want limit disk
>> space/download time...
>>
>> If you experience any errors, please let me know ! Main error that can
>> be found is one file in two packages (file conflict)...
> 
> Ubuntu has no piuparts testing? In Debian there exists piuparts which is
> testing several constellations of possible upgrading a package.
Not sure that it exist for PPA as it's not "official" archive ?


___
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] PPA: library packages modifications

[Jean-Samuel Reynaud]

Dear All,


A big job is done currently on KiCad libraries. Footprints are now on a
same repo [1], dedicated repo for templates [2], symbols [3], 3D
packages [4]...
So it's now time to change PPA libraries package also...


*Previous situation:*

There is only one package for libs: kicad-library
This package contain all libraries:
- modules/footprints
- symbols
- templates
- 3D (not all, just a subset)

This content is based on git repo:
https://github.com/KiCad/kicad-library
and
https://github.com/KiCad/*.pretty


With this schema it is not possible to install only symbols or
symbols+footprints without 3D or any other combination.

New repositories size are more or less like this:
symbols: ~ 20M
templates: ~ 10M
footprints: ~130M
3D: ~ 4G

Have a single big package look to be not really acceptable since
everybody could choose to don't download 3D (for example) if it's not
required (or footprint...).


*New package situation:*

So I have reshaped packages:

kicad-library
kicad-library-footprints
kicad-library-packages3d
kicad-library-symbols
kicad-library-templates


kicad-library is a meta package. It had a dependency (recommend, not
strong) to each others.
The version of this package will be prefixed with a "1:" to put it on
the front of older version of kicad-library.

kicad-library-packages3d own all 3D. This package have a large size (~
330M, 4G on disk) . It will have a recommended dependency to
kicad-library-footprint

kicad-library-footprints own all footprints
kicad-library-symbols same with symbols
kicad-library-templates same with ... templates ;)

All kicad-library-* packages have a conflict constraint to
kicad-library << 1:0.1 and kicad-common (as before).
There is also a recommended dependency to kicad-library >= 1:0.1.

This last point will avoid cross installation between kicad-library
version since those packages are be incompatible (shared files...).


*Migration*

No specific action are required. Update will do his jobs automatically.
Anyway you can now install only one package if you want limit disk
space/download time...


If you experience any errors, please let me know ! Main error that can
be found is one file in two packages (file conflict)...


[1] https://github.com/KiCad/kicad-footprints
[2] https://github.com/KiCad/kicad-templates
[3] https://github.com/KiCad/kicad-symbols
[4] https://github.com/KiCad/kicad-packages3D


___
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] Daily build for KiCad on Ubuntu (ppa)

[Jean-Samuel Reynaud]

Hi all,

 Ubuntu had re-enable the build farm but there is a large number of
other packages waiting for rebuild. As I see, it should take 1 or 2 days
before daily build of new packages.

Regards,
Le 09/01/2018 à 20:36, Jean-Samuel Reynaud a écrit :
> Hi all,
> 
> Launchpad build farm is currently disabled due to security issues
> (Meltdown and Spectre) [1]. So for the moment new KiCad daily build are
> disabled. 
> Existing packages are still available but not new build...
> Sorry for this (temporary) bad news.
> 
> 
> [1]
> https://lists.ubuntu.com/archives/launchpad-announce/2018-January/000103.html
> <https://lists.ubuntu.com/archives/launchpad-announce/2018-January/000103.html>


___
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] Daily build for KiCad on Ubuntu (ppa)

[Jean-Samuel Reynaud]

Hi all,

Launchpad build farm is currently disabled due to security issues (Meltdown
and Spectre) [1]. So for the moment new KiCad daily build are disabled.
Existing packages are still available but not new build...
Sorry for this (temporary) bad news.


[1] https://lists.ubuntu.com/archives/launchpad-announce/
2018-January/000103.html
___
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 fix for bug 1663173

[Jean-Samuel Reynaud]

Hi,

Sorry, corrected patch attached.

Regards
Le 18/10/2017 à 19:31, Wayne Stambaugh a écrit :
> Hi Jean-Samuel,
> 
> There are a few coding policy violations in your patch.
> 
> if( outline.OutlineCount() > 0) {
> 
> should be:
> 
> if( outline.OutlineCount() > 0 )
> {
> 
> This occurs several times.  Please fix this as resubmit the patch.
> 
> Thanks,
> 
> Wayne
> 
> On 10/18/2017 8:58 AM, Jean-Samuel Reynaud wrote:
>> Hi all,
>>
>> Since some recent modifications (I don't search from what version
>> exactly), bug 1663173 is coming back...
>>
>> See original description : https://bugs.launchpad.net/kicad/+bug/1663173
>>
>> Please find attached the patch to fix it.
>>
>> Following this issue I have two comments:
>>
>> - For any usage of "poly->Point( 0 )" or anything like, this should be
>> preceded by a check if value "0" is a valid value.
>>  Like this:
>> if( poly->PointCount() > 0)
>> {
>>// Use of poly->Point( 0 )
>>
>> Same with Outline :
>> if( outline.OutlineCount() > 0) {
>> // Use of outline.Outline( 0 );
>> Or any other way to ensure the index X (with X=0 in thoses case) is a
>> valid index...
>>
>> - Is it really logic to allow negative clearance in pads ? Should not be
>> an absolute value ? In this case, interface should avoid this case...
>>
>> Regards,
>>
>>
>>
>> ___
>> 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
> 

>From 1616c6519edb385b8e5b7af348ed480583589e9a Mon Sep 17 00:00:00 2001
From: Jean-Samuel Reynaud <js.reyn...@gmail.com>
Date: Thu, 19 Oct 2017 10:27:00 +0200
Subject: [PATCH] Fix crash with clearance is "too" negative. Same bug as
 #1663173
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2.7.4"

This is a multi-part message in MIME format.
--2.7.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit


Fixes: lp:1663173
* https://bugs.launchpad.net/kicad/+bug/1663173
---
 pcbnew/class_pad_draw_functions.cpp | 53 ++---
 1 file changed, 37 insertions(+), 16 deletions(-)


--2.7.4
Content-Type: text/x-patch; name="0001-Fix-crash-with-clearance-is-too-negative.-Same-bug-a.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0001-Fix-crash-with-clearance-is-too-negative.-Same-bug-a.patch"

diff --git a/pcbnew/class_pad_draw_functions.cpp b/pcbnew/class_pad_draw_functions.cpp
index 9d270b0..620e0b4 100644
--- a/pcbnew/class_pad_draw_functions.cpp
+++ b/pcbnew/class_pad_draw_functions.cpp
@@ -402,11 +402,17 @@ void D_PAD::DrawShape( EDA_RECT* aClipBox, wxDC* aDC, PAD_DRAWINFO& aDrawInfo )
 TransformShapeWithClearanceToPolygon( outline, aDrawInfo.m_PadClearance, SEGCOUNT, 1.0 );
 
 // Draw the polygon: Inflate creates only one convex polygon
-SHAPE_LINE_CHAIN& poly = outline.Outline( 0 );
+if( outline.OutlineCount() > 0 )
+{
+SHAPE_LINE_CHAIN& poly = outline.Outline( 0 );
 
-GRClosedPoly( aClipBox, aDC, poly.PointCount(),
-  (wxPoint*)( 0 ), false, 0,
-  aDrawInfo.m_Color, aDrawInfo.m_Color );
+if( poly.PointCount() > 0 )
+{
+GRClosedPoly( aClipBox, aDC, poly.PointCount(),
+  (wxPoint*)( 0 ), false, 0,
+  aDrawInfo.m_Color, aDrawInfo.m_Color );
+}
+}
 }
 break;
 
@@ -434,11 +440,17 @@ void D_PAD::DrawShape( EDA_RECT* aClipBox, wxDC* aDC, PAD_DRAWINFO& aDrawInfo )
 TransformRoundRectToPolygon( outline, shape_pos, size, GetOrientation(),
  corner_radius, 64 );
 
-SHAPE_LINE_CHAIN& poly = outline.Outline( 0 );
+if( outline.OutlineCount() > 0 )
+{
+SHAPE_LINE_CHAIN& poly = outline.Outline( 0 );
 
-GRClosedPoly( aClipBox, aDC, poly.PointCount(),
-  

[Kicad-developers] New fix for bug 1663173

[Jean-Samuel Reynaud]

Hi all,

Since some recent modifications (I don't search from what version
exactly), bug 1663173 is coming back...

See original description : https://bugs.launchpad.net/kicad/+bug/1663173

Please find attached the patch to fix it.

Following this issue I have two comments:

- For any usage of "poly->Point( 0 )" or anything like, this should be
preceded by a check if value "0" is a valid value.
 Like this:
if( poly->PointCount() > 0)
{
   // Use of poly->Point( 0 )

Same with Outline :
if( outline.OutlineCount() > 0) {
// Use of outline.Outline( 0 );
Or any other way to ensure the index X (with X=0 in thoses case) is a
valid index...

- Is it really logic to allow negative clearance in pads ? Should not be
an absolute value ? In this case, interface should avoid this case...

Regards,
From 2b0607ef915a3734f87c5c3b5159cb4340ff4e9c Mon Sep 17 00:00:00 2001
From: Jean-Samuel Reynaud <js.reyn...@gmail.com>
Date: Wed, 18 Oct 2017 14:41:52 +0200
Subject: [PATCH] Fix crash with clearance is "too" negative. Same bug as
 #1663173
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2.7.4"

This is a multi-part message in MIME format.
--2.7.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit


Fixes: lp:1663173
* https://bugs.launchpad.net/kicad/+bug/1663173
---
 pcbnew/class_pad_draw_functions.cpp | 50 +
 1 file changed, 34 insertions(+), 16 deletions(-)


--2.7.4
Content-Type: text/x-patch; name="0001-Fix-crash-with-clearance-is-too-negative.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0001-Fix-crash-with-clearance-is-too-negative.patch"

diff --git a/pcbnew/class_pad_draw_functions.cpp b/pcbnew/class_pad_draw_functions.cpp
index 9d270b0..a3884c6 100644
--- a/pcbnew/class_pad_draw_functions.cpp
+++ b/pcbnew/class_pad_draw_functions.cpp
@@ -402,11 +402,16 @@ void D_PAD::DrawShape( EDA_RECT* aClipBox, wxDC* aDC, PAD_DRAWINFO& aDrawInfo )
 TransformShapeWithClearanceToPolygon( outline, aDrawInfo.m_PadClearance, SEGCOUNT, 1.0 );
 
 // Draw the polygon: Inflate creates only one convex polygon
-SHAPE_LINE_CHAIN& poly = outline.Outline( 0 );
+if( outline.OutlineCount() > 0) {
+SHAPE_LINE_CHAIN& poly = outline.Outline( 0 );
 
-GRClosedPoly( aClipBox, aDC, poly.PointCount(),
-  (wxPoint*)( 0 ), false, 0,
-  aDrawInfo.m_Color, aDrawInfo.m_Color );
+if( poly.PointCount() > 0)
+{
+GRClosedPoly( aClipBox, aDC, poly.PointCount(),
+  (wxPoint*)( 0 ), false, 0,
+  aDrawInfo.m_Color, aDrawInfo.m_Color );
+}
+}
 }
 break;
 
@@ -434,11 +439,16 @@ void D_PAD::DrawShape( EDA_RECT* aClipBox, wxDC* aDC, PAD_DRAWINFO& aDrawInfo )
 TransformRoundRectToPolygon( outline, shape_pos, size, GetOrientation(),
  corner_radius, 64 );
 
-SHAPE_LINE_CHAIN& poly = outline.Outline( 0 );
+if( outline.OutlineCount() > 0) {
+SHAPE_LINE_CHAIN& poly = outline.Outline( 0 );
 
-GRClosedPoly( aClipBox, aDC, poly.PointCount(),
-  (wxPoint*)( 0 ), aDrawInfo.m_ShowPadFilled, 0,
-  aDrawInfo.m_Color, aDrawInfo.m_Color );
+if( poly.PointCount() > 0)
+{
+GRClosedPoly( aClipBox, aDC, poly.PointCount(),
+  (wxPoint*)( 0 ), aDrawInfo.m_ShowPadFilled, 0,
+  aDrawInfo.m_Color, aDrawInfo.m_Color );
+}
+}
 }
 
 if( aDrawInfo.m_PadClearance )
@@ -452,12 +462,17 @@ void D_PAD::DrawShape( EDA_RECT* aClipBox, wxDC* aDC, PAD_DRAWINFO& aDrawInfo )
 TransformRoundRectToPolygon( outline, shape_pos, size, GetOrientation(),
  corner_radius, 32 );
 
-// Draw the polygon: Inflate creates only one convex polygon
-SHAPE_LINE_CHAIN& clearance_poly = outline.Outline( 0 );
+if( outline.OutlineCount() > 0) {
+// Draw the polygon: Inflate creates only one convex polygon
+SHAPE_LINE_CHAIN& clearance_poly = outline.Outline( 0 );
 
-GRClosedPoly( aClipBox, aDC, clearance_poly.PointCount(),
-  (wxPoint*)_poly.Point( 0 ), false, 0,
-  aDrawInfo.m_Color, aDrawInfo.m_Color );
+if( clearance_poly.PointCount() > 0)
+{
+  

Re: [Kicad-developers] [BUG or FEATURE] Python action plugins updating

[Jean-Samuel Reynaud]

Hi,

Mainly it's a bug. To be more precice, it's a missing feature.
On plugin reloading, the plugin list is not cleanned but just updated.
So if a plugin is renamed, it is assumed as a new one. This affect only
use who change the plugin name.

Regards,
Le 28/09/2017 à 12:13, Константин Барановский a écrit :
> Recently I noticed strange behaviour of the python action plugins list
> in menu. But I can't decide is it bug or a feature.
> 
> To reproduce it and to understend what I mean, do the follows:
> 
> 1) create python action plugin from Pcbnew manual "Add date on PCB";
> 2) save it in acaptable place (for example, ~/.kicad_plugins in linux);
> 3) launch Pcbnew;
> 4) open menu Tools->External Plugins and seen "Add date on PCB" entry;
> 5) open plugin file in text editor and change name of plugin entry:
> from:
>         self.name = "Add date on PCB"
> to:
>         self.name = "Add date on PCB #2"
> 6) save changes;
> 7) in Pcbnew call Tools->External Plugins->Refresh Plugins;
> 8) open menu Tools->External Plugins and seen two entries:
> "Add date on PCB"
> "Add date on PCB #2";
> 
> Both plugins was loaded to memory and works fine. But "real" plugin is
> only second, if you close Pcbnew and launch it againe, in External
> Plugins menu will remains only "Add date on PCB #2" (that contains in file).
> 
> What do you think about it? Can we leave it as is or it needs be fixed?
> 
> 
> ___
> 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] Fix duplicated pin in case of multipart symbol creation

[Jean-Samuel Reynaud]

Hi All,

Please find attached a patch to fix issue like this bug report:
https://bugs.launchpad.net/kicad/+bug/1509936

Linked pin should be created (eeschema/pinedit.cpp:CreateImagePins) only
if the pin IS common to all unit.
So loop skip (continue instruction) should be called only if pin is NOT
common to all unit.

I know that schematic editor is currently undergoing major recontruction
but perhaps this quick fix could help some users...

Regards,
From f415afdff0dc16c00a81478fcecfaff5bf7a2a75 Mon Sep 17 00:00:00 2001
From: Jean-Samuel Reynaud <js.reyn...@gmail.com>
Date: Tue, 5 Sep 2017 18:25:30 +0200
Subject: [PATCH] Fix duplicated pin in case of multipart symbol creation.
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2.7.4"

This is a multi-part message in MIME format.
--2.7.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit


Should fix bug like: #1509936
---
 eeschema/pinedit.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


--2.7.4
Content-Type: text/x-patch; name="0001-Fix-duplicated-pin-in-case-of-multipart-symbol-creat.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0001-Fix-duplicated-pin-in-case-of-multipart-symbol-creat.patch"

diff --git a/eeschema/pinedit.cpp b/eeschema/pinedit.cpp
index 1f40a39..6433b1b 100644
--- a/eeschema/pinedit.cpp
+++ b/eeschema/pinedit.cpp
@@ -511,7 +511,7 @@ void LIB_EDIT_FRAME::CreateImagePins( LIB_PIN* aPin, int aUnit, int aConvert, bo
 
 for( ii = 1; ii <= aPin->GetParent()->GetUnitCount(); ii++ )
 {
-if( ii == aUnit || aPin->GetUnit() == 0 )
+if( ii == aUnit || aPin->GetUnit() != 0 )
 continue;   // Pin common to all units.
 
 NewPin = (LIB_PIN*) aPin->Clone();

--2.7.4--


___
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] Fix incorrect (missing) initialisation of m_cur_grid in, symbols libraries table dialog box

[Jean-Samuel Reynaud]

Hi all,

There is an incorrect initialisation of variable m_cur_grid in
DIALOG_SYMBOL_LIB_TABLE (file eeschema/dialogs/dialog_sym_lib_table.cpp).

This result of a crash on eeschema when:
- opening "Symbol Library Table"
- click on "Ok" button

If before clicking on "Ok" you switch between "Global libraries" and
"Project Specific Librairies", the tab switch set correctly m_cur_grid
variable (with the handler pageChangedHandler) and the bug is no more
reproductible.

Please find attached the patch to fix this.


Regards,
From 656814635fcf45480420c8bfc0ad3c09052b642f Mon Sep 17 00:00:00 2001
From: Jean-Samuel Reynaud <js.reyn...@gmail.com>
Date: Wed, 30 Aug 2017 19:36:03 +0200
Subject: [PATCH] Fix incorrect (missing) initialisation of m_cur_grid in
 symbols libraries table dialog box
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2.7.4"

This is a multi-part message in MIME format.
--2.7.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit

---
 eeschema/dialogs/dialog_sym_lib_table.cpp | 6 ++
 1 file changed, 6 insertions(+)


--2.7.4
Content-Type: text/x-patch; name="0001-Fix-incorrect-missing-initialisation-of-m_cur_grid-i.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0001-Fix-incorrect-missing-initialisation-of-m_cur_grid-i.patch"

diff --git a/eeschema/dialogs/dialog_sym_lib_table.cpp b/eeschema/dialogs/dialog_sym_lib_table.cpp
index ccaead2..cf091e5 100644
--- a/eeschema/dialogs/dialog_sym_lib_table.cpp
+++ b/eeschema/dialogs/dialog_sym_lib_table.cpp
@@ -202,9 +202,15 @@ DIALOG_SYMBOL_LIB_TABLE::DIALOG_SYMBOL_LIB_TABLE( wxTopLevelWindow* aParent,
 
 // for ALT+A handling, we want the initial focus to be on the first selected grid.
 if( m_pageNdx == 0 )
+{
 m_global_grid->SetFocus();
+m_cur_grid = m_global_grid;
+}
 else
+{
 m_project_grid->SetFocus();
+m_cur_grid = m_project_grid;
+}
 
 // On some window managers (Unity, XFCE), this dialog is
 // not always raised, depending on this dialog is run.

--2.7.4--


___
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.

[Jean-Samuel Reynaud]

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] bugs in stable 4.07

[Jean-Samuel Reynaud]

I will remove packages 4.0.7 since they are already compiled. No problem.


Le 24 juil. 2017 16:45, "Wayne Stambaugh"  a écrit :

> 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

Re: [Kicad-developers] Stable release 4.0.7

[Jean-Samuel Reynaud]

Hi,

Ok on my side (PPA/Ubuntu repo...)
Le 12/07/2017 à 17:06, Wayne Stambaugh a écrit :
> 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

[Kicad-developers] [PATCH] Avoid an infinite loop in PNS

[Jean-Samuel Reynaud]

Hi All,

Following bug 1702485, please find attached a patch to fix this infinite
loop.

Bug report containt all detail how to reproduce...


>From cbffb761a9b25307084aec5504dfbd5afeb67ffc Mon Sep 17 00:00:00 2001
From: Jean-Samuel Reynaud <js.reyn...@gmail.com>
Date: Thu, 6 Jul 2017 10:40:52 +0200
Subject: [PATCH] Avoid an infinite loop in PNS
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2.7.4"

This is a multi-part message in MIME format.
--2.7.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit


Fixes: lp:1702485
* https://bugs.launchpad.net/kicad/+bug/1702485
---
 pcbnew/router/pns_diff_pair.cpp | 4 
 1 file changed, 4 insertions(+)


--2.7.4
Content-Type: text/x-patch; name="0001-Avoid-an-infinite-loop-in-PNS.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0001-Avoid-an-infinite-loop-in-PNS.patch"

diff --git a/pcbnew/router/pns_diff_pair.cpp b/pcbnew/router/pns_diff_pair.cpp
index 0279e1b..6088907 100644
--- a/pcbnew/router/pns_diff_pair.cpp
+++ b/pcbnew/router/pns_diff_pair.cpp
@@ -410,6 +410,10 @@ static VECTOR2I makeGapVector( VECTOR2I dir, int length )
 {
 int l = length / 2;
 VECTOR2I rv;
+
+if( dir.EuclideanNorm() == 0 )
+return dir;
+
 do
 	{
 rv = dir.Resize( l );

--2.7.4--


___
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] Fix wrong directory building for python plugins

[Jean-Samuel Reynaud]

In fact it is existing actually since user's home ".kicad_plugins" 
directory was build in a bad way (string contact with tailing "/" 
instead of os.path.join) 

s/contact/concat/ ;)


___
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] Fix wrong directory building for python plugins

[Jean-Samuel Reynaud]

Hi Jean-Pierre,


old code:
if os.path.isdir(plugins_dir+module):
__import__(module, locals(), globals())

plugins_dir+module dir name never exists.
In fact it is existing actually since user's home ".kicad_plugins" 
directory was build in a bad way (string contact with tailing "/" 
instead of os.path.join)

new code:
if os.path.isdir(os.path.join(plugins_dir,module)):
__import__(module, locals(), globals())

Now, if a subdir exists in a plugins_dir (it was the case in my install),
__import__(module, locals(), globals()) is executed.
But, for me, this code makes no sense: I do not even understand the purpose of 
the code.
(however I am not a Python specialist, and to tell the Truth, my knowledge in 
Python is near zilch).

So I am inclined to remove this code (which was previously never executed) and 
commit your patch.
For me It can be useful to keep this feature. With this, we are able to 
maintain directory based python plugins.

An example there:
https://forum.kicad.info/t/howto-register-a-python-plugin-inside-pcbnew-tools-menu/5540/22
It follow some discussions like this:
https://forum.kicad.info/t/a-via-fence-generator-plugin-for-pcbnew/6638/15

If we have this feature we can maintain easily "really big python 
plugins" inside sub directories.


Anyway, I don't know in your case why it break your python. Perhaps you 
have a sub-directory with some bad things ?
In my case (Linux) It work properly. I had made a quick test in windows 
(an old XP) by manualy "patch" pcbnew.py on a fresh install and I don't 
have this issue.
If it's an error on a dirty sub directory, I propose to just move this 
code (if os.path.isdir...) under following try/except to avoid this kind 
of errors.



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

Re: [Kicad-developers] [PATCH] Fix wrong directory building for python plugins

[Jean-Samuel Reynaud]

Hi Jean-Pierre,

Very strange, It look like a python parse error but I can't reproduce
under Linux. Could you also confirm that python shell is not working
when patch is applied ?

Thanks,
Le 23/06/2017 à 13:47, jp charras a écrit :
> Le 22/06/2017 à 19:34, reynaud a écrit :
>> Hi all,
>>
>> See attached patch to use os.path.join instead of manual building of
>> path.
>>   The previous "plugins_dir+module" was not working in most case (when
>> plugins_dir don't have a tailing "/")
>>
>>   It will allow Python plugin inside directory to be correctly loaded
>> when those plugins are installed inside KiCad's system plugin directory
>>  (/usr/share/kicad/scripting/plugins for example in Linux)
>>
>>
>> Regards,
>>
> 
> Hi Jean-Samuel,
> 
> I tried your patch, but after applying it, Pythons scripts (both action 
> scripts and footprint
> wizards) are no longer loaded (W7, 32 bits).
> 
> Sorry.
> 


___
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] new connectivity algorithm - testers needed

[Jean-Samuel Reynaud]

Hi All,

I had perform some speed test on a complex board (12 layers, 42 zones,
649 nets, 2156 pads, 8556 tracks) and as far as I see it's really better:

- Open/close pcbnew test:
  => 24 seconds with current code
  => 8 seconds with this new algo

- Move a single module/footprint:
 => 14 seconds with current
 => 1 second with new algo

- Rebuild connectivity
  => 12 seconds
  => 1 seconds with new algo

Time measures are not really precise but even with an error margin, this
new algo is really faster...

About the algo himself. On my board there is no difference/error on
connectivity between current and new algo.


Le 13/06/2017 à 04:49, Jakub Kozdon a écrit :
> Hi Tomasz,
> 
> any updates about connectivity algorithm?
> 
> Jakub
> 
> Dne 25.4.2017 v 17:23 Tomasz Wlostowski napsal(a):
>> Hi all,
>>
>> I've pushed the branch [1] containing a rewrite of the pcbnew's
>> connectivity algorithm. By this algorithm, I mean:
>> - computing the ratsnest and checking if all connections are complete
>> - propagating net codes from the pads to the tracks/vias
>> - removing unconnected copper islands in zones
>>
>> Compared to the old algorithm, it introduces several new
>> features/improvements:
>> - no limitations in via/zone connections - you can have loose (stitching
>> vias), overlapping copper zones or zones connecting pads/vias without
>> direct track connections.
>> - items no longer loose their nets when not connected to any pad.
>> connecting to a new pad causes automatic net code propagation.
>> - the algorithm makes zero assumptions about connectivity of the items,
>> vias in particular. This removes another obstacle importing designs from
>> other tools (neither Eagle nor Altium make difference between stitching
>> and 'ordinary' vias).
>> - ratsnest can be calculated between any sort of copper items (not only
>> pads). This is a must-have if we want to have copper arcs or arbitrary
>> copper shapes in the future.
>> - show local ratsnest works for the GAL
>> - marking missing connections between overlapping objects on different
>> layers
>> - free via placement tool
>>
>> The branch also contains a bit of refactoring of the base pcbnew code:
>> - hidden DLISTS behind iterators. Now you can use ordinary C++11 range
>> based for to iterate over board's primitives. This is the first step
>> towards cleanin up the storage model.
>>
>> As with all new stuff, there are some still some issues to sort out:
>> - the legacy autorouter is currently disabled, as it relies a lot on the
>> old connectivity algorithm's data model. We're working to migrate it to
>> the new one alongside porting it to the GAL canvas.
>> - there's no automated via stitching tool yet. I'm waiting to review
>> Heikki's patches for the automagic via stitcher.
>> - the message panel does no longer show the 'links' and 'nodes' counters
>> as the new ratsnest has no direct counterpart for these. Is there any
>> purpose for these counters other than diagnostics/debug?
>> - some code formatting/cleanup may still be necessary
>>
>> @Heikki - once again, the sooner you'll publish your entire via
>> stitching code, the higher the chance you'll get it integrated in Kicad.
>> We can help with that.
>>
>> I encourage you to check out the branch, build it and test with your
>> designs. In particular, if you tried zone stitching with single-pad
>> components, try replacing them with vias and check if the board
>> connectivity is correctly resolved and there are no DRC errors.
>>
>> I'll send some boards demonstrating the new features soon.
>>
>> Your feedback will be greatly appreciated!
>>
>> Cheers,
>> Tom
>>
>> [1] https://github.com/twlostow/kicad-dev/tree/tom-connectivity-apr24
>>
>> PS. The final branch will also support per-net rat line visibility and
>> colors as a bonus ;-)
>>
>> ___
>> 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] [PATCH] Speed improvement for Duplicate functionality

[Jean-Samuel Reynaud]

Hi,

I had tested this patch and it's working good for me. For me it's a good
improvement in term of speed.

Regards,
Le 05/06/2017 à 10:13, Oliver Walters a écrit :
> Friendly bump - has anyone had a chance to review this?
> 
> On Sun, May 28, 2017 at 11:14 PM, Oliver Walters
> >
> wrote:
> 
> As a follow-up to this, I also notice that if you select a large
> number of items, the UI hangs for a *very long* time after the
> selection is complete. The same occurs when you click at an empty
> position to deselect all items. 
> 
> Can be a minute or more for large numbers of items.
> 
> I have not been able to find the cause for this but I do not think
> it is the fault of SELECTION_TOOL in this case.
> 
> Oliver
> 
> On Sun, May 28, 2017 at 10:40 PM, Oliver Walters
>  > wrote:
> 
> Hey all,
> 
> I noticed that the Duplicate functionality in pcbnew / modedit
> was woefully slow when copying more than a handful of items.
> 
> I benchmarked it with 1000 items, it took 58 seconds to perform
> the duplication (KiCAD was at 100% CPU the whole time).
> 
> I have attached a patch that reduces this time to ~200ms for the
> same set of items.
> 
> The speed issue is due to each item being passed through the
> tool framework multiple times. The patch adds a tool function to
> select / deselect a list of items with a single call
> 
> 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] Stable release status update.

[Jean-Samuel Reynaud]

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" <stambau...@gmail.com
> <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
> <js.reyn...@gmail.com <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

Re: [Kicad-developers] Somes download stats on daily build for PPA

[Jean-Samuel Reynaud]

If somebody have data, I can consolidate them on the same graph.


Le 03/03/2017 à 19:30, Jon Evans a écrit :
Cool! Are there stats available for the website packages? It would be 
interesting to see a comparison of the other OS's and stable vs. daily 
builds.


On Fri, Mar 3, 2017 at 1:07 PM, Jean-Samuel Reynaud 
<js.reyn...@gmail.com <mailto:js.reyn...@gmail.com>> wrote:


Hi All,

I had made some statistics on downloads for KiCad daily builds.
This is
valid only for PPA (Ubuntu...) on last 3 months.


To summarize:
- Major distribution used by our daily build users:
Ubuntu xenial (16.04) LTS

- Download are most of them in amd64 arch (95% ~ 5%) except for
some old
distro releases

- Between 4K and 7K downloads per month.


Find attached a graphical overview...

Regards,

___
Mailing list: https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
Post to : kicad-developers@lists.launchpad.net
<mailto:kicad-developers@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-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] Somes download stats on daily build for PPA

[Jean-Samuel Reynaud]

Le 03/03/2017 à 19:55, Kevin Cozens a écrit :

On 2017-03-03 01:07 PM, Jean-Samuel Reynaud wrote:

I had made some statistics on downloads for KiCad daily builds. This is
valid only for PPA (Ubuntu...) on last 3 months.


Have you noticed any uptick in downloads since the announcement about 
the change in licensing of Eagle?



Let me check that point. You know the exact date ?



___
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.

[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

[Kicad-developers] Somes download stats on daily build for PPA

[Jean-Samuel Reynaud]

Hi All,

I had made some statistics on downloads for KiCad daily builds. This is
valid only for PPA (Ubuntu...) on last 3 months.


To summarize:
- Major distribution used by our daily build users:
Ubuntu xenial (16.04) LTS

- Download are most of them in amd64 arch (95% ~ 5%) except for some old
distro releases

- Between 4K and 7K downloads per month.


Find attached a graphical overview...

Regards,


stats.pdf
Description: Adobe PDF document
___
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] Activation of ActionPlugin/Menu in PPA daily build

[Jean-Samuel Reynaud]

Hi All,

After many tests, I plan to activate action plugin submenu in PPA daily
build in few days. (cmake option -DKICAD_SCRIPTING_ACTION_MENU=ON)

Any comments ?

___
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] Ubuntu build commit IDs

[Jean-Samuel Reynaud]

Hi all,

In your example 7735 is the revno form the git repo (It is not related
to bzr). I had changed it with the git-commit keywork. I should be useful.

Le 26/02/2017 à 16:46, John Beard a écrit :
> Hi,
> 
> Would it be possible to get the ubuntu builds tagged with a commit
> hash? Version strings like  201702251416+7735~57~ubuntu16.10.1 are not
> very useful if you want to know exactly which commit a build relates
> to.
> 
> The exact commit is very useful when looking at a bug report from a
> nightly. If a regression arises between one nightly and the next, the
> date only approximately tells you where to start bisecting.
> 
> The Bzr-style rev number is almost entirely useless especially when
> the build is also tagged with a date, and Bzr is dead and gone.
> Date+git rev give you both an incrementing number for quick
> comparisons of age of build, and the git commit is an unambiguous
> pointer to the exact commit.
> 
> Nearly all "nightly" and "git tracker" pacakges (PPA, AUR, etc) put
> the git hash in the build number, pretty much for this exact reason.
> 
> 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

[Kicad-developers] pcbnew crash when pad clearance "too negative"

[Jean-Samuel Reynaud]

Hi all,

I experience a crash in pcbnew when pad clearance is "too negative"
according to the pad shape.

To reproduce:
- Open pcbnew (In OpenGL canvas)
- Open footprint editor
- Create a new footprint
- Place a new SMD rectangular PAD of 1.5mmx1.5mm size
- Change footprint properties and set "Pad clearance" to -1 (in mm)
=> pcbnew crash

It is crashing because at pcbnew/pcb_painter.cpp:777 a polyset is filled
based on shape and clearance:

aPad->TransformShapeWithClearanceToPolygon ...

But in this case (parameter of clearance) the returned polyset is empty

so code at pcbnew/pcb_painter.cpp:783

m_gal->DrawPolyline( polySet.COutline( 0 ) );

always crash because polySet has an empty m_poly property (crash in
COutline in fact...).

To fix this:
Check polySet is not empty:

if( polySet.OutlineCount() > 0 )
 m_gal->DrawPolyline( polySet.COutline( 0 ) );

other solution:
Modify SHAPE_POLY_SET::COutline(int aIndex)
(include/geometry/shape_poly_set.h:190)
To deny "aIndex" out of range values...


An other solution:
Perhaps it's not logical to allow negative values but in this case
interface should deny enter a negative value (and check existing values
from footprint/schematics...)...



Application: pcbnew
Version: no-vcs-found-7613~59~ubuntu16.04.1-experimental, release build
Libraries: wxWidgets 3.0.2
   libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.8 libidn/1.32 librtmp/2.3
Platform: Linux 4.4.0-62-generic x86_64, 64 bit, Little endian, wxGTK
- Build Info -
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.58.0
Curl: 7.47.0
KiCad - Compiler: GCC 5.4.0 with C++ ABI 1009
Settings: USE_WX_GRAPHICS_CONTEXT=OFF
  USE_WX_OVERLAY=OFF
  KICAD_SCRIPTING=ON
  KICAD_SCRIPTING_MODULES=ON
  KICAD_SCRIPTING_WXPYTHON=ON
  KICAD_SCRIPTING_ACTION_MENU=ON
  BUILD_GITHUB_PLUGIN=ON
  KICAD_USE_SCH_IO_MANAGER=ON
  KICAD_USE_OCE=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

[Kicad-developers] [PATCH] ActionPlugin undo and redo feature

[Jean-Samuel Reynaud]

Dear All,

 Find attached a patch to add undo/redo feature for external python
plugin called from the "External Plugins" menu.

 Attached:
- The patch himself
- A plugin to test is (named testundoredo.py):
   - Implement 3 plugins for undo/redo test purpose only
  - Remove all modules
  - Generate random content
  - Move elements randomly

To test it:

- Apply the patch and compile at least with option
KICAD_SCRIPTING_ACTION_MENU=ON
- Copy the script testundoredo.py into your plugin directory
(~/.kicad_plugins under Linux).
- Open pcbnew (from kicad or directly from command line)
- Run plugins in the order you wish to test it.


Regards,
From 5ec8199885de451d62765068cc889c52c0685ae7 Mon Sep 17 00:00:00 2001
From: Jean-Samuel Reynaud <js.reyn...@gmail.com>
Date: Thu, 2 Feb 2017 10:40:34 +0100
Subject: [PATCH] Adding Undo/Redo support for ActionPlugin calls from menu
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2.7.4"

This is a multi-part message in MIME format.
--2.7.4
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit

---
 pcbnew/swig/pcbnew_action_plugins.cpp | 196 --
 1 file changed, 187 insertions(+), 9 deletions(-)


--2.7.4
Content-Type: text/x-patch; name="0001-Adding-Undo-Redo-support-for-ActionPlugin-calls-from.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0001-Adding-Undo-Redo-support-for-ActionPlugin-calls-from.patch"

diff --git a/pcbnew/swig/pcbnew_action_plugins.cpp b/pcbnew/swig/pcbnew_action_plugins.cpp
index 7118f7f..2ecfbfb 100644
--- a/pcbnew/swig/pcbnew_action_plugins.cpp
+++ b/pcbnew/swig/pcbnew_action_plugins.cpp
@@ -36,6 +36,8 @@
 #include 
 #include 
 #include 
+#include 
+#include 
 #include 
 #include 
 
@@ -176,14 +178,190 @@ void PCB_EDIT_FRAME::OnActionPlugin( wxCommandEvent& aEvent )
 
 if( actionPlugin )
 {
-// TODO: Adding recovery point for jobs
-// BOARD_COMMIT commit( this );
-// commit.Push( _( "External plugin" ) );
+PICKED_ITEMS_LIST itemsList;
+BOARD*  currentPcb  = GetBoard();
+boolfromEmpty   = false;
 
-actionPlugin->Run();
+itemsList.m_Status = UR_CHANGED;
 
 OnModify();
 
+// Append tracks:
+for( BOARD_ITEM* item = currentPcb->m_Track; item != NULL; item = item->Next() )
+{
+ITEM_PICKER picker( item, UR_CHANGED );
+itemsList.PushItem( picker );
+}
+
+// Append modules:
+for( BOARD_ITEM* item = currentPcb->m_Modules; item != NULL; item = item->Next() )
+{
+ITEM_PICKER picker( item, UR_CHANGED );
+itemsList.PushItem( picker );
+}
+
+// Append drawings
+for( BOARD_ITEM* item = currentPcb->m_Drawings; item != NULL; item = item->Next() )
+{
+ITEM_PICKER picker( item, UR_CHANGED );
+itemsList.PushItem( picker );
+}
+
+// Append zones outlines
+for( int ii = 0; ii < currentPcb->GetAreaCount(); ii++ )
+{
+ITEM_PICKER picker( (EDA_ITEM*) currentPcb->GetArea(
+ii ), UR_CHANGED );
+itemsList.PushItem( picker );
+}
+
+// Append zones segm:
+for( BOARD_ITEM* item = currentPcb->m_Zone; item != NULL; item = item->Next() )
+{
+ITEM_PICKER picker( item, UR_CHANGED );
+itemsList.PushItem( picker );
+}
+
+if( itemsList.GetCount() > 0 )
+SaveCopyInUndoList( itemsList, UR_CHANGED, wxPoint( 0.0, 0.0 ) );
+else
+fromEmpty = true;
+
+itemsList.ClearItemsList();
+
+// Execute plugin himself...
+actionPlugin->Run();
+
+currentPcb->m_Status_Pcb = 0;
+
+// Get back the undo buffer to fix some modifications
+PICKED_ITEMS_LIST* oldBuffer = NULL;
+
+if( fromEmpty )
+{
+oldBuffer = new PICKED_ITEMS_LIST();
+oldBuffer->m_Status = UR_NEW;
+}
+else
+{
+oldBuffer = GetScreen()->PopCommandFromUndoList();
+wxASSERT( oldBuffer );
+}
+
+// Try do discover what was modified
+
+PICKED_ITEMS_LIST deletedItemsList;
+
+// Found deleted modules
+for( unsigned int i = 0; i < oldBuffer->GetCount(); i++ )
+{
+BOARD_ITEM* item = (BOARD_ITEM*) oldBuffer->GetPickedItem( i );
+ITEM_PICKER picker( item, UR_DELETED );
+
+wxASSERT( item );
+
+switch( item->Type() )
+{
+case PCB_NETINFO_T:
+case PCB_MARKER_T:
+case PCB_MODULE_T:
+case PCB_TRACE_T:
+case PCB_VIA_T:
+case PCB_LINE_T:
+ 

Re: [Kicad-developers] Current state of ActionPlugin

[Jean-Samuel Reynaud]

Dear All,

A quick update on this feature. I use it since it's committed and it
look to work as expected.

 I advance on my side to provide a undo/redo feature.
You will find attached a patch for that.
For the moment it's a request for comments.

 It successfully undo/redo multiples actions (modify elements, adding
items and remove items).
 Of course care must be taken if the python script delete elements
(Example: use "RemoveNative" instead of "Remove") but the undo/redo work.

Regards,
Le 23/01/2017 à 16:25, Nick Østergaard a écrit :
> Ok, feel free to remind me later then.
> 
> 2017-01-23 14:30 GMT+01:00 Wayne Stambaugh <stambau...@gmail.com>:
>> On 1/23/2017 8:30 AM, jp charras wrote:
>>> Le 23/01/2017 à 14:19, Nick Østergaard a écrit :
>>>> Should it be enabled in the windows nightlies now or should we wait a bit?
>>>>
>>>
>>> Before enabling it, please wait for a few tests from devs and J-S.
>>> Perhaps also a bit of doc and 2 or 3 samples which do not delete anything 
>>> (could be in demos) is
>>> welcome.
>>> This is in the J-S Reynaud's hands.
>>
>> I concur.  I think it would be wise to allow our python devs to test it
>> for a while be for we make it available for general testing.
>>
>>>
>>>
>>>> 2017-01-23 14:13 GMT+01:00 jp charras <jp.char...@wanadoo.fr>:
>>>>> Le 18/01/2017 à 18:00, Jean-Samuel Reynaud a écrit :
>>>>>> Just to know if this patch is now acceptable ? Did you plan to commit it 
>>>>>> ?
>>>>>>
>>>>>> Thanks,
>>>>>> Le 17/01/2017 à 19:46, Jean-Samuel Reynaud a écrit :
>>>>>>>> yes i was trying to subtly imply that :)
>>>>>>> ok, find attached the patch with the about box updated ;)
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>
>>>>> I committed the patch ( with fixes, see comments) in rev:
>>>>> 2b5769c0a8568e421c2152177a8f1c27d9bf9cb5
>>>>>
>>>>> Jean-Samuel, thanks, and please carefully test this rev, to be sure I did 
>>>>> not break anything.
>>>>>
>>>>> The action plugin feature must be currently seen as an experimental 
>>>>> feature, for developers, because
>>>>> it can easily break a board.
>>>>> It is enabled if the option -DKICAD_SCRIPTING_ACTION_MENU=ON is added to 
>>>>> the cmake command line.
>>>>>
>>>>> I am thinking this feature need to be tested, and enhancements added 
>>>>> (especially if a script deletes
>>>>> a board item), and this is the reason I see it as currently experimental.
>>>>>
>>>>> However, now it exists, it can be tested.
>>>>>
>>>>>
>>>>> --
>>>>> 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
> 
> ___
> 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
> 

diff --git a/pcbnew/swig/pcbnew_action_plugins.cpp b/pcbnew/swig/pcbnew_action_plugins.cpp
index 7118f7f..26cf1b8 100644
--- a/pcbnew/swig/pcbnew_action_plugins.cpp
+++ b/pcbnew/swig/pcbnew_action_plugins.cpp
@@ -36,6 +36,8 @@
 #include 
 #include 
 #include 
+#include 
+#include 
 #include 
 #include 
 
@@ -176,14 +178,174 @@ void PCB_EDIT_FRAME::OnActionPlugin( wxCommandEvent& aEvent )
 
 if( actionPlugin )
 {
-// TODO: Adding recovery point for jobs
-// BOARD_COMMIT commit( this );
-// commit.Push( _( "External plugin" ) );
+PICKED_ITEMS_LIST itemsList;
+BOARD* currentPcb = GetBoard();
 
-actionPlugin->Run();
+itemsList.m_Status = UR_CHANGED;
 
 OnModify();
 
+

Re: [Kicad-developers] Current state of ActionPlugin

[Jean-Samuel Reynaud]

Dear All,

As requested please find attached a patch to create 2 samples for the
action menu:
- add_automatic_border.py
Automaticaly found smaller area including all modules/coper area/text...
and build or update rectangular PCB edge

- text_by_date.py
Change any text with content "$date$" on the PCB to "$date$" + current date.
=> This example was the first I propose. It is also the one I put inside
the documentation.


Regards,
Le 23/01/2017 à 14:30, jp charras a écrit :
> Le 23/01/2017 à 14:19, Nick Østergaard a écrit :
>> Should it be enabled in the windows nightlies now or should we wait a bit?
>>
> 
> Before enabling it, please wait for a few tests from devs and J-S.
> Perhaps also a bit of doc and 2 or 3 samples which do not delete anything 
> (could be in demos) is
> welcome.
> This is in the J-S Reynaud's hands.
> 
> 
>> 2017-01-23 14:13 GMT+01:00 jp charras <jp.char...@wanadoo.fr>:
>>> Le 18/01/2017 à 18:00, Jean-Samuel Reynaud a écrit :
>>>> Just to know if this patch is now acceptable ? Did you plan to commit it ?
>>>>
>>>> Thanks,
>>>> Le 17/01/2017 à 19:46, Jean-Samuel Reynaud a écrit :
>>>>>> yes i was trying to subtly imply that :)
>>>>> ok, find attached the patch with the about box updated ;)
>>>>>
>>>>> Regards,
>>>>>
>>>
>>> I committed the patch ( with fixes, see comments) in rev:
>>> 2b5769c0a8568e421c2152177a8f1c27d9bf9cb5
>>>
>>> Jean-Samuel, thanks, and please carefully test this rev, to be sure I did 
>>> not break anything.
>>>
>>> The action plugin feature must be currently seen as an experimental 
>>> feature, for developers, because
>>> it can easily break a board.
>>> It is enabled if the option -DKICAD_SCRIPTING_ACTION_MENU=ON is added to 
>>> the cmake command line.
>>>
>>> I am thinking this feature need to be tested, and enhancements added 
>>> (especially if a script deletes
>>> a board item), and this is the reason I see it as currently experimental.
>>>
>>> However, now it exists, it can be tested.
>>>
>>>
>>> --
>>> 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
>>
> 
> 

From bcdd8c17da55b3d3c07252f1a370e7dd3890e96d Mon Sep 17 00:00:00 2001
From: Jean-Samuel Reynaud <js.reyn...@gmail.com>
Date: Fri, 27 Jan 2017 11:06:28 +0100
Subject: [PATCH] Add ActionPlugin example

---
 .../add_automatic_border.py| 247 +
 demos/python_scripts_examples/text_by_date.py  |  59 +
 2 files changed, 306 insertions(+)
 create mode 100644 demos/python_scripts_examples/add_automatic_border.py
 create mode 100644 demos/python_scripts_examples/text_by_date.py

diff --git a/demos/python_scripts_examples/add_automatic_border.py b/demos/python_scripts_examples/add_automatic_border.py
new file mode 100644
index 000..ad71c8f
--- /dev/null
+++ b/demos/python_scripts_examples/add_automatic_border.py
@@ -0,0 +1,247 @@
+#  add_automatic_border.py
+#
+# Copyright (C) 2017 KiCad Developers, see CHANGELOG.TXT for contributors.
+#
+#  This program is free software; you can redistribute it and/or modify
+#  it under the terms of the GNU General Public License as published by
+#  the Free Software Foundation; either version 2 of the License, or
+#  (at your option) any later version.
+#
+#  This program is distributed in the hope that it will be useful,
+#  but WITHOUT ANY WARRANTY; without even the implied warranty of
+#  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+#  GNU General Public License for more details.
+#
+#  You should have received a copy of the GNU General Public License
+#  along with this program; if not, write to the Free Software
+#  Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
+#  MA 02110-1301, USA.
+#
+#
+
+from pcbnew import *
+import re
+import datetime
+
+
+class add_automatic_border( ActionPlugin ):
+"""
+add_automatic_border: An other sample plugin as an example of ActionPlugin
+Build PCB edges to include all PCB elements
+How to use:
+- add all your modules/track/area/text...
+- Call the plugin
+- An including PCB edge will be created automaticaly
+"""
+
+def defaults( self ):
+"""
+Method defaults must be redefined
+self.name should be the menu label 

Re: [Kicad-developers] Current state of ActionPlugin

[Jean-Samuel Reynaud]

> Jean-Samuel, thanks, and please carefully test this rev, to be sure I did not 
> break anything.
> 
It look to work as I tested it before. I'm gonna use it more to see if
something was broken.
On same time, I prepare some examples.


___
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] Current state of ActionPlugin

[Jean-Samuel Reynaud]

Just to know if this patch is now acceptable ? Did you plan to commit it ?

Thanks,
Le 17/01/2017 à 19:46, Jean-Samuel Reynaud a écrit :
>> yes i was trying to subtly imply that :)
> ok, find attached the patch with the about box updated ;)
> 
> Regards,
> 


___
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] Current state of ActionPlugin

[Jean-Samuel Reynaud]

> yes i was trying to subtly imply that :)
ok, find attached the patch with the about box updated ;)

Regards,
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 8d71af2..52de977 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -63,6 +63,10 @@ option( KICAD_SCRIPTING_WXPYTHON
 "Build wxPython implementation for wx interface building in Python and py.shell (default OFF)."
 )
 
+option( KICAD_SCRIPTING_ACTION_MENU
+"Build a tools menu with registred python plugins: actions plugins (default OFF)."
+)
+
 option( KICAD_USE_SCH_IO_MANAGER
 "Build Eeschema with the I/O manager for handling schematic and symbol library I/O. (default OFF)"
 )
@@ -87,6 +91,12 @@ if ( KICAD_SCRIPTING_MODULES AND NOT KICAD_SCRIPTING )
 set ( KICAD_SCRIPTING ON )
 endif()
 
+# same with KICAD_SCRIPTING_ACTION_MENUS
+if ( KICAD_SCRIPTING_ACTION_MENU AND NOT KICAD_SCRIPTING )
+message(STATUS "Changing KICAD_SCRIPTING to ON as needed by KICAD_SCRIPTING_ACTION_MENU")
+set ( KICAD_SCRIPTING ON )
+endif()
+
 option( BUILD_GITHUB_PLUGIN "Build the GITHUB_PLUGIN for pcbnew." ON )
 
 option( KICAD_SPICE "Build Kicad with internal Spice simulator." OFF )
@@ -289,6 +299,10 @@ if( KICAD_SCRIPTING_WXPYTHON )
 add_definitions( -DKICAD_SCRIPTING_WXPYTHON )
 endif()
 
+if( KICAD_SCRIPTING_ACTION_MENU )
+add_definitions( -DKICAD_SCRIPTING_ACTION_MENU )
+endif()
+
 if( KICAD_SPICE )
 add_definitions( -DKICAD_SPICE )
 endif()
diff --git a/common/dialog_about/dialog_about.cpp b/common/dialog_about/dialog_about.cpp
index 7686bf6..3b992fd 100644
--- a/common/dialog_about/dialog_about.cpp
+++ b/common/dialog_about/dialog_about.cpp
@@ -546,6 +546,13 @@ void dialog_about::OnCopyVersionInfo( wxCommandEvent& event )
 msg_version << OFF;
 #endif
 
+msg_version << "  KICAD_SCRIPTING_ACTION_MENU=";
+#ifdef KICAD_SCRIPTING_ACTION_MENU
+msg_version << ON;
+#else
+msg_version << OFF;
+#endif
+
 wxTheClipboard->SetData( new wxTextDataObject( msg_version ) );
 wxTheClipboard->Close();
 copyVersionInfo->SetLabel( _( "Copied..." ) );
diff --git a/include/wxPcbStruct.h b/include/wxPcbStruct.h
index 2968614..dc4200e 100644
--- a/include/wxPcbStruct.h
+++ b/include/wxPcbStruct.h
@@ -117,6 +117,28 @@ protected:
  */
 void enableGALSpecificMenus();
 
+#if defined(KICAD_SCRIPTING) && defined(KICAD_SCRIPTING_ACTION_MENU)
+/**
+ * Function initActionPluginMenus
+ * Fill action menu with all registred action plugins
+ */
+void initActionPluginMenus();
+
+/**
+ * Function OnActionPlugin
+ * Launched by the menu when an action is called
+ * @param aEvent sent by wx
+ */
+void OnActionPlugin( wxCommandEvent& aEvent);
+
+/**
+ * Function OnActionPluginRefresh
+ * Refresh plugin list (reload Python plugins)
+ * @param aEvent sent by wx
+ */
+void OnActionPluginRefresh( wxCommandEvent& aEvent);
+#endif
+
 
 // Has meaning only if DKICAD_SCRIPTING_WXPYTHON option is on
 /**
diff --git a/pcbnew/CMakeLists.txt b/pcbnew/CMakeLists.txt
index be46007..f6f7023 100644
--- a/pcbnew/CMakeLists.txt
+++ b/pcbnew/CMakeLists.txt
@@ -274,6 +274,7 @@ set( PCBNEW_CLASS_SRCS
 zones_polygons_test_connections.cpp
 zones_test_and_combine_areas.cpp
 class_footprint_wizard.cpp
+class_action_plugin.cpp
 
 tools/selection_tool.cpp
 tools/selection_area.cpp
@@ -320,6 +321,7 @@ set( PCBNEW_SCRIPTING_PYTHON_HELPERS
 swig/python_scripting.cpp
 swig/pcbnew_scripting_helpers.cpp
 swig/pcbnew_footprint_wizards.cpp
+swig/pcbnew_action_plugins.cpp
 )
 
 if( KICAD_SCRIPTING )
diff --git a/pcbnew/class_action_plugin.cpp b/pcbnew/class_action_plugin.cpp
new file mode 100644
index 000..4133907
--- /dev/null
+++ b/pcbnew/class_action_plugin.cpp
@@ -0,0 +1,155 @@
+/*
+ * This program source code file is part of KiCad, a free EDA CAD application.
+ *
+ * Copyright (C) 2017 KiCad Developers, see CHANGELOG.TXT for contributors.
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License
+ * as published by the Free Software Foundation; either version 2
+ * of the License, or (at your option) any later version.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, you may find one here:
+ * http://www.gnu.org/licenses/old-licenses/gpl-2.0.html
+ * or you may search the http://www.gnu.org website for the version 2 license,
+ * or you may write to the Free Software Foundation, Inc.,
+ * 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA
+ */
+
+
+/**
+ * @file  class_action_plugin.cpp
+ * @brief Class ACTION_PLUGIN and 

Re: [Kicad-developers] Current state of ActionPlugin

[Jean-Samuel Reynaud]

Did you want I add it to the patch?

Regards.



Le 16 janv. 2017 20:35, "Wayne Stambaugh" <stambau...@gmail.com> a écrit :

> Yes.  This is a useful piece of information in case we suddenly get a
> rash of python scripting bug reports.
>
> On 1/16/2017 2:15 PM, Simon Wells wrote:
> > Should this option be added to the about box->copy version info for
> > completeness?
> >
> > On Tue, Jan 17, 2017 at 8:08 AM, Jean-Samuel Reynaud
> > <js.reyn...@gmail.com> wrote:
> >> Hi all,
> >>
> >> Please find attached the patch for the action plugin menu.
> >>
> >> There is a build option to enable/disable this feature:
> >> KICAD_SCRIPTING_ACTION_MENU
> >> => It's disabled by default
> >>
> >> Now there is a refresh button. It took new plugins, update existing ...
> >> like in footprint wizard dialog.
> >>
> >> I had remove the example from the patch as asked.
> >>
> >> Regards,
> >> Le 11/01/2017 à 18:58, jp charras a écrit :
> >>> Le 11/01/2017 à 17:36, Jean-Samuel Reynaud a écrit :
> >>>>>> Pay a particular attention to the fact plugins can be *now* updated
> (when the source file has
> >>>>>> changed), and therefore menus can also be updated.
> >>>>>> the "PCB_EDIT_FRAME::createActionPluginMenus()" method calls
> Connect, but Disconnect is never called
> >>>>>> by destructors.
> >>>>>> It can create issues when updating scripts, because it could be
> called more than once.
> >>>>>
> >>>>> If you need to update the menus when a script file changes, you would
> >>>>> have to connect a wxFileWatcherEvent to the appropriate wxMainFrame
> >>>>> object to monitor the loaded script file and update the menus
> >>>>> accordingly.  It can be done but I would proceed with caution here.
> >>>>>
> >>>> Is it really necessary to add a file watcher ? Once python plugins are
> >>>> loaded, python subsystem run the plugin as it was at start time (As I
> >>>> understand).
> >>>> I had perform a little test for that. If you modify a plugin while
> >>>> pcbnew is running, this is always the "old" version that is running.
> Not
> >>>> sure that is true for all OS...
> >>>
> >>> I am thinking you are talking only about tests on footprint wizards.
> >>>
> >>> On Windows, the newer is reloaded (as long as you run
> onUpdatePythonModulesClick).
> >>> This is easy to see if the description string in the footprint plugin
> is modified.
> >>>
> >>>> So menu are not supposed to change even if file change.
> >>>> An other point: if I implement that file watching, I should also
> >>>> implement a "directory watcher". In case a new plugins is installed
> >>>> during pcbnew is running ;)
> >>>> Perhaps an "update button": like onUpdatePythonModulesClick for
> >>>> footprint plugins ?
> >>>
> >>> From my experience when debugging a footprint wizard module:
> >>> An "update button" is certainly enough: it is mainly for python script
> developers when they are
> >>> writing and debugging a python script, not for an user who just uses a
> script.
> >>> An automatic update is not useful, and perhaps not good.
> >>>
> >>> The update button was asked since a long time, and I perfectly
> understand this wish.
> >>> (The old way was: closing and rerun kicad)
> >>> It is intended to reload python modules during their development.
> >>>
> >>> Remark: onUpdatePythonModulesClick updates all loaded python modules.
> >>> Of course only python modules which are newer than the currently
> loaded are reloaded.
> >>> Therefore onUpdatePythonModulesClick will also update the action
> plugins.
> >>>
> >>
> >>
> >> ___
> >> 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] Current state of ActionPlugin

[Jean-Samuel Reynaud]

Hi all,

Please find attached the patch for the action plugin menu.

There is a build option to enable/disable this feature:
KICAD_SCRIPTING_ACTION_MENU
=> It's disabled by default

Now there is a refresh button. It took new plugins, update existing ...
like in footprint wizard dialog.

I had remove the example from the patch as asked.

Regards,
Le 11/01/2017 à 18:58, jp charras a écrit :
> Le 11/01/2017 à 17:36, Jean-Samuel Reynaud a écrit :
>>>> Pay a particular attention to the fact plugins can be *now* updated (when 
>>>> the source file has
>>>> changed), and therefore menus can also be updated.
>>>> the "PCB_EDIT_FRAME::createActionPluginMenus()" method calls Connect, but 
>>>> Disconnect is never called
>>>> by destructors.
>>>> It can create issues when updating scripts, because it could be called 
>>>> more than once.
>>>
>>> If you need to update the menus when a script file changes, you would
>>> have to connect a wxFileWatcherEvent to the appropriate wxMainFrame
>>> object to monitor the loaded script file and update the menus
>>> accordingly.  It can be done but I would proceed with caution here.
>>>
>> Is it really necessary to add a file watcher ? Once python plugins are
>> loaded, python subsystem run the plugin as it was at start time (As I
>> understand).
>> I had perform a little test for that. If you modify a plugin while
>> pcbnew is running, this is always the "old" version that is running. Not
>> sure that is true for all OS...
> 
> I am thinking you are talking only about tests on footprint wizards.
> 
> On Windows, the newer is reloaded (as long as you run 
> onUpdatePythonModulesClick).
> This is easy to see if the description string in the footprint plugin is 
> modified.
> 
>> So menu are not supposed to change even if file change.
>> An other point: if I implement that file watching, I should also
>> implement a "directory watcher". In case a new plugins is installed
>> during pcbnew is running ;)
>> Perhaps an "update button": like onUpdatePythonModulesClick for
>> footprint plugins ?
> 
> From my experience when debugging a footprint wizard module:
> An "update button" is certainly enough: it is mainly for python script 
> developers when they are
> writing and debugging a python script, not for an user who just uses a script.
> An automatic update is not useful, and perhaps not good.
> 
> The update button was asked since a long time, and I perfectly understand 
> this wish.
> (The old way was: closing and rerun kicad)
> It is intended to reload python modules during their development.
> 
> Remark: onUpdatePythonModulesClick updates all loaded python modules.
> Of course only python modules which are newer than the currently loaded are 
> reloaded.
> Therefore onUpdatePythonModulesClick will also update the action plugins.
> 

diff --git a/CMakeLists.txt b/CMakeLists.txt
index 8d71af2..52de977 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -63,6 +63,10 @@ option( KICAD_SCRIPTING_WXPYTHON
 "Build wxPython implementation for wx interface building in Python and py.shell (default OFF)."
 )
 
+option( KICAD_SCRIPTING_ACTION_MENU
+"Build a tools menu with registred python plugins: actions plugins (default OFF)."
+)
+
 option( KICAD_USE_SCH_IO_MANAGER
 "Build Eeschema with the I/O manager for handling schematic and symbol library I/O. (default OFF)"
 )
@@ -87,6 +91,12 @@ if ( KICAD_SCRIPTING_MODULES AND NOT KICAD_SCRIPTING )
 set ( KICAD_SCRIPTING ON )
 endif()
 
+# same with KICAD_SCRIPTING_ACTION_MENUS
+if ( KICAD_SCRIPTING_ACTION_MENU AND NOT KICAD_SCRIPTING )
+message(STATUS "Changing KICAD_SCRIPTING to ON as needed by KICAD_SCRIPTING_ACTION_MENU")
+set ( KICAD_SCRIPTING ON )
+endif()
+
 option( BUILD_GITHUB_PLUGIN "Build the GITHUB_PLUGIN for pcbnew." ON )
 
 option( KICAD_SPICE "Build Kicad with internal Spice simulator." OFF )
@@ -289,6 +299,10 @@ if( KICAD_SCRIPTING_WXPYTHON )
 add_definitions( -DKICAD_SCRIPTING_WXPYTHON )
 endif()
 
+if( KICAD_SCRIPTING_ACTION_MENU )
+add_definitions( -DKICAD_SCRIPTING_ACTION_MENU )
+endif()
+
 if( KICAD_SPICE )
 add_definitions( -DKICAD_SPICE )
 endif()
diff --git a/include/wxPcbStruct.h b/include/wxPcbStruct.h
index 2968614..dc4200e 100644
--- a/include/wxPcbStruct.h
+++ b/include/wxPcbStruct.h
@@ -117,6 +117,28 @@ protected:
  */
 void enableGALSpecificMenus();
 
+#if defined(KICAD_SCRIPTING) && defined(KICAD_SCRIPTING_ACTION_MENU)
+/**
+ * Function initActionPluginMenus
+ * Fill action menu with all registred action plugins
+ */
+void ini

Re: [Kicad-developers] Current state of ActionPlugin

[Jean-Samuel Reynaud]

>> Pay a particular attention to the fact plugins can be *now* updated (when 
>> the source file has
>> changed), and therefore menus can also be updated.
>> the "PCB_EDIT_FRAME::createActionPluginMenus()" method calls Connect, but 
>> Disconnect is never called
>> by destructors.
>> It can create issues when updating scripts, because it could be called more 
>> than once.
> 
> If you need to update the menus when a script file changes, you would
> have to connect a wxFileWatcherEvent to the appropriate wxMainFrame
> object to monitor the loaded script file and update the menus
> accordingly.  It can be done but I would proceed with caution here.
> 
Is it really necessary to add a file watcher ? Once python plugins are
loaded, python subsystem run the plugin as it was at start time (As I
understand).
I had perform a little test for that. If you modify a plugin while
pcbnew is running, this is always the "old" version that is running. Not
sure that is true for all OS...
So menu are not supposed to change even if file change.
An other point: if I implement that file watching, I should also
implement a "directory watcher". In case a new plugins is installed
during pcbnew is running ;)
Perhaps an "update button": like onUpdatePythonModulesClick for
footprint plugins ?



___
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] Current state of ActionPlugin

[Jean-Samuel Reynaud]

Hi all,

So concerning this feature. You prefer to keep it on hold or I create a
patch without the python example (and code formatting fixes ;)

Regards,
Le 10/01/2017 à 18:23, Wayne Stambaugh a écrit :
> Here's my two cents.  I share JP and Chris' concerns about developing
> python scripts.  As project leader, I can see where a lot of things can
> go seriously wrong.  Maybe we should make it clear that there should be
> no expectation from python developers that the api will remain stable
> during development or between stable releases so I'm comfortable
> addressing anyone who makes fuss about api changes.  I'm also
> comfortable telling python devs if you break it you get to keep both
> pieces.  We are also under no obligation to include python scripts that
> are called by this interface.
> 
> That being said, I understand the usefulness of the python scripting.  I
> don't want to cut off python developers at the knees because of
> potential issues.  I'm OK with this patch as long as we do not include
> any python scripts that get called by this patch.  In other words, the
> user bears all responsibility for the performance of their python
> scripts not the kicad project.
> 
> On 1/10/2017 10:54 AM, Chris Pavlina wrote:
>> What do you do when the internal APIs change and the plugins stop
>> working?
>>
>> I think encouraging people to use this is very dangerous. It is tied so
>> much into our internal APIs at the moment. The more people who use it,
>> the more everybody is going to scream every single time we change
>> anything. We have so much poorly structured code that needs to be
>> rewritten - I'm sure a lot of it *will* be when it comes time to remove
>> the legacy canvas. If we end up with this many users of the scripting
>> API, we will never be able to touch anything again without breaking
>> everything.
>>
>> Wayne, JP: I'm making an appeal to you now to be conservative with
>> what you accept for use with the scripting API. This would be a very bad
>> point to lock ourselves into having to stabilize it as is. I do not
>> think we should be doing this until an interposing layer with a
>> formalized, stable API can be created.
>>
>> On Tue, Jan 10, 2017 at 04:25:10PM +0100, Jean-Samuel Reynaud wrote:
>>> Hi,
>>>
>>> Just from my point of view:
>>>  We use some python plugin currently and it's not really easy to open
>>> each time python console (and remember plugins name, call mode...).
>>>
>>>  I'm agree with you: During devs of scripts it's crashing and my devs
>>> have to find the rigth way to process.
>>>
>>>  But this kind of feature can increase number of users/devs of this kind
>>> of scripts and raise crash case easily.
>>>
>>> Regards,
>>> Le 10/01/2017 à 16:00, Chris Pavlina a écrit :
>>>> Frankly I don't think we should be encouraging users to use the Python
>>>> API until it is significantly improved. The issues JP raises make the
>>>> API completely unsuitable for plugin use. It's opaque and no users have
>>>> any idea how to write robust Python plugins given the current state of
>>>> the API.
>>>>
>>>> On Jan 10, 2017 09:55, "jp charras" <jp.char...@wanadoo.fr
>>>> <mailto:jp.char...@wanadoo.fr>> wrote:
>>>>
>>>> Le 10/01/2017 à 15:18, Maciej Sumiński a écrit :
>>>> > Hi Jean-Samuel,
>>>> >
>>>> > I think your patch will facilitate use of 3rd party python plugins, 
>>>> as
>>>> > the current way of executing commands from the Python shell is not
>>>> quite
>>>> > user friendly. I vote for merging the patch, but we need to fix some
>>>> > code formatting issues first.
>>>> >
>>>> > Also, I wonder if it would be the right thing to group menu entries 
>>>> by
>>>> > their categories to create submenus. It could be a simple way to
>>>> > organize the actions provided by python plugins. Just an idea.
>>>> >
>>>> > Another question is about the following lines:
>>>> > +if( IsGalCanvasActive() )
>>>> > +{
>>>> > +UseGalCanvas( GetGalCanvas() );
>>>> > +}
>>>> >
>>>> > What is exactly the goal here? If it is only about refreshing the
>>>> > canvas, then a simple Refresh() call should fix the problem.
>>>> >

Re: [Kicad-developers] Current state of ActionPlugin

[Jean-Samuel Reynaud]

> I'm sure you find this feature useful;
> that doesn't mean it's for full inclusion in KiCad proper.
Yes, many users of KiCad here on my side are waiting for a simpler use
of script we use internally. Anyway I understand your position.

> 
>>
>> An other point is that master branch is a *dev* branch ? So modification
>> on file format, API... can happen.
> 
> ...what?
> 
I mean that git master branch is for dev of new features. Those features
are not necessary stable so it's logical that, for example, API for
python will change in the future.




___
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] Current state of ActionPlugin

[Jean-Samuel Reynaud]

Ok I understand, but Is it mean that we have to disable python scripting
in all build by default ?

On daily build I manage, its activated by default...

On my side I will modify all plugin I use if the API change. They are
based on a dev branch so I accept that.

An other point is that master branch is a *dev* branch ? So modification
on file format, API... can happen.

Regards,
Le 10/01/2017 à 16:54, Chris Pavlina a écrit :
> What do you do when the internal APIs change and the plugins stop
> working?
> 
> I think encouraging people to use this is very dangerous. It is tied so
> much into our internal APIs at the moment. The more people who use it,
> the more everybody is going to scream every single time we change
> anything. We have so much poorly structured code that needs to be
> rewritten - I'm sure a lot of it *will* be when it comes time to remove
> the legacy canvas. If we end up with this many users of the scripting
> API, we will never be able to touch anything again without breaking
> everything.
> 
> Wayne, JP: I'm making an appeal to you now to be conservative with
> what you accept for use with the scripting API. This would be a very bad
> point to lock ourselves into having to stabilize it as is. I do not
> think we should be doing this until an interposing layer with a
> formalized, stable API can be created.
> 
> On Tue, Jan 10, 2017 at 04:25:10PM +0100, Jean-Samuel Reynaud wrote:
>> Hi,
>>
>> Just from my point of view:
>>  We use some python plugin currently and it's not really easy to open
>> each time python console (and remember plugins name, call mode...).
>>
>>  I'm agree with you: During devs of scripts it's crashing and my devs
>> have to find the rigth way to process.
>>
>>  But this kind of feature can increase number of users/devs of this kind
>> of scripts and raise crash case easily.
>>
>> Regards,
>> Le 10/01/2017 à 16:00, Chris Pavlina a écrit :
>>> Frankly I don't think we should be encouraging users to use the Python
>>> API until it is significantly improved. The issues JP raises make the
>>> API completely unsuitable for plugin use. It's opaque and no users have
>>> any idea how to write robust Python plugins given the current state of
>>> the API.
>>>
>>> On Jan 10, 2017 09:55, "jp charras" <jp.char...@wanadoo.fr
>>> <mailto:jp.char...@wanadoo.fr>> wrote:
>>>
>>> Le 10/01/2017 à 15:18, Maciej Sumiński a écrit :
>>> > Hi Jean-Samuel,
>>> >
>>> > I think your patch will facilitate use of 3rd party python plugins, as
>>> > the current way of executing commands from the Python shell is not
>>> quite
>>> > user friendly. I vote for merging the patch, but we need to fix some
>>> > code formatting issues first.
>>> >
>>> > Also, I wonder if it would be the right thing to group menu entries by
>>> > their categories to create submenus. It could be a simple way to
>>> > organize the actions provided by python plugins. Just an idea.
>>> >
>>> > Another question is about the following lines:
>>> > +if( IsGalCanvasActive() )
>>> > +{
>>> > +UseGalCanvas( GetGalCanvas() );
>>> > +}
>>> >
>>> > What is exactly the goal here? If it is only about refreshing the
>>> > canvas, then a simple Refresh() call should fix the problem.
>>> >
>>> > Regards,
>>> > Orson
>>> >
>>>
>>> This is a good work.
>>> Thanks Jean-Samuel.
>>>
>>> However, before merging we have to take care of issues which can
>>> easily crash Pcbnew:
>>> Because a python script can modify the board outside the control of
>>> pcbnew edit functions, I am
>>> thinking problems will arise with undo/redo lists (invalid
>>> pointers), ratsnest data and certainly a
>>> few other things.
>>>
>>> Especially for scripts which add or delete items, or change
>>> connectivity.
>>>
>>> Of course, undo/redo lists are alway incorrect after running such
>>> scripts.
>>> This is already a known issue for scripts that are run from the
>>> Pcbnew python console.
>>>
>>> --
>>> Jean-Pierre CHARRAS
>>>
>>> ___

Re: [Kicad-developers] Current state of ActionPlugin

[Jean-Samuel Reynaud]

Hi,

Just from my point of view:
 We use some python plugin currently and it's not really easy to open
each time python console (and remember plugins name, call mode...).

 I'm agree with you: During devs of scripts it's crashing and my devs
have to find the rigth way to process.

 But this kind of feature can increase number of users/devs of this kind
of scripts and raise crash case easily.

Regards,
Le 10/01/2017 à 16:00, Chris Pavlina a écrit :
> Frankly I don't think we should be encouraging users to use the Python
> API until it is significantly improved. The issues JP raises make the
> API completely unsuitable for plugin use. It's opaque and no users have
> any idea how to write robust Python plugins given the current state of
> the API.
> 
> On Jan 10, 2017 09:55, "jp charras"  > wrote:
> 
> Le 10/01/2017 à 15:18, Maciej Sumiński a écrit :
> > Hi Jean-Samuel,
> >
> > I think your patch will facilitate use of 3rd party python plugins, as
> > the current way of executing commands from the Python shell is not
> quite
> > user friendly. I vote for merging the patch, but we need to fix some
> > code formatting issues first.
> >
> > Also, I wonder if it would be the right thing to group menu entries by
> > their categories to create submenus. It could be a simple way to
> > organize the actions provided by python plugins. Just an idea.
> >
> > Another question is about the following lines:
> > +if( IsGalCanvasActive() )
> > +{
> > +UseGalCanvas( GetGalCanvas() );
> > +}
> >
> > What is exactly the goal here? If it is only about refreshing the
> > canvas, then a simple Refresh() call should fix the problem.
> >
> > Regards,
> > Orson
> >
> 
> This is a good work.
> Thanks Jean-Samuel.
> 
> However, before merging we have to take care of issues which can
> easily crash Pcbnew:
> Because a python script can modify the board outside the control of
> pcbnew edit functions, I am
> thinking problems will arise with undo/redo lists (invalid
> pointers), ratsnest data and certainly a
> few other things.
> 
> Especially for scripts which add or delete items, or change
> connectivity.
> 
> Of course, undo/redo lists are alway incorrect after running such
> scripts.
> This is already a known issue for scripts that are run from the
> Pcbnew python console.
> 
> --
> 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
> 


___
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] Current state of ActionPlugin

[Jean-Samuel Reynaud]

Hi Maciej,

> 
> I think your patch will facilitate use of 3rd party python plugins, as
> the current way of executing commands from the Python shell is not quite
> user friendly. I vote for merging the patch, but we need to fix some
> code formatting issues first.
Ok.

> 
> Also, I wonder if it would be the right thing to group menu entries by
> their categories to create submenus. It could be a simple way to
> organize the actions provided by python plugins. Just an idea.
I started without submenu but I can add it.

> 
> Another question is about the following lines:
> +if( IsGalCanvasActive() )
> +{
> +UseGalCanvas( GetGalCanvas() );
> +}
> 
> What is exactly the goal here? If it is only about refreshing the
> canvas, then a simple Refresh() call should fix the problem.
I fighted many time with refresh and other solution but nothing was
working. The only solution I found was this last one.





signature.asc
Description: OpenPGP digital signature
___
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] Current state of ActionPlugin

[Jean-Samuel Reynaud]

Hi,

Yes it is based against HEAD on master. But between the hour I produce
it and the hour you test it there was some modifications on
scripting/kicadplugins.i ...

Please find attached the updated patch.

Tell me if you get an other error but on my side this patch look to work
on a fresh "git clone" directory.



Le 09/01/2017 à 23:33, Nick Østergaard a écrit :
> I am unable to apply this patch, are you sure this is made against
> HEAD on master?
> 
> 2017-01-09 19:08 GMT+01:00 Jean-Samuel Reynaud <js.reyn...@gmail.com>:
>> Hi,
>>
>> Please find attached a patch with an implementation of this feature.
>>
>> I modified mainly the file pcbnew/menubar_pcbframe.cpp to add this menu
>> and some swig interface to implement python basics.
>>
>> I added
>> pcbnew/class_action_plugin.*
>> pcbnew/swig/pcbnew_action_plugins.*
>> to implement the feature
>>
>> I added
>> pcbnew/python/plugins/text_by_date.py
>> to share an example of how to use it.
>>  This sample example (with comments...) just change any text field on
>> the current board where the content is "$date$" to "$date$" + date in
>> iso format:
>> example "$date$ 2017-01-09"
>>
>>
>>
>> Regards,
>> Le 04/01/2017 à 22:14, Wayne Stambaugh a écrit :
>>> To my knowledge no one is currently working on that.
>>>
>>> On 1/4/2017 4:16 PM, Jean-Samuel Reynaud wrote:
>>>> Mainly Action plugins was supposed to add right click/menu/toolbar hooks.
>>>>
>>>> There is two reference of this:
>>>> scripting/kicadplugins.i
>>>> and
>>>> pcbnew/swig/TODO.txt
>>>>
>>>>
>>>>
>>>> Le 04/01/2017 à 20:14, Wayne Stambaugh a écrit :
>>>>> What do you mean by action plugin?  I'm working on the schematic I/O
>>>>> plugin.  AFAIK, that is the only plugin in progress.
>>>>>
>>>>> On 1/3/2017 10:02 AM, Jean-Samuel Reynaud wrote:
>>>>>> Dear All,
>>>>>>
>>>>>> Quick question about ActionPlugin. What is the current state ? Is there
>>>>>> anybody working on it ?
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> ___
>>>>>> 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
>>

diff --git a/include/wxPcbStruct.h b/include/wxPcbStruct.h
index 2968614..1b7ead4 100644
--- a/include/wxPcbStruct.h
+++ b/include/wxPcbStruct.h
@@ -117,6 +117,14 @@ protected:
  */
 void enableGALSpecificMenus();
 
+/**
+ * a function to fill the action plugin menu
+ */
+#if defined(KICAD_SCRIPTING_WXPYTHON)
+void createActionPluginMenus();
+void OnActionPlugin( wxCommandEvent& aEvent);
+#endif
+
 
 // Has meaning only if DKICAD_SCRIPTING_WXPYTHON option is on
 /**
diff --git a/pcbnew/CMakeLists.txt b/pcbnew/CMakeLists.txt
index 040f8e9..252c793 100644
--- a/pcbnew/CMakeLists.txt
++

Re: [Kicad-developers] Current state of ActionPlugin

[Jean-Samuel Reynaud]

Hi,

Please find attached a patch with an implementation of this feature.

I modified mainly the file pcbnew/menubar_pcbframe.cpp to add this menu
and some swig interface to implement python basics.

I added
pcbnew/class_action_plugin.*
pcbnew/swig/pcbnew_action_plugins.*
to implement the feature

I added
pcbnew/python/plugins/text_by_date.py
to share an example of how to use it.
 This sample example (with comments...) just change any text field on
the current board where the content is "$date$" to "$date$" + date in
iso format:
example "$date$ 2017-01-09"



Regards,
Le 04/01/2017 à 22:14, Wayne Stambaugh a écrit :
> To my knowledge no one is currently working on that.
> 
> On 1/4/2017 4:16 PM, Jean-Samuel Reynaud wrote:
>> Mainly Action plugins was supposed to add right click/menu/toolbar hooks.
>>
>> There is two reference of this:
>> scripting/kicadplugins.i
>> and
>> pcbnew/swig/TODO.txt
>>
>>
>>
>> Le 04/01/2017 à 20:14, Wayne Stambaugh a écrit :
>>> What do you mean by action plugin?  I'm working on the schematic I/O
>>> plugin.  AFAIK, that is the only plugin in progress.
>>>
>>> On 1/3/2017 10:02 AM, Jean-Samuel Reynaud wrote:
>>>> Dear All,
>>>>
>>>> Quick question about ActionPlugin. What is the current state ? Is there
>>>> anybody working on it ?
>>>>
>>>> Regards,
>>>>
>>>> ___
>>>> 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
> 

diff --git a/include/wxPcbStruct.h b/include/wxPcbStruct.h
index 2968614..1b7ead4 100644
--- a/include/wxPcbStruct.h
+++ b/include/wxPcbStruct.h
@@ -117,6 +117,14 @@ protected:
  */
 void enableGALSpecificMenus();
 
+/**
+ * a function to fill the action plugin menu
+ */
+#if defined(KICAD_SCRIPTING_WXPYTHON)
+void createActionPluginMenus();
+void OnActionPlugin( wxCommandEvent& aEvent);
+#endif
+
 
 // Has meaning only if DKICAD_SCRIPTING_WXPYTHON option is on
 /**
diff --git a/pcbnew/CMakeLists.txt b/pcbnew/CMakeLists.txt
index 040f8e9..252c793 100644
--- a/pcbnew/CMakeLists.txt
+++ b/pcbnew/CMakeLists.txt
@@ -274,6 +274,7 @@ set( PCBNEW_CLASS_SRCS
 zones_polygons_test_connections.cpp
 zones_test_and_combine_areas.cpp
 class_footprint_wizard.cpp
+class_action_plugin.cpp
 
 tools/selection_tool.cpp
 tools/selection_area.cpp
@@ -319,6 +320,7 @@ set( PCBNEW_SCRIPTING_PYTHON_HELPERS
 swig/python_scripting.cpp
 swig/pcbnew_scripting_helpers.cpp
 swig/pcbnew_footprint_wizards.cpp
+swig/pcbnew_action_plugins.cpp
 )
 
 if( KICAD_SCRIPTING )
diff --git a/pcbnew/class_action_plugin.cpp b/pcbnew/class_action_plugin.cpp
new file mode 100644
index 000..9f11392
--- /dev/null
+++ b/pcbnew/class_action_plugin.cpp
@@ -0,0 +1,119 @@
+/*
+ * This program source code file is part of KiCad, a free EDA CAD application.
+ *
+ * Copyright (C) 2017 KiCad Developers, see CHANGELOG.TXT for contributors.
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License
+ * as published by the Free Software Foundation; either version 2
+ * of the License, or (at your option) any later version.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, you may find one