Finally succesfully build kicad on a all fresh Ubuntu 14.04 yesterday.
/apt-get build-dep kicad/ installs wxWidget 2.8 by default (wx3.0 are on
other repo). It might be a good idea to advise to install wx3.0.2 before
executing /apt-get build-dep kicad /in this page:
http://www.kicad-pcb.org/dis
Le 13/10/2014 03:50, Carl Poirier a écrit :
Is component" the official naming? What about symbol?
I remember when I started using EDAs, I was looking for "symbol menu" to
put things on schematic. I think I was looking for symbol because we
call symbol what we draw on a schematic. Imo Component
My build does not have any scripting enabled.
But the problem is easy to reproduce. Just start pcbnew before eeschema, and
eeschema is totally unusable as the screen is an ugly reddish color and I could
not find a way to fix it.
Jean-Paul
AC9GH
On Oct 12, 2014, at 7:55 PM, Ian Woloschin wrot
If you want me to, I can help with modifying the script to enhance the two
error handling and testing it with Ubuntu 14.04.
On Sunday, October 12, 2014 3:55 PM, Wayne Stambaugh
wrote:
On 10/12/2014 1:49 PM, Mark Roszko wrote:
> He wasn't commenting about the wxWidgets version
Is component" the official naming? What about symbol? As was discussed in
the other thread, I am convinced the former should be reserved for a future
feature consisting of the marriage of different things, such as a symbol, a
footprint, a SPICE and 3d model. Else, how are we going to call these? I
Very minor but the main KiCAD window calls it "Schematic Library
Editor", eeschema calls it "Library Editor" and the window itself is
"Parts Library Editor".
Can the name be standardized?
It might be better to just call it "Component Library Editor" because
that's what the schematic symbols are c
I am able to reproduce this bug, using 5173. If I open PCBNew before
Eeschema then I just get a big red blob in the Eeschema window. If I open
Eeschema first it's fine. While somewhat annoying, it seems to resolve
itself by closing and re-opening the KiCad Project Manager, so it's a
pretty quick
No.
On Oct 12, 2014, at 3:01 PM, Nick Østergaard wrote:
> So are you able to reproduce now?
>
> 2014-10-12 23:44 GMT+02:00 Garth Corral :
>> This is not new; I saw it as far back as 5151. I didn’t correlate it with
>> any sort of launch order, though, and I wasn’t able to reproduce it.
>>
>>
So are you able to reproduce now?
2014-10-12 23:44 GMT+02:00 Garth Corral :
> This is not new; I saw it as far back as 5151. I didn’t correlate it with
> any sort of launch order, though, and I wasn’t able to reproduce it.
>
> Garth
>
>
> On Oct 12, 2014, at 1:17 PM, Bernhard Stegmaier
> wrote
On 10/12/2014 1:49 PM, Mark Roszko wrote:
> He wasn't commenting about the wxWidgets version in particular.
>
> He was saying that Ubuntu does not have the python libraries for 3.0x
> and the install script blindly uses a grouped package install command
> which will fail if any of the packages are
This is not new; I saw it as far back as 5151. I didn’t correlate it with any
sort of launch order, though, and I wasn’t able to reproduce it.
Garth
On Oct 12, 2014, at 1:17 PM, Bernhard Stegmaier wrote:
> I can’t confirm that with the rev. 5173 I am currently working on (which some
> impro
I can’t confirm that with the rev. 5173 I am currently working on (which some
improvements & fixes, but none of that should fix such a behavior). None of the
changes 5173-5176 looks like they would cause something like that.
I’ll push my changes to Wayne next days, you might want to try then.
I
He wasn't commenting about the wxWidgets version in particular.
He was saying that Ubuntu does not have the python libraries for 3.0x
and the install script blindly uses a grouped package install command
which will fail if any of the packages are missing even though the
python is rather optional f
Ok, I purged the wxGrid implementation and moved to a wxListCtrl which
is superior. Now all the special keys are properly caught.
The right click menu has been eliminated because wxListCtrl gets all
the onCharEvents that wxGrid did not pass.
The key conflict logic now checks between other section
Patch committed in r5176. Thank you for your contribution to KiCad.
Wayne
On 10/10/2014 2:45 AM, Mark Roszko wrote:
> Woops, should have grepped the fbp files this time which I didn't the
> first time either.
>
> Thanks to Konstantin for showing the errors of my way, attached patch
> that combi
KiCad now requires wxWidgets 3.0.0 or greater to build. We are in the
process of phasing out support for the 2.8 branch due to the number of
know problems. You can edit install_kicad.sh to build with wxWidgets
2.8.12 for your own purposes. Please note that you will pretty much be
on your own for
Pay attention, please:
https://bugs.launchpad.net/kicad/+bug/1375232
Regards, Konstantin.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
On 12.10.2014, at 07:38, Bob Gustafson wrote:
> I think it is working now. When I use eeschema and move around a component -
> no artifacts - hooray
Well, good to hear… :)
>
> Following the osx_build_wx.sh - there are still some problems:
>
> 1) The 'make install' step needs to be 'sudo make
18 matches
Mail list logo
