Hi,
On Wednesday 25 April 2007 07:52, Transistor Toaster wrote:
I would like to know if there's a way in gschem I can select a bunch
of resistors components and give the whole group the same footprint?
Yes. Select the resistors (even with the nets around) and call the add
attribute dialog.
The polygon is cut into many polygons, such that there are no holes
that need to be erased.
So some of your polygons overlap?
I'm probably making a bigger deal out of this than I need to: I just have
this board that I helped redesign in PCB, and I want to make sure it's
right before I get it
Hi Gurus, I'm migrating (finally) to Fedora core 6. When I try to compile
the latest greatest from the cvs repo, I get:
checking for LIBGEDA... no
configure: error: libgeda detection error: No package 'libgeda' found
make: *** [gschem/config.h] Error 1
$ ls /opt/geda/lib
libgeda.a libgeda.la
On 5/6/07, Craig Niederberger wrote:
Hi Gurus, I'm migrating (finally) to Fedora core 6. When I try to compile
the latest greatest from the cvs repo, I get:
checking for LIBGEDA... no
configure: error: libgeda detection error: No package 'libgeda' found
make: *** [gschem/config.h] Error 1
$
Thanks super, Chitlesh, and thanks super for the work you put into posting
Fedora snapshots of gEDA. I still like to compile the cvs repo, as I've
discovered it has new features and bug fixes that can be really useful.
/opt/geda/lib is in my path:
$ echo $LD_LIBRARY_PATH
/opt/geda/lib:
Any
...and ironically enough, trying to yum install geda-* on this FC6 system,
installs just fine, but
$ gschem
[1] 18029
[EMAIL PROTECTED] archive]$ gEDA/gschem version 20070216
gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more details.
This is free software, and you are welcome
On Sun, 6 May 2007, Craig Niederberger wrote:
...and ironically enough, trying to yum install geda-* on this FC6 system,
installs just fine, but
$ gschem
[1] 18029
[EMAIL PROTECTED] archive]$ gEDA/gschem version 20070216
gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more
Thanks super, Stuart. I discovered that export
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/opt/geda/lib was haunting my system, and
sure enough, upon removal of that def, the yum install for gschem now
works. But being the inquisitive cvs repo I'd like to use the geda part
that I am, I'd *still* like
Craig --
[Snip!]
What I don't
understand is this: if I set
# export LD_LIBRARY_PATH=/opt/geda/lib:$LD_LIBRARY_PATH
# export PATH=/opt/geda/bin:${PATH}
# export PKG_CONFIG_PATH=/opt/geda/lib/pkgconfig:$PKG_CONFIG_PATH
as instructed by the make script, why doesn't
# make
# export
One other thing...
But being the inquisitive cvs repo I'd like to use the geda part
that I am, I'd *still* like to be able to compile the repo for geda/gaf for
FC6 that I did for FC5 (which annoyingly still happily works).
When you finally do get gEDA to build on your system, I recommend you
Just curious - I know you just had another code sprint / freedaug meeting;
does that usual correspond with a formal code/version release? Is there a
set time table or metrics on when the suite will have a formal version
upgrade?
Regards,
Kurt
So some of your polygons overlap?
When pcb cuts them up, they don't overlap - they but up against each
other. But you can create overlapping polygons and they're printed
overlapping.
I'm probably making a bigger deal out of this than I need to:
Yup.
I just have this board that I helped
Hi Folks!
I've completed my first pass at converting Bill Wilson's tutorial from
HTML syntax to dokuwiki syntax. It may be viewed at
http://www.geda.seul.org/wiki/playground:playground. I wrote a perl
script to do the conversion and have attached it for your
entertainment. I don't know if I
Just curious - I know you just had another code sprint / freedaug
meeting; does that usual correspond with a formal code/version
release? Is there a set time table or metrics on when the suite
will have a formal version upgrade?
Not formally. It may be more of a trigger, though. The last
Just curious - I know you just had another code sprint / freedaug meeting;
does that usual correspond with a formal code/version release? Is there a
set time table or metrics on when the suite will have a formal version
upgrade?
No fixed time table, and no strong correlation between Free Dog
15 matches
Mail list logo
