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

[Miguel Angel Ajo]

See 


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

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

[Miguel Angel Ajo]

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 workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://github.com/KiCad/kicad-source-mirror.git # timeout=10
Fetching upstream changes from https://github.com/KiCad/kicad-source-mirror.git
 > git --version # timeout=10
 > git fetch --tags --progress https://github.com/KiCad/kicad-source-mirror.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 8552f3fedf184de96aeb7b2a70af821dd07dd5e1 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 8552f3fedf184de96aeb7b2a70af821dd07dd5e1
Commit message: "fix code after renaming files"
 > git rev-list --no-walk 39fc0656d1aaec4d1da17d67be847b193f8558c8 # timeout=10
[kicad-qa] $ /bin/sh -xe /tmp/jenkins6455932596073549841.sh
+ cmake --version
cmake version 3.0.2

CMake suite maintained and supported by Kitware (kitware.com/cmake).
+ gcc --version
gcc (Debian 4.9.2-10) 4.9.2
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

+ git --version
git version 2.1.4
+ OPTS= -DCMAKE_BUILD_TYPE=Debug -DBUILD_GITHUB_PLUGIN=ON -DKICAD_SCRIPTING=ON 
-DKICAD_SCRIPTING_MODULES=ON -DKICAD_SCRIPTING_WXPYTHON=ON
+ [ -d passed-qa ]
+ [ -d build ]
+ cd build
+ /usr/bin/cmake .. -DCMAKE_BUILD_TYPE=Debug -DBUILD_GITHUB_PLUGIN=ON 
-DKICAD_SCRIPTING=ON -DKICAD_SCRIPTING_MODULES=ON -DKICAD_SCRIPTING_WXPYTHON=ON
-- Kicad install dir: 
-- Check for installed GLEW -- found
-- Boost version: 1.55.0
-- Check for installed Python Interpreter -- found
-- Python module install path: lib/python2.7/dist-packages
-- wxPython version 3.0 found.
-- S3DSG version: 2.0.0
-- Boost version: 1.55.0
-- Found the following Boost libraries:
--   unit_test_framework
-- Boost version: 1.55.0
-- Found the following Boost libraries:
--   unit_test_framework
-- Boost version: 1.55.0
-- Found the following Boost libraries:
--   unit_test_framework
-- Configuring done
-- Generating done
-- Build files have been written to: 

+ echo CMAKE exit code is 0
CMAKE exit code is 0
+ rm -f pcbnew/pcbnewPYTHON_wrap.cxx
+ + grep -q ^MAKEJOBS=
env
+ echo The MAKEJOBS variable is empty
The MAKEJOBS variable is empty
+ JOBS=4
+ make -j4 pcbnew_python_module
[  0%] [  0%] [  0%] Built target lib_table_lexer_source_files
Built target netlist_lexer_source_files
Generating version string header
[  0%] Built target idf3
[  0%] -- Using Git to determine build version string.
Built target page_layout_lexer_source_files
-- Found Git: /usr/bin/git (found version "2.1.4") 
-- Git hash: 8552f3fedf184de96aeb7b2a70af821dd07dd5e1
-- Git branch: HEAD
-- Writing 
 file with 
version: (2018-01-29 revision 8552f3f)-HEAD
[  0%] Built target pcb_plot_lexer_source_files
[  0%] Built target version_header
[  0%] Built target pcb_lexer_source_files
[  1%] Built target kicad_3dsg
[  4%] [  5%] Built target gal
Built target lib_dxf
[  5%] Built target specctra_lexer_source_files
[  5%] Built target polygon
[ 48%] Built target bitmaps
Scanning dependencies of target pcbcommon
[ 48%] [ 48%] [ 48%] Building CXX object 
common/CMakeFiles/pcbcommon.dir/__/pcbnew/class_dimension.cpp.o
Building CXX object common/CMakeFiles/pcbcommon.dir/__/pcbnew/board_commit.cpp.o
Building CXX object 
common/CMakeFiles/pcbcommon.dir/__/pcbnew/board_items_to_polygon_shape_transform.cpp.o
Scanning dependencies of target common
[ 48%] Building CXX object common/CMakeFiles/common.dir/build_version.cpp.o
[ 48%] Building CXX object common/CMakeFiles/common.dir/wx_status_popup.cpp.o
[ 48%] Building CXX object 
common/CMakeFiles/pcbcommon.dir/__/pcbnew/class_drawsegment.cpp.o
[ 48%] Building CXX object 
common/CMakeFiles/pcbcommon.dir/__/pcbnew/class_edge_mod.cpp.o
[ 48%] Building CXX object common/CMakeFiles/common.dir/tool/tool_base.cpp.o
[ 48%] Building CXX object 
common/CMakeFiles/pcbcommon.dir/__/pcbnew/class_module.cpp.o
[ 48%] Building CXX object 
common/CMakeFiles/pcbcommon.dir/__/pcbnew/class_pad_draw_functions.cpp.o
[ 48%] Building CXX object 
common/CMakeFiles/pcbcommon.dir/__/pcbnew/class_pcb_target.cpp.o
[ 48%] Building CXX object 
common/CMakeFiles/common.dir/tool/tool_dispatcher.cpp.o
[ 48%] Building CXX object 
common/CMakeFiles/pcbcommon.dir/__/pcbnew/class_pcb_text.cpp.o
[ 48%] Building 

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

[Babar Malik]

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 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 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 University of Bradford
>>
>> On 29 January 2018 at 15:16, Jean-Samuel Reynaud 
>> wrote:
>>
>>> 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 <
>>> c.schoen...@t-online.de 
>>> > > >>
>>> wrote:
>>> > >
>>> > > Hello Babar,
>>> > >
>>> > > Am 29.01.2018 <29%2001%2020%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   : 

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

[Wayne Stambaugh]

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
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 the default.  There are (were?) known issues with occ the last I
heard and I believe we have all platforms working fine with oce.  I
would be more comfortable with making occ optional.

Thanks,

Wayne

On 01/29/2018 03:24 PM, Seth Hillbrand wrote:

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 linking)

- But there is also Clause 6 that covers us: "As an exception to the
Sections above, you may also combine or link a "work that uses the
Library" with the Library to produce a work containing portions of the
Library, and distribute that work under terms of your choice, provided
that the terms permit modification of the work for the customer's own
use and reverse engineering for debugging such modifications."

-S

2018-01-29 12:04 GMT-08:00 Wayne Stambaugh >:

 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 the LGPL (including the
 exception) so I am interpreting this as v2.1 only.  I do not have a copy
 (and I'm not going to sign up to get a copy so please check the
 copyright in the source to see if it matches the website) of the
 opencascade source archive to see if the license in the source
 specifically states "v2.1 or (at your option) any later version" which
 is typically how the GPL and LGPL are used.  If it does, than I can
 safely add this patch because I can make the claim that I am using
 opencascade under at later version of the LGPL which is compatible with
 the GPL 3 used by kicad.

 According to the folks at the FSF:

 "Please note that GPLv2 is, by itself, not compatible with GPLv3.
 However, most software released under GPLv2 allows you to use the terms
 of later versions of the GPL as well. When this is the case, you can use
 the code under GPLv3 to make the desired combination. To learn more
 about compatibility between GNU licenses, please see our FAQ."

 I hope this clarifies why I am hesitant to merge this patch and what
 needs to clarified.  Isn't licensing fun! ;)

 Thanks,

 Wayne

 On 1/29/2018 2:47 PM, Seth Hillbrand wrote:
 > 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 is compatible with GPLv2 and GPLv3."
 >
 > Did I miss something?
 >
 > -Seth
 >
 > 2018-01-29 11:18 GMT-08:00 Wayne Stambaugh 
 > >>:
 >
 >     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 this patch.  Please verify the OpenCascade
 license
 >     with something that I can verify to ensure we are not
 violating and
 >     licensing terms.
 >
 >     Cheers,
 >
 >     Wayne
 >
 >     [1]: https://www.opencascade.com/content/licensing
 
 >     >
 >     [2]:
 >
  https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses
 
 >
  >
 >
 >     On 1/29/2018 1:54 PM, Seth Hillbrand wrote:
 >     > ​Hi All-
 >     >

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

[Nick Østergaard]

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:
/opt/oce/lib/oce-0.17/../../include/oce
-- -- OCE/OpenCASCADE shared libraries directory:
-- Check for installed Python Interpreter -- found

The messages are with double -- and the shared libs.

But an improvement with your patch over what is currently in kicad is that
it found OCE on my system without explicitly specifind OCE_DIR. But how do
I make it use OCCT when I also have OCE installed?

What does CADx mean in that header?

What is this about?
-- Looking for
/home/amazingdude/kicad-source-mirror/build_seths_occt_patch_occt/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx
-- Looking for
/home/amazingdude/kicad-source-mirror/build_seths_occt_patch_occt/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx
- not found

I tried to test it with removing oce and just have occt installed and got
something like this:
-- Found OCC: /opt/opencascade/inc (found version "6.9.1")
-- -- Found OCE/OpenCASCADE version: 6.9.1
-- -- OCE/OpenCASCADE include directory: /opt/opencascade/inc
-- -- OCE/OpenCASCADE shared libraries directory: /opt/opencascade/lib

It did not build against community/opencascade 6.9.1-7. I got the following
error in a clean build dir.

$ make kicad2step -j1
[  0%] Linking CXX executable kicad2step
/usr/bin/ld: cannot find -lTKMesh
/usr/bin/ld: cannot find -lTKernel
/usr/bin/ld: cannot find -lTKG2d
/usr/bin/ld: cannot find -lTKG3d
/usr/bin/ld: cannot find -lTKMath
/usr/bin/ld: cannot find -lTKIGES
/usr/bin/ld: cannot find -lTKSTL
/usr/bin/ld: cannot find -lTKXSBase
/usr/bin/ld: cannot find -lTKBin
/usr/bin/ld: cannot find -lTKBO
/usr/bin/ld: cannot find -lTKCDF
/usr/bin/ld: cannot find -lTKBRep
/usr/bin/ld: cannot find -lTKTopAlgo
/usr/bin/ld: cannot find -lTKGeomAlgo
/usr/bin/ld: cannot find -lTKGeomBase
/usr/bin/ld: cannot find -lTKPrim
/usr/bin/ld: cannot find -lTKSTEP
/usr/bin/ld: cannot find -lTKSTEPBase
/usr/bin/ld: cannot find -lTKSTEPAttr
/usr/bin/ld: cannot find -lTKFeat
/usr/bin/ld: cannot find -lTKCAF
/usr/bin/ld: cannot find -lTKXCAF
/usr/bin/ld: cannot find -lTKLCAF
/usr/bin/ld: cannot find -lTKXDESTEP
/usr/bin/ld: cannot find -lTKXDEIGES
collect2: error: ld returned 1 exit status
make[3]: *** [utils/kicad2step/CMakeFiles/kicad2step.dir/build.make:355:
utils/kicad2step/kicad2step] Error 1
make[2]: *** [CMakeFiles/Makefile2:3007:
utils/kicad2step/CMakeFiles/kicad2step.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:3019:
utils/kicad2step/CMakeFiles/kicad2step.dir/rule] Error 2
make: *** [Makefile:979: kicad2step] Error 2

But those libs do existm, searched for the last one;
$ yaourt  -Ql opencascade | grep TKXDEIGES
opencascade /opt/opencascade/lib/libTKXDEIGES.so
opencascade /opt/opencascade/lib/libTKXDEIGES.so.0
opencascade /opt/opencascade/lib/libTKXDEIGES.so.0.0.0

I got these variables set in the CMakeCache

cat CMakeCache.txt  | grep "OCE\|OCC"
KICAD_USE_OCE:BOOL=ON
OCC_INCLUDE_DIR:PATH=/opt/opencascade/inc
OCC_LIBRARY:FILEPATH=/opt/opencascade/lib/libTKernel.so
//The directory containing a CMake configuration file for OCE.
OCE_DIR:PATH=OCE_DIR-NOTFOUND
//Details about finding OCC
FIND_PACKAGE_MESSAGE_DETAILS_OCC:INTERNAL=[/opt/opencascade/inc][v6.9.1()]

This is tested on archlinux.

2018-01-29 19:54 GMT+01:00 Seth Hillbrand :

> ​Hi All-
>
> Currently, the build requires the opencascade community edition.  For
> various reasons, I need to have the current non-community edition of
> OpenCASCADE installed on my work machine.
>
> The attached patch allows compiling KiCad with either the OpenCASCADE
> community edition or standard edition.
>
> I've tested on a homebrew-based Mac install as well as Linux but haven't
> verified MSW, if someone would be willing to test it there, that would be
> great!  The basic search routines are lightly modified from FreeCAD's logic
> and keep their LGPL copyright on the CMake file.
>
> -Seth​
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

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

[Wayne Stambaugh]

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 the default.  There are (were?) known issues with occ the last I
heard and I believe we have all platforms working fine with oce.  I
would be more comfortable with making occ optional.

Thanks,

Wayne

On 01/29/2018 03:24 PM, Seth Hillbrand wrote:
> 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 linking)
> 
> - But there is also Clause 6 that covers us: "As an exception to the
> Sections above, you may also combine or link a "work that uses the
> Library" with the Library to produce a work containing portions of the
> Library, and distribute that work under terms of your choice, provided
> that the terms permit modification of the work for the customer's own
> use and reverse engineering for debugging such modifications."
> 
> -S
> 
> 2018-01-29 12:04 GMT-08:00 Wayne Stambaugh  >:
> 
> 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 the LGPL (including the
> exception) so I am interpreting this as v2.1 only.  I do not have a copy
> (and I'm not going to sign up to get a copy so please check the
> copyright in the source to see if it matches the website) of the
> opencascade source archive to see if the license in the source
> specifically states "v2.1 or (at your option) any later version" which
> is typically how the GPL and LGPL are used.  If it does, than I can
> safely add this patch because I can make the claim that I am using
> opencascade under at later version of the LGPL which is compatible with
> the GPL 3 used by kicad.
> 
> According to the folks at the FSF:
> 
> "Please note that GPLv2 is, by itself, not compatible with GPLv3.
> However, most software released under GPLv2 allows you to use the terms
> of later versions of the GPL as well. When this is the case, you can use
> the code under GPLv3 to make the desired combination. To learn more
> about compatibility between GNU licenses, please see our FAQ."
> 
> I hope this clarifies why I am hesitant to merge this patch and what
> needs to clarified.  Isn't licensing fun! ;)
> 
> Thanks,
> 
> Wayne
> 
> On 1/29/2018 2:47 PM, Seth Hillbrand wrote:
> > 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 is compatible with GPLv2 and GPLv3."
> >
> > Did I miss something?
> >
> > -Seth
> >
> > 2018-01-29 11:18 GMT-08:00 Wayne Stambaugh  
> > >>:
> >
> >     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 this patch.  Please verify the OpenCascade
> license
> >     with something that I can verify to ensure we are not
> violating and
> >     licensing terms.
> >
> >     Cheers,
> >
> >     Wayne
> >
> >     [1]: https://www.opencascade.com/content/licensing
> 
> >      >
> >     [2]:
> >   
>  https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses
> 
> >   
>   >
> >
> >     On 1/29/2018 1:54 PM, Seth Hillbrand wrote:
> >     > ​Hi All-
> >     >
> >    

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

[Seth Hillbrand]

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 linking)

- But there is also Clause 6 that covers us: "As an exception to the
Sections above, you may also combine or link a "work that uses the Library"
with the Library to produce a work containing portions of the Library, and
distribute that work under terms of your choice, provided that the terms
permit modification of the work for the customer's own use and reverse
engineering for debugging such modifications."

-S

2018-01-29 12:04 GMT-08:00 Wayne Stambaugh :

> 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 the LGPL (including the
> exception) so I am interpreting this as v2.1 only.  I do not have a copy
> (and I'm not going to sign up to get a copy so please check the
> copyright in the source to see if it matches the website) of the
> opencascade source archive to see if the license in the source
> specifically states "v2.1 or (at your option) any later version" which
> is typically how the GPL and LGPL are used.  If it does, than I can
> safely add this patch because I can make the claim that I am using
> opencascade under at later version of the LGPL which is compatible with
> the GPL 3 used by kicad.
>
> According to the folks at the FSF:
>
> "Please note that GPLv2 is, by itself, not compatible with GPLv3.
> However, most software released under GPLv2 allows you to use the terms
> of later versions of the GPL as well. When this is the case, you can use
> the code under GPLv3 to make the desired combination. To learn more
> about compatibility between GNU licenses, please see our FAQ."
>
> I hope this clarifies why I am hesitant to merge this patch and what
> needs to clarified.  Isn't licensing fun! ;)
>
> Thanks,
>
> Wayne
>
> On 1/29/2018 2:47 PM, Seth Hillbrand wrote:
> > 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 is compatible with GPLv2 and GPLv3."
> >
> > Did I miss something?
> >
> > -Seth
> >
> > 2018-01-29 11:18 GMT-08:00 Wayne Stambaugh  > >:
> >
> > 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 this patch.  Please verify the OpenCascade license
> > with something that I can verify to ensure we are not violating and
> > licensing terms.
> >
> > Cheers,
> >
> > Wayne
> >
> > [1]: https://www.opencascade.com/content/licensing
> > 
> > [2]:
> > https://www.gnu.org/licenses/license-list.en.html#
> GPLCompatibleLicenses
> >  GPLCompatibleLicenses>
> >
> > On 1/29/2018 1:54 PM, Seth Hillbrand wrote:
> > > ​Hi All-
> > >
> > > Currently, the build requires the opencascade community edition.
> For
> > > various reasons, I need to have the current non-community edition
> of
> > > OpenCASCADE installed on my work machine.
> > >
> > > The attached patch allows compiling KiCad with either the
> OpenCASCADE
> > > community edition or standard edition.
> > >
> > > I've tested on a homebrew-based Mac install as well as Linux but
> > haven't
> > > verified MSW, if someone would be willing to test it there, that
> would
> > > be great!  The basic search routines are lightly modified from
> > FreeCAD's
> > > logic and keep their LGPL copyright on the CMake file.
> > >
> > > -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
> > 

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

[Wayne Stambaugh]

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 the GNU Lesser General Public
License version 2.1, you may distribute such object code incorporating
material from header files provided with the Open CASCADE Technology
libraries (including code of CDL generic classes) under terms of your
choice, provided that you give prominent notice in supporting
documentation to this code that it makes use of or is based on
facilities provided by the Open CASCADE Technology software."

So it appears since we are only using oce as a library and we are afaik
not modifying any of the oce or opencascade source files, we should be
able to use it with any license of our choice.  Anyone interpreting this
differently than I am?


On 1/29/2018 3:12 PM, José Ignacio wrote:
> 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:
> 
> "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 the LGPL (including the
> exception) so I am interpreting this as v2.1 only.  I do not have a copy
> (and I'm not going to sign up to get a copy so please check the
> copyright in the source to see if it matches the website) of the
> opencascade source archive to see if the license in the source
> specifically states "v2.1 or (at your option) any later version" which
> is typically how the GPL and LGPL are used.  If it does, than I can
> safely add this patch because I can make the claim that I am using
> opencascade under at later version of the LGPL which is compatible with
> the GPL 3 used by kicad.
> 
> According to the folks at the FSF:
> 
> "Please note that GPLv2 is, by itself, not compatible with GPLv3.
> However, most software released under GPLv2 allows you to use the terms
> of later versions of the GPL as well. When this is the case, you can use
> the code under GPLv3 to make the desired combination. To learn more
> about compatibility between GNU licenses, please see our FAQ."
> 
> I hope this clarifies why I am hesitant to merge this patch and what
> needs to clarified.  Isn't licensing fun! ;)
> 
> Thanks,
> 
> Wayne
> 
> On 1/29/2018 2:47 PM, Seth Hillbrand wrote:
> > 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 is compatible with GPLv2 and GPLv3."
> >
> > Did I miss something?
> >
> > -Seth
> >
> > 2018-01-29 11:18 GMT-08:00 Wayne Stambaugh  
> > >>:
> >
> >     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 this patch.  Please verify the OpenCascade
> license
> >     with something that I can verify to ensure we are not
> violating and
> >     licensing terms.
> >
> >     Cheers,
> >
> >     Wayne
> >
> >     [1]: https://www.opencascade.com/content/licensing
> 
> >      >
> >     [2]:
> >   
>  https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses
> 
> >   
>   >
> >
> >     On 1/29/2018 1:54 PM, Seth Hillbrand wrote:
> >     > ​Hi All-
> >     >
> >     > Currently, the build requires the opencascade community
> edition.  For
> >     > various reasons, I need to have the current non-community
> edition 

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

[José Ignacio]

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:
>
> "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 the LGPL (including the
> exception) so I am interpreting this as v2.1 only.  I do not have a copy
> (and I'm not going to sign up to get a copy so please check the
> copyright in the source to see if it matches the website) of the
> opencascade source archive to see if the license in the source
> specifically states "v2.1 or (at your option) any later version" which
> is typically how the GPL and LGPL are used.  If it does, than I can
> safely add this patch because I can make the claim that I am using
> opencascade under at later version of the LGPL which is compatible with
> the GPL 3 used by kicad.
>
> According to the folks at the FSF:
>
> "Please note that GPLv2 is, by itself, not compatible with GPLv3.
> However, most software released under GPLv2 allows you to use the terms
> of later versions of the GPL as well. When this is the case, you can use
> the code under GPLv3 to make the desired combination. To learn more
> about compatibility between GNU licenses, please see our FAQ."
>
> I hope this clarifies why I am hesitant to merge this patch and what
> needs to clarified.  Isn't licensing fun! ;)
>
> Thanks,
>
> Wayne
>
> On 1/29/2018 2:47 PM, Seth Hillbrand wrote:
> > 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 is compatible with GPLv2 and GPLv3."
> >
> > Did I miss something?
> >
> > -Seth
> >
> > 2018-01-29 11:18 GMT-08:00 Wayne Stambaugh  > >:
> >
> > 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 this patch.  Please verify the OpenCascade license
> > with something that I can verify to ensure we are not violating and
> > licensing terms.
> >
> > Cheers,
> >
> > Wayne
> >
> > [1]: https://www.opencascade.com/content/licensing
> > 
> > [2]:
> > https://www.gnu.org/licenses/license-list.en.html#
> GPLCompatibleLicenses
> >  GPLCompatibleLicenses>
> >
> > On 1/29/2018 1:54 PM, Seth Hillbrand wrote:
> > > ​Hi All-
> > >
> > > Currently, the build requires the opencascade community edition.
> For
> > > various reasons, I need to have the current non-community edition
> of
> > > OpenCASCADE installed on my work machine.
> > >
> > > The attached patch allows compiling KiCad with either the
> OpenCASCADE
> > > community edition or standard edition.
> > >
> > > I've tested on a homebrew-based Mac install as well as Linux but
> > haven't
> > > verified MSW, if someone would be willing to test it there, that
> would
> > > be great!  The basic search routines are lightly modified from
> > FreeCAD's
> > > logic and keep their LGPL copyright on the CMake file.
> > >
> > > -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: 

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

[Andrew Zonenberg]

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 module can be freely swapped for
the original (no signature checks etc)

Static linking is a whole other can of worms because now you have a new
derived work which is a combination of the two. It may indeed be the
case that LGPL 2.1-only and GPL 3+ cannot be STATICALLY linked. But my
reading of the license does not in any way prohibit dynamic linking.

On 29/01/18 12:04, Wayne Stambaugh wrote:
> 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 the LGPL (including the
> exception) so I am interpreting this as v2.1 only.  I do not have a copy
> (and I'm not going to sign up to get a copy so please check the
> copyright in the source to see if it matches the website) of the
> opencascade source archive to see if the license in the source
> specifically states "v2.1 or (at your option) any later version" which
> is typically how the GPL and LGPL are used.  If it does, than I can
> safely add this patch because I can make the claim that I am using
> opencascade under at later version of the LGPL which is compatible with
> the GPL 3 used by kicad.
> 
> According to the folks at the FSF:
> 
> "Please note that GPLv2 is, by itself, not compatible with GPLv3.
> However, most software released under GPLv2 allows you to use the terms
> of later versions of the GPL as well. When this is the case, you can use
> the code under GPLv3 to make the desired combination. To learn more
> about compatibility between GNU licenses, please see our FAQ."
> 
> I hope this clarifies why I am hesitant to merge this patch and what
> needs to clarified.  Isn't licensing fun! ;)
> 
> Thanks,
> 
> Wayne
> 
> On 1/29/2018 2:47 PM, Seth Hillbrand wrote:
>> 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 is compatible with GPLv2 and GPLv3."
>>
>> Did I miss something?
>>
>> -Seth
>>
>> 2018-01-29 11:18 GMT-08:00 Wayne Stambaugh > >:
>>
>> 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 this patch.  Please verify the OpenCascade license
>> with something that I can verify to ensure we are not violating and
>> licensing terms.
>>
>> Cheers,
>>
>> Wayne
>>
>> [1]: https://www.opencascade.com/content/licensing
>> 
>> [2]:
>> https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses
>> 
>>
>> On 1/29/2018 1:54 PM, Seth Hillbrand wrote:
>> > ​Hi All-
>> >
>> > Currently, the build requires the opencascade community edition.  For
>> > various reasons, I need to have the current non-community edition of
>> > OpenCASCADE installed on my work machine.
>> >
>> > The attached patch allows compiling KiCad with either the OpenCASCADE
>> > community edition or standard edition.  
>> >
>> > I've tested on a homebrew-based Mac install as well as Linux but
>> haven't
>> > verified MSW, if someone would be willing to test it there, that would
>> > be great!  The basic search routines are lightly modified from
>> FreeCAD's
>> > logic and keep their LGPL copyright on the CMake file.
>> >
>> > -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
>> 

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

[Simon Wells]

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 allow occ in place of 
oce as was my initial thoughts but i have not worked on this due to the issues 
experienced by nick


btw as oce is just a fork of occt would that not have the same issues?

> On 30/01/2018, at 9:04 AM, Wayne Stambaugh  wrote:
> 
> 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 the LGPL (including the
> exception) so I am interpreting this as v2.1 only.  I do not have a copy
> (and I'm not going to sign up to get a copy so please check the
> copyright in the source to see if it matches the website) of the
> opencascade source archive to see if the license in the source
> specifically states "v2.1 or (at your option) any later version" which
> is typically how the GPL and LGPL are used.  If it does, than I can
> safely add this patch because I can make the claim that I am using
> opencascade under at later version of the LGPL which is compatible with
> the GPL 3 used by kicad.
> 
> According to the folks at the FSF:
> 
> "Please note that GPLv2 is, by itself, not compatible with GPLv3.
> However, most software released under GPLv2 allows you to use the terms
> of later versions of the GPL as well. When this is the case, you can use
> the code under GPLv3 to make the desired combination. To learn more
> about compatibility between GNU licenses, please see our FAQ."
> 
> I hope this clarifies why I am hesitant to merge this patch and what
> needs to clarified.  Isn't licensing fun! ;)
> 
> Thanks,
> 
> Wayne
> 
> On 1/29/2018 2:47 PM, Seth Hillbrand wrote:
>> 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 is compatible with GPLv2 and GPLv3."
>> 
>> Did I miss something?
>> 
>> -Seth
>> 
>> 2018-01-29 11:18 GMT-08:00 Wayne Stambaugh > >>:
>> 
>>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 this patch.  Please verify the OpenCascade license
>>with something that I can verify to ensure we are not violating and
>>licensing terms.
>> 
>>Cheers,
>> 
>>Wayne
>> 
>>[1]: https://www.opencascade.com/content/licensing
>>> >
>>[2]:
>>https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses 
>> 
>>> >
>> 
>>On 1/29/2018 1:54 PM, Seth Hillbrand wrote:
>>> ​Hi All-
>>> 
>>> Currently, the build requires the opencascade community edition.  For
>>> various reasons, I need to have the current non-community edition of
>>> OpenCASCADE installed on my work machine.
>>> 
>>> The attached patch allows compiling KiCad with either the OpenCASCADE
>>> community edition or standard edition.  
>>> 
>>> I've tested on a homebrew-based Mac install as well as Linux but
>>haven't
>>> verified MSW, if someone would be willing to test it there, that would
>>> be great!  The basic search routines are lightly modified from
>>FreeCAD's
>>> logic and keep their LGPL copyright on the CMake file.
>>> 
>>> -Seth​
>>> 
>>> 
>>> 
>>> ___
>>> 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

[Wayne Stambaugh]

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 the LGPL (including the
exception) so I am interpreting this as v2.1 only.  I do not have a copy
(and I'm not going to sign up to get a copy so please check the
copyright in the source to see if it matches the website) of the
opencascade source archive to see if the license in the source
specifically states "v2.1 or (at your option) any later version" which
is typically how the GPL and LGPL are used.  If it does, than I can
safely add this patch because I can make the claim that I am using
opencascade under at later version of the LGPL which is compatible with
the GPL 3 used by kicad.

According to the folks at the FSF:

"Please note that GPLv2 is, by itself, not compatible with GPLv3.
However, most software released under GPLv2 allows you to use the terms
of later versions of the GPL as well. When this is the case, you can use
the code under GPLv3 to make the desired combination. To learn more
about compatibility between GNU licenses, please see our FAQ."

I hope this clarifies why I am hesitant to merge this patch and what
needs to clarified.  Isn't licensing fun! ;)

Thanks,

Wayne

On 1/29/2018 2:47 PM, Seth Hillbrand wrote:
> 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 is compatible with GPLv2 and GPLv3."
> 
> Did I miss something?
> 
> -Seth
> 
> 2018-01-29 11:18 GMT-08:00 Wayne Stambaugh  >:
> 
> 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 this patch.  Please verify the OpenCascade license
> with something that I can verify to ensure we are not violating and
> licensing terms.
> 
> Cheers,
> 
> Wayne
> 
> [1]: https://www.opencascade.com/content/licensing
> 
> [2]:
> https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses
> 
> 
> On 1/29/2018 1:54 PM, Seth Hillbrand wrote:
> > ​Hi All-
> >
> > Currently, the build requires the opencascade community edition.  For
> > various reasons, I need to have the current non-community edition of
> > OpenCASCADE installed on my work machine.
> >
> > The attached patch allows compiling KiCad with either the OpenCASCADE
> > community edition or standard edition.  
> >
> > I've tested on a homebrew-based Mac install as well as Linux but
> haven't
> > verified MSW, if someone would be willing to test it there, that would
> > be great!  The basic search routines are lightly modified from
> FreeCAD's
> > logic and keep their LGPL copyright on the CMake file.
> >
> > -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

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

[Seth Hillbrand]

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 is
compatible with GPLv2 and GPLv3."

Did I miss something?

-Seth

2018-01-29 11:18 GMT-08:00 Wayne Stambaugh :

> 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 this patch.  Please verify the OpenCascade license
> with something that I can verify to ensure we are not violating and
> licensing terms.
>
> Cheers,
>
> Wayne
>
> [1]: https://www.opencascade.com/content/licensing
> [2]: https://www.gnu.org/licenses/license-list.en.html#
> GPLCompatibleLicenses
>
> On 1/29/2018 1:54 PM, Seth Hillbrand wrote:
> > ​Hi All-
> >
> > Currently, the build requires the opencascade community edition.  For
> > various reasons, I need to have the current non-community edition of
> > OpenCASCADE installed on my work machine.
> >
> > The attached patch allows compiling KiCad with either the OpenCASCADE
> > community edition or standard edition.
> >
> > I've tested on a homebrew-based Mac install as well as Linux but haven't
> > verified MSW, if someone would be willing to test it there, that would
> > be great!  The basic search routines are lightly modified from FreeCAD's
> > logic and keep their LGPL copyright on the CMake file.
> >
> > -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

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

[Wayne Stambaugh]

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 this patch.  Please verify the OpenCascade license
with something that I can verify to ensure we are not violating and
licensing terms.

Cheers,

Wayne

[1]: https://www.opencascade.com/content/licensing
[2]: https://www.gnu.org/licenses/license-list.en.html#GPLCompatibleLicenses

On 1/29/2018 1:54 PM, Seth Hillbrand wrote:
> ​Hi All-
> 
> Currently, the build requires the opencascade community edition.  For
> various reasons, I need to have the current non-community edition of
> OpenCASCADE installed on my work machine.
> 
> The attached patch allows compiling KiCad with either the OpenCASCADE
> community edition or standard edition.  
> 
> I've tested on a homebrew-based Mac install as well as Linux but haven't
> verified MSW, if someone would be willing to test it there, that would
> be great!  The basic search routines are lightly modified from FreeCAD's
> logic and keep their LGPL copyright on the CMake file.
> 
> -Seth​
> 
> 
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 

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

Re: [Kicad-developers] wxwidgets fork progress

[Adam Wolf]

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 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 set the bug to “Fix Committed”.
>
>
> BTW @Adam:
> There are still 2 wxPython macOS patches:
> (1) The "wxpython-3.0.0_macosx.patch” is not needed as it is the overlay
> stuff for wxWidgets.
> (2) I don’t know about the “…_multiarch.patch”. You don’t apply it as far
> as I can see and it seems to be fine without?
>   => Still needed?
>
>
> Regards,
> Bernhard
>
>
> On 29. Jan 2018, at 13:47, Bernhard Stegmaier 
> wrote:
>
> 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,
> Bernhard
>
>
> On 29. Jan 2018, at 00:32, Adam Wolf 
> wrote:
>
> I think I see it now.  I can probably fix this tonight.  Thanks!
>
> Adam
>
> On Jan 28, 2018 5:30 PM, "Bernhard Stegmaier" 
> wrote:
>
>> Quick look into the build… seems to pull in wrong wxWidgets libs.
>> The build in question includes some 3.0.0 wxWidgets libraries which I
>> guess come from wxPython download.
>> The fork should create 3.0.4 libraries...
>>
>> On 29. Jan 2018, at 00:05, Bernhard Stegmaier 
>> wrote:
>>
>> I just had a quick look and it looks fine.
>>
>> Also my first guess is that maybe something got messed up in the folder
>> hierarchy when copying wxPython/wxWidgets together, so that e.g. here
>>   WXPYTHON_BUILD_OPTS="WX_CONFIG=`pwd`/../../wx-bin/bin/wx-config \
>> some wrong wxWidgets (not the one of the fork) gets pulled in.
>>
>> Too late here already to check just by review, will try tomorrow… :)
>>
>> On 29. Jan 2018, at 00:00, Adam Wolf 
>> wrote:
>>
>> Yeah.  The previous build script downloaded a wxpython tarball, which
>> included wxwidgets.
>>
>> All my update did was move the wxpython subdirectory into a git checkout
>> of the wxwidgets tree, and build that way.
>>
>> One quick thing would be to just do a diff between the wxwidgets included
>> with wxpython 3.0.2.0, and the tree.  At this point, nothing would surprise
>> me :)
>>
>> Adam
>>
>>
>>
>> On Jan 28, 2018 4:54 PM, "Bernhard Stegmaier" 
>> wrote:
>>
>>> Sure.
>>> I’ll have a look tomorrow and try to build wxWidgets/wxPython the same
>>> way the script does.
>>>
>>> On 28. Jan 2018, at 23:44, Nick Østergaard  wrote:
>>>
>>> You don't need to revert it. I can just choose the latest workin hash in
>>> the jenkins job. I would rather we fix it somehow. :)
>>>
>>> @Bernhard, the build scripts in question are
>>> https://github.com/wayneandlayne/KiCadMacOSPackaging
>>>
>>> Maybe you can have a got at it?
>>>
>>> 2018-01-28 23:41 GMT+01:00 Nick Østergaard :
>>>
 I assume this is the bug you are talking about:
 https://bugs.launchpad.net/kicad/+bug/1745868

 2018-01-28 23:14 GMT+01:00 Adam Wolf :

> I was able to get the wxwidgets stuff switched over but there's a bug
> in the big tracker saying it didn't work.  I will continue to look into it
> as I can.  I should be over this illness by the end of this week, it looks
> like.
>
> I can revert the packaging change so the next builds will work again.
>
> Sorry folks, I have lost weeks and weeks of productivity and am trying
> to do my best.
>
> 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] wxwidgets fork progress

[Bernhard Stegmaier]

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 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 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 set the bug to “Fix Committed”.
>> 
>> 
>> BTW @Adam:
>> There are still 2 wxPython macOS patches:
>> (1) The "wxpython-3.0.0_macosx.patch” is not needed as it is the overlay
>> stuff for wxWidgets.
>> (2) I don’t know about the “…_multiarch.patch”. You don’t apply it as
>> far as I can see and it seems to be fine without?
>>   => Still needed?
>> 
>> 
>> Regards,
>> Bernhard
>> 
>> 
>>> On 29. Jan 2018, at 13:47, Bernhard Stegmaier >> >> wrote:
>>> 
>>> 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,
>>> Bernhard
>>> 
>>> 
 On 29. Jan 2018, at 00:32, Adam Wolf 
 >> wrote:
 
 I think I see it now.  I can probably fix this tonight.  Thanks!
 
 Adam
 
 On Jan 28, 2018 5:30 PM, "Bernhard Stegmaier"
  
 >> wrote:
 
Quick look into the build… seems to pull in wrong wxWidgets libs.
The build in question includes some 3.0.0 wxWidgets libraries
which I guess come from wxPython download.
The fork should create 3.0.4 libraries...
 
>On 29. Jan 2018, at 00:05, Bernhard Stegmaier
> 
> >> wrote:
> 
>I just had a quick look and it looks fine.
> 
>Also my first guess is that maybe something got messed up in the
>folder hierarchy when copying wxPython/wxWidgets together, so
>that e.g. here
>  WXPYTHON_BUILD_OPTS="WX_CONFIG=`pwd`/../../wx-bin/bin/wx-config \
>some wrong wxWidgets (not the one of the fork) gets pulled in.
> 
>Too late here already to check just by review, will try tomorrow… :)
> 
>>On 29. Jan 2018, at 00:00, Adam Wolf
>>
>>> >> wrote:
>> 
>>Yeah.  The previous build script downloaded a wxpython tarball,
>>which included wxwidgets.
>> 
>>All my update did was move the wxpython subdirectory into a git
>>checkout of the wxwidgets tree, and build that way.
>> 
>>One quick thing would be to just do a diff between the
>>wxwidgets included with wxpython 3.0.2.0, and the tree.  At
>>this point, nothing would surprise me :)
>> 
>>Adam
>> 
>> 
>> 
>>On Jan 28, 2018 4:54 PM, "Bernhard Stegmaier"
>> 
>> >> wrote:
>> 
>>Sure.
>>I’ll have a look tomorrow and try to build
>>wxWidgets/wxPython the same way the script does.
>> 
>>>On 28. Jan 2018, at 23:44, Nick Østergaard
>>> 
>>> >> wrote:
>>> 
>>>You don't need to revert it. I can just choose the latest
>>>workin hash in the jenkins job. I would rather we fix it
>>>somehow. :)
>>> 
>>>@Bernhard, the build scripts in question are
>>>https://github.com/wayneandlayne/KiCadMacOSPackaging 
>>> 
>>>>> >
>>> 
>>>Maybe you 

Re: [Kicad-developers] wxwidgets fork progress

[Wayne Stambaugh]

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 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 set the bug to “Fix Committed”.
> 
> 
> BTW @Adam:
> There are still 2 wxPython macOS patches:
> (1) The "wxpython-3.0.0_macosx.patch” is not needed as it is the overlay
> stuff for wxWidgets.
> (2) I don’t know about the “…_multiarch.patch”. You don’t apply it as
> far as I can see and it seems to be fine without?
>   => Still needed?
> 
> 
> Regards,
> Bernhard
> 
> 
>> On 29. Jan 2018, at 13:47, Bernhard Stegmaier > > wrote:
>>
>> 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,
>> Bernhard
>>
>>
>>> On 29. Jan 2018, at 00:32, Adam Wolf >> > wrote:
>>>
>>> I think I see it now.  I can probably fix this tonight.  Thanks!
>>>
>>> Adam
>>>
>>> On Jan 28, 2018 5:30 PM, "Bernhard Stegmaier"
>>> > wrote:
>>>
>>> Quick look into the build… seems to pull in wrong wxWidgets libs.
>>> The build in question includes some 3.0.0 wxWidgets libraries
>>> which I guess come from wxPython download.
>>> The fork should create 3.0.4 libraries...
>>>
 On 29. Jan 2018, at 00:05, Bernhard Stegmaier
 > wrote:

 I just had a quick look and it looks fine.

 Also my first guess is that maybe something got messed up in the
 folder hierarchy when copying wxPython/wxWidgets together, so
 that e.g. here
   WXPYTHON_BUILD_OPTS="WX_CONFIG=`pwd`/../../wx-bin/bin/wx-config \
 some wrong wxWidgets (not the one of the fork) gets pulled in.

 Too late here already to check just by review, will try tomorrow… :)

> On 29. Jan 2018, at 00:00, Adam Wolf
>  > wrote:
>
> Yeah.  The previous build script downloaded a wxpython tarball,
> which included wxwidgets.
>
> All my update did was move the wxpython subdirectory into a git
> checkout of the wxwidgets tree, and build that way.
>
> One quick thing would be to just do a diff between the
> wxwidgets included with wxpython 3.0.2.0, and the tree.  At
> this point, nothing would surprise me :)
>
> Adam
>
>
>
> On Jan 28, 2018 4:54 PM, "Bernhard Stegmaier"
> > wrote:
>
> Sure.
> I’ll have a look tomorrow and try to build
> wxWidgets/wxPython the same way the script does.
>
>> On 28. Jan 2018, at 23:44, Nick Østergaard
>> > wrote:
>>
>> You don't need to revert it. I can just choose the latest
>> workin hash in the jenkins job. I would rather we fix it
>> somehow. :)
>>
>> @Bernhard, the build scripts in question are
>> https://github.com/wayneandlayne/KiCadMacOSPackaging
>> 
>>
>> Maybe you can have a got at it?
>>
>> 2018-01-28 23:41 GMT+01:00 Nick Østergaard
>> >:
>>
>> I assume this is the bug you are talking about:
>> https://bugs.launchpad.net/kicad/+bug/1745868
>> 
>>
>> 2018-01-28 23:14 GMT+01:00 Adam Wolf
>> > >:
>>
>> I was able to get the wxwidgets stuff switched
>> over but there's a bug in the big tracker saying
>> it didn't work.  I will continue to look into it
>> as I can.  I should be over this illness by the
>> end of this week, it looks like.
>>
>> I can revert the packaging change so the next
>> builds will work 

Re: [Kicad-developers] wxwidgets fork progress

[Bernhard Stegmaier]

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 set the bug to “Fix Committed”.


BTW @Adam:
There are still 2 wxPython macOS patches:
(1) The "wxpython-3.0.0_macosx.patch” is not needed as it is the overlay stuff 
for wxWidgets.
(2) I don’t know about the “…_multiarch.patch”. You don’t apply it as far as I 
can see and it seems to be fine without?
  => Still needed?


Regards,
Bernhard


> On 29. Jan 2018, at 13:47, Bernhard Stegmaier  wrote:
> 
> 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,
> Bernhard
> 
> 
>> On 29. Jan 2018, at 00:32, Adam Wolf > > wrote:
>> 
>> I think I see it now.  I can probably fix this tonight.  Thanks!
>> 
>> Adam
>> 
>> On Jan 28, 2018 5:30 PM, "Bernhard Stegmaier" > > wrote:
>> Quick look into the build… seems to pull in wrong wxWidgets libs.
>> The build in question includes some 3.0.0 wxWidgets libraries which I guess 
>> come from wxPython download.
>> The fork should create 3.0.4 libraries...
>> 
>>> On 29. Jan 2018, at 00:05, Bernhard Stegmaier >> > wrote:
>>> 
>>> I just had a quick look and it looks fine.
>>> 
>>> Also my first guess is that maybe something got messed up in the folder 
>>> hierarchy when copying wxPython/wxWidgets together, so that e.g. here
>>>   WXPYTHON_BUILD_OPTS="WX_CONFIG=`pwd`/../../wx-bin/bin/wx-config \
>>> some wrong wxWidgets (not the one of the fork) gets pulled in.
>>> 
>>> Too late here already to check just by review, will try tomorrow… :)
>>> 
 On 29. Jan 2018, at 00:00, Adam Wolf > wrote:
 
 Yeah.  The previous build script downloaded a wxpython tarball, which 
 included wxwidgets.
 
 All my update did was move the wxpython subdirectory into a git checkout 
 of the wxwidgets tree, and build that way.
 
 One quick thing would be to just do a diff between the wxwidgets included 
 with wxpython 3.0.2.0, and the tree.  At this point, nothing would 
 surprise me :)
 
 Adam
 
 
 
 On Jan 28, 2018 4:54 PM, "Bernhard Stegmaier" > wrote:
 Sure.
 I’ll have a look tomorrow and try to build wxWidgets/wxPython the same way 
 the script does.
 
> On 28. Jan 2018, at 23:44, Nick Østergaard  > wrote:
> 
> You don't need to revert it. I can just choose the latest workin hash in 
> the jenkins job. I would rather we fix it somehow. :)
> 
> @Bernhard, the build scripts in question are 
> https://github.com/wayneandlayne/KiCadMacOSPackaging 
> 
> 
> Maybe you can have a got at it?
> 
> 2018-01-28 23:41 GMT+01:00 Nick Østergaard  >:
> I assume this is the bug you are talking about:
> https://bugs.launchpad.net/kicad/+bug/1745868 
> 
> 
> 2018-01-28 23:14 GMT+01:00 Adam Wolf  >:
> I was able to get the wxwidgets stuff switched over but there's a bug in 
> the big tracker saying it didn't work.  I will continue to look into it 
> as I can.  I should be over this illness by the end of this week, it 
> looks like.
> 
> I can revert the packaging change so the next builds will work again.
> 
> Sorry folks, I have lost weeks and weeks of productivity and am trying to 
> do my best.
> 
> 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 
> 

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

[Jon Evans]

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 load, show/hide
d-codes, etc) on MacOS.  The change is somewhat less dramatic on Linux, and
I have not tested it on Windows.

The rationale for the change is that iterating over a std::bitset is
somewhat costly, and most items don't exist on that many layers, so I am
trading time for memory but I don't see it as a large memory cost.

-Jon


0001-Use-vector-instead-of-bitset-for-VIEW_ITEM_DATA-laye.patch
Description: Binary data
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

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

[Miguel Angel Ajo]

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 KB...]
   ^
: 
In member function ‘int MODULE_EDITOR_TOOLS::ExplodePadToShapes(const 
TOOL_EVENT&)’:
:332:16:
 warning: declaration of ‘selection’ shadows a member of 'this' [-Wshadow]
 SELECTION& selection = 
m_toolMgr->GetTool()->GetSelection();
^
: 
In member function ‘int MODULE_EDITOR_TOOLS::CreatePadFromShapes(const 
TOOL_EVENT&)’:
:373:16:
 warning: declaration of ‘selection’ shadows a member of 'this' [-Wshadow]
 SELECTION& selection = 
m_toolMgr->GetTool()->GetSelection();
^
: In member 
function ‘bool PAD_TOOL::haveFootprints()’:
:168:11: 
warning: declaration of ‘board’ shadows a member of 'this' [-Wshadow]
 auto& board = *getModel();
   ^
: In member 
function ‘int PAD_TOOL::applyPadSettings(const TOOL_EVENT&)’:
:208:17: 
warning: declaration of ‘selection’ shadows a member of 'this' [-Wshadow]
 const auto& selection = selTool.GetSelection();
 ^
:210:11: 
warning: declaration of ‘frame’ shadows a member of 'this' [-Wshadow]
 auto& frame = *getEditFrame();
   ^
: In member 
function ‘int PAD_TOOL::copyPadSettings(const TOOL_EVENT&)’:
:240:17: 
warning: declaration of ‘selection’ shadows a member of 'this' [-Wshadow]
 const auto& selection = selTool.GetSelection();
 ^
:242:11: 
warning: declaration of ‘frame’ shadows a member of 'this' [-Wshadow]
 auto& frame = *getEditFrame();
   ^
: In member 
function ‘int PAD_TOOL::pushPadSettings(const TOOL_EVENT&)’:
:320:17: 
warning: declaration of ‘selection’ shadows a member of 'this' [-Wshadow]
 const auto& selection = selTool.GetSelection();
 ^
:322:11: 
warning: declaration of ‘frame’ shadows a member of 'this' [-Wshadow]
 auto& frame = *getEditFrame();
   ^
:352:13: 
warning: declaration of ‘module’ shadows a member of 'this' [-Wshadow]
 MODULE* module = srcPad->GetParent();
 ^
: 
In member function ‘int PCB_EDITOR_CONTROL::TrackWidthInc(const TOOL_EVENT&)’:
:316:12:
 warning: declaration of ‘board’ shadows a member of 'this' [-Wshadow]
 BOARD* board = getModel();
^
: 
In member function ‘int PCB_EDITOR_CONTROL::TrackWidthDec(const TOOL_EVENT&)’:
:333:12:
 warning: declaration of ‘board’ shadows a member of 'this' [-Wshadow]
 BOARD* board = getModel();
^
: 
In member function ‘int PCB_EDITOR_CONTROL::ViaSizeInc(const TOOL_EVENT&)’:
:350:12:
 warning: declaration of ‘board’ shadows a member of 'this' [-Wshadow]
 BOARD* board = getModel();
^
: 
In member function ‘int PCB_EDITOR_CONTROL::ViaSizeDec(const TOOL_EVENT&)’:
:367:12:
 warning: declaration of ‘board’ shadows a member of 'this' [-Wshadow]
 BOARD* board = getModel();
^
: 
In member function ‘int PCB_EDITOR_CONTROL::PlaceModule(const TOOL_EVENT&)’:

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

[Nick Østergaard]

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
> 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 University of Bradford
>
> On 29 January 2018 at 15:16, Jean-Samuel Reynaud 
> wrote:
>
>> 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 <
>> c.schoen...@t-online.de 
>> > > >>
>> wrote:
>> > >
>> > > Hello Babar,
>> > >
>> > > Am 29.01.2018 <29%2001%2020%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
>> > 

Re: [Kicad-developers] wxwidgets fork progress

[Bernhard Stegmaier]

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,
Bernhard


> On 29. Jan 2018, at 00:32, Adam Wolf  wrote:
> 
> I think I see it now.  I can probably fix this tonight.  Thanks!
> 
> Adam
> 
> On Jan 28, 2018 5:30 PM, "Bernhard Stegmaier"  > wrote:
> Quick look into the build… seems to pull in wrong wxWidgets libs.
> The build in question includes some 3.0.0 wxWidgets libraries which I guess 
> come from wxPython download.
> The fork should create 3.0.4 libraries...
> 
>> On 29. Jan 2018, at 00:05, Bernhard Stegmaier > > wrote:
>> 
>> I just had a quick look and it looks fine.
>> 
>> Also my first guess is that maybe something got messed up in the folder 
>> hierarchy when copying wxPython/wxWidgets together, so that e.g. here
>>   WXPYTHON_BUILD_OPTS="WX_CONFIG=`pwd`/../../wx-bin/bin/wx-config \
>> some wrong wxWidgets (not the one of the fork) gets pulled in.
>> 
>> Too late here already to check just by review, will try tomorrow… :)
>> 
>>> On 29. Jan 2018, at 00:00, Adam Wolf >> > wrote:
>>> 
>>> Yeah.  The previous build script downloaded a wxpython tarball, which 
>>> included wxwidgets.
>>> 
>>> All my update did was move the wxpython subdirectory into a git checkout of 
>>> the wxwidgets tree, and build that way.
>>> 
>>> One quick thing would be to just do a diff between the wxwidgets included 
>>> with wxpython 3.0.2.0, and the tree.  At this point, nothing would surprise 
>>> me :)
>>> 
>>> Adam
>>> 
>>> 
>>> 
>>> On Jan 28, 2018 4:54 PM, "Bernhard Stegmaier" >> > wrote:
>>> Sure.
>>> I’ll have a look tomorrow and try to build wxWidgets/wxPython the same way 
>>> the script does.
>>> 
 On 28. Jan 2018, at 23:44, Nick Østergaard > wrote:
 
 You don't need to revert it. I can just choose the latest workin hash in 
 the jenkins job. I would rather we fix it somehow. :)
 
 @Bernhard, the build scripts in question are 
 https://github.com/wayneandlayne/KiCadMacOSPackaging 
 
 
 Maybe you can have a got at it?
 
 2018-01-28 23:41 GMT+01:00 Nick Østergaard >:
 I assume this is the bug you are talking about:
 https://bugs.launchpad.net/kicad/+bug/1745868 
 
 
 2018-01-28 23:14 GMT+01:00 Adam Wolf >:
 I was able to get the wxwidgets stuff switched over but there's a bug in 
 the big tracker saying it didn't work.  I will continue to look into it as 
 I can.  I should be over this illness by the end of this week, it looks 
 like.
 
 I can revert the packaging change so the next builds will work again.
 
 Sorry folks, I have lost weeks and weeks of productivity and am trying to 
 do my best.
 
 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 
>> 
> 

___
Mailing list: 

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

[Babar Malik]

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 University of Bradford

On 29 January 2018 at 15:16, Jean-Samuel Reynaud 
wrote:

> 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 <
> c.schoen...@t-online.de 
> > > >>
> 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
> > 
> > >
> >
> >
> > --

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] Kicad Build Issue on Ubuntu

[Nick Østergaard]

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 following error message.
"*[  0%] creating 'boost scratch repo' specifically for boost to track
boost patches*
*/bin/sh: 1: bzr: not found*
*make[2]: ***
[../../.downloads-by-cmake/boost_1_54_0/src/boost-stamp/boost-bzr_init_boost]
Error 127*
*make[1]: *** [CMakeFiles/boost.dir/all] Error 2*
*make: *** [all] Error 2*
"
Can you please have a look on that?
I will be really thankful for the assistance.

Regards,
Babar Malik.

Best Regards,
Muhammad Babar Malik
Namal College Mianwali
An Associate College of University of Bradford

On 26 January 2018 at 19:03, Jeff Young  wrote:

> If you don’t need Python you can turn it off by adding:
>
> -DKICAD_SCRIPTING_WXPYTHON=OFF
>
> to your cmake command.
>
> Might be a short-term solution until someone who knows Ubuntu can help get
> you up and running.
>
> Cheers,
> Jeff
>
> On 26 Jan 2018, at 13:45, Babar Malik  wrote:
>
> Dear all,
> I am trying to build Kicad on Ubuntu 14.04 but I am facing a problem with
> "wxPython". I tried a lot to install this package but the problem is still
> here. The exact error shown on the terminal is *"CMake Error at
> CMakeLists.txt:708 (message):*
> *  wxPython version 3.0 does not appear to be installed on the system.*
> *"*
> Can anyone please suggest me the solution. Your assistance will be highly
> appreciated.
>
>
>
>
>
>
>
>
> Best Regards,
> Muhammad Babar Malik
> Namal College Mianwali
> An Associate College of University of Bradford
> ___
> Mailing list: https://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