I am here to ask for a suggestion before (if ever) filing a bug that
could be a matter of personal taste.
I found strange tha the kicad project manager have not a hotkey list.
I mean, whenever I see a toolbar I think that I do not want to leave the
keyboard to just press a button on the screen, h
Hi Adam,
I just tried your build, and it works like a charm. I'm now looking forward to
regularly
using the Kicad OSX nightlies. Again, thank you for all your effort improving
the Kicad
experience for OSX users!
Best,
Johannes
> Am 23.02.2015 um 22:48 schrieb Adam Wolf :
>
> Hi Johannes,
>
Hi folks,
We have a user in IRC who tried the debug build I made after installing
dependencies with brew with --build-bottle (which forces them to build with
older CPU settings), and it works for them.
The regular nightlies tonight will pick those up as well. Thanks everyone
for the insights!
A
Thanks everyone!
On Mon, Feb 23, 2015 at 4:30 PM, Andy Peters wrote:
> I just wanted to say thanks to all of the developers working hard on
> Kicad. I lurk on this list and do as much OS X testing as possible (I do
> daily builds on two different machines), so I don't contribute as much as
> the
I just wanted to say thanks to all of the developers working hard on Kicad. I
lurk on this list and do as much OS X testing as possible (I do daily builds on
two different machines), so I don't contribute as much as the rest of you.
I just sent the design files for the second design I've done in
Hi all,
I am trying to understand how eeschema gets its preferences (i.e., libraries
and library path) on a completely fresh machine that has never seen KiCad
before.
From the code, I guess it should find a kicad.pro in the default search paths
eeschema still uses and shall copy it to some loc
Hi Johannes,
Can you try the build here:
http://downloads.kicad-pcb.org/osx/DEBUG/
Please let me know if it is the exact same crash, a different one, or if by
some miracle it works :)
Thanks!
Adam Wolf
On Mon, Feb 23, 2015 at 1:00 PM, Nick Østergaard wrote:
> 2015-02-23 19:17 GMT+01:00 Bob
2015-02-23 19:17 GMT+01:00 Bob Gustafson :
> I wonder whether the idea of the Nightlies is being torn between two goals:
>
> 1) Having a system that more or less 'all' Mac users can use.
> 2) Doing bleeding edge build/tests on the latest repository changes.
Those can easily coexist. Tell me why a
What's the best arch I should pass for compatibility reasons--I can do this
across the board for the brew dependencies.
Adam Wolf
On Mon, Feb 23, 2015 at 10:04 AM, Garth Corral wrote:
> The issue here isn’t with pixman, per se, it is down to the fact that it
> is being configured and built on o
The issue here isn’t with pixman, per se, it is down to the fact that it is
being configured and built on one machine with support for some newer vector
instructions, and run on another who’s cpu does not support those instructions.
So long as it’s built and run on the same machine you would no
On 2/23/2015 6:07 AM, Brian Sidebotham wrote:
> On 22 February 2015 at 03:00, Mark Roszko wrote:
>> Fixes some cases where n-1 bytes was used as a size but snprintf
>> protects against that internally. Also some hardcoded constant sizes
>> changed to sizeof()
>
>> And made a case where sprintf
You would think that would be the default behavior for a compiler used
for cross compilation to avoid opening security holes without realizing.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
U
Hi,
my own build of r5447 just finished and pcbnew does *not* crash.
I decided to change my build flags to match Adam's more closely, e.g. building
without
Scripting, here is what the version information *from my own build* gives now:
Application: kicad
Version: (2015-02-22 BZR 5447)-product Rel
Hi,
I don't know if it helps... I am building pixman with MacPorts, and I
used to have it compiled with X11, but I recently switched to use the
--without-x11.
For me both work, I don't see what the difference is (apart from less
X11-libraries needed in the bundle when compiling with --without-
Hello Adam, Garth, and Bernhard,
first, the build of last night (r5447) still crashes on my system with the same
report pointing towards libpixman.
My system is an older Mac Book Pro (middle 2010) with the following base specs:
Modellname: MacBook Pro
Modell-Identifizierung: Mac
On 22 February 2015 at 03:00, Mark Roszko wrote:
> Fixes some cases where n-1 bytes was used as a size but snprintf
> protects against that internally. Also some hardcoded constant sizes
> changed to sizeof()
> And made a case where sprintf was used into snprintf as the path input
> as aUserPlugi
That’s correct, at a minimum (if you want to do your own builds),
you need at least wxGTK3 from my copr build (and wxPython3 if you want
WXPYTHON enabled).
wxGTK3 in the copr build is built against gtk2, which will fix your issue
with drawing for now.
Now that you’re on f21 you should be able to
Awesome job!!! ;)
Miguel Ángel Ajo
On Monday, 23 de February de 2015 at 09:57, Javier Serrano wrote:
> On Sat, Feb 21, 2015 at 6:29 PM, Adam Wolf
> mailto:adamw...@feelslikeburning.com)> wrote:
> > Thanks everyone! Even though this was a lot of work from us at Wayne and
> > Layne, what we did w
On Sat, Feb 21, 2015 at 6:29 PM, Adam Wolf
wrote:
> Thanks everyone! Even though this was a lot of work from us at Wayne and
> Layne, what we did was only a drop in the bucket compared to what has
> already been done by the dev team and the OS X devs!
Adam, congratulations to you and the rest of
On Mon, Feb 23, 2015 at 1:20 AM, Wayne Stambaugh wrote:
> COPYRIGHT.txt was meant to be a convenience for devs to copy and paste
> the license into new source files. If it doesn't match what is in our
> source files then we should update COPYRIGHT.txt accordingly. I thought
> it was the same but
20 matches
Mail list logo
