FS#31559 - [kicad] cutout zones in pcbnew don't work

Attached to Project: Community Packages
Opened by Sebastian S. (LongHairedHacker) - Saturday, 15 September 2012, 14:58 GMT
Last edited by Kyle Keen (keenerd) - Friday, 16 November 2012, 17:10 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Kyle Keen (keenerd)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Pcbnew has a feauture to define unfilled 'cut out' zones inside of filled zones on a pcb.
This feature seem to have stopped working recently, since the cut outs get filled as well.

Additional info:
* package version : 20120119-2
* Installed from community
Should be kicads stable branch rev. 3256 on launchpad.

I've test this under x86_64 and i686, same bug on both architectures.
Also I've tested the same kicad version under ubuntu 12.04 and windows where I could not reproduce the bug.

Steps to reproduce:
1. Install kicad from community
2. Start kicad, create a new project
3. Start pcbnew
4. Create a new Zone (leave all zone options to defaults)
5. Rightclick the border of the Zone and click Zones -> Add cut out
6. Draw the cut out area anywhere you like, but fully inside the zone
7. Rightclick the border of the Zone again and click Zones -> Fill Zone

Expected result : The zone is filled except for the cut out area.
Actual result : The zone is completely filled.

For easier reproduction I've attached a small test project including a pcbnew file.
In that file I defined a zone with a cut out and filled it using the windows version, so the filling works correctly and I could make sure it's not just a wrong setting.
If you remove the filling and try filling it again under archlinux, the zone will become completely filled.

   test.zip (2.2 KiB)
This task depends upon

Closed by  Kyle Keen (keenerd)
Friday, 16 November 2012, 17:10 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 20120119-4
Comment by Alexander F. Rødseth (xyproto) - Monday, 17 September 2012, 07:00 GMT
Please report this upstream to the kicad developers. Ubuntu often applies their own patches. If this is the case here, upstream should be asked to include these patches for the next release. Thanks.
Comment by Sebastian S. (LongHairedHacker) - Wednesday, 26 September 2012, 14:49 GMT
Just for information :
I tried to build kicad using the sources used in the ubuntu package before reporting the bug upstream,
in order to check whether ubuntu has some kind of patch for this bug.
As far as I can tell there are no patches included in the ubuntu package (sources can be found http://packages.ubuntu.com/source/precise/kicad).
It seems to be build from a clean upstream bzr checkout.
Building the kicad package with their sources didn't solve the problem as well.

The report on launchpad can be found here : https://bugs.launchpad.net/kicad/+bug/1056926
Comment by Kyle Keen (keenerd) - Saturday, 29 September 2012, 00:10 GMT
I am also starting to think this a bug relating to building against boost 1.5.0. They bundle a version of boost but it seems it is not used for quite everything. This could be related to our build options.
Comment by Sebastian S. (LongHairedHacker) - Thursday, 04 October 2012, 18:39 GMT
I've just found the cause for this bug.

As far as I can tell kicad builds against the boost 1.40, they've bundled with it.
The current gcc version 4.7 used by archlinux seems incompatible with this rather old boost version.
It compiles with out errors but it does not work correctly.

I used gcc 4.4.6 (the version used in the recent ubuntu) from AUR (package gcc44) to build it and cut outs suddenly work fine.

Loading...