Re: gEDA-user: pcb option --layer-stack
On Sat, 13 Mar 2010 02:58:01 -0500, DJ Delorie wrote: You want the doc/extract-docs script, not gather-actions. So this is another outdated snippet in the pcb manual: / pcb/doc/pcb.html -- (...) Within the Pcb sources are specially crafted comments that mark all the actions, flags, menu hooks, and whatnot that Pcb offers. Read the file src/gather-actions in the Pcb source tree for documentation for these comments. \ Makes me wonder, how much of the manual is concurrent with the rest of the source ;^) ---(kaimartin)--- -- Kai-Martin Knaak tel: +49-511-762-2895 Universität Hannover, Inst. für Quantenoptik fax: +49-511-762-2211 Welfengarten 1, 30167 Hannover http://www.iqo.uni-hannover.de GPG key:http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmkop=get ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb option --layer-stack
So this is another outdated snippet in the pcb manual: No, it just has a different purpose than you think. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: debugging segfault
Hi, I would suggest using valgrind( [1]http://valgrind.org ) to debug this issue. It's very simple and direct to use, just read the quick intro( [2]http://valgrind.org/docs/manual/quick-start.html ) of its documentation and you're ready to go. You must compile with -g O0 in order to avoid invalid reports from valgrind. something like $valgrind pcb --blablabla should just work, but there are other useful options I just don't remember well right now. It's an excellent tool for debugging memory leaks very quickly. Best Regards, Felipe. -- Felipe De la Puente Christen Mobile Phone: +56 9 93199807 MSN/GTalk : [3]fdelapue...@gmail.com On Sat, 2010-03-13 at 05:05 +, Kai-Martin Knaak wrote: On Fri, 12 Mar 2010 22:45:28 -0500, DJ Delorie wrote: But what I really want, is a print of the components on the bottom side of the board. Add the solderside layer to your layer stack string (see attached code snippet) Thanks. This finally worked :-) I added this tip to the wiki. For the archive: pcb -x eps --layer-stack outline,silk,solderside \ --as-shown \ --action-string 'Display(Value)' \ --eps-file /tmp/out.eps phasen.pcb Any idea where to look for a reason for the segfault? gdb? I feared so ;-) Looks like the manual is derived from pcb/doc/pcb.texi . So I'll edit this file and and post a diff to this mailing list, right? Yup. Git patch format, please. That is, use the command git format-patch ? Any options to add? ---(kaimartin)--- References 1. http://valgrind.org/ 2. http://valgrind.org/docs/manual/quick-start.html 3. mailto:fdelapue...@gmail.com signature.asc Description: This is a digitally signed message part ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb option --layer-stack
DJ Delorie wrote: You want the doc/extract-docs script, not gather-actions. oh yeah. I shouldn't reply to the list past midnight ;) Actually... do we even use gather-actions anymore or was that a pre-HID split deal? I can't seem to see where it is ever used. -Dan ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb option --layer-stack
We used to use it to gather up all the actions and stuff for runtime,
but we switched to the REGISTER_* macros at some point:
# Action, Attribute, and Flag lists.
core_lists.h : ${PCB_SRCS} Makefile
true $@
(for f in ${PCB_SRCS} ; do cat $(srcdir)/$$f ; done) | grep ^REGISTER
$...@.tmp
mv $...@.tmp $@
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: getting used to git (almost trivial pcb patch)
To familiarize myself with the patch production I did this
almost trivial patch of the pcb source. It replaces the old URL
at sourceforge.net with the new one at gpleda.org.
$ git fetch
$ git reset --hard origin/master
$ ( do the edits)
$ git commit -a
$ git format-patch -1
The last command got me a file named 0001-replaces-...-org.patch whose
contents I attached below. Is this the way patches should be submitted?
---(kaimartin)---
Kai-Martin Knaak
Öffentlicher PGP-Schlüssel:
http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x6C0B9F53
---
From 6f0416253ccd6065c04b520b9add89e166b0a718 Mon Sep 17 00:00:00 2001
From: Kai-Martin Knaak k...@lilalaser.de
Date: Sat, 13 Mar 2010 17:52:09 +0100
Subject: [PATCH] replaces pcb.sourceforge.net with pcb.gpleda.org
---
README |5 ++---
doc/pcb.texi |5 ++---
src/main.c |2 +-
win32/Readme.txt |3 +--
4 files changed, 6 insertions(+), 9 deletions(-)
diff --git a/README b/README
index be006fd..9b9da9a 100644
--- a/README
+++ b/README
@@ -6,9 +6,8 @@ For additional information read the manual (doc/pcb.pdf)
If you are updating you may wish to read the ChangeLog
-There is also a bug tracking system and user forum available
-on the sourceforge project page which can be found from
-http://pcb.sourceforge.net.
+There is also a bug tracking system available which can
+be found from http://pcb.gpleda.org.
-
diff --git a/doc/pcb.texi b/doc/pcb.texi
index b1adb89..2eeaeb0 100644
--- a/doc/pcb.texi
+++ b/doc/pcb.texi
@@ -5274,9 +5274,8 @@ Centroid (X-Y) data for driving automated assembly
equipment.
@cindex xcircuit, how to interface with
If anyone cares to contribute this section, it will get added. Please
-submit changes to the bug tracking system at the sourceforge project
-page for PCB which can be found from the PCB homepage at
-...@url{http://pcb.sourceforge.net}.
+submit changes to the bug tracking system for PCB which can be found from
+the PCB homepage at @url{http://pcb.gpleda.org}.
@c --- Appendix A ---
diff --git a/src/main.c b/src/main.c
index a0b38f3..b25093e 100644
--- a/src/main.c
+++ b/src/main.c
@@ -246,7 +246,7 @@ usage (void)
n_exporter++;
}
- u (PCB Printed Circuit Board editing program, http://pcb.sourceforge.net;);
+ u (PCB Printed Circuit Board editing program, http://pcb.gpleda.org;);
u (%s [-h|-V|--copyright]\t\t\tHelp, version, copyright, Progname);
u (%s [gui options] pcb file\t\tto edit, Progname);
u (Available GUI hid%s:, n_gui == 1 ? : s);
diff --git a/win32/Readme.txt b/win32/Readme.txt
index 7d73a68..93273a4 100644
--- a/win32/Readme.txt
+++ b/win32/Readme.txt
@@ -4,8 +4,7 @@
This is the windows port of the pcb printed circuit board
layout editor.
-Please visit http://pcb.sourceforge.net for more information
-about PCB.
+Please visit http://pcb.gpleda.org for more information about PCB.
The windows port makes use of GTK+ for windows. Please visit
http://www.gtk.org for more information about GTK. Without all the hard
--
1.6.5
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb option --layer-stack
On Sat, 13 Mar 2010 11:12:13 -0500, DJ Delorie wrote: So this is another outdated snippet in the pcb manual: No, it just has a different purpose than you think. What purpose does it have? ---(kaimartin)--- -- Kai-Martin Knaak Öffentlicher PGP-Schlüssel: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x6C0B9F53 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: On integrating simulator in gschem
The question of integrating into gschem a simulator (namely gnucap) was recently discussed here. With the help of Ivan I'm writing a viewer, oscopy (http://repo.or.cz/w/oscopy.git) based draft #4 of this page: http://geda.seul.org/wiki/geda:data_plotting_improvements Although far from being completed, oscopy support running a netlister and a simulator, I mean there is a menu option FileRun netlister and simulate... where you can specify which command to use. It run both, and then automagically update the loaded signals, recursively for the maths-based ones. Since basic support for updating through DBus is also implemented, I wrote a small scheme script to integrate it within gschem, like pcb does. Maybe this could be a first start to what is described here: http://geda.seul.org/wiki/geda:circuit_simulation_improvements Arnaud. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: pcb option --layer-stack
What purpose does it have? It used to be used to build pcb's internal tables of actions etc. Now we use grep in the Makefile. It was never used for documentation. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: getting used to git (almost trivial pcb patch)
I can't see why it complains, but... maybe cr/lf or whitespace differences, which mail might have munged? Also, I had to cut the patch out of your email, perhaps it assumes the patch *is* the mail, rather than being *in* the mail? $ git am -s /tmp/foo Applying: replaces pcb.sourceforge.net with pcb.gpleda.org /envy/dj/geda/pcb-git/pcb/.git/rebase-apply/patch:20: trailing whitespace. be found from http://pcb.gpleda.org. error: patch failed: win32/Readme.txt:4 error: win32/Readme.txt: patch does not apply Patch failed at 0001 replaces pcb.sourceforge.net with pcb.gpleda.org When you have resolved this problem run git am --resolved. If you would prefer to skip this patch, instead run git am --skip. To restore the original branch and stop patching run git am --abort. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: getting used to git (almost trivial pcb patch)
DJ Delorie wrote: I can't see why it complains, but... maybe cr/lf or whitespace differences, which mail might have munged? the win32/Readme.txt file certainly is (and needs to remain) a DOS style file. It's a bit of a pain with non-DOS aware vi's but this file's purpose in life is to show up under the pcb start menu group in windows and be read by a curious windows user. -Dan ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
