Re: [Kicad-developers] [PATCH] Allow OpenCASCADE standard edition

Seth, Looking at the information at hand, I'm comfortable adding occ. I was working under the assumption that you were making occ and option for oce but after looking at the patch, I see that is not the case. Please revise your patch to make occ an optional replacement for oce and keep oce as

Re: [Kicad-developers] [PATCH] Allow OpenCASCADE standard edition

Hi Seth, I just took the patch for a testrun and will state some comments below. This looks a bit strange: -- Boost version: 1.66.0 -- -- OpenCASCADE Community Edition has been found. -- -- Found OCE/OpenCASCADE version: 6.8.0 -- -- OCE/OpenCASCADE include directory:

Re: [Kicad-developers] wxwidgets fork progress

Wayne, yes, from my side you can delete them. Even if deleted they are in git anyway, so we can restore them if really needed. I’ll try to change documentation ASAP. Regards, Bernhard > On 29. Jan 2018, at 19:15, Wayne Stambaugh wrote: > > Bernhard, > > Am I safe

Re: [Kicad-developers] [PATCH] Allow OpenCASCADE standard edition

please see https://lists.launchpad.net/kicad-developers/msg31544.html There are different minimum versions required of OCCT and nick also had issues with occt working iirc i think i would still prefer being able to set whether to

Re: [Kicad-developers] [PATCH] Allow OpenCASCADE standard edition

Hi Wayne- My reading of your links is different. Here's the relevant quote: "GNU Lesser General Public License (LGPL) version 2.1 (#LGPLv2.1) This is the previous version of the LGPL: a free software license, but not a strong copyleft license, because it permits linking with nonfree modules. It

Re: [Kicad-developers] [PATCH] Allow OpenCASCADE standard edition

Hey Seth, One of us missed something. Here is my interpretation: The opencascade website license states: "Open CASCADE Technology version 6.7.0 and later are governed by GNU Lesser General Public License (LGPL) version 2.1 with additional exception." It makes no mention of later versions of

Re: [Kicad-developers] [PATCH] Allow OpenCASCADE standard edition

I think you might be confusing the GPL with the *L*GPL, they are very different licenses in practice On Mon, Jan 29, 2018 at 2:04 PM, Wayne Stambaugh wrote: > Hey Seth, > > One of us missed something. Here is my interpretation: > > The opencascade website license states:

Re: [Kicad-developers] [PATCH] Allow OpenCASCADE standard edition

My understanding is that LGPL can be DYNAMICALLY linked with arbitrarily licensed code (GPL of any version, proprietary, permissive, etc) as long as: 1) any modifications to the LGPL'd module are redistributed under the copyleft terms of the LGPL, and 2) patched/updated versions of the LGPL

Re: [Kicad-developers] [PATCH] Allow OpenCASCADE standard edition

We might actually have an out. The exception specifies: "Open CASCADE exception (version 1.0) to GNU LGPL version 2.1. The object code (i.e. not a source) form of a "work that uses the Library" can incorporate material from a header file that is part of the Library. As a special exception to

Re: [Kicad-developers] wxwidgets fork progress

Bernhard, Am I safe deleting the macos patches from the source repo or do I need to hold off until the dust has settle on the new wx repo? Thanks, Wayne On 1/29/2018 1:11 PM, Bernhard Stegmaier wrote: > The full original soname patch seems to fix the issue in my builds (I > did apply only half

Re: [Kicad-developers] wxwidgets fork progress

That patch may be needed to build on older macOS versions and older targets. I am not worried about removing it--it hasn't been in builds for a long time. Good work Bernhard. Adam On Jan 29, 2018 12:11 PM, "Bernhard Stegmaier" wrote: > The full original soname patch

Re: [Kicad-developers] wxwidgets fork progress

The full original soname patch seems to fix the issue in my builds (I did apply only half of it to our fork because of the comments in wxWidgets trac). I pushed it to the fork. The next build should pick it up automatically and be good again… sorry for not having checked this before. I also did

Re: [Kicad-developers] [PATCH] Allow OpenCASCADE standard edition

Maybe the confusion is between LGPL v2.1, which is compatible with GPL3 and GPL2, which is not. There are two aspects here: - Clause 3 states that we can substitute GPL v2 or any newer version instead of LGPL v2.1. That would apply if we decided to use a copy of the library (e.g. static

[Kicad-developers] [PATCH] Use vector instead of bitset for VIEW_ITEM_DATA layer storage

I have been working on https://bugs.launchpad.net/kicad/+bug/1745203 looking for ways to squeeze performance out of rendering large numbers of items on the GAL canvas. The attached patch is the first "low-risk" change I have found. This change results in a 10-15% speedup in operations (file

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

Dear Jean, Thank you so much, you are right as i am able to install these packages. I was facing this problem from three days and you provided a quick solution. Thanks a lot for the help. :) Regards, Babar Malik. Best Regards, Muhammad Babar Malik Namal College Mianwali An Associate College of

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

Read the error message and try to figure out what is missing. I should be a good excercise for you. :) Den 29. jan. 2018 08.39 skrev "Babar Malik" : I turned off python then the kicad was built sucessfully. But when i used "make" command after building it, it shown

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

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

Re: [Kicad-developers] wxwidgets fork progress

Just a short status… I just tried the compile_wx.sh script and it generally seems to be fine. But, I can see that obviously the wxPython installer duplicates libs instead of symlinking them. Maybe the original soname patch we had is needed for that one to work correctly. I’ll check… Regards,

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

In the future, remember to state your goal and expectation when asking these sort of questions. I will make it easier for people to help you. 2018-01-29 11:30 GMT+01:00 Babar Malik : > Dear Jean, > Thank you so much, you are right as i am able to install these packages. I >

[Kicad-developers] Build failed in Jenkins: kicad-qa #3438

See Changes: [jean-pierre charras] Rename files according to the name of classes they are defining [jean-pierre charras] Fix code after renaming files -- [...truncated 49.73

Re: [Kicad-developers] [PATCH] Allow OpenCASCADE standard edition

Please ignore this, I see that you've chosen occ as the fallback. Sorry about the noise. Wayne On 01/29/2018 05:28 PM, Wayne Stambaugh wrote: Seth, Looking at the information at hand, I'm comfortable adding occ. I was working under the assumption that you were making occ and option for oce

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

Thank you Nick, But I am still figuring out the problem. Best Regards, Muhammad Babar Malik Namal College Mianwali An Associate College of University of Bradford On 29 January 2018 at 18:42, Nick Østergaard wrote: > In the future, remember to state your goal and

[Kicad-developers] Build failed in Jenkins: kicad-qa #3441

See Changes: [jean-pierre charras] rename files [jean-pierre charras] fix code after renaming files -- Started by an SCM change Building remotely on debian8 (clang gcc linux) in

[Kicad-developers] Jenkins build is back to normal : kicad-qa #3442

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] [PATCH] Allow OpenCASCADE standard edition

Seth, There maybe licensing issues involved with this. OpenCascade is licensed using LGPL v2.1 not v2.1[1] or later. LGPL v2.1 is not compatible with GPL 3[2]. If OpenCascade is willing to change their license LPGL 2.1 or later or if this is just an oversight on their part, than I can include