On Mon, Apr 28, 2014 at 03:00:41PM -0400, Jean-Paul Louis wrote:
> US is really sticking to the Imperial system, but the rest of the world is
> metric. So who will win is not obvious, but I would bet on the metric on the
> long run.
OK, there is a rule for this too :D IPC7351B says 'everything i
Marco,
It looks like the previous problem has been fixed, and I am now able to
complete the build.
I just finished to build the BZR4837 without trouble.
I understand what you said about the install. but the cake process is not
working right.
During the "make install", a “bin" directory is added
On 28/apr/2014, at 19:25, Jean-Paul Louis wrote:
Jean-Paul,
You should try bzr 4835, look to ML “OSX - Issue with the last Compiler
Update”, as you see is not always simple to keep up the ML.
I’ve waited you on IRC until 1am Local time, then i’m an Human i need sleeptime
too.
You weren’t supp
On 28/apr/2014, at 21:44, Maciej Sumiński wrote:
Great Maciej, please commit it :)
Bye
> Hi Marco,
>
> I am currently away from CERN, so I do not have any access to OS X at the
> moment. Usually, when I hear about errors related to Mac, I build KiCad with
> clang under Linux, but this time
Hi Marco,
I am currently away from CERN, so I do not have any access to OS X at
the moment. Usually, when I hear about errors related to Mac, I build
KiCad with clang under Linux, but this time it is not enough (everything
compiles fine on my machine).
I see that you have already changed the c
I am also a strong supporter on good and stable conventions that allows
consistency in the electrical symbols.
Naming conventions are important as they help to understand what the part is.
I don’t really care about the unit used for the symbols, but we need to pick
one up and stick to it, and rej
Hi,
I was hoping for some convention like this to array soon since I'm making
new components for every project and I would love them to follow the KiCad
convention so they can be contributed.
Carl, could you please upload a document with those conventions that are
already decided? Like naming, pe
Marco,
I have been working on the Mac OS X build for quite a while now, and I was
successful in the build.
The weak part was the install, as the default install was installing the
bundles in /usr/local/bin which is wrong for Apple OS X.
So I added a “-DCMAKE_INSTALL_PREFIX=$INSTALL_DIR” in my sc
On 27/04/14 20:18, Francesco Del Degan wrote:
>
> Yes, I will try to reuse the helper classes that was committed few days ago,
> and fix some issues with it. (I just discovered that actual BGA
> footprint uses all
> 26 letters, but only ABCDEFGHJKLMNPRTUVWY should be allowed) .
My bad, thanks fo
Jean-Paul,
I've well realized that there are problems to build Kicad on OSX, i've
worked a lot since 2008 to let it work as it does now including a lot of
patches needed to make it work.
The documentation on how to compile Kicad is in
Documentation/compiling/mac-osx.txt, do you have tried following
On Sun, Apr 27, 2014 at 03:38:53PM -0400, Carl Poirier wrote:
> Yes, obviously the rules will be separated in the corresponding sections in
> the complete version. We however also have to discuss pin placement on
> symbols, especially the black-box ones. What do the standards say about it?
Not muc
11 matches
Mail list logo
