Re: [Kicad-developers] eeschema field placement feature branch question

Thanks, Wayne. I'm not sure if the original patch would apply anyway, it's been quite a while. Here's a new one. Not sure if you would want to merge it as a single patch (it's a bit long, about 2k lines), or if you'd rather I split it. I can split it into at least two patches: one to add the

Re: [Kicad-developers] [PATCH 1/4] Use CMake high-level facility for visibility

Hello! I managed to build everything without any downloaded deps on OS X. I’ve already updated my Portfile to build the 4.0.0 stable, and so far it builds and runs. I’ll try to use and test it some more later today. On 2 dicembre 2015 at 16:51:54, Wayne Stambaugh (stambau...@gmail.com) wrote:

Re: [Kicad-developers] [PATCH 1/4] Use CMake high-level facility for visibility

I can but I need to get the 4.0.0 build out first. If someone else can do it sooner than end of this week/weekend, please do :) On Wed, Dec 2, 2015 at 8:30 AM, Wayne Stambaugh wrote: > Would one of our OSX devs please confirm this doesn't break anything on > OSX builds

Re: [Kicad-developers] [PATCH 1/4] Use CMake high-level facility for visibility

Would one of our OSX devs please confirm this doesn't break anything on OSX builds before I commit it. Thanks, Wayne On 12/1/2015 2:14 AM, Simon Richter wrote: > > CMake 3.0 defines two new variables, > > * CMAKE_CXX_VISIBILITY_PRESET and > * CMAKE_VISIBILITY_INLINES_HIDDEN > > to control

Re: [Kicad-developers] [PATCH 1/4] Use CMake high-level facility for visibility

No hurry. The stable release OSX package has priority. I just need confirmation on OSX builds that the patch wont break anything. One other question: do you use the KICAD_BUILD_STATIC or KICAD_BUILD_DYNAMIC options for your build configuration? I can't see where they were used outside of

Re: [Kicad-developers] [PATCH 1/4] Use CMake high-level facility for visibility

O yea I was going to submit a patch to add a note along with some more elaboration on "hard way" building because its incomplete for a fresh install. i.e. missing make and cmake packages. Also the run "pacman -Syu" after fresh install is wrong as it will throw errors, theres a command you have to

Re: [Kicad-developers] access IDF export function through python

Hi Miguel and Cirilo, the function is void PCB_EDIT_FRAME::ExportToIDF3( wxCommandEvent& event ) the best would be if that could be executed from a python call (included in pcbnew.py) ... a second thing that I would like to ask is the ability to have a button to be configured to execute

Re: [Kicad-developers] [PATCH 1/4] Use CMake high-level facility for visibility

On 12/2/2015 11:03 AM, Mark Roszko wrote: >> In the not too distant future, you will have to build boost (probably >> version 1.59) > > If there's ever a recommendation written somewhere. There needs to be > a big note somewhere that 1.59 is broken on 64-bit windows in > boost::context. I

Re: [Kicad-developers] Occasional hang in Cvpcb when retrieving footprint libraries from github

2015-12-02 17:53 GMT+01:00 Kristian Nielsen : > Sometimes, but not everytime, Cvpcb hangs for me when started when it tries > to read the footprints from Github. It looks like a race, maybe a bug in > Boost. I suspect this might have been the causeof bugs like >

[Kicad-developers] Occasional hang in Cvpcb when retrieving footprint libraries from github

Sometimes, but not everytime, Cvpcb hangs for me when started when it tries to read the footprints from Github. It looks like a race, maybe a bug in Boost. I suspect this might have been the causeof bugs like https://bugs.launchpad.net/kicad/+bug/1489128, just the random nature of the bug making

Re: [Kicad-developers] Occasional hang in Cvpcb when retrieving footprint libraries from github

So last night I actually almost completed a patch for the replacement of avhttp/boost with libcurl. Extremely lightweight, <300 lines of code with a reusable wrapper class. Would be interesting to see how it does given its a extremely stable and mature library so expect it to work far better than

Re: [Kicad-developers] Fwd: [PATCH] Eagle board importer fixes

Excellent! Thanks for remembering this JP! Jon On Dec 2, 2015 03:48, "jp charras" wrote: > Le 14/11/2015 22:28, Jon Neal a écrit : > > Hi all, > > > > I have two patches right now, one is a little higher priority than the > > other. > > > > The first is

Re: [Kicad-developers] Occasional hang in Cvpcb when retrieving footprint libraries from github

The other option is compile footprint_info.cpp with #define USE_WORKER_THREADS 0 This will download the libraries serially instead of in parallel with multiple threads. I've never had any issues with this so I'm not sure why all of a sudden we are having issues with this. On 12/2/2015

Re: [Kicad-developers] access IDF export function through python

We export functions from BOARD, modules, etc…, IMO, if we want to export that, “ExportToIDF3” may be a BOARD method (I haven’t looked at it yet), once that happens, ExportToIDF3 is available for python consumption. my_board.ExportToIDF3(“idf_file”) Best, Miguel Ángel Ajo On Wednesday 2

Re: [Kicad-developers] [PATCH 1/4] Use CMake high-level facility for visibility

I will see about pulling in Aljaž's work--not sure how much of it is Macports specific until I take a look. On Wed, Dec 2, 2015 at 10:05 AM, Wayne Stambaugh wrote: > On 12/2/2015 11:03 AM, Mark Roszko wrote: > >> In the not too distant future, you will have to build boost

Re: [Kicad-developers] eeschema field placement feature branch question

2015-12-02 15:09 GMT+01:00 Wayne Stambaugh : > Chris, > > I cannot find the original request for this patch. I do like the > feature. Since I don't have the patch or a url to your branch, I cannot > review the code. From the video, I have one minor suggestion. It looks >

Re: [Kicad-developers] eeschema field placement feature branch question

'Course it does. I always document my features, don't I? :) On Dec 2, 2015 2:37 PM, "Nick Østergaard" wrote: > 2015-12-02 15:09 GMT+01:00 Wayne Stambaugh : > > Chris, > > > > I cannot find the original request for this patch. I do like the > > feature.

Re: [Kicad-developers] Occasional hang in Cvpcb when retrieving footprint libraries from github

Nick Østergaard writes: > Did you specifically use -DKICAD_SKIP_BOOST=YES ? If now then you are > using boost 1.54 that kicad downloaded. > > You can see the version used in the help meny in any of the main apps, > help -> copy version info No, I did not use

Re: [Kicad-developers] proposal for introduction of 3D refactor changes

2015-12-02 14:21 GMT+01:00 Wayne Stambaugh : > Since this is most likely going to be one big merge, I will not merge it > until I've had a chance to build it and test it on windows and linux. I > will also have to review the code which will take a while since it's > such a

Re: [Kicad-developers] eeschema field placement feature branch question

Yes, but this should not be the exception :P 2015-12-02 20:39 GMT+01:00 Chris Pavlina : > 'Course it does. I always document my features, don't I? :) > > On Dec 2, 2015 2:37 PM, "Nick Østergaard" wrote: >> >> 2015-12-02 15:09 GMT+01:00 Wayne Stambaugh

Re: [Kicad-developers] Occasional hang in Cvpcb when retrieving footprint libraries from github

2015-12-02 20:05 GMT+01:00 Kristian Nielsen : > Nick Østergaard writes: > >> Did you specifically use -DKICAD_SKIP_BOOST=YES ? If now then you are >> using boost 1.54 that kicad downloaded. >> >> You can see the version used in the help meny in any of

Re: [Kicad-developers] [PATCH 1/4] Use CMake high-level facility for visibility

I am on a stock MacPorts boost since over a year now… 1.58 and now 1.59 (don’t know since when). I didn’t see any problems with it. Regards, Bernhard > On 02 Dec 2015, at 16:51, Wayne Stambaugh wrote: > > In the not too distant future, you will have to build boost

Re: [Kicad-developers] Fwd: [PATCH] Eagle board importer fixes

Le 14/11/2015 22:28, Jon Neal a écrit : > Hi all, > > I have two patches right now, one is a little higher priority than the > other. > > The first is eagle_keepout_area_fix.patch. When I "fixed" importing > polygons in the eagle importer a few months ago I neglected to handle > keepout areas

Re: [Kicad-developers] eagle_pcbnew.cpp eagle import part NAME and VALE display fix

Le 01/12/2015 16:03, Lachlan Audas a écrit : > Bug: pcbnew always shows NAME and VALUE fields, even there are not > present in Eagle brd package definition. > Also when the "both option" is enable in Eagle, on part > NAME or part VALE fields, it should display"NAME = R1"

[Kicad-developers] Build failed in Jenkins: KiCad (Linux, all options, Debug) #935

See Changes: [jean-pierre charras] Eagle importer support dimensions -- Started by an SCM change Building on master in workspace $ bzr revision-info -d

Re: [Kicad-developers] proposal for introduction of 3D refactor changes

I just tested out the first change Cirilo wants to add. It works pretty well and is a lot nicer than the current system. One note about the 3d preview for Cirilo: I need to test this on my laptop, but I doubt that the 3d tab will be small enough to fit on its display (1366x768). I will test it

Re: [Kicad-developers] Occasional hang in Cvpcb when retrieving footprint libraries from github

Nick Østergaard writes: > If you feel like testing you could make a new build with 1.55 and see > if it makes a difference. Wayne Stambaugh writes: > The other option is compile footprint_info.cpp with > > #define USE_WORKER_THREADS 0 As it turns

Re: [Kicad-developers] access IDF export function through python

The export function which Maurice mentioned is a dialog. The export function is in pcbnew/exporters/export_idf.cpp : bool Export_IDF3( BOARD* aPcb, const wxString& aFullFileName, bool aUseThou, double aXRef, double aYRef ) aFullFileName: full path for the output file and should

Re: [Kicad-developers] access IDF export function through python

Hi Miguel, could you please have a look at my query to tell me if this option is handled by KiCad? thank you Maurice On 27/11/2015 23.24, easyw wrote: Hi Miguel, is there a way to access IDF export function by a command in python with pcbnew APIs? Maurice

[Kicad-developers] Jenkins build is back to normal : KiCad (Linux, all options, Debug) #936

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

Re: [Kicad-developers] proposal for introduction of 3D refactor changes

Since this is most likely going to be one big merge, I will not merge it until I've had a chance to build it and test it on windows and linux. I will also have to review the code which will take a while since it's such a large change set. I will also need and OSX dev to build and test it. The

Re: [Kicad-developers] eeschema field placement feature branch question

Chris, I cannot find the original request for this patch. I do like the feature. Since I don't have the patch or a url to your branch, I cannot review the code. From the video, I have one minor suggestion. It looks like you added 3 new check boxes to the Eeschema options dialog which makes it