Re: [Kicad-developers] [PATCH] Fix for bug/1754049

[hauptmech]

Updated patch attached. Coding standard stuff fixed.

I took a second look at the case where all items in a module are deleted.

I checked the parser and writer. In the case where all items are 
deleted, the modules are still OK as far as reading and writing to the file.


I don't think deleting the module is the right way to go. They are on 
layers which cannot be deleted in the current implementation.


Most modules will have pads on the undeleteable layers, so they will be 
fine.


For the case of someone with modules composed only of non-top/bottom 
elements and who are messing with the layer setup midway through the 
design, I think we should just leave it as it is. Either they are a 
ninja doing things that kicad should stay out of the way of  or they are 
a very confused beginner for whom a little extra cruft in the file is 
the least of their problems.


-hauptmech



On 15/03/18 05:17, Seth Hillbrand wrote:

Hi hautmech-

Looks good. Two comments:

- Code style. There are a couple of small issues: one line is too 
long, there should be spaces in parentheses for 
pad->GetParent()->Remove(pad) and no space before parentheses in "if ( 
pad->GetLayerSet()..."


- We need to handle the case where all items in a module are deleted. 
Currently, the code will remove all items except the value and 
reference.  This means that we can no longer select the module in 
pcbnew to delete it.  Either we need to fully delete the module when 
the last selectable item is removed or we need to keep sufficient 
information to allow the module to be selected when the layers are 
re-enabled.


Best-
Seth

2018-03-14 2:54 GMT-07:00 hauptmech >:


https://bugs.launchpad.net/kicad/+bug/1754049


This patch follows the edict (stated in dialog_layers_setup.cpp)
that items on a layer that is removed must be deleted.



___
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





>From a1dee36c3f0fde28646d5448d7aacd25996e159d Mon Sep 17 00:00:00 2001
From: hauptmech 
Date: Wed, 14 Mar 2018 22:31:59 +1300
Subject: [PATCH] Fix Layer setup can be changed leading to data loss Edit
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2.16.2"

This is a multi-part message in MIME format.
--2.16.2
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit


Check for items inside modules and delete them if they belong to the layer we are removing.
Pads get the offending layer removed from their layers list and deleted if they have no more layers.

Fixes: lp:1754049
https://bugs.launchpad.net/kicad/+bug/1754049
---
 pcbnew/collectors.cpp  | 14 +-
 pcbnew/dialogs/dialog_layers_setup.cpp | 27 ++-
 2 files changed, 39 insertions(+), 2 deletions(-)


--2.16.2
Content-Type: text/x-patch; name="0001-Fix-Layer-setup-can-be-changed-leading-to-data-loss-.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0001-Fix-Layer-setup-can-be-changed-leading-to-data-loss-.patch"

diff --git a/pcbnew/collectors.cpp b/pcbnew/collectors.cpp
index 2219886c2..6e1477f52 100644
--- a/pcbnew/collectors.cpp
+++ b/pcbnew/collectors.cpp
@@ -65,6 +65,9 @@ const KICAD_T GENERAL_COLLECTOR::BoardLevelItems[] = {
 PCB_VIA_T,
 PCB_TRACE_T,
 PCB_MODULE_T,
+PCB_MODULE_TEXT_T,
+PCB_MODULE_EDGE_T,
+PCB_PAD_T,
 PCB_ZONE_T,
 PCB_ZONE_AREA_T,
 EOT
@@ -499,7 +502,16 @@ SEARCH_RESULT PCB_LAYER_COLLECTOR::Inspect( EDA_ITEM* testItem, void* testData )
 {
 BOARD_ITEM* item = (BOARD_ITEM*) testItem;
 
-if( item->GetLayer() == m_layer_id )
+if( item->Type() == PCB_PAD_T )
+{
+D_PAD* pad = nullptr;
+
+wxASSERT( !pad );
+pad = static_cast( item );
+if( pad->GetLayerSet()[m_layer_id] )
+Append( testItem );
+}
+else if( item->GetLayer() == m_layer_id )
 Append( testItem );
 
 return SEARCH_CONTINUE;
diff --git a/pcbnew/dialogs/dialog_layers_setup.cpp b/pcbnew/dialogs/dialog_layers_setup.cpp
index 28b4d2d33..0c9817b2e 100644
--- a/pcbnew/dialogs/dialog_layers_setup.cpp
+++ b/pcbnew/dialogs/dialog_layers_setup.cpp
@@ -35,6 +35,7 @@
 #include 
 
 #include 
+#include 
 
 
 // some define to choose how copper layers widgets are shown
@@ -655,7 +656,31 @@ bool DIALOG_LAYERS_SETUP::TransferDataFromWindow()
 if( collector.GetCount() != 0 )
 {
 for( int i = 0; i < collector.GetCount(); i++ )
- 

Re: [Kicad-developers] [PATCH] Fix for bug/1754049

[Eeli Kaikkonen]

2018-03-18 11:09 GMT+02:00 hauptmech :

>
>
> For the case of someone with modules composed only of non-top/bottom
> elements and who are messing with the layer setup midway through the
> design, I think we should just leave it as it is. Either they are a ninja
> doing things that kicad should stay out of the way of  or they are a very
> confused beginner for whom a little extra cruft in the file is the least of
> their problems.
>
> -hauptmech
>
>
>
I agree. Of course an extra warning could be added to the already existing
warning dialog. Maybe it would be good to warn anyways if footprints are
changed because of removed layers. It may not be obvious, especially if the
user doesn't happen to know how the fooprints used are constructed.
___
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] Missing translation macros in common/dialog_about/AboutDialog_main.cpp ?

[Carsten Schoenert]

Am 17.03.2018 um 20:21 schrieb Carsten Schoenert:
> Is this somehow intended that these needed macros are removed in the
> file common/dialog_about/AboutDialog_main.cpp?
> Are there any more files to look at?
> 
> Btw: The hyperlink to the libraries needs too be reworked too.

I'm answering myself and adding two patches that adding back the i18n
strings.

-- 
Regards
Carsten Schoenert
>From 9c7b75807df13dcfb87966e164cbf506c1f5ae80 Mon Sep 17 00:00:00 2001
From: Carsten Schoenert 
Date: Sun, 18 Mar 2018 10:26:55 +0100
Subject: [PATCH 1/2] AboutDialog_main.cpp: re-adding i18n macros

Some strings in the About Kicad dialog are not displayed as translated
strings due the strings not marked as i18n based strings.
---
 common/dialog_about/AboutDialog_main.cpp | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/common/dialog_about/AboutDialog_main.cpp b/common/dialog_about/AboutDialog_main.cpp
index 7c780d064..dd40d3bc3 100644
--- a/common/dialog_about/AboutDialog_main.cpp
+++ b/common/dialog_about/AboutDialog_main.cpp
@@ -129,16 +129,16 @@ static void buildKicadAboutBanner( EDA_BASE_FRAME* aParent, ABOUT_APP_INFO& aInf
 // bullet-ed list with some http links
 description << "";
 description << ""
-<< "The official KiCad website - "
+<< _( "The official KiCad website - " )
 << HtmlHyperlink( "http://www.kicad-pcb.org"; )
 << "";
 description << ""
-<< "Developer website on Launchpad - "
+<< _( "Developer website on Launchpad - " )
 << HtmlHyperlink( "https://launchpad.net/kicad"; )
 << "";
 
 description << ""
-<< "Official KiCad library repositories - "
+<< _(" Official KiCad library repositories - " )
 << HtmlHyperlink( "https://github.com/KiCad/"; )
 << "";
 
@@ -151,7 +151,7 @@ static void buildKicadAboutBanner( EDA_BASE_FRAME* aParent, ABOUT_APP_INFO& aInf
 // bullet-ed list with some http links
 description << "";
 description << ""
-<< "Report or examine bugs - "
+<< _( "Report or examine bugs - " )
 << HtmlHyperlink( "https://bugs.launchpad.net/kicad/+bugs?orderby=-id&start=0";,
   "https://bugs.launchpad.net/kicad"; )
 << "";
@@ -163,12 +163,12 @@ static void buildKicadAboutBanner( EDA_BASE_FRAME* aParent, ABOUT_APP_INFO& aInf
 
 description << "";
 description << ""
-<< "KiCad forum - "
+<< _( "KiCad forum - " )
 << HtmlHyperlink( "https://forum.kicad.info"; )
 << "";
 
 description << ""
-<< "KiCad user's group - "
+<<_(  "KiCad user's group - " )
 << HtmlHyperlink( "https://groups.yahoo.com/neo/groups/kicad-users/info"; )
 << "";
 
-- 
2.16.2

>From abf90f16a6c423a24abefb71673ba571124e8098 Mon Sep 17 00:00:00 2001
From: Carsten Schoenert 
Date: Sun, 18 Mar 2018 10:31:13 +0100
Subject: [PATCH 2/2] AboutDialog_main.cpp: update the link to the libraries

The KiCad official libraries have now a own dedicated website.
---
 common/dialog_about/AboutDialog_main.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/common/dialog_about/AboutDialog_main.cpp b/common/dialog_about/AboutDialog_main.cpp
index dd40d3bc3..b58f6f3c0 100644
--- a/common/dialog_about/AboutDialog_main.cpp
+++ b/common/dialog_about/AboutDialog_main.cpp
@@ -139,7 +139,7 @@ static void buildKicadAboutBanner( EDA_BASE_FRAME* aParent, ABOUT_APP_INFO& aInf
 
 description << ""
 << _(" Official KiCad library repositories - " )
-<< HtmlHyperlink( "https://github.com/KiCad/"; )
+<< HtmlHyperlink( "https://kicad.github.io"; )
 << "";
 
 description << "";
-- 
2.16.2

___
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 search paths and environment variables

[Jeff Young]

There’s no good reason these are edited in separate dialogs, right?  It’s just 
a historical artefact?

(Note that I’m not suggesting a single list, just a single dialog with both 
lists.)

Thanks,
Jeff.
___
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] Missing translation macros in common/dialog_about/AboutDialog_main.cpp ?

[Jon Evans]

Committed, thanks!

On Sun, Mar 18, 2018 at 5:42 AM, Carsten Schoenert 
wrote:

> Am 17.03.2018 um 20:21 schrieb Carsten Schoenert:
> > Is this somehow intended that these needed macros are removed in the
> > file common/dialog_about/AboutDialog_main.cpp?
> > Are there any more files to look at?
> >
> > Btw: The hyperlink to the libraries needs too be reworked too.
>
> I'm answering myself and adding two patches that adding back the i18n
> strings.
>
> --
> 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] [PATCH] Fixes in GAL selection filter

[Jon Evans]

I tested these patches and they work fine for me.  I also think it's great
to add the via filtering checkbox, because I was just in need of that
feature on a layout a few days ago...
But I will defer to Wayne on whether or not this should go in for rc2.

-Jon

On Sat, Mar 17, 2018 at 12:32 PM, Andrzej Wolski 
wrote:

> Hi,
>
> there are couple problems with selection filter in GAL mode:
>
> - vias are not filtered, they are always left selected regardless of
> "Include tracks" checkbox
> - text filtering does not work
> - "Include items on invisible layers" does not work
>
> Attached patch 0001 addresses these problems.
>
> In addition, patch 0002 adds "Include vias" checkbox which allows
> independent filtering of tracks and vias, however, I'm not sure if such
> change should go into rc2?
>
> Andrzej
>
>
> ___
> 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] Fixes in GAL selection filter

[Jeff Young]

I’ve always considered a jagged feature envelope a design bug.  I’d support 
adding the via checkbox.

Cheers,
Jeff.


> On 18 Mar 2018, at 15:31, Jon Evans  wrote:
> 
> I tested these patches and they work fine for me.  I also think it's great to 
> add the via filtering checkbox, because I was just in need of that feature on 
> a layout a few days ago...
> But I will defer to Wayne on whether or not this should go in for rc2.
> 
> -Jon
> 
> On Sat, Mar 17, 2018 at 12:32 PM, Andrzej Wolski  > wrote:
> Hi,
> 
> there are couple problems with selection filter in GAL mode:
> 
> - vias are not filtered, they are always left selected regardless of "Include 
> tracks" checkbox
> - text filtering does not work
> - "Include items on invisible layers" does not work
> 
> Attached patch 0001 addresses these problems.
> 
> In addition, patch 0002 adds "Include vias" checkbox which allows independent 
> filtering of tracks and vias, however, I'm not sure if such change should go 
> into rc2?
> 
> Andrzej
> 
> 
> ___
> 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] - File format shim for clearance data

[Jeff Young]

OK, for your guys’ (re)viewing pleasure, a patch which losslessly round-trips stuff it doesn’t understand.

0001-Lossless-round-tripping-of-unknown-constructs.patch
Description: Binary data
On 16 Mar 2018, at 19:15, hauptmech  wrote:While i would still like to see this (my) shim go in, I agree with wayne. Until/unless a less brittle approach is used for the parser, it's better to signal a problem painfully and maintain the integrity of the file.I have to admit that when i first heard the s-expressions idea I assumed that the intention was to use a lisp like virtual machine for loading and maintaining design data. I've used vm's for data storage before (lua and python), and it's great. Parsing is free and you can jam in functions and other data when needed. On 17 Mar 2018 07:17, "Jeff Young"  wrote:Hi Wayne,

Patch reverted.

However, I think your concern is misplaced.  If we want to prevent dataloss (ie: from reading a 6.0 file into 5.0), then we should warn the user based on the version string (and give them a chance to say “I still want to open”).

But either way, actually failing to read the file leaves the user in a pickle (especially when it’s easy enough for them to try out a nightly that may very well be ahead of their stable).

(And for that reason I think it’s important to put it into 5.0, as otherwise it won’t help until we start making 7.0 file format changes.)

Cheers,
Jeff.

> On 16 Mar 2018, at 18:00, Wayne Stambaugh  wrote:
>
> Jeff,
>
> Please revert this patch.  Any changes to the board file parser and/or
> formatter need to be discussed before the changes are committed.  It has
> been the intention that the board parser be pendantic by design to
> prevent data loss by ignoring unknown formatting.  Allowing anything
> outside of the expected formatting in the board file is not something
> that I want to introduce without some discussion.  Even should we decide
> to accept this patch, I would prefer we put it off until v6.
>
> That being said, the patch fails to build on windows with following error:
>
> C:/msys64/home/wstambaugh/src/kicad-trunk/pcbnew/pcb_parser.cpp: In
> member function 'void PCB_PARSER::parseUnknown()':
> C:/msys64/home/wstambaugh/src/kicad-trunk/pcbnew/pcb_parser.cpp:1269:12:
> error: request for member 'LogText' in '__acrt_iob_func(2)', which is of
> pointer type  FILE* {aka _iobuf*}' (maybe you meant to use '->' ?)
>     stderr.LogText( msg );
>            ^~~
>
> Cheers,
>
> Wayne
>
> On 3/16/2018 1:08 PM, Jeff Young wrote:
>> Perhaps somewhat germane to this discussion I have removed the strict-format nags from the PCB parser.  It now logs warnings to stderr but otherwise ignores structures it doesn’t understand.
>>
>> I’m not sure that helps hauptmech much as if the file is subsequently written the unknown markup will be lost, but I thought I’d mention it.
>>
>> Cheers,
>> Jeff.
>>
>>> On 7 Mar 2018, at 20:12, hauptmech  wrote:
>>>
>>> Hi Thomasz,
>>>
>>> I hope I'm able to address you concerns. I'm stuck using kicad stable in many situations. I brought clearances up for discussion last July but no one moved on it, nor are they required to. Clearance management is a major pain point for me so I wrote a fix. This patch will let us (me and the people I collaborate with) work using version 5, but open and close files written with a version patched with clearance handling code.
>>>
>>> I believe that code exactly like this will go into version 6. Getting it in earlier makes a huge difference to me, so I'm submitting it.
>>>
>>> On 07/03/18 23:30, Tomasz Wlostowski wrote:
 Hi hauptmech,

 I'm sorry but IMHO we can't accept your patch:
 - it changes the file format while we are already in feature freeze.
 This is a way too big change to accept for the V5.
>>>
>>> This patch simply adds tokens to the file format. No clearance data is saved for files that use the netclass only. Files without clearance tokens continue to remain without them.
>>>
>>> Yes it is a backward compatible file format change, but it does no harm to V5 files already in the wild.
>>>
 - we are planning to overhaul the clearance/design rules system in V6.
 Storing the clearance *DIRECTLY* for each track segment/via will
 conflict with any more sophisticated design rule management system.

>>> I'm glad you are planning this. I am sure that regardless of the sophistication of the rule system, you will store clearance directly for exactly the same reason that track width is stored directly now. There are always exceptions to the rules.
>>>
>>> If kicad choose a direction that does not store clearances per item, then it is easy to rip these few lines back out.
>>>
>>> Did this answer your existing concerns about this patch? Are there any other concerns you have about this patch?
>>>
>>>
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~kicad-

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

[Nick Østergaard]

Hi Seth,

I tried to test your patch. It bascially works. Some observations follows:

I think the message printed from cmake
"from /opt/oce/lib/libTKernel.so I found /opt/oce/lib"
should be removed from the output, it looks liek a debug message to me. I
guess the same information is available in the CMakeCache.txt if needed
later on.

It defaults to OCE as expected, builds, and runs.

If I remove OCE it will find my normal opencascade installation, builds and
runs.

I think it also did use OCC if I set KICAD_USE_OCC=ON, where it built and
ran fine. But when this happens I still see KICAD_USE_OCE=ON in the cache.
This might be ok, but could be confusing.

I canẗ make it use an alterntive install location of OCC, I tried to set
OCC_INCLUDE_DIR=/opt/opencascade7/inc. This fails. What variable do I need
to set to select another version of opencascade?

I tested this on archlinux. I think it could be improved to be less
errorprone, but could possibly be comitted as is if that debug log is
removed. It seems to work fine if you are not switching between OCE and OCC
in the same build dir, that is, a clean config.

Nick

2018-03-17 0:51 GMT+01:00 Nick Østergaard :

> Thank you very much, I will try to remember it after the weekend.
>
> 2018-03-17 <20%2018%2003%2017> 0:46 GMT+01:00 Seth Hillbrand <
> seth.hillbr...@gmail.com>:
>
>> Hi Nick-
>>
>> I finally found a moment to figure out Docker and get this up and running
>> in your build configuration.
>>
>> Please take a look when you have a chance and let me know if you have any
>> issues with this patch.
>>
>> Best-
>> Seth
>>
>> 2018-02-10 <20%2018%2002%2010> 7:12 GMT-08:00 Seth Hillbrand <
>> seth.hillbr...@gmail.com>:
>>
>>> Nick was having an unknown issue but I haven't heard back from him on
>>> whether the issue was resolved by doing a clean cmake.  If it isn't then
>>> I'll need to address that.
>>>
>>> Nick did you have a chance to test that?
>>>
>>> -S
>>>
>>> 2018-02-10 <20%2018%2002%2010> 6:18 GMT-08:00 Wayne Stambaugh <
>>> stambau...@gmail.com>:
>>>
 Seth,

 What is the current status of this patch?  I would like to get it merged
 before rc1 so the package devs can test it.

 Cheers,

 Wayne

 On 01/30/2018 02:12 PM, Seth Hillbrand wrote:
 > Nick-
 >
 > Thanks for the test.  I'm attaching revised patch that allows multiple
 > OpenCASCADE installations on a single machine.
 >
 > I've tested with a few different OpenCASCADE versions down to 6.8 with
 > no issues installed alongside OCE 0.17.  You can choose which you want
 > to link by using either "-DKICAD_USE_OCE" or "-DKICAD_USE_OCC".  If
 both
 > are specified, "-DKICAD_USE_OCC" will override.
 >
 > I corrected the cmake message display to be less doubled and correctly
 > show the library location.
 >
 > I've also added the OCC version and type to the about window version
 info.
 >
 > The "Based on" line was taken from
 > (https://github.com/FreeCAD/FreeCAD/blob/master/src/FCConfig.h) when
 > trying to determine how FreeCAD likes to refer to themselves.  The
 > actual FindOpenCascade.cmake file did not have a copyright header
 > attached but falls under the license from
 > (https://github.com/FreeCAD/FreeCAD/blob/master/COPYING).  I note
 that I
 > had it written as "FreeCAD CADx development system".  I've corrected
 > this to read "FreeCAD CAx development system".
 >
 > I'm not sure to what the "CheckSymbolExists" line is referring.  I
 don't
 > see it on my machine.
 >
 > -Seth
 >
 > 2018-01-29 14:30 GMT-08:00 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_patc
 h_occt/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx
 > -- Looking for
 > /home/amazingdude/kicad-source-mirror/build_seths_occt_patc
 h_occt/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx
 > - not found