Wow, good good Marco!,
Having our own python build looks interesting to overcome the OSX
version problems with python.
The bad point of having our own python is that we stop from having the
python community libraries
(I guess) probably it's a matter of including easy_python or pip in the
bu
Well, two interesting things here:
1) the git-bzr-ng looks great, we can add some documentation to the website
based on what inkscape provides.
This should make people more used to git happier, and we have an easy
migration path if something
goes wrong with launchpad or bzr (I don't fores
- Original Message -
> From: Wayne Stambaugh
> To: kicad-developers@lists.launchpad.net
> Cc:
> Sent: Wednesday, February 5, 2014 11:04 AM
> Subject: Re: [Kicad-developers] Revisiting the Git decision
>
> On 2/4/2014 9:57 AM, Tomasz Wlostowski wrote:
>> On 02/04/2014 12:57 PM, Brian Si
Hi,
My notebook has a keyboard that doesn't have a 'Delete' key, only
'Backspace'. This makes deleting objects in eeschema quite cumbersome as
this always requires to use the right-mouse button menu.
Since 'Backspace' is not bound to anything in eeschema, this patch adds the
Backspace key to be eq
On 4 February 2014 18:36, Blair Bonnett wrote:
>
> On 5 February 2014 15:03, Henner Zeller wrote:
>>
>> ...snip...
>>
>> This sounds excellent. I think I am going to base my pending work on
>> your mirror until the official kicad-source-mirror is fixed to be
>> up-to-date.
>>
>> We need to make s
On 5 February 2014 15:03, Henner Zeller wrote:
> ...snip...
>
> This sounds excellent. I think I am going to base my pending work on
> your mirror until the official kicad-source-mirror is fixed to be
> up-to-date.
>
> We need to make sure though that the reverse path back into the KiCad
> source
On 4 February 2014 10:07, Blair Bonnett wrote:
> On 5 February 2014 03:07, Brian Sidebotham
> wrote:
>>
>>
>> ...snip...
>>
>>
>> I sent the other link very much on purpose, as on that page, a few
>> paragraphs in is a link to this page:
>> http://www.inkscape.org/en/develop/using-git-repositorie
On 2/4/2014 9:57 AM, Tomasz Wlostowski wrote:
> On 02/04/2014 12:57 PM, Brian Sidebotham wrote:
>> I suspect it's all just a documentation issue too as someone else
>> suggested because it's so easy to branch the code and generate a patch
>> using Bazaar.
>>
>> Perhaps the best place for anyone who
Sorry, I forgot to reply to all
Miguel,
As you can see i've committed the part to make possibile the linking of Kicad
also with dynamic linking and making binaries portable
(scripts/osx_fixbundle.sh )
I'm in those days working on wxPython, i'm confident to release a similar
mechanism for Python
There is a script in the source tree that does something like this. I
think Dick wrote it.
Adam Wolf
W&L
On Tue, Feb 4, 2014 at 4:02 PM, Maciej Sumiński wrote:
> I guess you could run uncrustify and do a diff, but unfortunately you
> cannot apply uncrustify blindly - sometimes its output seems
I guess you could run uncrustify and do a diff, but unfortunately you
cannot apply uncrustify blindly - sometimes its output seems a bit odd.
One possible solution is to check how many lines were corrected by
uncrustify, if above a set threshold (relatively to the whole patch
length) - send an
- Original Message -
> From: Joel Holdsworth
> To: kicad-developers@lists.launchpad.net
> Cc:
> Sent: Wednesday, February 5, 2014 12:04 AM
> Subject: Re: [Kicad-developers] Revisiting the Git decision
>
> Hi All,
>
> Thank you all for taking the time to respond to my original e-mail
I have a Mac running 10.6, and a pretty powerful build server running OSX
10.9 with Windows and Linux VMs for this. They were purchased by Wayne and
Layne pretty much exclusively for this purpose.
The 10.6 is one of the best ways to create a single Mac package that works
on 10.6-current on all sy
Hmmm,
Do we have something to check coding style compliance?
Not sure if uncrustify does code checking along with reformating if we
had that
we could automatically check submitted code for style compliance.
---
irc: ajo / mangelajo
Miguel Angel Ajo Pelayo
+34 636 52 25 69
skype: ajoajoajo
>
> From: Fabrizio Tappero
>To: James Hagerman
>Cc: "kicad-developers@lists.launchpad.net"
>
>Sent: Tuesday, February 4, 2014 8:32 PM
>Subject: Re: [Kicad-developers] Revisiting the Git decision (I come in peace!
>- with a patch)
>
>
>
>Hi James,
>thanks for y
Dear Joel,
thank you for your messages,
"The KiCad website and KiCad Launchpad page are full of broken or
misleading links to old, outdated, or conflicting information.
Binaries (and libraries) for all platforms are not readily available
on either site."
Could you please point out those many bro
> There is another option for people who want to use Git: a mirror. There is a
> mirror under the KiCad user account (the one with all the libraries) on
> GitHub:
>
> https://github.com/KiCad/kicad-source-mirror
>
> However, it usually seems to be out of date, and very sporadically updated.
> For s
On 5 February 2014 03:07, Brian Sidebotham wrote:
>
> ...snip...
>
> I sent the other link very much on purpose, as on that page, a few
> paragraphs in is a link to this page:
> http://www.inkscape.org/en/develop/using-git-repositories/
>
> in other words, fill your boots, work with Git on the KiC
> After reading Adam's last email, I think that a complete binary
archive/installer for all platforms would make sense (including our own
boost/wx libs, just like LibreOffice/Mozilla). Just unpack or run the
installer and enjoy!
Also, being able to update from inside the program itself is a really
On Tue, Feb 04, 2014 at 03:57:40PM +0100, Tomasz Wlostowski wrote:
> $du -h ./kicad-feat1
> 203M
Wait until you compile :P
3,1Gkicad-bzr
Also unstripped binaries are a little scary:
-rwxr-xr-x 1 lomarcan lomarcan 114433370 feb 3 19:39 pcbnew
(yes, ld time is painful). No i7 here, just a D
On 02/04/2014 12:57 PM, Brian Sidebotham wrote:
I suspect it's all just a documentation issue too as someone else
suggested because it's so easy to branch the code and generate a patch
using Bazaar.
Perhaps the best place for anyone who has decided Bazaar is dead (it
works for me by the way!) an
On 04/02/14 14:21, Adam Wolf wrote:
> I'd like to make a quick point: producing a package for Kicad
> that works on all the Ubuntu flavors, works in both Python
> integration modes, *and* follows Ubuntu packaging policy is not a
> simple task. I'm about 100 hours into it, maybe more, and while
>
This should be a wiki page, and the more time consuming steps should be a
wiki pave as well. How amazing (and helpful) would that be?
On Feb 4, 2014 3:57 AM, "Brian Sidebotham"
wrote:
> I suspect it's all just a documentation issue too as someone else
> suggested because it's so easy to branch th
I'd like to make a quick point: producing a package for Kicad that works
on all the Ubuntu flavors, works in both Python integration modes, *and*
follows Ubuntu packaging policy is not a simple task. I'm about 100 hours
into it, maybe more, and while I'm just about finished, there is still
plenty
On 4 February 2014 13:04, Joel Holdsworth wrote:
> Hi All,
>
> Thank you all for taking the time to respond to my original e-mail. It
> seems to me that whatever the outcome this discussion it is well worth
> having.
>
>
> On 04/02/14 11:57, Brian Sidebotham wrote:
>> I suspect it's all just a doc
Hi All,
Thank you all for taking the time to respond to my original e-mail. It
seems to me that whatever the outcome this discussion it is well worth
having.
On 04/02/14 11:57, Brian Sidebotham wrote:
> I suspect it's all just a documentation issue too as someone else
> suggested because it's s
On 4 February 2014 09:10, Simon Turner wrote:
> The process is probably single core anyway, my machine sat practically idle.
>
> Simon
Unfortunately until some source files have been created by CMake,
KiCad-Winbuilder cannot run parallel jobs because the generated source
files get corrupted. So t
I suspect it's all just a documentation issue too as someone else
suggested because it's so easy to branch the code and generate a patch
using Bazaar.
Perhaps the best place for anyone who has decided Bazaar is dead (it
works for me by the way!) and therefore cannot contribute (and
particularly gi
On Tue, Feb 04, 2014 at 03:08:49AM -0800, Rick Walker wrote:
> Then, just use the magic of merge to sync the work between both systems
> from time to time.
>
> So, just fork it and stay in touch.
Isn't painful to keep in sync the merge infos between git and bzr... or
is there an automated 'bridg
Hey Guys,
The answer seems simple. The point of both VCSs is to make
merges easy.
So just break into two different teams.
A friendly code-fork.
One group works in git and another in Bazaar. New people would have to
choose the group to join based on 1) what things they wanted to work on
an
Hi James,
thanks for your message.
Could you please point me to the (say 5) most serious problems that the
official kicad website has. I might have some time/ability to fix it.
thanks
Fab.
On Tue, Feb 4, 2014 at 3:00 AM, James Hagerman wrote:
> Hi there,
>
> I've been lurking and haven't gotte
The process is probably single core anyway, my machine sat practically idle.
Simon
On 03/02/2014 21:13, Brian Sidebotham wrote:
On 3 February 2014 18:38, Milan Horák wrote:
Hi,
and I am compiling KiCad on VirtualBox Windows XP machine, limited to one
core of Phenom 955 and 512MB RAM :-)
Mil
Dear KiCad friends,
Here's a quick update on what we have been up to at CERN lately, and
also some words on plans for the immediate future, along with opinions
on some of the latest subjects discussed in the list:
Current developments: Orson is working on porting pcbnew tools to the
new tool fram
33 matches
Mail list logo
