Re: [Kicad-developers] kicad StepUp for kicad users after stable release has come out

[easyw]

Hi Mark

It is not a kicad feature, in fact it doesn't
even run inside kicad. It's better off on the FreeCAD's website as a
feature than KiCad because its entirely a freecad plugin.


at the moment the script cannot be easily invoked from inside pcbnew 
because of some missing python API interface...
I'm hoping that something similar to the following request could become 
a reality :)

https://bugs.launchpad.net/kicad/+bug/1526064
"Ability to assign shortcuts to run a specific script or adding toolbar 
buttons would be great!"


Anyway I'm trying to let kicad users knowing about the exporter in kicad 
website, because kicad users are the people who will use the exporter to 
get a mechanical model of their board and parts...
FreeCAD is used as a 3D MCAD converter, nothing is required by the user 
apart launching the script


I think that many kicad users would be aware of using a different MCAD 
sw they are used to, so forcing them to learn howto use FreeCAD to 
convert their artwork is not my preferred way ...


With kicad StepUp script very little knowledge of FreeCAD is necessary, 
and for the conversion, it is just possible only to install FreeCAD and 
run the script, without doing anything in FreeCAD...


I could also configure the exporter to run the conversion hidden, so the 
FreeCAD process could be not even displayed, but I prefer to see the 
script in action :)

I know it is mine, so it natural that I like it a lot ;)
but have a look at the crazyflie exporter conversion:
https://youtu.be/XmNGdqkKbpM


I was going to create a more fancy external tools section akin to the
made with kicad pages.


please let me know in which way you would like the format to add some 
description to the new section, asap it will be ready, and I'll be happy 
to pull the request


@Wayne

This is what I was thinking.

thank you for your mail and of course for your great work with kicad!

Maurice

On 14/12/2015 17.11, Wayne Stambaugh wrote:

On 12/14/2015 10:04 AM, Mark Roszko wrote:

The problem was he was trying to push it into the features section of
the website previously. It is not a kicad feature, in fact it doesn't
even run inside kicad. It's better off on the FreeCAD's website as a
feature than KiCad because its entirely a freecad plugin.


Agreed.  StepUp is not a KiCad feature.  It is an external tool albeit a
very useful one.




I was going to create a more fancy external tools section akin to the
made with kicad pages.



This is what I was thinking.



___
Mailing list: https://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] FreeCAD StepUp tools Openfile dialog issue on OSX

[easyw]

Hi Jose,

good to know! :)

I think that FreeCAD would be a very useful companion for KiCad...
It is open source and works an the same platforms on which KiCad works

I'm also building a 3D mechanical library that is based on KiCad 
official '.pretty' modules, that will let users to benefit of 3D MCAD 
models in a easier way


please have a look at the kicad forum
https://forum.kicad.info/t/3d-new-library-for-mechanical-cad-exporting-and-enclosure-design/1763
I managed to do most of SMD parts just using my parametric script to 
build the 3D models, and I'm getting some help from people used to MCAD 
sw to build other models, connectors included...


keep in touch
Maurice :)

On 14/12/2015 20.56, Jose A. Saumell wrote:

No problem, thank you for the tools, I am working on a new board and
using the FreeCAD only workflow. Today created a PCB 3D model in step
which is really valuable!
Take care

On Mon, Dec 14, 2015 at 4:43 PM easyw > wrote:

Hi Jose,

I can reproduce it in OSX Lion, so I can debug :)

Thank you for reporting it and also for the solution-workaround you have
found!

keep in touch
Maurice :)

On 14/12/2015 16.43, Jose A. Saumell wrote:
 > Hi,
 >
 > I've ran into an issue whenever I had to use the StepUp tools on
Freecad
 > to open a footprint and do the alignment of 3D model.
 >
 > I would get an open file dialog but nothing would happen after
selecting
 > the .kicad_mod file.
 >
 > Inside kicad-StepUp-tools.FCMacro:
 > The name[0] variable would return an empty value.
 >
 > I worked around the problem by not using native OSX Open file dialog:
 > //
 >
 > name=QtGui.QFileDialog.getOpenFileName(self, 'Open file',
 > last_file_path,"kicad module files (*.kicad_mod)",
 > options=QtGui.QFileDialog.DontUseNativeDialog )[0]
 >
 > //
 >
 > This is working for me now, not sure exactly why it is not
working with
 > native OSX dialog.
 >
 >
 > Cheers, Jose
 >
 >
 >
 >
 >
 >
 > ___
 > Mailing list: https://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] Removal of download_boost.cmake.

[Wayne Stambaugh]

Your patch was committed to the product branch r6375.  Thank you for
your contribution to KiCad.

Cheers,

Wayne

On 12/14/2015 6:02 PM, Kristian Nielsen wrote:
> Ok, looking further, I think it is just an oversight, GLM_INCLUDE_DIR is
> missing in 3d-viewer/CMakeLists.txt. Adding it as per the attached patch
> fixes the error for me. The problem will only be seen when GLM is in a
> different location from other libraries already included in CMakeLists.txt.
> 
> Wayne, will you pick up the attached one-liner patch directly?
> 
> Wayne Stambaugh  writes:
> 
>> What is the result of `grep GLM < CMakeCache.txt` when run from your
>> build folder?  You should see something like:
> 
> Yes, it's very similar:
> 
> $ grep GLM < CMakeCache.txt 
> //GLM library header path.
> GLM_INCLUDE_DIR:PATH=/home/knielsen/kicad/include
> //Details about finding GLM
> FIND_PACKAGE_MESSAGE_DETAILS_GLM:INTERNAL=[/home/knielsen/kicad/include][0.9.6.3][v0.9.6.3(0.9.5.4)]
> //ADVANCED property for variable: GLM_INCLUDE_DIR
> GLM_INCLUDE_DIR-ADVANCED:INTERNAL=1
> GLM_VERSION_MAJOR:INTERNAL=0
> GLM_VERSION_MINOR:INTERNAL=9
> GLM_VERSION_PATCH:INTERNAL=6
> GLM_VERSION_TWEAK:INTERNAL=3
> 
> Clearly, cmake is finding my installed GLM library from the
> CMAKE_INSTALL_PREFIX (as that is the only place ~/kicad/ is mentioned). I
> get the same error if I explicitly put -DGLM_ROOT_DIR=$HOME/kicad/include on
> the cmake line. It's probably just the missing GLM_INCLUDE_DIR in
> 3d-viewer/CMakeLists.txt
> 
>  - Kristian.
> 


___
Mailing list: https://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] 3D-Viewer openGL (legacy) render

[Mário Luzeiro]

Hello all,

Here are some screenshots of my WIP for a new 3d-viewer, this time it is a 
render based on openGL (legacy):

https://meocloud.pt/link/6f7c5d91-80ec-48a3-808f-09e5ba3b99b3/kicad_3d-viewer-hackrf-one.brd-01.png/
https://meocloud.pt/link/5f192ae1-0c66-4593-a4d4-537b28990a76/kicad_3d-viewer-hackrf-one.brd-02.png/
https://meocloud.pt/link/c52e325e-4626-45a1-a91e-07c30d380b85/kicad_3d-viewer-video.kicad_pcb-01.png/

They show a technical color rendering of the layers. There are still missing 
vias and other (realistic) materials that will be added latter.. (or early next 
year).
Hope back to you when I got the things a bit more polished and give you some 
technical details.

Enjoy a good Christmas / holidays / season!
Mario Luzeiro

___
Mailing list: https://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] some spelling fix

[Marco Ciampa]

On Mon, Dec 14, 2015 at 03:37:16PM +0100, Nick Østergaard wrote:
> Hi Fabien
> 
> What make you think that "Internationalisation" is wrong? That is
> perfectly valid english (british).
> 

Seems that even British people are not so "monolithic" on its correct usage:

https://en.wikipedia.org/wiki/American_and_British_English_spelling_differences#-ise.2C_-ize_.28-isation.2C_-ization.29

I think it is indifferent.

--


Marco Ciampa

I know a joke about UDP, but you might not get it.

++
| GNU/Linux User  #78271 |
| FSFE fellow   #364 |
++


___
Mailing list: https://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 StepUp for kicad users after stable release has come out

[Wayne Stambaugh]

On 12/14/2015 10:04 AM, Mark Roszko wrote:
> The problem was he was trying to push it into the features section of
> the website previously. It is not a kicad feature, in fact it doesn't
> even run inside kicad. It's better off on the FreeCAD's website as a
> feature than KiCad because its entirely a freecad plugin.

Agreed.  StepUp is not a KiCad feature.  It is an external tool albeit a
very useful one.

> 
> 
> I was going to create a more fancy external tools section akin to the
> made with kicad pages.
> 

This is what I was thinking.

___
Mailing list: https://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] FreeCAD StepUp tools Openfile dialog issue on OSX

[Jose A. Saumell]

Hi,

I've ran into an issue whenever I had to use the StepUp tools on Freecad to
open a footprint and do the alignment of 3D model.

I would get an open file dialog but nothing would happen after selecting
the .kicad_mod file.

Inside kicad-StepUp-tools.FCMacro:
The name[0] variable would return an empty value.

I worked around the problem by not using native OSX Open file dialog:
//

name=QtGui.QFileDialog.getOpenFileName(self, 'Open file', last_file_path,"kicad
module files (*.kicad_mod)", options=QtGui.QFileDialog.DontUseNativeDialog
)[0]

//

This is working for me now, not sure exactly why it is not working with
native OSX dialog.


Cheers, Jose
___
Mailing list: https://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 4/4] Drop gcc optimizer bug workaround

[Mark Roszko]

Hence why I am asking, is it intended that we no longer enforce a
single optimization mode at all? It seems like a can of worms because
previously we could assume everyone is -O2. Now with people compiling
at different levels, who knows level dependent bugs could crop up.

On Mon, Dec 14, 2015 at 10:37 AM, Wayne Stambaugh  wrote:
> This should depend on your platforms gcc default setting or spec file if
> you use one.  I'm not sure how this done with clang.  On Debain testing,
> -O2 is the default build optimization setting and -O3 on msys2/mingw32
> and msys2/mingw64.
>
> On 12/14/2015 10:32 AM, Bernhard Stegmaier wrote:
>> I also assumed something like that and therefore had a look yesterday.
>> On OSX it seems to default to -O3, at least that's what I have seen with
>> "make VERBOSE=1".
>>
>>
>> Regards,
>> Bernhard
>>
>> On 2015-12-14 16:01, Mark Roszko wrote:
>>> Stupid question, doesn't this change remove -O2 entirely for all gcc
>>> builds? Previously it defaulted to -O2 if the bug wasn't present. Now
>>> it never optimizes as -O0 is the default.
>>>
>>> On Sat, Dec 12, 2015 at 2:59 PM, Wayne Stambaugh
>>>  wrote:
 I committed your patch in the product branch r6370.  I tested it on
 msys1/mingw32, msys2/mingw32, msys2/mingw64, and Debian testing without
 issues.  You should also be able to be more aggressive with your
 optimization settings should you so desire.  Please keep in mind, if you
 do this and it breaks, you get keep both pieces.

 On 12/1/2015 2:14 AM, Simon Richter wrote:
>
> As boost::polygon is gone, we can drop the workaround for older gcc.
> ---
>  CMakeLists.txt | 15 ---
>  1 file changed, 15 deletions(-)
>
>
>
> ___
> Mailing list: https://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



-- 
Mark

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

Re: [Kicad-developers] [PATCH 4/4] Drop gcc optimizer bug workaround

[Mark Roszko]

Stupid question, doesn't this change remove -O2 entirely for all gcc
builds? Previously it defaulted to -O2 if the bug wasn't present. Now
it never optimizes as -O0 is the default.

On Sat, Dec 12, 2015 at 2:59 PM, Wayne Stambaugh  wrote:
> I committed your patch in the product branch r6370.  I tested it on
> msys1/mingw32, msys2/mingw32, msys2/mingw64, and Debian testing without
> issues.  You should also be able to be more aggressive with your
> optimization settings should you so desire.  Please keep in mind, if you
> do this and it breaks, you get keep both pieces.
>
> On 12/1/2015 2:14 AM, Simon Richter wrote:
>>
>> As boost::polygon is gone, we can drop the workaround for older gcc.
>> ---
>>  CMakeLists.txt | 15 ---
>>  1 file changed, 15 deletions(-)
>>
>>
>>
>> ___
>> Mailing list: https://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



-- 
Mark

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

Re: [Kicad-developers] kicad StepUp for kicad users after stable release has come out

[Mark Roszko]

The problem was he was trying to push it into the features section of
the website previously. It is not a kicad feature, in fact it doesn't
even run inside kicad. It's better off on the FreeCAD's website as a
feature than KiCad because its entirely a freecad plugin.


I was going to create a more fancy external tools section akin to the
made with kicad pages.

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

Re: [Kicad-developers] New development policies.

[Mark Roszko]

I assume I have to update the libcurl patch to add to the
CopyVersionInfoToClipboard mess.

___
Mailing list: https://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] Text rotation Angle and part rotation Angle pcbnew

[Wayne Stambaugh]

On 12/13/2015 8:00 PM, Lachlan Audas wrote:
> You can't set text rotation angle of part reference's and vale's in
> pcbnew,  only part rotation angle,

The code for supporting rotated text is already in the pcbnew file
format.  I just don't know how well Pcbnew itself will handle rotated
text so there may be a lot of work to do.  I'm not trying to scare you
off but it may not be as easy to resolve as it appears.

> 
> This is bit of a problem  for importing eagle  pcb's,   as parts
> reference/vales may have angle's set,  also when manually setting
> angle's you need to enter 900 for 90..  etc
> instead of 90.5 etc  this very odd way of entering angles,   is they any
> objection make a patch to change this to the standard way of entering
> angle's, and allowing rations of
> reference/vale fields ? 

The only solution that I would accept would be a proper wxValidator
designed for angle entry.  There is already wxFloatingPointValidator
that you could reuse to make your life easier.  Your derived version
should clamp the angles from 0 to 360 and have an accessor to return the
converted angle as an integer.

> 
> Lachlan
> 
> 
> 
> 
> 
> ___
> Mailing list: https://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 4/4] Drop gcc optimizer bug workaround

[Bernhard Stegmaier]

I also assumed something like that and therefore had a look yesterday.
On OSX it seems to default to -O3, at least that's what I have seen with 
"make VERBOSE=1".



Regards,
Bernhard

On 2015-12-14 16:01, Mark Roszko wrote:

Stupid question, doesn't this change remove -O2 entirely for all gcc
builds? Previously it defaulted to -O2 if the bug wasn't present. Now
it never optimizes as -O0 is the default.

On Sat, Dec 12, 2015 at 2:59 PM, Wayne Stambaugh  
wrote:

I committed your patch in the product branch r6370.  I tested it on
msys1/mingw32, msys2/mingw32, msys2/mingw64, and Debian testing 
without

issues.  You should also be able to be more aggressive with your
optimization settings should you so desire.  Please keep in mind, if 
you

do this and it breaks, you get keep both pieces.

On 12/1/2015 2:14 AM, Simon Richter wrote:


As boost::polygon is gone, we can drop the workaround for older gcc.
---
 CMakeLists.txt | 15 ---
 1 file changed, 15 deletions(-)



___
Mailing list: https://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 4/4] Drop gcc optimizer bug workaround

[Wayne Stambaugh]

Optimization levels have typically been at the discretion of the builder
in other projects.  I never liked the idea of us forcing an optimization
level even though it resolved an issue related to the boost polygon
library.  You are correct.  There may be some optimization level bugs
but I haven't run into any up to this point.  I would rather the builder
override the system default optimization level if it is using and overly
aggressive level.  Now that we are providing nightly builds for most
platforms, the reason for controlling the build optimization level is
less critical.  When we were asking users to compile from source, it
made more sense.  We'll see, I may regret this decision.  If it becomes
a huge issue like it used to be, I can always change it back.

On 12/14/2015 10:57 AM, Mark Roszko wrote:
> Hence why I am asking, is it intended that we no longer enforce a
> single optimization mode at all? It seems like a can of worms because
> previously we could assume everyone is -O2. Now with people compiling
> at different levels, who knows level dependent bugs could crop up.
> 
> On Mon, Dec 14, 2015 at 10:37 AM, Wayne Stambaugh  
> wrote:
>> This should depend on your platforms gcc default setting or spec file if
>> you use one.  I'm not sure how this done with clang.  On Debain testing,
>> -O2 is the default build optimization setting and -O3 on msys2/mingw32
>> and msys2/mingw64.
>>
>> On 12/14/2015 10:32 AM, Bernhard Stegmaier wrote:
>>> I also assumed something like that and therefore had a look yesterday.
>>> On OSX it seems to default to -O3, at least that's what I have seen with
>>> "make VERBOSE=1".
>>>
>>>
>>> Regards,
>>> Bernhard
>>>
>>> On 2015-12-14 16:01, Mark Roszko wrote:
 Stupid question, doesn't this change remove -O2 entirely for all gcc
 builds? Previously it defaulted to -O2 if the bug wasn't present. Now
 it never optimizes as -O0 is the default.

 On Sat, Dec 12, 2015 at 2:59 PM, Wayne Stambaugh
  wrote:
> I committed your patch in the product branch r6370.  I tested it on
> msys1/mingw32, msys2/mingw32, msys2/mingw64, and Debian testing without
> issues.  You should also be able to be more aggressive with your
> optimization settings should you so desire.  Please keep in mind, if you
> do this and it breaks, you get keep both pieces.
>
> On 12/1/2015 2:14 AM, Simon Richter wrote:
>>
>> As boost::polygon is gone, we can drop the workaround for older gcc.
>> ---
>>  CMakeLists.txt | 15 ---
>>  1 file changed, 15 deletions(-)
>>
>>
>>
>> ___
>> Mailing list: https://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] Removal of download_boost.cmake.

[Wayne Stambaugh]

The only boost patch that is not mingw or osx specific is
boost_cstdint.patch and I'm not sure this patch makes any difference.
There is one way to find out.  Build kicad with stock boost on 14.04 and
see there are any issues.  Would someone please test this since there
seems to be a lot of ubuntu 14.04 users out there?


On 12/14/2015 9:35 AM, Nick Østergaard wrote:
> Are you sure this is a good idea? We do patch boost 1.54 anyway, or do
> you remember what the consequences was and we can just ignore them if
> of on ubuntu 14.04 (LTS)?
> 
> 2015-12-14 14:36 GMT+01:00 Wayne Stambaugh :
>> I'll use 1.54 until the next Ubuntu LTS is released then I'll bump it to
>> 1.55 which is the current Debian stable version.
>>
>> On 12/13/2015 7:36 PM, Mark Roszko wrote:
>>> Debian never had 1.54 in stable.. It has 1.55 now(jessie) and the last 
>>> release
>>> was 1.49 (wheezy).
>>>
>>> Debian had 1.54 as "unstable" in 2013, it never shipped as stable.
>>>
>>> But yes, ubuntu 14 has 1.54.
>>>
>>> ___
>>> Mailing list: https://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 4/4] Drop gcc optimizer bug workaround

[Wayne Stambaugh]

This should depend on your platforms gcc default setting or spec file if
you use one.  I'm not sure how this done with clang.  On Debain testing,
-O2 is the default build optimization setting and -O3 on msys2/mingw32
and msys2/mingw64.

On 12/14/2015 10:32 AM, Bernhard Stegmaier wrote:
> I also assumed something like that and therefore had a look yesterday.
> On OSX it seems to default to -O3, at least that's what I have seen with
> "make VERBOSE=1".
> 
> 
> Regards,
> Bernhard
> 
> On 2015-12-14 16:01, Mark Roszko wrote:
>> Stupid question, doesn't this change remove -O2 entirely for all gcc
>> builds? Previously it defaulted to -O2 if the bug wasn't present. Now
>> it never optimizes as -O0 is the default.
>>
>> On Sat, Dec 12, 2015 at 2:59 PM, Wayne Stambaugh
>>  wrote:
>>> I committed your patch in the product branch r6370.  I tested it on
>>> msys1/mingw32, msys2/mingw32, msys2/mingw64, and Debian testing without
>>> issues.  You should also be able to be more aggressive with your
>>> optimization settings should you so desire.  Please keep in mind, if you
>>> do this and it breaks, you get keep both pieces.
>>>
>>> On 12/1/2015 2:14 AM, Simon Richter wrote:

 As boost::polygon is gone, we can drop the workaround for older gcc.
 ---
  CMakeLists.txt | 15 ---
  1 file changed, 15 deletions(-)



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

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

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

[Kicad-developers] New development policies.

[Wayne Stambaugh]

Now that the series 4 stable release is out an we are starting to move
forward again with new development, I have two policy announcements
regarding KiCad development moving forward.

1) It will no longer be acceptable to allow new features to be added to
only the Pcbnew legacy canvas.  The acceptable options are either gal
canvas only or gal and legacy canvases.  Please keep in mind that the
goal is to eventually remove the legacy canvas once all of the editing
tools are ported to the gal canvas.

2) Now that I have begun to remove the dependency builders from the
kicad build configuration, I am making it mandatory that any new
dependency and it's version information be add to the version
information string (see EDA_BASE_FRAME::CopyVersionInfoToClipboard() in
common/basicframe.cpp).  The reason I'm making this mandatory is I
foresee the potential of more dependency library version related bugs
and asking users to figure out which version of a dependency library
they are using in a bug report is a bit unrealistic.  I'll add the
missing information for the existing dependencies (although I wont be
offended if someone can get to it before I do) when I get a chance.

At some point I will create some type of policy document and add it to
the dev docs.  Thank you for your cooperation .

Cheers,

Wayne

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

Re: [Kicad-developers] Removal of download_boost.cmake.

[Wayne Stambaugh]

I'll use 1.54 until the next Ubuntu LTS is released then I'll bump it to
1.55 which is the current Debian stable version.

On 12/13/2015 7:36 PM, Mark Roszko wrote:
> Debian never had 1.54 in stable.. It has 1.55 now(jessie) and the last release
> was 1.49 (wheezy).
> 
> Debian had 1.54 as "unstable" in 2013, it never shipped as stable.
> 
> But yes, ubuntu 14 has 1.54.
> 
> ___
> Mailing list: https://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] Removal of download_boost.cmake.

[Nick Østergaard]

Are you sure this is a good idea? We do patch boost 1.54 anyway, or do
you remember what the consequences was and we can just ignore them if
of on ubuntu 14.04 (LTS)?

2015-12-14 14:36 GMT+01:00 Wayne Stambaugh :
> I'll use 1.54 until the next Ubuntu LTS is released then I'll bump it to
> 1.55 which is the current Debian stable version.
>
> On 12/13/2015 7:36 PM, Mark Roszko wrote:
>> Debian never had 1.54 in stable.. It has 1.55 now(jessie) and the last 
>> release
>> was 1.49 (wheezy).
>>
>> Debian had 1.54 as "unstable" in 2013, it never shipped as stable.
>>
>> But yes, ubuntu 14 has 1.54.
>>
>> ___
>> Mailing list: https://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] some spelling fix

[FabienM]

Hi Nick

On 14/12/2015 15:37, Nick Østergaard wrote:
> Hi Fabien
>
> What make you think that "Internationalisation" is wrong? That is
> perfectly valid english (british).

Ok. I've just seen that wikipedia use 'z':
https://en.wikipedia.org/wiki/Internationalization

But english is not my first langage then if you said that's correct, it
should be right.

Regards

>
> 2015-12-14 14:58 GMT+01:00 FabienM :
>> Hi all,
>>
>> Here just some spelling fixies to learn how to submit patch for kicad
>>
>> Regards.
>>
>> Martoni
>>
>> ___
>> Mailing list: https://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: To facilitate easier Via Curtain/Filling

[Tomasz Wlostowski]

On 12.12.2015 02:41, Strontium wrote:
> This change should not break or modify any current behaviour, EXCEPT to
> retain the nets of tracks/vias which Kicad is otherwise incapable of
> determining automatically.

Hi Steven,

Thanks for the patch, it also (partially) fixes the via stitching issue
many people have been complaining about. The origin of the problem is
that the net propagation code does not take zones into account - so a
via that is not connected to any pad with a chain of tracks is treated
as disconnected.

Adding zone support in the net calculation code should AFAIK fix this
for good, but it may also require enhancing the DRC (so that it will
report every object with no pad connection) and the 'clean tracks'
tool code.

Regards,
Tom

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

Re: [Kicad-developers] PATCH: To facilitate easier Via Curtain/Filling

[Strontium]

Hi Thomas,

I considered this, but tracking zones is non trivial.

For example, imagine the stackup:

GND
VCC
GND
VCC

A Through Via, from top to bottom could be connected validly connected 
to either GND or VCC.


Once the net is removed from the via by the reassignment pass, there is
no longer any information left to tell kicad which pair of zones was 
connected by the via.


The approach I suggest will fix this problem, because it just wont 
change the net for those vias.  It wont consider if there is a zone or 
not, it just says "hey, you gave it the GND net, so i will leave it as GND."



On 14/12/15 21:21, Tomasz Wlostowski wrote:

On 12.12.2015 02:41, Strontium wrote:

This change should not break or modify any current behaviour, EXCEPT to
retain the nets of tracks/vias which Kicad is otherwise incapable of
determining automatically.

Hi Steven,

Thanks for the patch, it also (partially) fixes the via stitching issue
many people have been complaining about. The origin of the problem is
that the net propagation code does not take zones into account - so a
via that is not connected to any pad with a chain of tracks is treated
as disconnected.

Adding zone support in the net calculation code should AFAIK fix this
for good, but it may also require enhancing the DRC (so that it will
report every object with no pad connection) and the 'clean tracks'
tool code.

Regards,
Tom




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

Re: [Kicad-developers] PATCH: To facilitate easier Via Curtain/Filling

[Tomasz Wlostowski]

On 14.12.2015 14:40, Strontium wrote:
> Hi Thomas,
> 
> I considered this, but tracking zones is non trivial.
> 
> For example, imagine the stackup:
> 
> GND
> VCC
> GND
> VCC
> 
> A Through Via, from top to bottom could be connected validly connected
> to either GND or VCC.
> 
> Once the net is removed from the via by the reassignment pass, there is
> no longer any information left to tell kicad which pair of zones was
> connected by the via.

Indeed, in case of such a conflict retaining the via's net is IMHO the
only good solution.

> 
> The approach I suggest will fix this problem, because it just wont
> change the net for those vias.  It wont consider if there is a zone or
> not, it just says "hey, you gave it the GND net, so i will leave it as
> GND."

It also seems Altium is managing via's nets this way. I would vote for
merging the patch.

Cheers,
Tom

> 
> 
> On 14/12/15 21:21, Tomasz Wlostowski wrote:
>> On 12.12.2015 02:41, Strontium wrote:
>>> This change should not break or modify any current behaviour, EXCEPT to
>>> retain the nets of tracks/vias which Kicad is otherwise incapable of
>>> determining automatically.
>> Hi Steven,
>>
>> Thanks for the patch, it also (partially) fixes the via stitching issue
>> many people have been complaining about. The origin of the problem is
>> that the net propagation code does not take zones into account - so a
>> via that is not connected to any pad with a chain of tracks is treated
>> as disconnected.
>>
>> Adding zone support in the net calculation code should AFAIK fix this
>> for good, but it may also require enhancing the DRC (so that it will
>> report every object with no pad connection) and the 'clean tracks'
>> tool code.
>>
>> Regards,
>> Tom
>>
> 


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

[Kicad-developers] [PATCH] some spelling fix

[FabienM]

Hi all,

Here just some spelling fixies to learn how to submit patch for kicad

Regards.

Martoni
>From 1210bc60f646b1b80969a78f878a2a67c6eb58b8 Mon Sep 17 00:00:00 2001
From: Fabien Marteau 
Date: Thu, 10 Dec 2015 21:46:26 +0100
Subject: [PATCH] some spelling fix

Signed-off-by: Fabien Marteau 
---
 README.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.txt b/README.txt
index 5a7fe27..a079141 100644
--- a/README.txt
+++ b/README.txt
@@ -11,9 +11,9 @@ CMakeList.txt   - CMAKE build tool script
 COPYRIGHT.txt   - A copy of the GNU General Public License Version 2
 CTestConfig.cmake   - Support for CTest and CDash testing tools
 Doxyfile- Doxygen config file for Kicad
-INSTALL.txt - The release (binairy) installation instructions
+INSTALL.txt - The release (binary) installation instructions
 TODO.txt- Todo list
-uncrustify.cfg  - Uncrustify config file for uncrustify sorces formatting tool
+uncrustify.cfg  - Uncrustify config file for uncrustify sources formatting tool
 
 Subdirectories
 --
@@ -30,7 +30,7 @@ eeschema   - Sourcecode of the schematic editor
 gerbview   - Sourcecode of the gerber viewer
 helpers- Helper tools and utilities for development
 include- Interfaces to the common library
-internat   - Internationalisation files
+internat   - Internationalization files
 kicad  - Sourcecode of the project manager
 packaging  - Files for packaging on Windows and Mac OSX
 pcbnew - Sourcecode of the printed circuit board editor
-- 
2.1.4

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

Re: [Kicad-developers] [PATCH] some spelling fix

[Nick Østergaard]

Hi Fabien

What make you think that "Internationalisation" is wrong? That is
perfectly valid english (british).

2015-12-14 14:58 GMT+01:00 FabienM :
> Hi all,
>
> Here just some spelling fixies to learn how to submit patch for kicad
>
> Regards.
>
> Martoni
>
> ___
> Mailing list: https://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 4/4] Drop gcc optimizer bug workaround

[Mário Luzeiro]

My 2 cents:

In my experience, I sometimes use the optimizations levels as a "verification 
tool".
Ex: If I run it in debug (or without optimization) and it works and then I 
switch to optimizations and it doesn't produce the same results, then, there is 
a bug somewhere (as it was in boost)

I saw in some projects I worked before, they release versions of 
software/firmware in "debug mode" because it doesn't run in "release" mode :/ 
(and they dont know why!) .. and it was not fixed ..and started to get the 
things ugly... (because the sources have ghost bugs)

For the developers, the source should run in all optimizations levels (if the 
compiler is not bugged)
>From the user point of an enjoyable user experience, the release should have 
>the best optimization that compiler can provide.

The only possible cons are:
- Slower builds
- Bigger .executables
but guess none is a really issue this days..

MRL

From: Kicad-developers 
[kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of 
Wayne Stambaugh [stambau...@gmail.com]
Sent: 14 December 2015 16:09
To: Mark Roszko
Cc: KiCad Developers; Kicad-developers
Subject: Re: [Kicad-developers] [PATCH 4/4] Drop gcc optimizer bug workaround

Optimization levels have typically been at the discretion of the builder
in other projects.  I never liked the idea of us forcing an optimization
level even though it resolved an issue related to the boost polygon
library.  You are correct.  There may be some optimization level bugs
but I haven't run into any up to this point.  I would rather the builder
override the system default optimization level if it is using and overly
aggressive level.  Now that we are providing nightly builds for most
platforms, the reason for controlling the build optimization level is
less critical.  When we were asking users to compile from source, it
made more sense.  We'll see, I may regret this decision.  If it becomes
a huge issue like it used to be, I can always change it back.

On 12/14/2015 10:57 AM, Mark Roszko wrote:
> Hence why I am asking, is it intended that we no longer enforce a
> single optimization mode at all? It seems like a can of worms because
> previously we could assume everyone is -O2. Now with people compiling
> at different levels, who knows level dependent bugs could crop up.
>
> On Mon, Dec 14, 2015 at 10:37 AM, Wayne Stambaugh  
> wrote:
>> This should depend on your platforms gcc default setting or spec file if
>> you use one.  I'm not sure how this done with clang.  On Debain testing,
>> -O2 is the default build optimization setting and -O3 on msys2/mingw32
>> and msys2/mingw64.
>>
>> On 12/14/2015 10:32 AM, Bernhard Stegmaier wrote:
>>> I also assumed something like that and therefore had a look yesterday.
>>> On OSX it seems to default to -O3, at least that's what I have seen with
>>> "make VERBOSE=1".
>>>
>>>
>>> Regards,
>>> Bernhard
>>>
>>> On 2015-12-14 16:01, Mark Roszko wrote:
 Stupid question, doesn't this change remove -O2 entirely for all gcc
 builds? Previously it defaulted to -O2 if the bug wasn't present. Now
 it never optimizes as -O0 is the default.

 On Sat, Dec 12, 2015 at 2:59 PM, Wayne Stambaugh
  wrote:
> I committed your patch in the product branch r6370.  I tested it on
> msys1/mingw32, msys2/mingw32, msys2/mingw64, and Debian testing without
> issues.  You should also be able to be more aggressive with your
> optimization settings should you so desire.  Please keep in mind, if you
> do this and it breaks, you get keep both pieces.
>
> On 12/1/2015 2:14 AM, Simon Richter wrote:
>>
>> As boost::polygon is gone, we can drop the workaround for older gcc.
>> ---
>>  CMakeLists.txt | 15 ---
>>  1 file changed, 15 deletions(-)
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
>

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

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

Re: [Kicad-developers] New development policies.

[Wayne Stambaugh]

On 12/14/2015 11:20 AM, Mark Roszko wrote:
> I assume I have to update the libcurl patch to add to the
> CopyVersionInfoToClipboard mess.
> 

Yes please.  CopyVersionInfoToClipboard may be a mess but it's damn
useful mess.  Before it's existence, getting worth while build and
platform information from users was a painful experience.  If you can
figure out how to make it less messy, I'm open to suggestion.  Be
careful with the wxWidgets stuff because the default information
provided by wxWidgets is incomplete.  That's why all of the wxWidgets
stringization macro ugliness is in there.

___
Mailing list: https://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] FreeCAD StepUp tools Openfile dialog issue on OSX

[easyw]

Hi Jose,

if you post the .kicad_mod file I will check it
(better if zipped)

PS which is the version of kicad StepUp tools you are using?

Maurice

On 14/12/2015 16.43, Jose A. Saumell wrote:

Hi,

I've ran into an issue whenever I had to use the StepUp tools on Freecad
to open a footprint and do the alignment of 3D model.

I would get an open file dialog but nothing would happen after selecting
the .kicad_mod file.

Inside kicad-StepUp-tools.FCMacro:
The name[0] variable would return an empty value.

I worked around the problem by not using native OSX Open file dialog:
//

name=QtGui.QFileDialog.getOpenFileName(self, 'Open file',
last_file_path,"kicad module files (*.kicad_mod)",
options=QtGui.QFileDialog.DontUseNativeDialog )[0]

//

This is working for me now, not sure exactly why it is not working with
native OSX dialog.


Cheers, Jose






___
Mailing list: https://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] Text rotation Angle and part rotation Angle pcbnew

[Jon Neal]

There is something weird that goes on with that section of the code base.

I was messing around with it before when doing the eagle importer stuff.
For whatever reason text is limited to less than around 90 degrees of
rotation.

There are 5+ places in the pcbnew code where the rotation of text is
changed. It is a mess. Good luck Lachlan!

On Mon, Dec 14, 2015 at 4:23 PM Cirilo Bernardo 
wrote:

> That shouldn't be a problem; something like this would do it:
>
> wxFloatingPointValidator< float > valRotate( 1 );
> valRotate.SetRange( -180.0, 180.0 );
>
> Then it's just a matter of (a) specifying a max. character length in the
> input box, (b) using the constructor with the validator specified, and (c)
> returning kicad's expected
> integer value (degrees * 10) for rotations.
>
> On Tue, Dec 15, 2015 at 2:19 AM, Wayne Stambaugh 
> wrote:
>
>> On 12/13/2015 8:00 PM, Lachlan Audas wrote:
>> > You can't set text rotation angle of part reference's and vale's in
>> > pcbnew,  only part rotation angle,
>>
>> The code for supporting rotated text is already in the pcbnew file
>> format.  I just don't know how well Pcbnew itself will handle rotated
>> text so there may be a lot of work to do.  I'm not trying to scare you
>> off but it may not be as easy to resolve as it appears.
>>
>> >
>> > This is bit of a problem  for importing eagle  pcb's,   as parts
>> > reference/vales may have angle's set,  also when manually setting
>> > angle's you need to enter 900 for 90..  etc
>> > instead of 90.5 etc  this very odd way of entering angles,   is they any
>> > objection make a patch to change this to the standard way of entering
>> > angle's, and allowing rations of
>> > reference/vale fields ?
>>
>> The only solution that I would accept would be a proper wxValidator
>> designed for angle entry.  There is already wxFloatingPointValidator
>> that you could reuse to make your life easier.  Your derived version
>> should clamp the angles from 0 to 360 and have an accessor to return the
>> converted angle as an integer.
>>
>> >
>> > Lachlan
>> >
>> >
>> >
>> >
>> >
>> > ___
>> > Mailing list: https://launchpad.net/~kicad-developers
>> > Post to : kicad-developers@lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~kicad-developers
>> > More help   : https://help.launchpad.net/ListHelp
>> >
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] kicad StepUp for kicad users after stable release has come out

[Cirilo Bernardo]

On Sun, Dec 13, 2015 at 12:17 AM, easyw  wrote:

> Hi Wayne,
>
> following your previously mail
>
>> I haven't had a chance to use this yet but it sounds really interesting
>> so it will be near the top of my list of things to include during the
>> next development cycle.
>>
> https://lists.launchpad.net/kicad-developers/msg20210.html
>
> do you think it could be more space on the official page to let the users
> know that the option to export board and parts to mechanical environment is
> available for kicad?
>
> please have a look at a recent comment in the forum
>
>> @maui, you are doing fantastically useful work, thank you!
>> I hope some (or all) of what you are building will get pulled into KiCad,
>> so that we can all just click "Export STEP" and be done with it.
>>
>
> https://forum.kicad.info/t/trouble-importing-full-3d-pcb-into-solidworks/569/32
>
> I'm thinking that it would be a useful tool for kicad users, in awaiting
> of the new 3d refactoring and STEP support.
>
>
STEP support is still a long way off unless someone else implements it;
it took me ~8 months to write libIGES and it looks like it may take almost
an entire year of refactoring to finish the 3D refactor + add an Export
plugin interface just to finally enable IGES export; IGES rendering within
the
browser is a different problem. There was some discussion before of using
OCE to enable viewing and construction of STEP files via the proposed
plugin scheme in the 3D refactor.  Tom has looked at OCE in some detail;
perhaps he can add a few comments to the CERN Roadmap on 3D Model
integration so it's easier for other people interested in STEP support to
follow on with using OCE via the plugins.

- Cirilo

Consider I'm also building a library of 3D models in VRML and STEP to be
> used with kicad .pretty module libraries
>
> Please let me know your opinion.
>
> Thank you and best regards
> Maurice
>
> ___
> Mailing list: https://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] Removal of download_boost.cmake.

[Kristian Nielsen]

Wayne Stambaugh  writes:

> The only boost patch that is not mingw or osx specific is
> boost_cstdint.patch and I'm not sure this patch makes any difference.
> There is one way to find out.  Build kicad with stock boost on 14.04 and
> see there are any issues.  Would someone please test this since there
> seems to be a lot of ubuntu 14.04 users out there?

I did a test build on a fresh Ubuntu 14.04 (amd64) that I had lying
around. It seems to work ok:

  cmake -DKICAD_SKIP_BOOST=YES -DCMAKE_INSTALL_PREFIX=/home/knielsen/kicad ../

This was from newest Git (Bzr 6372, Git 5d429ed).

The build succeeds, and KiCAD seems to run ok (schematics, pcbnew,
3d-viewer, ...). So removing bundled boost seems ok from Ubuntu 14.04
perspective.

To get it to build, I had to install libwx 3.0.2 and GLM 0.9.6.3 from
source, since Ubuntu had too old versions. I used this to install remaining
dependencies:

  sudo apt-get install git build-essential cmake checkinstall doxygen 
zlib1g-dev libwebkitgtk-dev libglew-dev libcairo2-dev libbz2-dev libssl-dev 
libgles2-mesa-dev libgl1-mesa-dev libglu1-mesa-dev libopenvg1-mesa-dev 
libosmesa6-dev libwebkitgtk-dev libboost-all-dev

I did have one issue with GLM, which should be unrelated to boost. I
installed GLM in CMAKE_INSTALL_PREFIX, and cmake finds it:

  -- Found GLM: /home/knielsen/kicad/include (found suitable version "0.9.6.3", 
minimum required is "0.9.5.4") 

But the build still fails, it looks like cmake did not add the required -I
option for the path it found:

cd /home/knielsen/kicad/kicad-source-mirror/build/3d-viewer && /usr/bin/c++   
-DHAVE_STDINT_H -DKICAD_KEEPCASE -DPCBNEW -DUSE_OPENMP -DWXUSINGDLL 
-DWX_COMPATIBILITY -D_FILE_OFFSET_BITS=64 -D__WXGTK__ -Wall  
-fvisibility=hidden -fvisibility-inlines-hidden -Wno-unused-local-typedefs 
-Wno-strict-aliasing -fopenmp -pthread -O3 -DNDEBUG -DNDEBUG -fPIC 
-I/home/knielsen/kicad/kicad-source-mirror/include 
-I/home/knielsen/kicad/kicad-source-mirror/3d-viewer/. -isystem 
/home/knielsen/kicad/lib/wx/include/gtk2-unicode-3.0 -isystem 
/home/knielsen/kicad/include/wx-3.0 
-I/home/knielsen/kicad/kicad-source-mirror/3d-viewer/textures 
-I/home/knielsen/kicad/kicad-source-mirror/3d-viewer/../pcbnew 
-I/home/knielsen/kicad/kicad-source-mirror/3d-viewer/../polygon 
-I/home/knielsen/kicad/kicad-source-mirror/build-o 
CMakeFiles/3d-viewer.dir/dialogs/dialog_3D_view_option.cpp.o -c 
/home/knielsen/kicad/kicad-source-mirror/3d-viewer/dialogs/dialog_3D_view_option.cpp

In file included from 
/home/knielsen/kicad/kicad-source-mirror/3d-viewer/./3d_struct.h:36:0,
 from 
/home/knielsen/kicad/kicad-source-mirror/3d-viewer/./3d_viewer.h:40,
 from 
/home/knielsen/kicad/kicad-source-mirror/3d-viewer/dialogs/dialog_3D_view_option.cpp:26:
/home/knielsen/kicad/kicad-source-mirror/3d-viewer/./3d_material.h:35:23: fatal 
error: glm/glm.hpp: No such file or directory

I fixed it with a quick hack (ln -s ../glm ~/kicad/include/wx-3.0/), as I
was too lazy to look up how to pass extra -I options with cmake. I should
probably try to come up with a small patch to make cmake add the required -I
automatically for GLM.

Hope this helps, let me know if there is anything further that needs
testing.

 - Kristian.

___
Mailing list: https://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] Removal of download_boost.cmake.

[Wayne Stambaugh]

What is the result of `grep GLM < CMakeCache.txt` when run from your
build folder?  You should see something like:

$ grep GLM < CMakeCache.txt
//GLM library header path.
GLM_INCLUDE_DIR:PATH=C:/MinGW/include
//Details about finding GLM
FIND_PACKAGE_MESSAGE_DETAILS_GLM:INTERNAL=[C:/MinGW/include][0.9.7.1][v0.9.7.1(0
.9.5.4)]
//ADVANCED property for variable: GLM_INCLUDE_DIR
GLM_INCLUDE_DIR-ADVANCED:INTERNAL=1
GLM_VERSION_MAJOR:INTERNAL=0
GLM_VERSION_MINOR:INTERNAL=9
GLM_VERSION_PATCH:INTERNAL=7
GLM_VERSION_TWEAK:INTERNAL=1

Obviously this is a windows build but the variable you care about is
GLM_INCLUDE_PATH.  If it's not pointing to the correct path, you can
either configure with cmake using -DGLM_ROOT_DIR=/path/to/glm/ or set
the GLM_ROOT_DIR environment variable and it should fine the correct
path.  You can also hand edit CMakeCache.txt as well.

On 12/14/2015 4:47 PM, Kristian Nielsen wrote:
> Wayne Stambaugh  writes:
> 
>> The only boost patch that is not mingw or osx specific is
>> boost_cstdint.patch and I'm not sure this patch makes any difference.
>> There is one way to find out.  Build kicad with stock boost on 14.04 and
>> see there are any issues.  Would someone please test this since there
>> seems to be a lot of ubuntu 14.04 users out there?
> 
> I did a test build on a fresh Ubuntu 14.04 (amd64) that I had lying
> around. It seems to work ok:
> 
>   cmake -DKICAD_SKIP_BOOST=YES -DCMAKE_INSTALL_PREFIX=/home/knielsen/kicad ../
> 
> This was from newest Git (Bzr 6372, Git 5d429ed).
> 
> The build succeeds, and KiCAD seems to run ok (schematics, pcbnew,
> 3d-viewer, ...). So removing bundled boost seems ok from Ubuntu 14.04
> perspective.
> 
> To get it to build, I had to install libwx 3.0.2 and GLM 0.9.6.3 from
> source, since Ubuntu had too old versions. I used this to install remaining
> dependencies:
> 
>   sudo apt-get install git build-essential cmake checkinstall doxygen 
> zlib1g-dev libwebkitgtk-dev libglew-dev libcairo2-dev libbz2-dev libssl-dev 
> libgles2-mesa-dev libgl1-mesa-dev libglu1-mesa-dev libopenvg1-mesa-dev 
> libosmesa6-dev libwebkitgtk-dev libboost-all-dev
> 
> I did have one issue with GLM, which should be unrelated to boost. I
> installed GLM in CMAKE_INSTALL_PREFIX, and cmake finds it:
> 
>   -- Found GLM: /home/knielsen/kicad/include (found suitable version 
> "0.9.6.3", minimum required is "0.9.5.4") 
> 
> But the build still fails, it looks like cmake did not add the required -I
> option for the path it found:
> 
> cd /home/knielsen/kicad/kicad-source-mirror/build/3d-viewer && /usr/bin/c++   
> -DHAVE_STDINT_H -DKICAD_KEEPCASE -DPCBNEW -DUSE_OPENMP -DWXUSINGDLL 
> -DWX_COMPATIBILITY -D_FILE_OFFSET_BITS=64 -D__WXGTK__ -Wall  
> -fvisibility=hidden -fvisibility-inlines-hidden -Wno-unused-local-typedefs 
> -Wno-strict-aliasing -fopenmp -pthread -O3 -DNDEBUG -DNDEBUG -fPIC 
> -I/home/knielsen/kicad/kicad-source-mirror/include 
> -I/home/knielsen/kicad/kicad-source-mirror/3d-viewer/. -isystem 
> /home/knielsen/kicad/lib/wx/include/gtk2-unicode-3.0 -isystem 
> /home/knielsen/kicad/include/wx-3.0 
> -I/home/knielsen/kicad/kicad-source-mirror/3d-viewer/textures 
> -I/home/knielsen/kicad/kicad-source-mirror/3d-viewer/../pcbnew 
> -I/home/knielsen/kicad/kicad-source-mirror/3d-viewer/../polygon 
> -I/home/knielsen/kicad/kicad-source-mirror/build-o 
> CMakeFiles/3d-viewer.dir/dialogs/dialog_3D_view_option.cpp.o -c 
> /home/knielsen/kicad/kicad-source-mirror/3d-viewer/dialogs/dialog_3D_view_option.cpp
> 
> In file included from 
> /home/knielsen/kicad/kicad-source-mirror/3d-viewer/./3d_struct.h:36:0,
>  from 
> /home/knielsen/kicad/kicad-source-mirror/3d-viewer/./3d_viewer.h:40,
>  from 
> /home/knielsen/kicad/kicad-source-mirror/3d-viewer/dialogs/dialog_3D_view_option.cpp:26:
> /home/knielsen/kicad/kicad-source-mirror/3d-viewer/./3d_material.h:35:23: 
> fatal error: glm/glm.hpp: No such file or directory
> 
> I fixed it with a quick hack (ln -s ../glm ~/kicad/include/wx-3.0/), as I
> was too lazy to look up how to pass extra -I options with cmake. I should
> probably try to come up with a small patch to make cmake add the required -I
> automatically for GLM.
> 
> Hope this helps, let me know if there is anything further that needs
> testing.
> 
>  - Kristian.
> 

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

Re: [Kicad-developers] [rfc patch] replace avhttp with libcurl

[Adam Wolf]

I tested this last patch on the build box for OS X by adding a part from
github to a board, and downloaded a few with the wizard.  Everything worked
as expected.

Good work, folks.

Adam Wolf
Cofounder and Engineer
W

On Fri, Dec 11, 2015 at 12:04 AM, Mark Roszko  wrote:

> Removed some rogue whitespaces to stop complaints and fixed two
> renamed function headers.
>
> On Wed, Dec 9, 2015 at 9:58 PM, Jon Neal  wrote:
> > I tested it on windows 8 and it seemed to work just fine.
> >
> > On Wed, Dec 9, 2015 at 9:39 PM Mark Roszko 
> wrote:
> >>
> >> >If it works on all platforms without the user having to jump through
> >> > configuration hoops to get it to work
> >>
> >> I will eat a shoe if anyone has do anything extreme. :)
> >>
> >>
> >> Here's a build with it patched with curl and all dependencies included:
> >>
> >>
> http://downloads.kicad-pcb.org/windows/kicad-product-r6362.0427189-x86_64.exe
> >>
> >> Which works for me.
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
>
>
>
> --
> Mark
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://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] Removal of download_boost.cmake.

[Adam Wolf]

Hi folks,

We should probably remove the

"""WARNING: You decided to skip building boost library.

  KiCad developers strongly advise you to build the bundled boost library,
as
  it is known to work with KiCad.

  Other versions may contain bugs that may result in KiCad errors."""

warning soon, right?

Adam Wolf
Cofounder and Engineer
W

On Mon, Dec 14, 2015 at 10:15 AM, Wayne Stambaugh 
wrote:

> The only boost patch that is not mingw or osx specific is
> boost_cstdint.patch and I'm not sure this patch makes any difference.
> There is one way to find out.  Build kicad with stock boost on 14.04 and
> see there are any issues.  Would someone please test this since there
> seems to be a lot of ubuntu 14.04 users out there?
>
>
> On 12/14/2015 9:35 AM, Nick Østergaard wrote:
> > Are you sure this is a good idea? We do patch boost 1.54 anyway, or do
> > you remember what the consequences was and we can just ignore them if
> > of on ubuntu 14.04 (LTS)?
> >
> > 2015-12-14 14:36 GMT+01:00 Wayne Stambaugh :
> >> I'll use 1.54 until the next Ubuntu LTS is released then I'll bump it to
> >> 1.55 which is the current Debian stable version.
> >>
> >> On 12/13/2015 7:36 PM, Mark Roszko wrote:
> >>> Debian never had 1.54 in stable.. It has 1.55 now(jessie) and the last
> release
> >>> was 1.49 (wheezy).
> >>>
> >>> Debian had 1.54 as "unstable" in 2013, it never shipped as stable.
> >>>
> >>> But yes, ubuntu 14 has 1.54.
> >>>
> >>> ___
> >>> Mailing list: https://launchpad.net/~kicad-developers
> >>> Post to : kicad-developers@lists.launchpad.net
> >>> Unsubscribe : https://launchpad.net/~kicad-developers
> >>> More help   : https://help.launchpad.net/ListHelp
> >>>
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Removal of download_boost.cmake.

[Wayne Stambaugh]

It will get removed when download_boost.cmake is removed.  I just need
an answer on whether or not the 1.54 boost on ubuntu 14.04 will work or not.

On 12/14/2015 1:35 PM, Adam Wolf wrote:
> Hi folks,
> 
> We should probably remove the 
> 
> """WARNING: You decided to skip building boost library.
> 
>   KiCad developers strongly advise you to build the bundled boost
> library, as
>   it is known to work with KiCad.
> 
>   Other versions may contain bugs that may result in KiCad errors."""
> 
> warning soon, right?
> 
> Adam Wolf
> Cofounder and Engineer
> W
> 
> On Mon, Dec 14, 2015 at 10:15 AM, Wayne Stambaugh  > wrote:
> 
> The only boost patch that is not mingw or osx specific is
> boost_cstdint.patch and I'm not sure this patch makes any difference.
> There is one way to find out.  Build kicad with stock boost on 14.04 and
> see there are any issues.  Would someone please test this since there
> seems to be a lot of ubuntu 14.04 users out there?
> 
> 
> On 12/14/2015 9:35 AM, Nick Østergaard wrote:
> > Are you sure this is a good idea? We do patch boost 1.54 anyway, or do
> > you remember what the consequences was and we can just ignore them if
> > of on ubuntu 14.04 (LTS)?
> >
> > 2015-12-14 14:36 GMT+01:00 Wayne Stambaugh  >:
> >> I'll use 1.54 until the next Ubuntu LTS is released then I'll
> bump it to
> >> 1.55 which is the current Debian stable version.
> >>
> >> On 12/13/2015 7:36 PM, Mark Roszko wrote:
> >>> Debian never had 1.54 in stable.. It has 1.55 now(jessie) and
> the last release
> >>> was 1.49 (wheezy).
> >>>
> >>> Debian had 1.54 as "unstable" in 2013, it never shipped as stable.
> >>>
> >>> But yes, ubuntu 14 has 1.54.
> >>>
> >>> ___
> >>> Mailing list: https://launchpad.net/~kicad-developers
> >>> Post to : kicad-developers@lists.launchpad.net
> 
> >>> Unsubscribe : https://launchpad.net/~kicad-developers
> >>> More help   : https://help.launchpad.net/ListHelp
> >>>
> >>
> >> ___
> >> Mailing list: https://launchpad.net/~kicad-developers
> >> Post to : kicad-developers@lists.launchpad.net
> 
> >> Unsubscribe : https://launchpad.net/~kicad-developers
> >> More help   : https://help.launchpad.net/ListHelp
> 
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> 
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 
> 

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

[Kicad-developers] Windows installer: help files

[Iñigo]

Hi,

I'm a KiCad for Windows user.
I use my own libraries, so when installing KiCad I deselect both 
Schematic and Footprint libraries. Required space for installation goes 
from 1.1GB to 366.3MB. Fine.
But if I deselect the help files it goes to 177.3MB. So more than half 
of the installation are the help files.
Can the installer be changed to select the help files language and 
bypass the rest of the files?


Keep the good work!
Thanks!

Iñigo.

P.S. I know storage space is cheap. But I really hate unneeded files.

___
Mailing list: https://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] Removal of download_boost.cmake.

[Mário Luzeiro]

Hi Wayne,

As in accord with my email: 
https://lists.launchpad.net/kicad-developers/msg21844.html

I might have influenced the choice of the version number,
so I suggested that you can use at this moment whichever version you believe it 
serves the best purposes and kicad interests.
Then, in a future moment we will discuss and see what best version apply.


Just for note, I am reviewing my code in order to support older versions of GLM 
lib.

MRL


From: Kicad-developers 
[kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of 
Wayne Stambaugh [stambau...@gmail.com]
Sent: 14 December 2015 18:40
To: kicad-developers@lists.launchpad.net
Subject: Re: [Kicad-developers] Removal of download_boost.cmake.

I believe this is the currently the minimum version of GLM that we can
use for the upcoming 3D viewer changes (please correct me if I'm wrong).
___
Mailing list: https://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] Removal of download_boost.cmake.

[Sergey Borshch]

On 14.12.2015 21:27, Wayne Stambaugh wrote:

Mario,
However (this is a notice to all
developers), I do not want the progress of the development branch to be
hindered because we are trying to support building on older distros.
This is what the stable releases are for.  If you are using older
distros, it becomes incumbent upon you to build newer versions of the
kicad build dependencies if you want to continue to use the development
version.
My Linux Mint distro was released a week ago. It's the newest Linux Mint 
distro. Unfortunately Linux Mint based on Ubuntu LTS repo since 17.0 
release. Seems like I really should build libglm from sources.


Thanks for a quick response.


On 12/14/2015 2:08 PM, Mário Luzeiro wrote:

Hi Wayne,

As in accord with my email:
https://lists.launchpad.net/kicad-developers/msg21844.html

I might have influenced the choice of the version number,
so I suggested that you can use at this moment whichever version you believe it 
serves the best purposes and kicad interests.
Then, in a future moment we will discuss and see what best version apply.


Just for note, I am reviewing my code in order to support older versions of GLM 
lib.

MRL


From: Kicad-developers 
[kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of 
Wayne Stambaugh [stambau...@gmail.com]
Sent: 14 December 2015 18:40
To: kicad-developers@lists.launchpad.net
Subject: Re: [Kicad-developers] Removal of download_boost.cmake.

I believe this is the currently the minimum version of GLM that we can
use for the upcoming 3D viewer changes (please correct me if I'm wrong).



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




--
Regards,
   Sergey A. Borshchmailto: sb...@users.sourceforge.net
 SB ELDI ltd. Riga, Latvia

___
Mailing list: https://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] Windows installer: help files

[Nick Østergaard]

Possibly, but please set that as an issue on
https://github.com/nickoe/KiCad-Winbuilder instead.

2015-12-14 20:07 GMT+01:00 Iñigo :
> Hi,
>
> I'm a KiCad for Windows user.
> I use my own libraries, so when installing KiCad I deselect both Schematic
> and Footprint libraries. Required space for installation goes from 1.1GB to
> 366.3MB. Fine.
> But if I deselect the help files it goes to 177.3MB. So more than half of
> the installation are the help files.
> Can the installer be changed to select the help files language and bypass
> the rest of the files?
>
> Keep the good work!
> Thanks!
>
> Iñigo.
>
> P.S. I know storage space is cheap. But I really hate unneeded files.
>
> ___
> Mailing list: https://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 4/4] Drop gcc optimizer bug workaround

[Simon Richter]

Hi,

Am 14.12.2015 um 16:01 schrieb Mark Roszko:

> Stupid question, doesn't this change remove -O2 entirely for all gcc
> builds? Previously it defaulted to -O2 if the bug wasn't present. Now
> it never optimizes as -O0 is the default.

The default depends on the build type -- if your source tree is
configured for Debug, then it falls back to -O0.

   Simon



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

Re: [Kicad-developers] Removal of download_boost.cmake.

[Wayne Stambaugh]

Mario,

The minimum version was based on your input and the current Debian
stable glm version.  If you can get by with an earlier version, let me
know and I will adjust it accordingly.  However (this is a notice to all
developers), I do not want the progress of the development branch to be
hindered because we are trying to support building on older distros.
This is what the stable releases are for.  If you are using older
distros, it becomes incumbent upon you to build newer versions of the
kicad build dependencies if you want to continue to use the development
version.  If we try to be all things to all people, we will end up being
nothing to anyone.

On 12/14/2015 2:08 PM, Mário Luzeiro wrote:
> Hi Wayne,
> 
> As in accord with my email: 
> https://lists.launchpad.net/kicad-developers/msg21844.html
> 
> I might have influenced the choice of the version number,
> so I suggested that you can use at this moment whichever version you believe 
> it serves the best purposes and kicad interests.
> Then, in a future moment we will discuss and see what best version apply.
> 
> 
> Just for note, I am reviewing my code in order to support older versions of 
> GLM lib.
> 
> MRL
> 
> 
> From: Kicad-developers 
> [kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of 
> Wayne Stambaugh [stambau...@gmail.com]
> Sent: 14 December 2015 18:40
> To: kicad-developers@lists.launchpad.net
> Subject: Re: [Kicad-developers] Removal of download_boost.cmake.
> 
> I believe this is the currently the minimum version of GLM that we can
> use for the upcoming 3D viewer changes (please correct me if I'm wrong).
> 

___
Mailing list: https://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] FreeCAD StepUp tools Openfile dialog issue on OSX

[easyw]

Hi Jose,

I can reproduce it in OSX Lion, so I can debug :)

Thank you for reporting it and also for the solution-workaround you have 
found!


keep in touch
Maurice :)

On 14/12/2015 16.43, Jose A. Saumell wrote:

Hi,

I've ran into an issue whenever I had to use the StepUp tools on Freecad
to open a footprint and do the alignment of 3D model.

I would get an open file dialog but nothing would happen after selecting
the .kicad_mod file.

Inside kicad-StepUp-tools.FCMacro:
The name[0] variable would return an empty value.

I worked around the problem by not using native OSX Open file dialog:
//

name=QtGui.QFileDialog.getOpenFileName(self, 'Open file',
last_file_path,"kicad module files (*.kicad_mod)",
options=QtGui.QFileDialog.DontUseNativeDialog )[0]

//

This is working for me now, not sure exactly why it is not working with
native OSX dialog.


Cheers, Jose






___
Mailing list: https://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] FreeCAD StepUp tools Openfile dialog issue on OSX

[Jose A. Saumell]

Hi Maurice,

It is not related to the .kicad_mod file. Failed with with many I tried.
The Macro did not load the 'name' variable from the opendialog window. It
came back empty and thus the next if statement gave false result:

  if len(name) > 0:

txtFile = open(name,"r")

content = txtFile.readlines()

content.append(" ")

last_file_path=os.path.dirname(txtFile.name)

txtFile.close()

On Mon, Dec 14, 2015 at 2:33 PM easyw  wrote:

> Hi Jose,
>
> if you post the .kicad_mod file I will check it
> (better if zipped)
>
> PS which is the version of kicad StepUp tools you are using?
>
> Maurice
>
> On 14/12/2015 16.43, Jose A. Saumell wrote:
> > Hi,
> >
> > I've ran into an issue whenever I had to use the StepUp tools on Freecad
> > to open a footprint and do the alignment of 3D model.
> >
> > I would get an open file dialog but nothing would happen after selecting
> > the .kicad_mod file.
> >
> > Inside kicad-StepUp-tools.FCMacro:
> > The name[0] variable would return an empty value.
> >
> > I worked around the problem by not using native OSX Open file dialog:
> > //
> >
> > name=QtGui.QFileDialog.getOpenFileName(self, 'Open file',
> > last_file_path,"kicad module files (*.kicad_mod)",
> > options=QtGui.QFileDialog.DontUseNativeDialog )[0]
> >
> > //
> >
> > This is working for me now, not sure exactly why it is not working with
> > native OSX dialog.
> >
> >
> > Cheers, Jose
> >
> >
> >
> >
> >
> >
> > ___
> > Mailing list: https://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] Removal of download_boost.cmake.

[Sergey Borshch]

On 14.12.2015 18:15, Wayne Stambaugh wrote:

The only boost patch that is not mingw or osx specific is
boost_cstdint.patch and I'm not sure this patch makes any difference.
There is one way to find out.  Build kicad with stock boost on 14.04 and
see there are any issues.  Would someone please test this since there
seems to be a lot of ubuntu 14.04 users out there?


I'm unable to build kicad "out of the box" on 14.04 (Linux Mint 17.3) 
anymore:


CMake Error at 
/usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108 
(message):
  Could NOT find GLM: Found unsuitable version "0.9.5.1", but required 
is at least "0.9.5.4" (found /usr/include)


:~/build/kicad$ apt-cache policy libglm-dev
libglm-dev:
  Installed: 0.9.5.1-1
  Candidate: 0.9.5.1-1
  Version table:
 *** 0.9.5.1-1 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status


~$ uname -a
Linux ** 3.19.0-33-generic #38~14.04.1-Ubuntu SMP Fri Nov 6 18:17:28 
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux


--
Regards,
   Sergey A. Borshchmailto: sb...@users.sourceforge.net
 SB ELDI ltd. Riga, Latvia

___
Mailing list: https://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] Removal of download_boost.cmake.

[Wayne Stambaugh]

On 12/14/2015 1:31 PM, Sergey Borshch wrote:
> On 14.12.2015 18:15, Wayne Stambaugh wrote:
>> The only boost patch that is not mingw or osx specific is
>> boost_cstdint.patch and I'm not sure this patch makes any difference.
>> There is one way to find out.  Build kicad with stock boost on 14.04 and
>> see there are any issues.  Would someone please test this since there
>> seems to be a lot of ubuntu 14.04 users out there?
> 
> I'm unable to build kicad "out of the box" on 14.04 (Linux Mint 17.3)
> anymore:
> 
> CMake Error at
> /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108
> (message):
>   Could NOT find GLM: Found unsuitable version "0.9.5.1", but required
> is at least "0.9.5.4" (found /usr/include)

I believe this is the currently the minimum version of GLM that we can
use for the upcoming 3D viewer changes (please correct me if I'm wrong).
 If this is actually the case, you will have to stick with the stable
version (currently 4.0.1) or install a newer version of glm on your
system if you wish to continue using the development branch.

> 
> :~/build/kicad$ apt-cache policy libglm-dev
> libglm-dev:
>   Installed: 0.9.5.1-1
>   Candidate: 0.9.5.1-1
>   Version table:
>  *** 0.9.5.1-1 0
> 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
> 100 /var/lib/dpkg/status
> 
> 
> ~$ uname -a
> Linux ** 3.19.0-33-generic #38~14.04.1-Ubuntu SMP Fri Nov 6 18:17:28
> UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
> 

___
Mailing list: https://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] Text rotation Angle and part rotation Angle pcbnew

[Cirilo Bernardo]

That shouldn't be a problem; something like this would do it:

wxFloatingPointValidator< float > valRotate( 1 );
valRotate.SetRange( -180.0, 180.0 );

Then it's just a matter of (a) specifying a max. character length in the
input box, (b) using the constructor with the validator specified, and (c)
returning kicad's expected
integer value (degrees * 10) for rotations.

On Tue, Dec 15, 2015 at 2:19 AM, Wayne Stambaugh 
wrote:

> On 12/13/2015 8:00 PM, Lachlan Audas wrote:
> > You can't set text rotation angle of part reference's and vale's in
> > pcbnew,  only part rotation angle,
>
> The code for supporting rotated text is already in the pcbnew file
> format.  I just don't know how well Pcbnew itself will handle rotated
> text so there may be a lot of work to do.  I'm not trying to scare you
> off but it may not be as easy to resolve as it appears.
>
> >
> > This is bit of a problem  for importing eagle  pcb's,   as parts
> > reference/vales may have angle's set,  also when manually setting
> > angle's you need to enter 900 for 90..  etc
> > instead of 90.5 etc  this very odd way of entering angles,   is they any
> > objection make a patch to change this to the standard way of entering
> > angle's, and allowing rations of
> > reference/vale fields ?
>
> The only solution that I would accept would be a proper wxValidator
> designed for angle entry.  There is already wxFloatingPointValidator
> that you could reuse to make your life easier.  Your derived version
> should clamp the angles from 0 to 360 and have an accessor to return the
> converted angle as an integer.
>
> >
> > Lachlan
> >
> >
> >
> >
> >
> > ___
> > Mailing list: https://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: remove some trailing whitespace

[Wayne Stambaugh]

Patch committed in product branch r6373.  Thanks.

On 12/9/2015 8:02 PM, Cirilo Bernardo wrote:
> I was inspired to check sources for trailing white space and found a few
> - in fact
> very few for a project the size of kicad. Naturally all the
> auto-generated code
> was ignored.
> 
> This patch removes trailing white space from the following files:
> 
> pcbnew/router/time_limit.cpp
> pcbnew/tools/point_editor.cpp
> pcbnew/dialogs/dialog_plot.cpp
> 3d-viewer/CImage.cpp
> 3d-viewer/CBBox.cpp
> eeschema/sch_sheet_path.h
> 3d-viewer/CImage.h
> polygon/math_for_graphics.h
> polygon/poly2tri/sweep/cdt.h
> polygon/poly2tri/poly2tri.h
> 
> Note: the following also have tabs (not replaced):
> pcbnew/router/time_limit.cpp
> pcbnew/tools/point_editor.cpp
> 
> 
> - Cirilo
> 
> 
> ___
> Mailing list: https://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] Removal of download_boost.cmake.

[Kristian Nielsen]

Ok, looking further, I think it is just an oversight, GLM_INCLUDE_DIR is
missing in 3d-viewer/CMakeLists.txt. Adding it as per the attached patch
fixes the error for me. The problem will only be seen when GLM is in a
different location from other libraries already included in CMakeLists.txt.

Wayne, will you pick up the attached one-liner patch directly?

Wayne Stambaugh  writes:

> What is the result of `grep GLM < CMakeCache.txt` when run from your
> build folder?  You should see something like:

Yes, it's very similar:

$ grep GLM < CMakeCache.txt 
//GLM library header path.
GLM_INCLUDE_DIR:PATH=/home/knielsen/kicad/include
//Details about finding GLM
FIND_PACKAGE_MESSAGE_DETAILS_GLM:INTERNAL=[/home/knielsen/kicad/include][0.9.6.3][v0.9.6.3(0.9.5.4)]
//ADVANCED property for variable: GLM_INCLUDE_DIR
GLM_INCLUDE_DIR-ADVANCED:INTERNAL=1
GLM_VERSION_MAJOR:INTERNAL=0
GLM_VERSION_MINOR:INTERNAL=9
GLM_VERSION_PATCH:INTERNAL=6
GLM_VERSION_TWEAK:INTERNAL=3

Clearly, cmake is finding my installed GLM library from the
CMAKE_INSTALL_PREFIX (as that is the only place ~/kicad/ is mentioned). I
get the same error if I explicitly put -DGLM_ROOT_DIR=$HOME/kicad/include on
the cmake line. It's probably just the missing GLM_INCLUDE_DIR in
3d-viewer/CMakeLists.txt

 - Kristian.

diff --git a/3d-viewer/CMakeLists.txt b/3d-viewer/CMakeLists.txt
index b48e505..47014f6 100644
--- a/3d-viewer/CMakeLists.txt
+++ b/3d-viewer/CMakeLists.txt
@@ -6,6 +6,7 @@ include_directories(
 ../pcbnew
 ../polygon
 ${GLEW_INCLUDE_DIR}
+${GLM_INCLUDE_DIR}
 ${INC_AFTER}
 )
 
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp