Steven,
On 7/30/21 4:24 PM, Steven A. Falco wrote:
[...]
> -- Found PythonLibs: /usr/lib64/libpython3.10.so (found suitable version
> "3.10.0b4", minimum required is "3.6")
> Traceback (most recent call last):
> File "", line 1, in
> File "/usr/lib64/python3.10/site-packages/wx/__init__.py",
On 1/2/21 6:31 PM, jp charras wrote:
>
> Le 02/01/2021 à 18:11, Carsten Schoenert a écrit :
>> Am 02.01.21 um 18:07 schrieb jp charras:
>>> What is the problem with these files?
>> They are build in tree in case you do a configure out of tree?
>>
>>> They are already the final header files built f
piler: GCC 7.2.1 with C++ ABI 1011
>
> Build settings:
> USE_WX_GRAPHICS_CONTEXT=OFF
> USE_WX_OVERLAY=OFF
> KICAD_SCRIPTING=OFF
> KICAD_SCRIPTING_MODULES=OFF
> KICAD_SCRIPTING_WXPYTHON=OFF
> KICAD_SCRIPTING_ACTION_MENU=OFF
> BUILD_GITHUB_PLUGIN=ON
> KIC
Hi everyone,
I've been reading on this list for quite a while, but quietly...
Today this changes - I stumbled across a bug in 4.0.7 stable, and since
I don't have a launchpad ID, I'm reporting it here. I don't seem to
recall this being addressed recently though if it's fixed in master I'll
happil
I strongly believe that's because many people come from Eagle originally
(even via a different professional tool) and Eagle has this distinction.
A symbol is what you place in the schematic, a footprint is what you
place on the PCB and a component is what defines their relationship (and
links to a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/08/2015 11:36 PM, Chris Pavlina wrote:
> On Mon, Jun 08, 2015 at 11:28:08PM +0200, Heiko Rosemann wrote:
>>> A given component should have exactly ONE available footprint.
>>> If your opamp comes in PDIP-8 and SOIC-8, those
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/08/2015 10:41 PM, Andy Peters wrote:
>
>> On Jun 8, 2015, at 12:19 PM, Heiko Rosemann
>> wrote:
>>
>> So you have a single "canonical" version of each footprint and
>> symbol. No need to copy symbols
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/08/2015 06:42 PM, Andy Peters wrote:
>
>> On Jun 7, 2015, at 1:33 AM, Eldar Khayrullin
>> wrote:
>>
>>> What problem is this trying to solve?
>
>> No copy sch symbols, no copy pcb footprints, more ready parts
>> with same sch symbol and footp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/22/2014 01:44 AM, Cirilo Bernardo wrote:
>> From: Jon Neal
>>
>>
>> Looking from the outside that is very aggressive, harsh, and
>> childish. I thought you were stepping away from the project Dick
>> (At least t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/03/2014 04:49 AM, tiger12506 wrote:
> This is a guess (i'm not OP), but it's pretty common to shun
> assignment within an if condition. The second line probably just
> masks the warning from the compiler -- the check that triggers the
> warning p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/05/2014 12:23 PM, Vesa Solonen wrote:
> 05/04/14 12:29, Nick Østergaard kirjoitti:
>> 2014-04-05 11:09 GMT+02:00 Vesa Solonen :
>>> 05/04/14 01:23, Heiko Rosemann kirjoitti:
>
>>>> I came to kicad from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/05/2014 11:29 AM, Nick Østergaard wrote:
> 2014-04-05 11:09 GMT+02:00 Vesa Solonen :
>> 05/04/14 01:23, Heiko Rosemann kirjoitti:
>>> On 04/04/2014 10:45 PM, Carl Poirier wrote:
>>>> I think this is a very goo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/04/2014 10:45 PM, Carl Poirier wrote:
> I think this is a very good idea. I will add this to our upcoming
> KiCad library convention. Many transistors use letters already.
I do not agree for footprints, because - at least if I understand the
pro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/11/2013 09:04 PM, Alex G. wrote:
> On 07/11/2013 09:06 AM, Milan Horák wrote:
>> Hi there
>>
>> Why are the distributions' versions of kicad so outdated? Like
>> an year ago in Debian!
>>
> The version that is packaged is really at the package
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/21/2013 09:05 PM, Dick Hollenbeck wrote:
> On 06/21/2013 11:23 AM, Wayne Stambaugh wrote:
>> KiCad failed to build against the latest build of wxWidgets
>> 2.8.12 on Debian testing. Apparently they have dropped building
>> wxWidgets with libgnom
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/29/2013 07:08 PM, Lorenzo Marcantonio wrote:
> Looking around for angles I noticed a thing... especially when
> computing distance (like using hypot or a whole sqrt expression),
> sometimes the result is KiROUND-ed while often a simple (int)
> tr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/22/2012 03:01 PM, László Monda wrote:
> Ah, that makes sense then. Given that the increased resolution is
> explicitly stated on the Eagle 6 page I'm pretty sure that they
> moved from 100 nm to about 1 pm order of magnitude-wise and from 32
>
Hi everyone,
after some trouble building current kicad-bzr (3491 and 3494) I found
the time to investigate today. Seems there is - apart from the
well-documented --with-gnomeprint-requirement in wxgtk - an
incompatibility in the boost-library included in the kicad-tree with gcc
4.7.0 (at leas
On 04/08/2012 06:59 PM, lajos kamocsay wrote:
However it's easy to rebuild wxgtk on arch with libgnomeprint support:
- install libgnomeprint and libgnomeprint from aur:
- yaourt -Sy libgnomeprint libgnomeprintui
- build wxgtk from abs, it will automatically detect libgnomeprint,
so no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Everyone,
On 03/21/2012 10:44 PM, Brian F. G. Bidulock wrote:
> Dick,
>
> Because only artistic works, software and chip masks are protected
> by copyright (internationally). Functional items such a PCB
> boards are not protected. Using library da
Hi everyone,
not sure whether bug reports to the library also go here: I found some
parts in the atmel.lib to specify a "wanted footprint" of TQPF44 - the
real name would be TQFP44.
The attached patch fixes this. I built it on a bzr checkout from today -
at least if the archlinux packages do what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/30/10 11:44, Lorenzo Marcantonio wrote:
> I can't select anymore in eeschema dragging with the left mouse
> button... did something change?
I had trouble with this as well, because wxWidgets sends an extra
"MouseEntered" event every time the mou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/13/10 16:26, Dick Hollenbeck wrote:
> $ bzr up
> Tree is up to date at revision 2448 of branch
> bzr+ssh://bazaar.launchpad.net/~kicad-testing-committers/kicad/testing
>
>
> $ patch --dry-ru
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello everyone,
I have come across the same problem as Jacques mentioned in
http://tech.dir.groups.yahoo.com/group/kicad-users/message/7780 - group
selection does not work, dragging the mouse with left button pressed
shows no reaction. This was on gen
24 matches
Mail list logo