Hi Wayne-
I deleted the build directory, compiled from scratch and now the issue is
gone. So it must have been a cmake cache problem as you suspected. Lesson
learned ;)
Thanks
Lajos
On Apr 15, 2012 11:21 AM, Wayne Stambaugh stambau...@verizon.net wrote:
On 4/15/2012 11:08 AM, lajos kamocsay
On 16 April 2012 18:06, lajos kamocsay panka.nos...@gmail.com wrote:
Hi Wayne-
I deleted the build directory, compiled from scratch and now the issue is
gone. So it must have been a cmake cache problem as you suspected. Lesson
learned ;)
Thanks
Lajos
Sorry, I'm coming to the party
Thanks for the tip Brian, I'll try that next time.
On Apr 16, 2012 1:36 PM, Brian Sidebotham brian.sidebot...@gmail.com
wrote:
On 16 April 2012 18:06, lajos kamocsay panka.nos...@gmail.com wrote:
Hi Wayne-
I deleted the build directory, compiled from scratch and now the issue is
gone. So
On 4/14/2012 11:18 PM, lajos kamocsay wrote:
Hi-
When I build revno 3511, the tracks that I draw in pcbnew are huge
(wider than the default page) (screenshot attached).
I use these flags for cmake:
cmake ../kicad.latest -DKICAD_STABLE_VERSION=ON -DCMAKE_BUILD_TYPE=Release \
Like so many suggestions, they are often good ideas that never get done,
because they do
not rise to a sufficient level of need within an individual capable of doing
the work.
This is especially true in free software, which in fact is never free.
Feature bounties might be a workable
On 04/13/2012 02:04 AM, jean-pierre charras wrote:
Le 12/04/2012 20:53, Wayne Stambaugh a écrit :
On 4/12/2012 9:05 AM, Dick Hollenbeck wrote:
On 04/11/2012 06:41 PM, Dan Chianucci wrote:
This new format looks great, I have a few comments/questions
1) in some spots like module pads
On 04/13/2012 02:32 AM, Solonen Vesa wrote:
Like so many suggestions, they are often good ideas that never get done,
because they do
not rise to a sufficient level of need within an individual capable of doing
the work.
This is especially true in free software, which in fact is never free.
This is one of those areas where I am relying on the knowledge of
someone who know about the BOARD_ITEM internals that I do. If there is
^ knows more^ than
I really need to get away from my computer :)
Wayne
That will only make you worse at typing.
On 4/13/2012 8:39 AM, Dick Hollenbeck wrote:
On 04/13/2012 02:04 AM, jean-pierre charras wrote:
Le 12/04/2012 20:53, Wayne Stambaugh a écrit :
On 4/12/2012 9:05 AM, Dick Hollenbeck wrote:
On 04/11/2012 06:41 PM, Dan Chianucci wrote:
This new format looks great, I have a few comments/questions
On 04/13/2012 10:18 AM, Wayne Stambaugh wrote:
On 4/13/2012 8:39 AM, Dick Hollenbeck wrote:
On 04/13/2012 02:04 AM, jean-pierre charras wrote:
Le 12/04/2012 20:53, Wayne Stambaugh a écrit :
On 4/12/2012 9:05 AM, Dick Hollenbeck wrote:
On 04/11/2012 06:41 PM, Dan Chianucci wrote:
This new
On 04/11/2012 06:41 PM, Dan Chianucci wrote:
This new format looks great, I have a few comments/questions
1) in some spots like module pads there is (net nutNum netName) and
in other
spots like track segments it only has (net netNum).
2)What do the edge tags represent in the
On 04/11/2012 07:14 AM, Solonen Vesa wrote:
Some salt on the popcorn?
Regarding net classes handling... Flexible automatic design rules would need
differential net classes that means different rules for a net depending on
surrounding nets.
As an example I'll explain the problem of a
On 4/12/2012 9:05 AM, Dick Hollenbeck wrote:
On 04/11/2012 06:41 PM, Dan Chianucci wrote:
This new format looks great, I have a few comments/questions
1) in some spots like module pads there is (net nutNum netName) and
in other
spots like track segments it only has (net netNum).
- Original Message -
From: Wayne Stambaugh stambau...@verizon.net
To: kicad-developers@lists.launchpad.net
Cc:
Sent: Friday, April 13, 2012 4:53 AM
Subject: Re: [Kicad-developers] New Pcbnew file format.
[snip]
4) What are the two (at) tags in module_text for? why not only 1
On 04/12/2012 01:53 PM, Wayne Stambaugh wrote:
On 4/12/2012 9:05 AM, Dick Hollenbeck wrote:
On 04/11/2012 06:41 PM, Dan Chianucci wrote:
This new format looks great, I have a few comments/questions
1) in some spots like module pads there is (net nutNum netName)
and in other
spots like
class EDGE_MODULE is derived from DRAWSEGMENT and comes in types
S_SEGMENT, S_CIRCLE, S_ARC, S_POLYGON.
So it is basically a graphical line, circle, arc, or polygon.
Basically a graphic, so that word is one candidate. It is not confined to
the module's
edge, but is often used to
- Original Message -
From: Dan Chianucci trump211...@gmail.com
To: Dick Hollenbeck d...@softplc.com
Cc: kicad-developers@lists.launchpad.net
Sent: Friday, April 13, 2012 9:58 AM
Subject: Re: [Kicad-developers] New Pcbnew file format.
[snip]
To Cirilo:
I agree with what you are saying
Sorry for top-posting! Just wanted to say well done Wayne! Again,
excellent work that is so beneficial to the project! And don't think
your UI changes have gone unnoticed, KiCad is a lot more together
since you started work on the UI tidy up.
Thanks for your continued efforts! :D
Best Regards,
On 04/09/2012 03:52 PM, Miguel Angel Ajo Pelayo wrote:
I love the plan, it matches and extends the tiny idea I had but it's well
planned!!,
About the SWEET_HTTP_LIB source and even SWEET servers, and web apps,
I propose that we could use our (future) new python powers, that are
On 4/11/2012 4:02 AM, Brian Sidebotham wrote:
Sorry for top-posting! Just wanted to say well done Wayne! Again,
excellent work that is so beneficial to the project! And don't think
your UI changes have gone unnoticed, KiCad is a lot more together
since you started work on the UI tidy up.
Human readability/usability/ease of learning would also be helped with
some standardization.
On 8/04/2012 8:23 p.m., Dick Hollenbeck wrote:
On 04/08/2012 11:38 AM, lajos kamocsay wrote:
Hi Wayne-
The new file format looks awesome. Very simple and readable.
Would it be possible to
On 8/04/2012 8:23 p.m., Dick Hollenbeck wrote:
On 04/08/2012 11:38 AM, lajos kamocsay wrote:
Hi Wayne-
The new file format looks awesome. Very simple and readable.
Would it be possible to standardize the transformation data? Currently
there seems to be a couple different formats, some
On 4/9/2012 6:28 AM, jean-pierre charras wrote:
On 8/04/2012 8:23 p.m., Dick Hollenbeck wrote:
On 04/08/2012 11:38 AM, lajos kamocsay wrote:
Hi Wayne-
The new file format looks awesome. Very simple and readable.
Would it be possible to standardize the transformation data? Currently
there
Hi Wayne-
I've had a conversation with Dick, and he asked me to clarify my
suggestion about standardizing the transformation data.
Standardizing would save you work and debugging time because you would
only need to write the encoder and decoder (parser) once. Instead of
every object taking care
Le 09/04/2012 17:02, Wayne Stambaugh a écrit :
On 4/9/2012 6:28 AM, jean-pierre charras wrote:
On 8/04/2012 8:23 p.m., Dick Hollenbeck wrote:
On 04/08/2012 11:38 AM, lajos kamocsay wrote:
Hi Wayne-
The new file format looks awesome. Very simple and readable.
Would it be possible to
On 04/09/2012 10:07 AM, Wayne Stambaugh wrote:
On 4/9/2012 9:43 AM, Dick Hollenbeck wrote:
Wayne and all,
I feel better now about PCBNEW loading a BOARD with USE_PCBNEW_NANOMETRES
defined after
some work I did this weekend.
Dick,
Great work! Thanks for fixing this so we can keep the
Now that may be we're still in time (well in fact, now I think that could
be added lately without big impact..)
What do you think about adding a UUID (I see now that you used 'LPID'
for SWEET) to the PCB files, and also a revision number (that goes
incrementally on every modified save).
On 04/09/2012 02:55 PM, Miguel Angel Ajo Pelayo wrote:
Now that may be we're still in time (well in fact, now I think that could be
added
lately without big impact..)
What do you think about adding a UUID (I see now that you used 'LPID'
for SWEET)
to the PCB files, and also a
I love the plan, it matches and extends the tiny idea I had but it's well
planned!!,
About the SWEET_HTTP_LIB source and even SWEET servers, and web apps,
I propose that we could use our (future) new python powers, that are
proficient
in handling XML-RPC, Databases, and similar things with very
Hi Wayne-
The new file format looks awesome. Very simple and readable.
Would it be possible to standardize the transformation data? Currently
there seems to be a couple different formats, some examples:
(draw line (pts xy(76.581 47.9425) xy(77.724 47.9425)) (layer 21)
(width 0.127))
(size
On 04/08/2012 11:38 AM, lajos kamocsay wrote:
Hi Wayne-
The new file format looks awesome. Very simple and readable.
Would it be possible to standardize the transformation data? Currently
there seems to be a couple different formats, some examples:
(draw line (pts xy(76.581 47.9425)
I must be doing something very silly
just pulled from bzr, and then
mkdir building
cd building
cmake -i ../
make
and make says nothing at all, and exists :-?
I must re-read the compiling guide ':-)
2012/4/8 Dick Hollenbeck d...@softplc.com
On 04/08/2012 11:38 AM,
Hi Miguel-
You probably figured it out already, but here's my super simple build
script for the latest. Assuming you already have the bzr branch in
this structure:
42
|- build_latest# build script, chmod a+x
|- kicad.latest# as it says
|- build.latest # this folder the script makes
It took long than I anticipated (doesn't always?) but I just committed
the code to allow saving board files to the new s-expression based file
format. I would like as many folks as possible to save their favorite
board file using File-Save As to the new format and take a look at the
result. My
Oops! To be able to save to the new file format you must add
-DUSE_PCBNEW_SEXPR_FILE_FORMAT=ON and -DUSE_PCBNEW_NANOMETRES=ON when
invoking CMake in order to build the new code.
On 4/7/2012 2:09 PM, Wayne Stambaugh wrote:
It took long than I anticipated (doesn't always?) but I just committed
35 matches
Mail list logo
