Re: [Kicad-developers] [PATCH] Rename instances of "module" to "footprint" for consistency

[Benoît Roehr]

On 30/10/2014 13:13, Wayne Stambaugh wrote:

On 10/30/2014 6:54 AM, Benoît Roehr wrote:

On 30/10/2014 08:50, Marco Ciampa wrote:

On Thu, Oct 30, 2014 at 01:22:34AM +0100, Benoît Roehr wrote:

Beware here, they are not footprint anymore when they are on the
board, have a value, a reference and so on... They are components.

Footprint is the right term for the standalone "print" a component
will drop on a PCB. You can name them so in the footprint library,
in the component propriety and so on... In the PCB editor, this
object is a Components and should be named so.

Ok, clear, thank you very much for the explanation.

So we have:

a symbol = a generic graphic for schematic
a component  = a graphic with a meaning (value, reference, etc.) for
schematic
a footprint  = a generic graphic for pcb
a module = a graphic with a meaning (value, reference, etc.) for pcb

In the case the object is part of an assembly (have a designator, value,
reference, footprint...) I would name it Component, not module.

I think calling "Component" both the schematic parts and the pcb parts
is the right way to go.

No.  Do not use components for both PCBs and schematics.  It will only
make things more confusing.
The fact is that, I strongly believe there is no difference between a 
Component in the Schematic and a Component in the PCB. They are the same 
thing and should be named equally.


For example:
If U1 is a component on the PCB, it have a symbol and a footprint. In 
eeschema it is represented by its symbol, in pcbnew it is represented by 
its footprint. But the object behind the symbol or footprint 
representation is still U1, and U1 is a Component !


Footprint = PCB features upon which a component is mounted

Indeed :)


Component = Schematic symbol with value, reference, etc.

Personally I prefer symbol instead of component but for historical
reasons, changing it will most likely confuse users so I would rather
keep it component unless there is a huge outcry from users.  Given that
it hasn't happened, it's not likely to happen.

Keep it simple.  My main concern is consistency.

Well, about consistency:

Let's say I have a method returning a list of objects in the PCB.

A list of footprint would be:
- SOT-23, SOT-23, SOT-23...
- SOIC-8, SOIC-8, SOIC-8...
- ...

Or a list of footprint would be
- Q1, Q2, Q3... (all SOT-23)
- U1, U2, U3... (all SOIC-8)
- ...

???
The second list is a list of component. Those are two distinct things 
that could not be both called footprint. It is context dependant.



I answered to the patch because I made the assumption that this part of 
the code:


 RR( _( "Values" ),  MOD_VALUES_VISIBLE, UNSPECIFIED_COLOR,  _( 
"Show footprint's values") ),
 RR( _( "References" ),  MOD_REFERENCES_VISIBLE, UNSPECIFIED_COLOR,  _( 
"Show footprint's references") ),

refers to components implanted on board. If it is only related to the 
footprints drawing, then footprint suits.


But ! If 'values' refer to the value of a component (10k resistance for 
example), and/or if reference could be something like 'ATmega32U4', then 
it should say 'Show component's value'. It is consistant because you 
call all the devices that will be implanted on the PCB -> Component, and 
this naming convention starts in eeschema. Calling them footprint here 
is not consistant in this context.


Please think about it.



a symbol = a generic graphic for schematic
a footprint  = a generic graphic for pcb
a component  = a graphic with a meaning (value, reference, etc.) for
schematic and PCB


right?



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Rename instances of "module" to "footprint" for consistency

[Benoît Roehr]

On 30/10/2014 08:50, Marco Ciampa wrote:

On Thu, Oct 30, 2014 at 01:22:34AM +0100, Benoît Roehr wrote:

Beware here, they are not footprint anymore when they are on the
board, have a value, a reference and so on... They are components.

Footprint is the right term for the standalone "print" a component
will drop on a PCB. You can name them so in the footprint library,
in the component propriety and so on... In the PCB editor, this
object is a Components and should be named so.

Ok, clear, thank you very much for the explanation.

So we have:

a symbol = a generic graphic for schematic
a component  = a graphic with a meaning (value, reference, etc.) for schematic
a footprint  = a generic graphic for pcb
a module = a graphic with a meaning (value, reference, etc.) for pcb
In the case the object is part of an assembly (have a designator, value, 
reference, footprint...) I would name it Component, not module.


I think calling "Component" both the schematic parts and the pcb parts 
is the right way to go.


a symbol = a generic graphic for schematic
a footprint  = a generic graphic for pcb
a component  = a graphic with a meaning (value, reference, etc.) for schematic 
and PCB


right?




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Rename instances of "module" to "footprint" for consistency

[Benoît Roehr]

On 29/10/2014 23:56, Marco Ciampa wrote:

Another patch:

=== modified file 'pcbnew/class_pcb_layer_widget.cpp'
--- pcbnew/class_pcb_layer_widget.cpp   2014-09-14 15:34:37 +
+++ pcbnew/class_pcb_layer_widget.cpp   2014-10-29 22:52:43 +
@@ -73,8 +73,8 @@
  RR( _( "Anchors" ), ANCHOR_VISIBLE, WHITE,  _( "Show 
footprint and text origins as a cross" ) ),
  RR( _( "Grid" ),GRID_VISIBLE,   WHITE,  _( "Show the 
(x,y) grid dots" ) ),
  RR( _( "No-Connects" ), NO_CONNECTS_VISIBLE,UNSPECIFIED_COLOR,  _( 
"Show a marker on pads which have no net connected" ) ),
-RR( _( "Modules Front" ),   MOD_FR_VISIBLE, UNSPECIFIED_COLOR,  _( 
"Show footprints that are on board's front") ),
-RR( _( "Modules Back" ),MOD_BK_VISIBLE, UNSPECIFIED_COLOR,  _( 
"Show footprints that are on board's back") ),
+RR( _( "Footprints Front" ),   MOD_FR_VISIBLE, UNSPECIFIED_COLOR,  _( 
"Show footprints that are on board's front") ),
+RR( _( "Footprints Back" ),MOD_BK_VISIBLE, UNSPECIFIED_COLOR,  _( 
"Show footprints that are on board's back") ),
  RR( _( "Values" ),  MOD_VALUES_VISIBLE, UNSPECIFIED_COLOR,  _( 
"Show footprint's values") ),
  RR( _( "References" ),  MOD_REFERENCES_VISIBLE, UNSPECIFIED_COLOR,  _( 
"Show footprint's references") ),
  };
Beware here, they are not footprint anymore when they are on the board, 
have a value, a reference and so on... They are components.


Footprint is the right term for the standalone "print" a component will 
drop on a PCB. You can name them so in the footprint library, in the 
component propriety and so on... In the PCB editor, this object is a 
Components and should be named so.




=== modified file 'pcbnew/menubar_modedit.cpp'
--- pcbnew/menubar_modedit.cpp  2014-10-15 11:40:38 +
+++ pcbnew/menubar_modedit.cpp  2014-10-29 22:52:56 +
@@ -273,7 +273,7 @@
  // Anchor
  AddMenuItem( placeMenu, ID_MODEDIT_ANCHOR_TOOL,
   _( "A&nchor" ),
- _( "Place footprint module reference anchor" ),
+ _( "Place footprint reference anchor" ),
   KiBitmap( anchor_xpm ) );
  
  // Menu Help:


=== modified file 'pcbnew/muonde.cpp'
--- pcbnew/muonde.cpp   2014-08-24 07:05:07 +
+++ pcbnew/muonde.cpp   2014-10-29 22:52:53 +
@@ -1075,7 +1075,7 @@
  
  if( pad == NULL )

  {
-DisplayError( this, _( "No pad for this module" ) );
+DisplayError( this, _( "No pad for this footprint" ) );
  return;
  }
  
@@ -1083,7 +1083,7 @@
  
  if( next_pad == NULL )

  {
-DisplayError( this, _( "Only one pad for this module" ) );
+DisplayError( this, _( "Only one pad for this footprint" ) );
  return;
  }
  




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Incremental build speeds.

[Benoît Roehr]

On 22/10/2014 15:33, Brian Sidebotham wrote:

On 22 October 2014 14:16, Benoît Roehr  wrote:

It takes about 20 seconds for me.

Ubuntu 14.04
i7 @ 2.2GHz

I've read somewhere linux is better for compiling because of something
called pipelining. It is present on linux (or better implemented) but not on
windows.


The compilers turn source code into pre-processed source code, then
into assembler which is then assembled to get the object code. This
used to use a temporary file at each intermediary stage, however these
days I'm sure the -pipe option is enabled on all platforms for gcc and
uses pipes instead of temporary files.

So I don't think that's any longer a difference between Windows and Linux.

Okay thanks for the info ;)


Best Regards,

Brian.



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Incremental build speeds.

[Benoît Roehr]

On 22/10/2014 15:16, Lorenzo Marcantonio wrote:

On Wed, Oct 22, 2014 at 02:01:44PM +0100, Tim Hutt wrote:

Hi,

I'm trying to do some kicad development on windows. I initially downloaded
& built it with kicad-winbuilder which went without a hitch. Kicad runs
fine.

However, if I perform a null-rebuild (i.e. I don't change anything and just
run `make` again), it takes about 70 seconds to run. That's quite a while
isn't it? My PC is pretty fast (quad core 3.3 GHz i5, 16GB RAM), so I
wouldn't have expected it to take so long. Is this just a feature of cmake?

It needs to check *a lot* of dependencies and timestamps; also each
submakefile has its own overhead.

Probably cmake is slightly slower than automake, but IMHO not really
significant on a typical build. In fact even with distcc, I find linking
the heaviest step... consider this output for a full debug build:

-rwxr-xr-x 1 lomarcan lomarcan 268684355 ott  4 15:51 _pcbnew.kiface

Yes, it's more than 256MB of stuff :D it takes a while to do that (if
only to read and write from disk).
Yes, and also, some antiviruses are filtering access to disk, which 
takes a bit of time each time a file is accessed. I remember very slow 
build for Arduino (30-40 seconds) in Win7 when using Commodo Firewall.





___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Incremental build speeds.

[Benoît Roehr]

It takes about 20 seconds for me.

Ubuntu 14.04
i7 @ 2.2GHz

I've read somewhere linux is better for compiling because of something 
called pipelining. It is present on linux (or better implemented) but 
not on windows.


On 22/10/2014 15:01, Tim Hutt wrote:

Hi,

I'm trying to do some kicad development on windows. I initially 
downloaded & built it with kicad-winbuilder which went without a 
hitch. Kicad runs fine.


However, if I perform a null-rebuild (i.e. I don't change anything and 
just run `make` again), it takes about 70 seconds to run. That's quite 
a while isn't it? My PC is pretty fast (quad core 3.3 GHz i5, 16GB 
RAM), so I wouldn't have expected it to take so long. Is this just a 
feature of cmake?


Build output is below. How long does it take for you guys? Am I doing 
something wrong?


Cheers,

Tim

-

C:\Users\Tim\Local\kicad-winbuilder-3.4\build\Release>mingw32-make
[  0%] Built target boost
[ 30%] Built target bitmaps
[ 30%] Built target lib-dependencies
[ 38%] Built target common
[ 38%] Generating headers containing GLSL source code
Headers are up-to-date
[ 38%] Built target shader_headers
[ 39%] Built target gal
[ 43%] Built target pcbcommon
[ 44%] Built target 3d-viewer
[ 44%] Built target polygon
[ 45%] Built target pcad2kicadpcb
[ 46%] Built target openssl
[ 46%] Built target avhttp
[ 46%] Built target github_plugin
[ 47%] Built target cvpcb_kiface
[ 47%] Built target cvpcb
[ 57%] Built target eeschema_kiface
[ 58%] Built target eeschema
[ 61%] Built target gerbview_kiface
[ 61%] Built target gerbview
[ 61%] Built target lib_dxf
[ 62%] Built target idf3
[ 64%] Built target pnsrouter
[ 79%] Built target _pcbnew
[ 79%] Fixing swig_import_helper in Kicad scripting modules
swig_import_helper fixed for 
C:/Users/Tim/Local/kicad-winbuilder-3.4/build/Relea

se/pcbnew/pcbnew.py
[ 79%] Built target FixSwigImportsModuleScripting
[ 94%] Built target pcbnew_kiface
[ 94%] Built target pcbnew
[ 95%] Built target pl_editor_kiface
[ 95%] Built target pl_editor
[ 96%] Built target potrace
[ 96%] Built target bitmap2component
[ 98%] Built target pcb_calculator_kiface
[ 98%] Built target pcb_calculator
[100%] Built target kicad
[100%] Built target dxf2idf
[100%] Built target idf2vrml
[100%] Built target idfcyl
[100%] Built target idfrect



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] KiCad and CLion

[Benoît Roehr]

On 20/10/2014 16:48, Adam Wolf wrote:

Hi folks,

Has anyone gotten KiCad to work with CLion?  It's a new C++ IDE by the 
Jetbrains folks.
I took a look at CLion this afternoon. I didn't tried it but it looks 
very very promising.


I spent a few minutes this weekend, but I couldn't get it to find some 
libraries.


Adam Wolf
Cofounder and Engineer
W&L


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Stable release version numbers.

[Benoît Roehr]

On 20/10/2014 18:53, Wayne Stambaugh wrote:

On 10/20/2014 12:38 PM, Nick Østergaard wrote:

2014-10-20 18:07 GMT+02:00 Benoît Roehr :

Not a dev, but my 2 femto cents:

I really like the #major.#minor.#dev - #buildNo scheme, but I would add
these details about the version incrementation:

A lot of info in there, read on.


2.0
New release, majors changes over the 1.9.

2.1.0
Stable release with new features and bug fixes over 2.0.0.

I am still not really sure what the last should be used to, accoring
to Wayne's original suggestion. (maybe I misread something somewhere)


2.1.25
Development version, unstable/beta releases for edgers and tests. #dev is
calulated with build number. If v2.1.0 was build 6120, v2.1.25 may be build
6145. (6145 - 6120 = 25)

Interresting concept of including the difference in revisions since
last release, but I think this is useless, because the project is not
big enough IMHO to support this convoluted release process. I would
rather replace it with the product branch revision from where the
snapshot/release was taken from. This could aslo work even with git
where it would be something like 2.1.01315b4, or just 2.1.5231 with
bazaar.


If 2.1.25 is tested and stable, then it is renamed 2.2.0 and released.
Reference buildNo is now 6145 (avoid code regression).

I really think that this beta testing you call it, is really not
existant as seperate minor-minor releases. The daily builds are
responsible for this.


Edgers using beta before release would see v2.1 in windows description, and
2.1.25 - 6145 in "about".
After release, users would see v2.2, and v2.2.0 - 6145 in "about".

Will also work with my proposed scheme.


That's just an idea But I don't know how doable it is...?

I think the diff thing is overcomplicating things.

I want to keep things as simple as possible.  The numerical triplet
version numbering would only be used for stable releases.  We should
continue to use bzr commit number as the version for daily builds since
they will always be built from the head of the product branch so there
should be no confusion.

I think I agree with this.

I would probably use the triplet instead using
major.minor just in case at some point in the future we decide to
support minor version incremental releases.  Since we have plenty of
time to think about this, there is no need to make a decision right now.
  It's just something to think about.


I am not really in favour of the time bound version, such as the
proposed matlab or altium like versioning scheme.


On 20/10/2014 17:27, Tomasz Wlostowski wrote:

On 20.10.2014 17:25, Marco Ciampa wrote:

On Mon, Oct 20, 2014 at 08:47:54AM -0400, Carl Poirier wrote:

I feel like we wouldn't use the last digit much in a triplet number
because, IIRC, backporting of fixes is not planned. That being said, I
would also begin with at least 2.1, as Cirilo said.

However, I personally vote for numbering the versions a la MATLAB.


I am not a dev, I know, so my 0.002 cents on N.N numbering starting from
2.0
or 2.1 ...


How about an Ubuntu-ish scheme with year/month? e.g. 2015.01?

My 10e-6 cents...

Cheers,
Tom


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Stable release version numbers.

[Benoît Roehr]

Not a dev, but my 2 femto cents:

I really like the #major.#minor.#dev - #buildNo scheme, but I would add 
these details about the version incrementation:


2.0
New release, majors changes over the 1.9.

2.1.0
Stable release with new features and bug fixes over 2.0.0.

2.1.25
Development version, unstable/beta releases for edgers and tests. #dev 
is calulated with build number. If v2.1.0 was build 6120, v2.1.25 may be 
build 6145. (6145 - 6120 = 25)


If 2.1.25 is tested and stable, then it is renamed 2.2.0 and released. 
Reference buildNo is now 6145 (avoid code regression).


Edgers using beta before release would see v2.1 in windows description, 
and 2.1.25 - 6145 in "about".

After release, users would see v2.2, and v2.2.0 - 6145 in "about".

That's just an idea But I don't know how doable it is...?


On 20/10/2014 17:27, Tomasz Wlostowski wrote:

On 20.10.2014 17:25, Marco Ciampa wrote:

On Mon, Oct 20, 2014 at 08:47:54AM -0400, Carl Poirier wrote:

I feel like we wouldn't use the last digit much in a triplet number
because, IIRC, backporting of fixes is not planned. That being said, I
would also begin with at least 2.1, as Cirilo said.

However, I personally vote for numbering the versions a la MATLAB.


I am not a dev, I know, so my 0.002 cents on N.N numbering starting 
from 2.0

or 2.1 ...


How about an Ubuntu-ish scheme with year/month? e.g. 2015.01?

My 10e-6 cents...

Cheers,
Tom


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Stable release version numbers.

[Benoît Roehr]

For the love of G-d, whatever you do, don't adopt that Altium "Season" 
scheme ... Summer 2011 and what-not. Is Winter 2011 earlier or later 
than Winter 2010? What hemisphere are you in? I'm perfectly fine with 
the dotted-triplet thing, Major.minor.more-minor -a 
Yes, and also these make you fell very dumb. You are on Winter 04 when 
Summer 14 is already released? Come on BUY BUY BUY !!!



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] kicad-install.sh requiring python-wxgtk3.0

[Benoît Roehr]

Hi Adam,

I'm now on a Ubuntu 14.04 daily. Just tell me what to test exactly and
how... But there is chance I'll build Kicad today so dependencies may be
installed on this machine today.

Also: wx3.0 is available in the official repositories now (I use synaptic)

2014-10-18 15:20 GMT+02:00 Adam Wolf :

> *sigh*
>
> I have begun the backports process.
> https://wiki.ubuntu.com/UbuntuBackports
>
> What this means is that I am creating a PPA of packages that are needed
> for KiCad and are already in 14.10 (utopic), but rejiggering the packages
> so they're meant for 14.04 (trusty).
>
> If I can find a few savvy volunteers here who use their 14.04 machines
> regularly and also want to test this for me, I can propose it be included
> in official backports.
>
> Hopefully this goes as smoothly as getting wxWidgets 3.0 working on this
> week's OS X release.  (Sometimes I feel we spend more time working on our
> dependencies than on KiCad!)
>
> Adam Wolf
> Cofounder and Engineer
> Wayne and Layne, LLC
>
> On Sat, Oct 18, 2014 at 5:21 AM, Jake  wrote:
>
>> i did try this and it said it couldn't satisfy the dependancies..
>>
>>
>> On Sat, 18 Oct 2014, Nick Østergaard wrote:
>>
>>  So did you ever try what Moses suggested?
>>>
>>> https://lists.launchpad.net/kicad-developers/msg15067.html
>>>
>>> 2014-10-18 10:30 GMT+02:00 Jake :
>>>
 so i'm trying to install kicad on a fresh install of Ubuntu 14.04,
 which is
 this years' long-term support version of Ubuntu.

 it should be easy right?

 but immediately, the kicad-install.sh script says
 E: Unable to locate package python-wxgtk3.0
 E: Couldn't find any package by regex 'python-wxgtk3.0'

 i looked into it and i see that python-wxgtk3.0 is only available for
 bleeding-edge installs of Ubuntu 14.10 which only just now came out.

 this is very frustrating and basically means that anyone not running
 literally the latest system software can't install kicad.  Is this
 really
 necessary?  I have python-wxgtk2.8 available to me, is that not
 sufficient?

 I am not an expert with aptitude and sources, and i have no idea how to
 get
 python-wxgtk3.0 onto my system, so i just installed python-wxgtk2.8
 and i took out that line from kicad-install.sh and i'm trying again.

 but if possible, i think it would be ideal if this requirement were
 taken
 out.  I can't in good conscience keep telling people that they should
 switch
 to kicad if i can't even figure out how to install it myself.

 apologies if i'm missing something basic, or if my tone is frustrated.

 thank you,
 -jake

 ___
 Mailing list: https://launchpad.net/~kicad-developers
 Post to : kicad-developers@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~kicad-developers
 More help   : https://help.launchpad.net/ListHelp

>>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Possible 4.6 gerber issue?

[Benoît Roehr]

Le 16/10/2014 11:28, A. V. Dolganoff a écrit :
(not helping the discussion in any way): I find the result rather 
cool! Those circles look like it was intended, the "design" reflects 
well the RFID idea.

Lol, I was thinking the same :). Coolest bug ever ! Don't fix it please :D


On Thu, Oct 16, 2014 at 11:23 AM, Nick Østergaard <mailto:oe.n...@gmail.com>> wrote:


My image showing the origin of the circles clearly shows they are form
this board only. Aslo hackvana showed images from some other boards,
the rendering only showed one board.

Nick

2014-10-16 11:17 GMT+02:00 Benoît Roehr mailto:benoit.roehr...@gmail.com>>:
> Is this manufacturer panelizing artworks of different client ?
> If the technician in charge of the data processing forgot to
clip the
> silkscreen by project, it is possible that what you have on you
board are in
> fact circles from another client board.
>
> Le 16/10/2014 08:40, Nick Østergaard a écrit :
>
> I believe that a pcb with just a grapic circle works, but not
sure about
> that. It could be that all circles that is not pads work. You
might try to
> add some more of theese objects to the pcb.
>
> Den 16/10/2014 08.36 skrev "Mitch Davis"
mailto:mjd%2blaunchpad@afork.com>>:
>>
>> Hi guys,
>>
>> On Thu, Oct 16, 2014 at 5:11 AM, Nick Østergaard
mailto:oe.n...@gmail.com>>
>> wrote:
>> >
>> > I have attached a minimal board that I think should show the bug.
>> > Mitch, can you please try to send that though your fabs viewer?
>>
>> I will.  Is it possible to supply one that we think does and
does not
>> have the problem?
>>
>> Mitch.
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> Post to : kicad-developers@lists.launchpad.net
<mailto:kicad-developers@lists.launchpad.net>
> Unsubscribe : https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> Post to : kicad-developers@lists.launchpad.net
<mailto:kicad-developers@lists.launchpad.net>
> Unsubscribe : https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
> More help   : https://help.launchpad.net/ListHelp
>

___
Mailing list: https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
Post to : kicad-developers@lists.launchpad.net
<mailto:kicad-developers@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~kicad-developers
<https://launchpad.net/%7Ekicad-developers>
More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Possible 4.6 gerber issue?

[Benoît Roehr]

Is this manufacturer panelizing artworks of different client ?
If the technician in charge of the data processing forgot to clip the 
silkscreen by project, it is possible that what you have on you board 
are in fact circles from another client board.


Le 16/10/2014 08:40, Nick Østergaard a écrit :


I believe that a pcb with just a grapic circle works, but not sure 
about that. It could be that all circles that is not pads work. You 
might try to add some more of theese objects to the pcb.


Den 16/10/2014 08.36 skrev "Mitch Davis" >:


Hi guys,

On Thu, Oct 16, 2014 at 5:11 AM, Nick Østergaard
mailto:oe.n...@gmail.com>> wrote:
>
> I have attached a minimal board that I think should show the bug.
> Mitch, can you please try to send that though your fabs viewer?

I will.  Is it possible to supply one that we think does and does not
have the problem?

Mitch.



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Library Editor naming consistency

[Benoît Roehr]

Le 15/10/2014 07:23, Mark Roszko a écrit :

I'm leaning towards one of the markdown formats myself.

I vote for markdown :D

Me too !!


In fact, here, I ran a quick convert of ODT to markdown and imported
it into a gitbook setup. Here's chapter 1 and 2 being served from
markdown and combined with Gitbook and then being served from a git
repo via nodejs.  Literally just a 5 minute hack job to demonstrate
how easy it is.

http://kicad.borkedlabs.com:4000/

This is beautiful, and I guess, as being .md, easy to maintain :)


which is running off this repo:
https://github.com/marekr/kicad-doc-test

Also the first time I actually read the *part* of the manual, but what
kind of crazy person does that? :P

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Library Editor naming consistency

[Benoît Roehr]

Le 13/10/2014 16:51, Carl Poirier a écrit :
Benoît, this is exactly what I tried to say. I wasn't talking about 
symbols in Altium, but about components.
They are already associated with footprints and so on, thus making 
them components.

They can be not associated and still used...

Here a view of the schematic editor, with the library panel open and a 
totally empty component selected.



Here is a view of the schematic library list in the schematic library 
editor. Notice all the fields:



The models linked can be a footprint, a simulation model, an ibis model 
and a signal integrity model. You can add several footprints for one 
component which is useful for N, M, L IPC densities and generic components.


The drawing that we are working on in the schematic library editor is 
a symbol.

This is where I don't agree.

You are indeed drawing a symbol, but mostly you will also set other 
proprieties making it a component. It doesn't need to have a footprint. 
For example, an ATMega128rfa1 is a component, not a symbol.
In the component properties, we can only put a filter on footprints 
for it, but AFAIK, that's about it.

So I'd say it still stands as a symbol.
If some more pairing is going to be done in this editor, such as a 
unique footprint, a SPICE model, and so on, then we might as well call 
the editor a component editor.
I totally agree with this. The name Component Editor is ambiguous in 
this context and shouldn't be used here at all, never. I see a 
/Component editor/ like an editing tool for both the schematic component 
and the footprint in the same time, and store the resulting footprint 
privately attached to the component to avoid corrupting the other 
component using the same base footprint.


I think the editor should be called /Schematic Library Editor/, to 
explicitly say that what you edit is for eeschema. The footprint editor 
should be called /PCB Library Editor/ to keep consistancy. In fact those 
are the name altium folks choosed.



But what if it's used to create only a symbol?
I will take this example: PCB Libraries can contain things that are not 
footprint (fiducials, holes...). But footprints are not called PCB Features.


[off topic]
Also, Eeschema should have a method for adding logos or other stuffs (I 
think it has), and these elements shouldn't be added in a schematic the 
same way a component is added. You may not store these graphical items 
in a schlib. You don't want the logo of you company to appears in BOM 
component list, you just want it in your printings.


Also, and this is important: you may put in the schema every objects 
that will become physical or logical parts of the project (the pcb, the 
box, screws, cables...). Some electronic engineer even put the firmware 
version in the schematic which is very smart and would have saved me a 
lot of time if I knew that when I started. I even burned down a mcu 
because of wrong version. Now, you want to upload some code but don't 
remember what is what, well IT'S IN THE BOM, YAY :D.

This is good design practice.
Components that aren't implantable (screws, box, fiducials) are marked 
NI in the BOM (not implantable) for the PCB assemblers to know it's not 
their business.

[/off topic]

Furthermore, how would the symbol and component libraries be 
differentiated, once some more serious associations are done? Will 
they all be mixed together? I think that's also part of the problem.
I don't know what is planned about this, but I would strongly support a 
2 libraries system based on what already exists, with an All-in-one 
schematic library containing the abstracts schematics datas of a 
component (symbol, simulation model, link to footprint) along with a 
All-In-One PCB library containing the real world PCB datas (footprint, 
3d model). A component like a screw for example is very easily used in 
the whole project. A third library would be useful to make footprints 
private and pre linked to a schematic component, but it's a pain in the 
ass using and managing them (Altium daunting system). I don't recommend 
it, there should be better solutions no one has found yet. The project 
library is a good feature for this :)


On Mon, Oct 13, 2014 at 8:10 AM, Benoît Roehr 
mailto:benoit.roehr...@gmail.com>> wrote:


In KiCAD each project can have its own library of footprints,
so this idea duplicates, that exist already.

OK thanks ! I did not know about it before :)

Le 13/10/2014 13:21, LordBlick a écrit :

In response to a message written on 13.10.2014
 12:04, from Benoît Roehr:

Le 13/10/2014 11:40, LordBlick a écrit :

        In response to a message written on 13.10.2014
 08:01, from Benoît Roehr:

For kicad, it could be a good thing to be able to
embed a single footprint to a
com

Re: [Kicad-developers] Library Editor naming consistency

[Benoît Roehr]

In KiCAD each project can have its own library of footprints, so this idea 
duplicates, that exist already.

OK thanks ! I did not know about it before :)

Le 13/10/2014 13:21, LordBlick a écrit :

In response to a message written on 13.10.2014 12:04, from Benoît Roehr:

Le 13/10/2014 11:40, LordBlick a écrit :

In response to a message written on 13.10.2014 08:01, from Benoît Roehr:

For kicad, it could be a good thing to be able to embed a single footprint to a
component if the footprint is really special, but it's non sens if you can
appropriately tag the footprint and put it with the others.

There is a special field to assign footprint to schematic element…

Yes i know, I was meaning if you need a very special footprint just for one
component, you may not want to pollute your existing pcblibrary with this
footprint. For example, you have just one component packaged in a 2 rows QFN
package. You don't want this in your standard QFN lib.
So the ability to attach a single footprint directly to the component without
creating or modifying a PCBLib can be useful.
But it is new feature and it doesn't have to be implemented yet. Not important.
Footprint have to be well named, and all searchable in the same place, not
hidden. ;) More important for me would be a footprint preview in schlib editor.

In KiCAD each project can have its own library of footprints, so this idea ​​
duplicates, that exist already.



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] [Solved] CMake fails to find wxWidget in a fresh Ubuntu 14.04 install when trying to build KiCad

[Benoît Roehr]

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/display/DEV/Building+KiCad+on+Linux

Thanks a lot for your help guys :)

Le 10/10/2014 15:41, Benoît Roehr a écrit :

Hello guys,

My problem with wxWidget 3.0 and CMake continues, I've tried to make 
this work for at least 10 hours now, and can't find any solution 
anywhere. I'm too noob with linux for the moment.


List of what I tried:
Installing latest wxWidget package (3.0.2)
Removing wx2.8
Removing wx3.0.2
Installing wx3.0.0...

Each of the wx3.0.2 and 3.0.0 install were returning correct version 
number to the command wx-config --verion-full. I created a link each 
tim using sudo ln -sv wx-3.0/wx wx ...But still, cmake try to find a 
3.0 minimum required version in a wx-2.8 folder which doesn't exist 
anymore... Here is the terminal output below: I give up for today...


purebasic@purebasic-VirtualBox:~/build/kicad/kicad.bzr/build$ cmake 
../CMake Error at CMakeModules/FindwxWidgets.cmake:868 (file):

  file Internal CMake error when trying to open file:
  /usr/include//_*wx-2.8*_//wx/version.h for reading.
Call Stack (most recent call first):
  CMakeLists.txt:411 (find_package)


CMake Error at CMakeModules/FindPackageHandleStandardArgs.cmake:136 
(message):
  Could NOT find wxWidgets: Found unsuitable version "..", but 
required is at

  least "3.0.0" (found
-L/usr/lib/i386-linux-gnu;-pthread;;;-lwx_gtk2u_gl-3.0;-lwx_gtk2u_aui-3.0;-lwx_gtk2u_adv-3.0;-lwx_gtk2u_html-3.0;-lwx_gtk2u_core-3.0;-lwx_baseu_net-3.0;-lwx_baseu-3.0;-lwx_baseu_xml-3.0)
Call Stack (most recent call first):
  CMakeModules/FindPackageHandleStandardArgs.cmake:341 
(_FPHSA_FAILURE_MESSAGE)

  CMakeModules/FindwxWidgets.cmake:902 (find_package_handle_standard_args)
  CMakeLists.txt:411 (find_package)


-- Configuring incomplete, errors occurred!
See also 
"/home/purebasic/build/kicad/kicad.bzr/build/CMakeFiles/CMakeOutput.log".







___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Library Editor naming consistency

[Benoît Roehr]

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 still stands 
because of the following.


See pictures attached.

_This is a Symbol: _

Lines and circles, it looks like a NPN

_This is a Component:_

Symbol, designator, pin numbers, logical connexions, reference, footprint.

The symbol is indeed what we see in the eeschema, and one of the thing 
we edit in the editor, but the logical object behind contains a lot of 
other parameters, including the symbol. Also, when working, if I show a 
schematic to a coworker, I will say 'look at this symbol' to show him a 
cool looking 18 pin photoexciter or a crazy mosfet, but i'll say 
'component' when referring to the device. Imagine this: "Where is this 
symbol on this schematic ?" and the guy go crazy saying "Here ! 
here here and here !" :D


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 have used Altium, and as Andy 
Peters said, this is how these guys call it, too.

I'm checking Altium v14.3.9 right now and I can't find "Symbol".

When you say "the marriage of different things", this is a good feature 
existing in Altium indeed. They call it an Integrated library (or 
compiled library). These libs contain both SchLibraries and 
PCBLibraries, strongly linked together. You use this type of library 
when you know the footprints you create for a family of product will not 
be used elsewhere, like a connector family for example. You can't edit it.


But even with this, a non integrated Component is still a component in 
the SchEditor. He is just waiting to be binded with a footprint. You 
still see a symbol with designator, reference, pins...etc. The only 
difference is that the footprints and 3d models are private and can't be 
used by another component.


[off topic]
There is no editor in Altium for these lib(which is a pain in the a**), 
you have to extract the source libraries, edit the two libs separately 
and then recompile the integrated library. And btw, all the components 
you get by default with Altium are in this format. All footprint 
private. A nightmare ! Usually I just extract sources from these intLibs 
depending on what i need and then I allow them to live freely on my HDD :)
For kicad, it could be a good thing to be able to embed a single 
footprint to a component if the footprint is really special, but it's 
non sens if you can appropriately tag the footprint and put it with the 
others.
The way kicad libraries work needs improvement (footprint linking in 
component editor with preview ;) ) but shouldn't be drastically changed. 
Everything is quickly accessible and the 3d model is already 'embedded' 
or linked to the footprint. Perfect !
Also if you have time, take a look at CompOrg. 
https://github.com/cidadao/Component-Organizer It's a little free 
software for datasheet and application ot management. It can give ideas 
for Kicad.

[/off topic]



On Sun, Oct 12, 2014 at 9:14 PM, Mark Roszko > wrote:


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 called instead of Parts.

Just
like PCB Footprint Editor is for Footprints.



I would go for "Schematic Library Editor" and "PCB Library Editor".



--
Mark

___
Mailing list: https://launchpad.net/~kicad-developers

Post to : kicad-developers@lists.launchpad.net

Unsubscribe : https://launchpad.net/~kicad-developers

More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] CMake fails to find wxWidget in a fresh Ubuntu 14.04 install when trying to build KiCad

[Benoît Roehr]

Le 10/10/2014 21:33, inkblotter a écrit :

been there, done that.

You are close..   All that removing of this and that is/should be 
unnecessary and even undesirable


you should be using
-DwxWidgits_CONFIG_EXECUTABLE=/path/to/the/correct/wx-config
Oh noes ! I totally forgot to try that !!! Well, I'll remove the wx-2.8 
fake folder I made once the build is finished and try this option.

config option to cmake.  Also make sure that  the path to the wx bin directory 
is on your PATH so it can execute wx-config

Even with the development files gone you should still use this option.
If it still fails for you after doing that (and it did so for me on fedora 20) 
then we can change (hack) a couple lines in a cmake file.

Some day I will figure out why this is necessary and how to rearrange the 
culprit cmake file.

Let me know and I will tell you what to do further.


On 10/10/2014 08:41 AM, Benoît Roehr wrote:

Hello guys,

My problem with wxWidget 3.0 and CMake continues, I've tried to make 
this work for at least 10 hours now, and can't find any solution 
anywhere. I'm too noob with linux for the moment.


List of what I tried:
Installing latest wxWidget package (3.0.2)
Removing wx2.8
Removing wx3.0.2
Installing wx3.0.0...

Each of the wx3.0.2 and 3.0.0 install were returning correct version 
number to the command wx-config --verion-full. I created a link each 
tim using sudo ln -sv wx-3.0/wx wx ...But still, cmake try to find a 
3.0 minimum required version in a wx-2.8 folder which doesn't exist 
anymore... Here is the terminal output below: I give up for today...


purebasic@purebasic-VirtualBox:~/build/kicad/kicad.bzr/build$ cmake 
../CMake Error at CMakeModules/FindwxWidgets.cmake:868 (file):

  file Internal CMake error when trying to open file:
  /usr/include//_*wx-2.8*_//wx/version.h for reading.
Call Stack (most recent call first):
  CMakeLists.txt:411 (find_package)


CMake Error at CMakeModules/FindPackageHandleStandardArgs.cmake:136 
(message):
  Could NOT find wxWidgets: Found unsuitable version "..", but 
required is at

  least "3.0.0" (found
-L/usr/lib/i386-linux-gnu;-pthread;;;-lwx_gtk2u_gl-3.0;-lwx_gtk2u_aui-3.0;-lwx_gtk2u_adv-3.0;-lwx_gtk2u_html-3.0;-lwx_gtk2u_core-3.0;-lwx_baseu_net-3.0;-lwx_baseu-3.0;-lwx_baseu_xml-3.0) 


Call Stack (most recent call first):
  CMakeModules/FindPackageHandleStandardArgs.cmake:341 
(_FPHSA_FAILURE_MESSAGE)
  CMakeModules/FindwxWidgets.cmake:902 
(find_package_handle_standard_args)

  CMakeLists.txt:411 (find_package)


-- Configuring incomplete, errors occurred!
See also 
"/home/purebasic/build/kicad/kicad.bzr/build/CMakeFiles/CMakeOutput.log".








___
Mailing list:https://launchpad.net/~kicad-developers
Post to :kicad-developers@lists.launchpad.net
Unsubscribe :https://launchpad.net/~kicad-developers
More help   :https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] CMake fails to find wxWidget in a fresh Ubuntu 14.04 install when trying to build KiCad

[Benoît Roehr]

Hello guys,

Thanks for your help, but it didn't worked.

It's nonsense for me, wxWidget 2.8 have been removed, and wx-config 
--version returns the right version:


purebasic@purebasic-VirtualBox:~/build/kicad/kicad.bzr/build$ wx-config 
--version

3.0.2

I also made a link to the wxWidget includes using sudo ln -sv 
usr/include/wx-3.0-unofficial/wx wx.

So maybe the old link is still there ?

Cmake looks in the wx-2.8 folder, and it looks like the path is 
hard-coded somewhere:

purebasic@purebasic-VirtualBox:~/build/kicad/kicad.bzr/build$ cmake ../
CMake Error at CMakeModules/FindwxWidgets.cmake:868 (file):
  file Internal CMake error when trying to open file:
*  /usr/include/wx-2.8/wx/version.h for reading.*
Call Stack (most recent call first):
  CMakeLists.txt:411 (find_package)

I finally found a get around: I made a wx-2.8 directory and copied the 
./wx-3.0-unofficial/wx folder in it. It worked !

KiCad is building right now :D

See you ;)

Le 10/10/2014 18:30, Adam Wolf a écrit :

Hi Benoit,

Just expanding upon Wayne's answer, the way you would remove wxWidgets 
2.8.12 development package on Ubuntu would be


sudo apt-get remove wxwidgets2.8-dev

or

sudo aptitude remove wxwidgets2.8-dev

I do not recommend modifying the CMake files to remove features.  
There are command line switches to turn on and off nearly everything 
in the build files.  Especially as a beginner looking to start 
development, I think it is best to modify the build behavior with the 
command line switches as compared to modifying the file.


Adam Wolf
Cofounder and Engineer
W&L, LLC

On Fri, Oct 10, 2014 at 11:16 AM, Wayne Stambaugh 
mailto:stambau...@verizon.net>> wrote:


Add -DwxWidgits_CONFIG_EXECUTABLE=/path/to/the/correct/wx-config when
running cmake.  Otherwise, the cmake module that finds wxWidgets will
find the first one it discovers which in you case is 2.8.12.  The
other
option it to remove the the wxWidgets 2.8.12 development package.

    On 10/10/2014 11:34 AM, Benoît Roehr wrote:
> Aw sorry everyone. I just noticed my previous mail was only sent to
> Brian. It was a reply made in the build-under-windows subject. I
join it
> in this subject here:
> On 09/10/2014 11:28, Brian Sidebotham wrote:
>> Lastly, if you do want to develop KiCad I would strongly urge
moving
>> to Linux for development because it's just s much easier and
>> faster! We always require heavy testing on Windows, but
developing on
>> Windows is a real pain.
> It has been a while I want to switch OS. I'm proud to announce
this mail
> is sent from an Ubuntu VM ! However, I fail here:
>
> purebasic@purebasic-VirtualBox:~/build/kicad/kicad.bzr/build$ cmake
> -DKICAD_STABLE_VERSION=ON ../
> CMake Error at CMakeModules/FindPackageHandleStandardArgs.cmake:136
> (message):
>   Could NOT find wxWidgets: Found unsuitable version "2.8.12",
but required
>   is at least "3.0.0" (found
>

-L/usr/lib/i386-linux-gnu;-pthread;;;-lwx_gtk2u_unofficial_gl-3.0;-lwx_gtk2u_unofficial_aui-3.0;-lwx_gtk2u_unofficial_adv-3.0;-lwx_gtk2u_unofficial_html-3.0;-lwx_gtk2u_unofficial_core-3.0;-lwx_baseu_unofficial_net-3.0;-lwx_baseu_unofficial-3.0;-lwx_baseu_unofficial_xml-3.0)
>
> Call Stack (most recent call first):
>  CMakeModules/FindPackageHandleStandardArgs.cmake:341
> (_FPHSA_FAILURE_MESSAGE)
>   CMakeModules/FindwxWidgets.cmake:901
(find_package_handle_standard_args)
>   CMakeLists.txt:411 (find_package)
>
>
> -- Configuring incomplete, errors occurred!
> See also
>
"/home/purebasic/build/kicad/kicad.bzr/build/CMakeFiles/CMakeOutput.log".
>
> For info, I've installed wxWidget 3.0.2 Trusty (i'm on u14.04) using
> Synaptic. Do I need to change something else manually ? For me
it looks
> like cmake try to use the last wx version which is still
installed...
>
> Le 10/10/2014 15:41, Benoît Roehr a écrit :
>> Hello guys,
>>
>> My problem with wxWidget 3.0 and CMake continues, I've tried to
make
>> this work for at least 10 hours now, and can't find any solution
>> anywhere. I'm too noob with linux for the moment.
>>
>> List of what I tried:
>> Installing latest wxWidget package (3.0.2)
>> Removing wx2.8
>> Removing wx3.0.2
>> Installing wx3.0.0...
>>
>> Each of the wx3.0.2 and 3.0.0 install were returning correct
version
>> number to the command wx-config --verion-full. I created a link
each
>> tim using sudo ln -sv wx-3.0/wx wx ...But still, cmake try to
find a
>> 3.0 minimu

Re: [Kicad-developers] CMake fails to find wxWidget in a fresh Ubuntu 14.04 install when trying to build KiCad

[Benoît Roehr]

Aw sorry everyone. I just noticed my previous mail was only sent to 
Brian. It was a reply made in the build-under-windows subject. I join it 
in this subject here:

On 09/10/2014 11:28, Brian Sidebotham wrote:

Lastly, if you do want to develop KiCad I would strongly urge moving
to Linux for development because it's just s much easier and
faster! We always require heavy testing on Windows, but developing on
Windows is a real pain.
It has been a while I want to switch OS. I'm proud to announce this mail 
is sent from an Ubuntu VM ! However, I fail here:


purebasic@purebasic-VirtualBox:~/build/kicad/kicad.bzr/build$ cmake 
-DKICAD_STABLE_VERSION=ON ../
CMake Error at CMakeModules/FindPackageHandleStandardArgs.cmake:136 
(message):
  Could NOT find wxWidgets: Found unsuitable version "2.8.12", but 
required

  is at least "3.0.0" (found
-L/usr/lib/i386-linux-gnu;-pthread;;;-lwx_gtk2u_unofficial_gl-3.0;-lwx_gtk2u_unofficial_aui-3.0;-lwx_gtk2u_unofficial_adv-3.0;-lwx_gtk2u_unofficial_html-3.0;-lwx_gtk2u_unofficial_core-3.0;-lwx_baseu_unofficial_net-3.0;-lwx_baseu_unofficial-3.0;-lwx_baseu_unofficial_xml-3.0) 


Call Stack (most recent call first):
  CMakeModules/FindPackageHandleStandardArgs.cmake:341 
(_FPHSA_FAILURE_MESSAGE)

  CMakeModules/FindwxWidgets.cmake:901 (find_package_handle_standard_args)
  CMakeLists.txt:411 (find_package)


-- Configuring incomplete, errors occurred!
See also 
"/home/purebasic/build/kicad/kicad.bzr/build/CMakeFiles/CMakeOutput.log".


For info, I've installed wxWidget 3.0.2 Trusty (i'm on u14.04) using 
Synaptic. Do I need to change something else manually ? For me it looks 
like cmake try to use the last wx version which is still installed...


Le 10/10/2014 15:41, Benoît Roehr a écrit :

Hello guys,

My problem with wxWidget 3.0 and CMake continues, I've tried to make 
this work for at least 10 hours now, and can't find any solution 
anywhere. I'm too noob with linux for the moment.


List of what I tried:
Installing latest wxWidget package (3.0.2)
Removing wx2.8
Removing wx3.0.2
Installing wx3.0.0...

Each of the wx3.0.2 and 3.0.0 install were returning correct version 
number to the command wx-config --verion-full. I created a link each 
tim using sudo ln -sv wx-3.0/wx wx ...But still, cmake try to find a 
3.0 minimum required version in a wx-2.8 folder which doesn't exist 
anymore... Here is the terminal output below: I give up for today...


purebasic@purebasic-VirtualBox:~/build/kicad/kicad.bzr/build$ cmake 
../CMake Error at CMakeModules/FindwxWidgets.cmake:868 (file):

  file Internal CMake error when trying to open file:
  /usr/include//_*wx-2.8*_//wx/version.h for reading.
Call Stack (most recent call first):
  CMakeLists.txt:411 (find_package)


CMake Error at CMakeModules/FindPackageHandleStandardArgs.cmake:136 
(message):
  Could NOT find wxWidgets: Found unsuitable version "..", but 
required is at

  least "3.0.0" (found
-L/usr/lib/i386-linux-gnu;-pthread;;;-lwx_gtk2u_gl-3.0;-lwx_gtk2u_aui-3.0;-lwx_gtk2u_adv-3.0;-lwx_gtk2u_html-3.0;-lwx_gtk2u_core-3.0;-lwx_baseu_net-3.0;-lwx_baseu-3.0;-lwx_baseu_xml-3.0)
Call Stack (most recent call first):
  CMakeModules/FindPackageHandleStandardArgs.cmake:341 
(_FPHSA_FAILURE_MESSAGE)

  CMakeModules/FindwxWidgets.cmake:902 (find_package_handle_standard_args)
  CMakeLists.txt:411 (find_package)


-- Configuring incomplete, errors occurred!
See also 
"/home/purebasic/build/kicad/kicad.bzr/build/CMakeFiles/CMakeOutput.log".







___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] CMake fails to find wxWidget in a fresh Ubuntu 14.04 install when trying to build KiCad

[Benoît Roehr]

Hello guys,

My problem with wxWidget 3.0 and CMake continues, I've tried to make 
this work for at least 10 hours now, and can't find any solution 
anywhere. I'm too noob with linux for the moment.


List of what I tried:
Installing latest wxWidget package (3.0.2)
Removing wx2.8
Removing wx3.0.2
Installing wx3.0.0...

Each of the wx3.0.2 and 3.0.0 install were returning correct version 
number to the command wx-config --verion-full. I created a link each tim 
using sudo ln -sv wx-3.0/wx wx ...But still, cmake try to find a 3.0 
minimum required version in a wx-2.8 folder which doesn't exist 
anymore... Here is the terminal output below: I give up for today...


purebasic@purebasic-VirtualBox:~/build/kicad/kicad.bzr/build$ cmake 
../CMake Error at CMakeModules/FindwxWidgets.cmake:868 (file):

  file Internal CMake error when trying to open file:
  /usr/include//_*wx-2.8*_//wx/version.h for reading.
Call Stack (most recent call first):
  CMakeLists.txt:411 (find_package)


CMake Error at CMakeModules/FindPackageHandleStandardArgs.cmake:136 
(message):
  Could NOT find wxWidgets: Found unsuitable version "..", but required 
is at

  least "3.0.0" (found
-L/usr/lib/i386-linux-gnu;-pthread;;;-lwx_gtk2u_gl-3.0;-lwx_gtk2u_aui-3.0;-lwx_gtk2u_adv-3.0;-lwx_gtk2u_html-3.0;-lwx_gtk2u_core-3.0;-lwx_baseu_net-3.0;-lwx_baseu-3.0;-lwx_baseu_xml-3.0)
Call Stack (most recent call first):
  CMakeModules/FindPackageHandleStandardArgs.cmake:341 
(_FPHSA_FAILURE_MESSAGE)

  CMakeModules/FindwxWidgets.cmake:902 (find_package_handle_standard_args)
  CMakeLists.txt:411 (find_package)


-- Configuring incomplete, errors occurred!
See also 
"/home/purebasic/build/kicad/kicad.bzr/build/CMakeFiles/CMakeOutput.log".





___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Turn key build system for poking and messing around with the sources

[Benoît Roehr]

Le 09/10/2014 08:36, Lorenzo Marcantonio a écrit :

On Wed, Oct 08, 2014 at 11:33:39PM +0200, Benoît Roehr wrote:

Does someone have a turnkey solution for building and running eeschema alone
? Can it be done by tweaking winbuilder ? (help help !)

Well, if you only touch eeschema the rebuild will only recompile that!

So I see no needs for tweakings...

You answered exactly my concern ! I was searching a way to speed up the 
compilation.
Ok, so now, I'm digging into the cMake script to build kicad from local 
source. I'll find this I think.



What is it that you are trying to do that you want a standalone eeschema?


There are a lot of ideas I would like to see become real in KiCad. But 
for the moment, I need to dig into the sources and poke things around, 
seeing what is doing what, what is possible or not, and I prefer to do 
it locally because I'm a beginner for big projects and I want clean and 
working code, which follows coding style rules. I also need to learn 
more about wxWidget, openGL, Canvas, Cairos, boost...etc...


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Turn key build system for poking and messing around with the sources

[Benoît Roehr]

Hello, dear developers,

I have some ideas of improvement for the Schematic editor. Making C++ in 
microcontrollers is no problem for me but I know very little about 
software compilation for x86 platforms. I'll will also need to learn 
about wxWidget :D


Does someone have a turnkey solution for building and running eeschema 
alone ? Can it be done by tweaking winbuilder ? (help help !)


Cheers !

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Rename instances of "module" to "footprint" for consistency

[Benoît Roehr]

Le 08/10/2014 19:40, Andy Peters a écrit :

On Oct 8, 2014, at 5:08 AM, Mark Roszko  wrote:

I use footprint myself.  Though footprint seems to imply what a PCB
must have in order to accommodate a part, eg, pads, silk.  Are the 3d
models part of this?  If they are, then footprint might not be the
best term.
I agree with this. What you want to rename "Footprint" is more or less a 
container unifying different PCB objects (pads, lines, 3d model...), but may not be a 
footprint (logos, mounting holes, screws...)

Personally I think "Components" may be an even better word than
"modules" or "footprints" but suggesting that may have been even more
radical and conflicting agaisn't the next point

My two cents, based on the terminology used by every employer for whom I've 
worked:

a) A footprint is what defines how a part gets attached to a PCB. It includes the 
pad/holes for lead attach, as well as silkscreen for refdes and outline, and the other 
assembly layers such as soldermask, solder paste and glue dots. "Land patterns" 
really only describe the lead attach, and not the other stuff.

I think Pads calls this a "decal." The only context I've seen the term "module" 
refer to a PCB footprint is in Kicad.

"Footprint" is the term used by most of us here in the colonies.

Yes, i couldn't agree more :D


b) A symbol is what defines a part for a schematic.
Well, seeing it from a productivity point of view, I prefer the term 
Component for the schematic. You are indeed using a symbol in eeschema 
but it represents a component.


c) A component is the marriage of the footprint and the symbol, and possibly a 
3D model, a SPICE model, a VHDL entity or Verilog module, and so forth. This is 
the Altium nomenclature.
Yes, except in all the libraries, every item in them are called 
component. Why ? Well I think they use the same library browser for all 
the library types, and Component is the default string in the list header.


d) A module is a completed assembly or subassembly which is installed as one 
unit on a PCBA. The various DC-DC converters you can buy from TI and Linear 
Tech are modules.

So my vote, if there's a move to change Kicad terminology, is to replace the term 
"module" with "footprint."
In my opinion, once the footprint represents a component, it should be 
called Component.


What I propose (if I can, I have not contributed that much for the 
moment) is to change almost nothingto how KiCad names stuffs already.


Here is my dream:

- In the Schematic Library editor, the symbol is the symbol you are 
drawing, but will be embeded in the component root with one or more 
footprint.

Designator: Q?
Value: 2N7002
Footprint: SOT-23 / TO220 / MoreFootprints
Datasheets: http://manufacturer-of-mosfet/2n7002.pdf

- In the Schematic editor, every symbols represent a Component which 
will be physically present on the board: for exemple:

Designator: Q1
Value: 2N7002
Footprint: SOT-23< footprint selected for this project
Datasheet: http://manufacturer-of-mosfet#1/2n7002_SOT.pdf

- In the footprint editor, you edit footprint, used by the components
- In the PCB editor, you deal with components having footprints, or free 
footprints representing other components.


From what I see in KiCad, all these stuff have already be done except 
for the multiple footprint selection and/or footprint direct linking (I 
haven't digged enough to use the 'filter'). The only occurences of 
Module I can see atm is in the PCBEditor and they should be replaced by 
Footprint or Component depending on the context.


See you :D

-a


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Rename instances of "module" to "footprint" for consistency

[Benoît Roehr]

Hello dear developers.

Le 08/10/2014 10:08, Andrew Zonenberg a écrit :

Second the vote for consistency, no matter which way it goes.

Personally, I have a slight preference for "footprint" over "module" as
well.

On Wed, 2014-10-08 at 18:56 +1100, Mitch Davis wrote:

On Wed, Oct 8, 2014 at 5:47 PM, Mark Roszko  wrote:

Hehe, well, I guess everything can be renamed in the opposite
direction. But consistency is needed.

YES PLEASE!  A number of people I've spoken to were really confused by
this inconsistency.

I use footprint myself.  Though footprint seems to imply what a PCB
must have in order to accommodate a part, eg, pads, silk.  Are the 3d
models part of this?  If they are, then footprint might not be the
best term.
I agree with this. What you want to rename "Footprint" is more or less a 
container unifying different PCB objects (pads, lines, 3d model...), but 
may not be a footprint (logos, mounting holes, screws...)


Altium folks use the "Component" term both in Schematic libraries and 
PCB libraries. You know what you are looking at knowing what type of 
library is browsed. I don't remember for Proteus.


Benoît.


Mitch.

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Newcomer

[Benoît Roehr]

To speak frankly, Altium is looking very good !

It was not really that functionalities were lacking, I just hadn't had the
time to dig into it properly. For what I remember I tried different EDAs at
this time: Eagle, Proteus, KiCad, gEDA. The boss in the company I worked
for decided to stick to Proteus rather than switching to Altium, and KiCad
were not looking better than Proteus or Eagle. I decided to stick to Altium
for my personal projects, waiting for KiCad to improve. Now is the time ;)

A+,
Benoît

2014-09-10 15:06 GMT+02:00 A. V. Dolganoff :

> Salut to fellow Frenchie ;)
>
> Can you elaborate more on what aspects of Kicad you didn't like the
> most the last time?
>
> a+, Alexei.
>
> On Wed, Sep 10, 2014 at 3:02 PM, Benoît Roehr 
> wrote:
> > Hello everyone,
> >
> > First of all I really want to thank you all for the great improvements
> KiCad
> > had recently. The last time I tried to use it (about a year ago) I made
> the
> > decision to return to Altium because of the lake of important features.
> >
> > Now that CERN is also on board, switching to KiCad, helping and following
> > the development sounds really exciting :}
> >
> > A bit about me: I live in Strasbourg and I work for the Strasbourg
> > University in Cronenbourg as an electronic technician since one week.
> Before
> > that I was one of the head hardware designer of Ideovitra, and I worked
> on
> > the sensybee products for two years.
> >
> > My competences are quite wide: schematic capture and routing, board
> > prototyping and repairing, python, LabView and C++... I haven't done a
> lot
> > of code for computers, as I mostly make program for microcontrollers.
> >
> > I would be really glade to participate in the development of KiCad. I
> used
> > Altium a lot and at the moment it is still my favorite EDA, but Altium is
> > far from perfect. For example, the library management is very daunting,
> and
> > of course, it's not free and opensource.
> >
> > These next days, I will think about a project I could realize with KiCad
> to
> > take it on hand and dig into while keeping notes about what could be
> > improved, and/or bugs.
> >
> > Also, if help is needed somewhere else, just tell me what I can do I will
> > help, for sure.
> >
> > Cheers,
> > Benoît
> >
> > ___
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to : kicad-developers@lists.launchpad.net
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
> >
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Newcomer

[Benoît Roehr]

Hello everyone,

First of all I really want to thank you all for the great improvements
KiCad had recently. The last time I tried to use it (about a year ago) I
made the decision to return to Altium because of the lake of important
features.

Now that CERN is also on board, switching to KiCad, helping and following
the development sounds really exciting :}

A bit about me: I live in Strasbourg and I work for the Strasbourg
University in Cronenbourg as an electronic technician since one week.
Before that I was one of the head hardware designer of Ideovitra, and I
worked on the sensybee products for two years.

My competences are quite wide: schematic capture and routing, board
prototyping and repairing, python, LabView and C++... I haven't done a lot
of code for computers, as I mostly make program for microcontrollers.

I would be really glade to participate in the development of KiCad. I used
Altium a lot and at the moment it is still my favorite EDA, but Altium is
far from perfect. For example, the library management is very daunting, and
of course, it's not free and opensource.

These next days, I will think about a project I could realize with KiCad to
take it on hand and dig into while keeping notes about what could be
improved, and/or bugs.

Also, if help is needed somewhere else, just tell me what I can do I will
help, for sure.

Cheers,
Benoît
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp