On 03.11.2015 15:30, Joseph Chen wrote:
> I recently started seeing lots of lines of printed texts on the terminal
> where kicad is started in Linux, and a quick grep shows the following
> line does the printouts:
>
> pcbnew/router/pns_line_placer.cpp:1046:printf("H-net %d\n",
> aHead.Net());
The Paltatech boards were the closest ones to "commerical" but they
have had the linked added.
http://www.paltatech.com/eiti/
http://www.paltatech.com/electrosmart/
On Tue, Nov 3, 2015 at 9:53 AM, Wayne Stambaugh wrote:
> I'm OK with this. I don't know if we even have any
This is exactly what I am looking for. It doesn't need to be a big
production, just a link to our website.
On 11/3/2015 10:08 AM, Mark Roszko wrote:
> The Paltatech boards were the closest ones to "commerical" but they
> have had the linked added.
> http://www.paltatech.com/eiti/
>
On Mon, Nov 2, 2015 at 8:53 PM, Wayne Stambaugh wrote:
> I know it's noisy but I want developer input on this as well as website
> developer input. I think the developers have a right to know how their
> work is being used and have a say in it. The CERN folks may want some
Hi, I was looking at the source code, and my old brain need's some real
help with all the endless includes.. etc
I was wondering if any one had put up the source code using Lxr, like
http://lxr.free-electrons.com/
if not how much interested would here be from other developers.. ?
I was thinking
Hi, the current version of the Linux/debian/RedHad install script has some
short comings which I'm attempting to to fix,
I have put up a test version with enhancements at
http://www.cosmosc.com/kicad/ for developers to try out and give me feed
back.
It's only be tested on Debian, as I don't have
On Tue, Nov 3, 2015 at 12:39 AM, Wayne Stambaugh wrote:
> Yes. The P router still has a serious segfault issue. I've talked to
> Tom about it and he is working on it. As soon as the fixes are
> committed, I will be rolling out rc2. I'm hoping it will be soon.
Last time
The Bug:layers 95 and 96 don't exist in Eagle PCB there only in sch.
The source incorrectly show's layers from 91 to 98 as
being pcb layers there not. Only sch layers.
In Eagle you can not crate layers 95 and 96 you just get a
error. Only layers 100 and
On Tue, Nov 03, 2015 at 12:03:03PM +0200, Lachlan Audas wrote:
> PS: I can't get the doc's to build, the current URL for doc's for bzr
> is out of date.. or damage.. or ?
> Has any one the correct one for the docs?
Old bzr docs are disabled as for new docs are now in the github repo:
Sorry did not finish the post so continue..
Here are to patch's first one reassign import layers 95 and 96 to 160 and
161, and remove's the comments about layers 91-98 being
Eagle PCB layers. I prefer this one, as my eagle to kicad conversion scrip
can document change I have made on those
Hello,
I reported the bug #1511552 and suggested to provide a patch. I'd like to hear
your suggestions and objections to what I was to going to do.
In short (details in the bug report):
In EESchema, it is hard to create a schema that can be used simultaneously for
Spice simulations and Pcb
So it turns out all the demo files in KiCad are also affected by the
translated layer name mess.
They all more or less have the french layer names. So none of them
load as of bzr 6292 in pcbnew.
So ignoring that issue for a moment, is there any reason why we cannot
add a more friendly error
"Proprietary" does sound better for the cases people are not
particularly selling but rather showcasing
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe :
On Tue, Nov 3, 2015 at 6:11 PM, Mário Luzeiro wrote:
> That is good news. Olimex precedes Arduino and the boom of opensource
> hardware we are at moment. I remember long years ago that Olimex was already
> a reference in embedded systems with their development boards.
> It
Hi Cirilo and all,
is there a way to invoke / export the pcb board to IDF from a python
command in pcbnew python kicad console?
I went through pcbnew.py file but it seems to me there is no command to
do it with the pcbnew python APIs...
Maurice
Hi,
Olimex did already some small boards / interfaces in kicad (probably to
test the new version)
https://github.com/OLIMEX/BB-CH340T/raw/master/bb-ch340t.kicad_pcb
https://github.com/OLIMEX/MOD-MPU9150/raw/master/HARDWARE/MOD-MPU9150-Rev.A/mod-mpu9150.kicad_pcb
"Olimex is paving the way with their migration from Eagle to KiCad. Hopefully
the
Arduinos, Adrafruits and Sparkfuns of the world will one day choose to
use KiCad too."
That is good news. Olimex precedes Arduino and the boom of opensource hardware
we are at moment. I remember long years ago
I found the issue, this packages are missing in the instructions:
pacman -S mingw-w64-i686-toolchain
pacman -S make
Mario
From: Kicad-developers
[kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of
Mário Luzeiro [mrluze...@ua.pt]
>> http://ci.kicad-pcb.org/job/kicad-doxygen/ws/Documentation/doxygen/html/md_Documentation_development_compiling.html#build_windows.
Hi all,
I am following the build kicad instruction on windows for the first time but
cmake is failing. Is something missing in the instructions?
Help!
Thanks
I don't have the prompt right here, but maybe there must not be a
space between the G and the "MSYS...
2015-11-03 23:28 GMT+01:00 Mário Luzeiro :
>>> http://ci.kicad-pcb.org/job/kicad-doxygen/ws/Documentation/doxygen/html/md_Documentation_development_compiling.html#build_windows.
Someone please add these boards to the made with kicad when you get a
chance.
Thanks,
Wayne
On 11/3/2015 2:35 PM, easyw wrote:
> Hi,
>
> Olimex did already some small boards / interfaces in kicad (probably to
> test the new version)
>
>
Patch committed in the product branch r6296. Thank you for your
contribution to KiCad.
Cheers,
Wayne
On 11/3/2015 12:21 AM, Mark Roszko wrote:
> Quick pass. Removed a little dead includes, unused variables and some
> type casts. No functional or anything changes. Manually performed.
>
>
>
Still need help on this:
Now it failed to link in the end:
$ make
[ 29%] Built target bitmaps
[ 29%] Built target page_layout_lexer_source_files
[ 29%] Built target boost
[ 29%] Built target lib-dependencies
[ 29%] Generating version string header
-- Using Bazaar to determine build version
You installed the i686 toolchain, not the x86_64 toolchain which is
required for 64 bit builds as well as the appropriate x86_64 libraries.
You told cmake to point to /mingw64 which is the 64 bit mingw path.
Did you run the correct bat file for 64 bit builds? If you are trying
to build a 64 bit
Hello
I'm just a lurker and still not started to contribute, but I have some
ideas:
- Indian Institute of Technology Bombay: I see technological and
educational institutions as potential contributors at this stage of
development. Indian Institute of Technology Bombay developed the Oscad
package
1. Fixed copy paste error in append_board_to_current.cpp ruining a if
else condition, should fix a possible bounding box computation bug
2. Whole bunch of pointless casts removed
3. Unused variables removed
4. Fix bug caused by JP on April 25, 2015 where strings were adjusted
for translation and
I'm OK with this. I don't know if we even have any commercial boards on
our made with KiCad page. I'm really not trying to stir up controversy
here. I merely want to protect the best interests of the project.
Wayne
On 11/3/2015 9:36 AM, Adam Wolf wrote:
> It might be easier to agree on a
AFAIK, kicadwinbuilder is no longer being maintained. The preferred
method for building kicad on windows is to us the new msys2/mingw32/64
environment. See
http://ci.kicad-pcb.org/job/kicad-doxygen/ws/Documentation/doxygen/html/md_Documentation_development_compiling.html#build_windows.
Please
?
This one is maintained:
https://github.com/nickoe/KiCad-Winbuilder
That automates the whole process with msys2. The PKGBUILD is probably
better than what msys2 has in its own system because we actually
package libxslt! and disable the gcc 5.1,5.2 warning spam bug.
On Tue, Nov 3, 2015 at 8:36
It might be easier to agree on a policy for projects where they provide
KiCad design files, and figure out the policy for ones where they don't
later.
Cut the problem in half, and tackle the easy one :)
Adam Wolf
Cofounder and Engineer
Wayne and Layne
On Tue, Nov 3, 2015 at 8:26 AM, Wayne
On 11/3/2015 5:34 AM, Tomasz Wlostowski wrote:
> On 03.11.2015 20:13, Javier Serrano wrote:
>> On Tue, Nov 3, 2015 at 12:39 AM, Wayne Stambaugh
>> wrote:
>>> Yes. The P router still has a serious segfault issue. I've talked to
>>> Tom about it and he is working on it.
Yaps, Nick told me to try this new one. Sorry I was outdated :/
I will try latter...
From: Kicad-developers
[kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of
Wayne Stambaugh [stambau...@gmail.com]
Sent: 03 November 2015 13:36
To:
Hi Lachlan,
I seem to remember that kicad-install.sh will not be maintained as part of
KiCad going forward--perhaps you're a great future maintainer :)
Docs are now in https://github.com/KiCad/kicad-doc.
Adam Wolf
On Tue, Nov 3, 2015 at 4:03 AM, Lachlan Audas wrote:
> Hi,
Adam is correct. This script has been way more trouble than it's worth
so I'm not interested in maintaining it. Feel free to use it at your
own risk.
The legacy doc repo has been renamed to
https://code.launchpad.net/~stambaughw/kicad/doc-read-only. That's why
the doc build is failing. This
Le 03/11/2015 15:02, Mark Roszko a écrit :
> ?
> This one is maintained:
> https://github.com/nickoe/KiCad-Winbuilder
>
> That automates the whole process with msys2. The PKGBUILD is probably
> better than what msys2 has in its own system because we actually
> package libxslt! and disable the gcc
On 11/3/2015 5:09 AM, Javier Serrano wrote:
> On Mon, Nov 2, 2015 at 8:53 PM, Wayne Stambaugh wrote:
>> I know it's noisy but I want developer input on this as well as website
>> developer input. I think the developers have a right to know how their
>> work is being used
On 03.11.2015 20:13, Javier Serrano wrote:
> On Tue, Nov 3, 2015 at 12:39 AM, Wayne Stambaugh wrote:
>> Yes. The P router still has a serious segfault issue. I've talked to
>> Tom about it and he is working on it. As soon as the fixes are
>> committed, I will be rolling
Hi all,
I cannot comment much about the policies and decisions. I believe they are a
delicate subject.
But as a contributor and "word spread" of kicad, I like to know and see my work
being used. That is the only way I feel I received my "payment".
I will be happy to know about open license
While we're at this, Olimex is working on a nice board using KiCad:
https://olimex.wordpress.com/2015/10/16/we-work-on-a64-olinuxino-the-first-open-source-hardware-64-bit-development-board/
https://olimex.wordpress.com/2015/10/23/a64-olinuxino-update/
Which allows me to repeat my mantra :) The
On 11/3/2015 10:47 AM, Mark Roszko wrote:
> So it turns out all the demo files in KiCad are also affected by the
> translated layer name mess.
Huh? I just checked. All of the kicad demo boards open just fine for me.
Remember, copper layers can be translated because they have fixed
ordinal
Actually I just noticed I had a old kicad vs new kicad conflict on
this machine. So my bad on that.
But the nicer error message point still a concern as I've seen other
users asking about it recently. I am just not sure the best way to
word the message/dictate.
On Tue, Nov 3, 2015 at 11:37 AM,
41 matches
Mail list logo