(jw at mip.informatik.uni-kiel.de).
+# Jan Mrázek (email at honzamrazek.cz)
#
# Based on previous works of:
# Jan Woetzel (FindwxWindows.cmake),
@@ -728,6 +729,38 @@ else()
endforeach()
endmacro()
+#
+# Check if all the required libraries are present in the build. The only
would think that depending on this to be
consistent might be wishful thinking leading to maintenance issues. I
am not thrilled with the idea of patching our build config to fix what
seems to me to be a packaging issue.
On 3/20/2017 10:16 AM, Jan Mrázek wrote:
Both official one and KiCad one version
Hi,
I have taken your points in account and made a much nicer solution
(patch attached).
Dne 20.3.2017 v 18:33 Wayne Stambaugh napsal(a):
On 3/20/2017 11:15 AM, Jan Mrázek wrote:
There are no missing headers, only some parts of the headers are
#ifdefed out. This is the reason I looked for
My bad, wrong directory. Correct patch attached.
Dne 21.3.2017 v 13:12 Wayne Stambaugh napsal(a):
This looks like the same patch as the first one.
On 3/20/2017 3:49 PM, Jan Mrázek wrote:
Hi,
I have taken your points in account and made a much nicer solution
(patch attached).
Dne 20.3.2017
FindwxWidgets.cmake.
Patch attached.
Honza
Dne 20.3.2017 v 20:49 Jan Mrázek napsal(a):
Hi,
I have taken your points in account and made a much nicer solution
(patch attached).
Dne 20.3.2017 v 18:33 Wayne Stambaugh napsal(a):
On 3/20/2017 11:15 AM, Jan Mrázek wrote:
There are no missing headers, only
Hi,
I am a little confused. What exactly is wrong with the patch? According
to the IRC discussion a while ago, I think it was with nickoe, the best
approach is probably to adopt the changes in FindwxWidgets and when
KiCAD upgrades to a reasonably new CMake, get rid of the KiCAD copy and
use t
Hello,
I develop and maintain several KiCAD plugins. Many of my users started
switching/would like to KiCAD 5.99 as it brings many exciting features.
Therefore, I get frequently a question when KiCAD v5.99 will be
supported. However, as there were some breaking changes and some parts
of the A
Hello Wayne and others,
I am really looking forward for the release. As a maintainer of several
KiCAD plugins, I would like to add support for KiCAD 6 to them before
it is released so my users can migrate right away. However, the last
time I wanted to add the support I run into a problem of m
Hello Seth,
thank you for explaining the situation about the current situation with
API. I really appreciate it. You don't have to be sorry about no having
a shiny new API for v6 - the whole team have done a tremendous amount of
great work and v6 look awesome! I don't know a single plugin deve
Hi Lev,
I wrote a simple library for parsing the schematic for KiKit:
https://github.com/yaqwsx/KiKit/blob/master/kikit/eeschema_v6.py
Jan
On 17. 01. 22 0:51, Levente wrote:
Hello devs,
I miss the sch.py from kicad-library-utils for v6, and I thought I
write it myself. Do I miss somethin
Chris and Wayne,
I have the latest nightly build and I can confirm a slow-down when I try
to add a component in a schematic. The first usage after KiCAD startup
takes roughly 3-5 seconds to load. Every other usage takes approx. 0.5
seconds and it is quite annoying and productivity killing.
I
I am sorry for a mistype; automatically -> immediately.
Dne 28.12.2017 v 23:36 Jan Mrázek napsal(a):
Chris and Wayne,
I have the latest nightly build and I can confirm a slow-down when I
try to add a component in a schematic. The first usage after KiCAD
startup takes roughly 3-5 seconds
) that has all of the symbol
libraries in the default symbol library table and compare the
performance with this many libraries using version 4. I'm guessing you
will see a similar performance hit.
On 12/28/2017 05:36 PM, Jan Mrázek wrote:
Chris and Wayne,
I have the latest nightly build and
13 matches
Mail list logo
