On Wed, 2009-01-14 at 21:08 -0500, Ales Hvezda wrote:
[snip]
AC_LIBTOOL_WIN32_DLL
AM_PROG_LIBTOOL
I didn't try the AC_LIBTOOL_WIN32_DLL line, but I did revert
back to the original AM_PROG_LIBTOOL only line.
I'd very much appreciate if someone else (it worked for me) could test
if
On Thu, 2009-01-15 at 02:56 +, Kai-Martin Knaak wrote:
So I tried the next recipe:
AC_LIBTOOL_WIN32_DLL
AM_PROG_LIBTOOL
With these options the current git-head compiled and installed fine.
Thanks for the detailed advice.
Ok, thanks for the info! (Didn't spot that before I
I'd very much appreciate if someone else (it worked for me) could test
if adding AC_LIBTOOL_WIN32_DLL before the AM_PROG_LIBTOOL line works
without damaging the Linux / Unix build on older libtools.
Everything builds OK for me with this change. Unfortunately not on old
libttools (Ubuntu
Hello all,
I have just 2 question. I use last version of PCB on Windows and would like
following features - if it is possible (maybe on Linux it already works) :
- free arcs - now it is possible just quarter of circle. But I can do ellipse
in PCB source files by manual edit. Can I define just
Hello,
I am trying to create a simbol for LM6142 (dual opamp). But when I
place it into a schematic, and try to declare slot=2, the pin numbers
are not changing.
Here is the sym file (I hope it will not be truncated):
BOF
v 20081231 1
L 200 800 200 0 3 0 0 0 -1 -1
L 200 0 800 400 3 0 0 0 -1 -1
Hi DJ,
I have the link to your pictures of you making a pcb at:
[1]http://geda.seul.org/projects/djs_pcbs/
I was wondering do you have written directions, not that the pictures
aren't self explanitory, that go along with it? Or should I go by
Direct Etch PCB's website? I
[snip]
I have the link to your pictures of you making a pcb at:
[1]http://geda.seul.org/projects/djs_pcbs/
I was wondering do you have written directions, not that the pictures
aren't self explanitory, that go along with it? Or should I go by
Direct Etch PCB's website? I
Is it pretty much just following the pictures or is there some trick I
should know?
On Fri, Jan 16, 2009 at 10:57 AM, Ales Hvezda [1]ahve...@gmail.com
wrote:
[snip]
I have the link to your pictures of you making a pcb at:
- free arcs - now it is possible just quarter of circle. But I can
do ellipse in PCB source files by manual edit. Can I define just
endpoints by clicking on canvas ?
Not at this time.
- puller - I found it on DJ Delorie's page. Feature looks very good
but seems not yet in the main
I was wondering do you have written directions, not that the pictures aren't
self explanitory, that go along with it? Or should I go by Direct Etch
PCB's website? I thought I'd check before trying it.
My technique, as shown, is not really much different than what is
documented online. You
Oliver Lehmann oli...@freebsd.org writes:
Have you tried my two uploaded examples?
Both render in landscape for me, in the PS files. One is auto-rotated
by ps2pdf, but for both, the print is properly rotated with respect to
the page it's rendered on.
John Doty wrote:
On Jan 16, 2009, at 7:22 AM, Robas, Teodor wrote:
Hello,
I am trying to create a simbol for LM6142 (dual opamp). But when I
place it into a schematic, and try to declare slot=2, the pin numbers
are not changing.
Several problems.
1. You have your pinseq= attributes
On Fri, 16 Jan 2009 13:09:00 +, Peter Clifton wrote:
The new colour map syntax Peter B introduced after 1.5.1 requires a
different line:
(load (build-path geda-rc-path gschem-colormap-lightbg)) ; light
background
We could provide a gschem-lightbg.scm available to make this backwards
On Fri, 2009-01-16 at 13:18 +, gdedwa...@blueyonder.co.uk wrote:
I'd very much appreciate if someone else (it worked for me) could test
if adding AC_LIBTOOL_WIN32_DLL before the AM_PROG_LIBTOOL line works
without damaging the Linux / Unix build on older libtools.
Everything builds
On Fri, 2009-01-16 at 16:57 +, Kai-Martin Knaak wrote:
On Fri, 16 Jan 2009 13:09:00 +, Peter Clifton wrote:
The new colour map syntax Peter B introduced after 1.5.1 requires a
different line:
(load (build-path geda-rc-path gschem-colormap-lightbg)) ; light
background
We
On Mon, 2007-09-24 at 08:59 +0530, Ramakrishnan Muthukrishnan wrote:
Hi,
I am trying to create a gschem symbol for an Opamp IC. One of the pins
on that IC is usually unconnected, so I didn't have a pin for it in
the gschem symbol. But I get a warning from gsymcheck saying tha the
number of
On Thu, 2009-01-15 at 16:21 -0500, DJ Delorie wrote:
But just to make sure that it doesn't ride on the edge at least
I'd try some rapid load changes.
Good idea. Hey - a flashlight bulb makes a handy 0.9A 5V load! Nope,
no problems, and pretty good regulation.
One of these days I'm
On Thu, 15 Jan 2009 13:44:24 -0800
Joerg joerg...@analogconsultants.com
wrote:
Levente Kovacs wrote:
On Wed, 14 Jan 2009 18:12:07 -0800
Joerg joerg...@analogconsultants.com
wrote:
Levente Kovacs wrote:
Hi,
My temperature sensor/logger finaly works!
http://logonex.eu/tc/
On Fri, 2009-01-16 at 01:11 -0500, DJ Delorie wrote:
I run this command:
gschem -p -o ethernet.ps -s ./print.scm ethernet.sch
with this script:
[snip]
; light background
(load /envy/dj/geda/share/gEDA/gschem-lightbg)
Syntax for that has changed in git HEAD since the last release. Did
Not digital, but this is similar to a load circuit I built in the lab.
Yeah, something like that.
Kudos to email-able schematics :-)
The actual circuit ended up with most of RLoad in the emitters of
the FETs to ensure better balancing.
Did your FETs have positive or negative thermal
DJ Delorie wrote:
My technique, as shown, is not really much different than what is
documented online. You can read pretty much any toner-transfer
description and follow along with my photos.
Note, however, that I've switched to using photofilm and CuCl etchant,
so I don't actually use the
That tin plate solution is really old or you didn't clean the board
right ...
I just forgot to rinse it after plating, that's all. It works fine
all the other times.
And worst is that old thing CuCl, you are buying copper to etch copper
and drain twice the copper way.
Except that I
On Fri, 2009-01-16 at 12:30 -0500, DJ Delorie wrote:
Not digital, but this is similar to a load circuit I built in the lab.
Yeah, something like that.
Kudos to email-able schematics :-)
The actual circuit ended up with most of RLoad in the emitters of
the FETs to ensure better
On Fri, 2009-01-16 at 12:31 -0500, DJ Delorie wrote:
Executing guile script [./print.scm]
In unknown file:
?: 0* [primitive-load /envy/dj/geda/share/gEDA/gschem-lightbg]
In /envy/dj/geda/share/gEDA/gschem-lightbg:
60: 1* (background-color 0 grey94 null 1 1 1)
On Friday 16 January 2009 13:09:00 Peter Clifton wrote:
When started gschem presents a GUI with a black background, although my
local gsemrc configures a light background with the line
(load (build-path geda-rc-path gschem-lightbg))
The new colour map syntax Peter B introduced after
On Thu, 2009-01-15 at 06:42 +, Kai-Martin Knaak wrote:
On Wed, 14 Jan 2009 23:32:50 -0600, Kipton Moravec wrote:
It looks like if the part already has a number, neither renumber program
touches it. That is good in most cases, but not in my case. Is there a
secret way to force a
On Friday 16 January 2009 17:56:56 Peter Clifton wrote:
On Fri, 2009-01-16 at 12:31 -0500, DJ Delorie wrote:
Executing guile script [./print.scm]
In unknown file:
?: 0* [primitive-load /envy/dj/geda/share/gEDA/gschem-lightbg]
In /envy/dj/geda/share/gEDA/gschem-lightbg:
60: 1*
Ah, switching to loading the new scheme file works.
However, the print doesn't match the schematics...
http://www.delorie.com/electronics/powermeter/
Compare powermeter.pdf to channel.sch... (channel.ps in my build dir
matches the pdf):
R10, R11, R12, R14, R15 values are not printed. Other
it's called the knack.
http://www.youtube.com/watch?v=CmYDgncMhXw
:-)
On Jan 15, 2009, at 8:50 PM, Steve Meier wrote:
or in DJ's case I
think he just can't help but be creative
___
geda-user mailing list
geda-user@moria.seul.org
DJ Delorie wrote:
Oliver Lehmann oli...@freebsd.org writes:
Have you tried my two uploaded examples?
Both render in landscape for me, in the PS files. One is auto-rotated
by ps2pdf, but for both, the print is properly rotated with respect to
the page it's rendered on.
yeah - you are
it's called the knack.
http://www.youtube.com/watch?v=CmYDgncMhXw
Yup, that's me, although my social skills have improved over the
years.
My mom tells this story about when I was a little tike... We had two
TVs in the house, one working, one broken. One night she heard noises
I'm not sure how to fix the ps2pdf step, but the latest acroread
knows how to auto-rotate pages to fit the printed paper. I suspect
ps2pdf looks for which way text is oriented... pcb doesn't have this
problem, but it always prints something at the bottom of each page.
The auto rotate tries to use the orientation of text the most of the
test on the page, auto rotate may want to be turned off for your runs
I have hit this problem with postscripts files before, so i usually
force the pages to landscape in ps2pdf
here are some tips. i also hit similar
On Fri, Jan 16, 2009 at 1:00 PM, DJ Delorie d...@delorie.com wrote:
I'm not sure how to fix the ps2pdf step, but the latest acroread
knows how to auto-rotate pages to fit the printed paper. I suspect
ps2pdf looks for which way text is oriented... pcb doesn't have this
problem, but it always
it should be this option
-dAutoRotatePages=/None
On Jan 16, 2009, at 11:00 AM, DJ Delorie wrote:
I'm not sure how to fix the ps2pdf step, but the latest acroread
knows how to auto-rotate pages to fit the printed paper. I suspect
ps2pdf looks for which way text is oriented... pcb
When I was 4 my parents gave me a real screwdriver set for
Christmas.
I took apart the telephone in the basement 2 or three times before
they found out I was taking it apart and putting it back together.
They only found out that I was taking it apart, when i decided to use
dad's wire
Steven Michalske wrote:
-dAutoRotatePages=/None
I used -dAutoRotatePages=/All now
It looks like /All worked because then ps2pdf detects the orientation
only once and then rotates all the pages to the same orientation? This is
what I'm guessing. And because my 1st page is rotated well the
Looks like page 13 has lots of rotated text. that probably
confused the auto rotator.
:-)
On Jan 16, 2009, at 11:21 AM, Oliver Lehmann wrote:
Steven Michalske wrote:
-dAutoRotatePages=/None
I used -dAutoRotatePages=/All now
It looks like /All worked because then ps2pdf detects the
Steve Meier wrote:
Do either of you think that one size shoe should fit all peoples feet?
No, but it seems this thread shows two different sizes. The rest would
mostly be in between :-)
The market place of jobs will have opportunities for specialists and for
generalists and for ranges in
Levente Kovacs wrote:
On Thu, 15 Jan 2009 13:44:24 -0800
Joerg joerg...@analogconsultants.com
wrote:
Levente Kovacs wrote:
On Wed, 14 Jan 2009 18:12:07 -0800
Joerg joerg...@analogconsultants.com
wrote:
Levente Kovacs wrote:
Hi,
My temperature sensor/logger finaly works!
Am Freitag, den 16.01.2009, 19:56 +0100 schrieb Oliver Lehmann:
yeah - you are completly right - the PS files are fine - its a
autorotation problem of ps2pdf (respectively ghostscript) - sorry that
I've not understood you in the first place or having seen this by my
self...
If you are
On Jan 16, 2009, at 1:46 PM, Joerg wrote:
Steve Meier wrote:
Do either of you think that one size shoe should fit all peoples
feet?
No, but it seems this thread shows two different sizes. The rest would
mostly be in between :-)
gEDA belongs to the software user's tradition, not to the
The generalist will be at a disadvantage when faced with a task
that pushes state of the art for a specific field.
Absolutely not. The generalist has a huge advantage, because at the
cutting edge there is no specific field, only a problem to be
solved. To truly push the state of the art
On Friday 16 January 2009, Steven Michalske wrote:
it's called the knack.
http://www.youtube.com/watch?v=CmYDgncMhXw
:-)
Chuckle, I was wondering when somebody would make a video out of that classic.
Thanks for the link, bookmarked for future use. :)
On Jan 15, 2009, at 8:50 PM, Steve
I think this discussion has gone on for long enough without input from
the core developers. As one of them, I add this, hoping to appease
both sides and not scare away any potential users/contributors...
gEDA/PCB should be flexible for those who need flexibility, and easy
to use for those who
On Jan 16, 2009, at 3:00 PM, der Mouse wrote:
The generalist will be at a disadvantage when faced with a task
that pushes state of the art for a specific field.
Absolutely not. The generalist has a huge advantage, because at the
cutting edge there is no specific field, only a problem to be
Hi all,
I have a few mostly-unrelated proposals that I hoped people might to
hear about. These might be suitable for implementation in the 1.7
development series.
1. Non-Turing-complete configuration files.
2. Plugin system.
3. Embedding system revamp.
4. New window functionality.
5.
Currently, the gEDA configuration files are executed by a Scheme
interpreter. This has a number of flaws:
1. An error in a configuration file will cause it not to be fully
interpreted. This can potentially leave gEDA applications in an
unusable state or even cause it not to start at all.
Currently, Scheme is the only available extension language for
gEDA. However, in future it may be desirable to extend gEDA apps in
other languages, including possibly as native code loaded from .so
files.
Furthermore, if configuration files are no longer executable (see
previous e-mail), some
gEDA currently allows symbols or pictures to be embedded in a
schematic. However, the current embedding system requires the full
data to be embedded for each instance of an embedded item.
This has a number of shortcomings:
1. It bloats filesize by requiring multiple redundant copies of the same
The New window functiona in gschem is getting in my way (for a variety
of rather technical reasons that I can go into if someone really wants
me to). [*]
Does anyone actually use this? Will anyone miss it enormously if it is
removed? If it shouldn't be removed, could it be sufficiently replaced
Currently, if you 'copy' in gschem and 'paste' in another program,
nothing useful happens. We should ideally try and use the X
clipboard.
I propose that we enable (in the following order):
1. Copy in gschem, paste in text editor. Should it paste schematic file
source code equivalent to
Currently, running any gEDA suite program leaves behind a log file in
the current working directory. I would like to change the default to not
generating log files, so that I (and other users who use the default
configuration) don't end up with gschem.log and gnetlist.log files
scattered over
I needed a Gantt chart for a project report, so I drew one in gschem.
gantt.sch
Description: Gantt chart
Oh, the strange things one can achieve with gEDA! (BTW, Cairo gschem
looks feels amazing, and Peter C. deserves donations towards his
secret evil mastermind laboratory/bunker).
This is an excellent idea.
On Jan 16, 2009, at 3:44 PM, Peter TB Brett wrote:
Currently, the gEDA configuration files are executed by a Scheme
interpreter. This has a number of flaws:
1. An error in a configuration file will cause it not to be fully
interpreted. This can potentially
On Jan 16, 2009, at 3:45 PM, Peter TB Brett wrote:
The New window functiona in gschem is getting in my way (for a
variety
of rather technical reasons that I can go into if someone really wants
me to). [*]
Does anyone actually use this?
Yes.
Will anyone miss it enormously if it is
On Friday 16 January 2009 23:11:18 John Doty wrote:
Will anyone miss it enormously if it is
removed?
Well, I sometimes use it when doing cut/paste between pages. Not too
often. Won't blight my life if it goes away.
If it shouldn't be removed, could it be sufficiently replaced
by
On Jan 16, 2009, at 3:45 PM, Peter TB Brett wrote:
Currently, if you 'copy' in gschem and 'paste' in another program,
nothing useful happens. We should ideally try and use the X
clipboard.
I propose that we enable (in the following order):
1. Copy in gschem, paste in text editor. Should
On Jan 16, 2009, at 3:54 PM, Peter TB Brett wrote:
Oh, the strange things one can achieve with gEDA!
Yep. The difference between user software and consumer software.
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
j...@noqsi.com
Better would be to have the plugin itself have some well-known
function that registers itself, like pcb's plugins do. Thus, all you
really have to do is dl_open() any .so's you find, and call their
well-known function.
___
geda-user mailing list
It would be really cool if you could cut/copy in gschem, and paste in
*pcb*, and have the right footprint show up.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
On Friday 16 January 2009 23:21:19 DJ Delorie wrote:
Better would be to have the plugin itself have some well-known
function that registers itself, like pcb's plugins do. Thus, all you
really have to do is dl_open() any .so's you find, and call their
well-known function.
Having been stung by
On Fri, January 16, 2009 5:45 pm, Peter TB Brett wrote:
Currently, running any gEDA suite program leaves behind a log file in
the current working directory. I would like to change the default to not
generating log files, so that I (and other users who use the default
configuration) don't end
On Friday 16 January 2009 23:35:22 DJ Delorie wrote:
Having been stung by this in the past, I would prefer the majority
of plugins to be opt-in than opt-out (i.e. loaded only when the
current project needs to use them).
The counter-sting is trying to automatically install N plugins, each
Sure. Any ideas how to get the best of both worlds?
If the problem is to avoid loading the wrong plugins, there
are some options:
1. separate subdirs for each plugin type
2. the well-known function name can differ from app to app
3. let the user choose which ones to put in the subdir like
Sure. Any ideas how to get the best of both worlds?
Another option is to include a blacklist in your personal config, so
that the default is load all but you can explicitly deny those that
are problematic, without (1) having to list all other plugins
somewhere, or (2) having to uninstall a
On Fri, 2009-01-16 at 18:35 -0500, DJ Delorie wrote:
Having been stung by this in the past, I would prefer the majority
of plugins to be opt-in than opt-out (i.e. loaded only when the
current project needs to use them).
The counter-sting is trying to automatically install N plugins, each
On Fri, 2009-01-16 at 18:50 -0500, DJ Delorie wrote:
Most apps just pre-load any available plugins, though.
Loading them is one thing, but enabling is completely another.
I think they should automatically be enumerated when they are found,
queried for text / description / a graphic even? to
On Fri, Jan 16, 2009 at 10:44 PM, Peter TB Brett pe...@peter-b.co.uk wrote:
Currently, the gEDA configuration files are executed by a Scheme
interpreter. This has a number of flaws:
1. An error in a configuration file will cause it not to be fully
interpreted. This can potentially leave
On Friday 16 January 2009, Peter TB Brett wrote:
On Friday 16 January 2009 23:21:19 DJ Delorie wrote:
Better would be to have the plugin itself have some
well-known function that registers itself, like pcb's
plugins do. Thus, all you really have to do is dl_open()
any .so's you find, and
It is my impression that the PCB plugin system is almost the same,
except that the well-known function is used instead of static
constructors.
I originally did it with constructors, but to do it in C required a
gcc extension. So I changed it.
Should plugins use the .so extension, (or is
KISS says
key = value \n
next key = its value \n
anything can parse this simple format
an unknown key is a warning,
On Jan 16, 2009, at 2:44 PM, Peter TB Brett wrote:
Currently, the gEDA configuration files are executed by a Scheme
interpreter. This has a number of flaws:
1. An error in
On Saturday 17 January 2009 00:08:17 r wrote:
On Fri, Jan 16, 2009 at 10:44 PM, Peter TB Brett pe...@peter-b.co.uk
wrote:
Currently, the gEDA configuration files are executed by a Scheme
interpreter. This has a number of flaws:
1. An error in a configuration file will cause it not to be
On Saturday 17 January 2009 00:15:46 Steven Michalske wrote:
KISS says
key = value \n
next key = its value \n
anything can parse this simple format
an unknown key is a warning,
I don't see how this is any different from:
(key value)
Except that in the case of using a Scheme-like syntax:
On Saturday 17 January 2009 00:10:54 al davis wrote:
Should plugins use the .so extension, (or is that .dll) which
is system dependent, or should they use another extension that
is application specific but consistent across systems?
Everyone is fixating on link-library plugins, but don't
On Fri, 2009-01-16 at 11:04 -0500, Rob Butts wrote:
Is it pretty much just following the pictures or is there some trick I
should know?
Just follow the pictures, though DJ luck is much better than mine. I
have a laminator, etching tank and 4 litre bottle of enchant that I've
been trying to
On Jan 16, 2009, at 5:25 PM, Peter TB Brett wrote:
On Saturday 17 January 2009 00:15:46 Steven Michalske wrote:
KISS says
key = value \n
next key = its value \n
anything can parse this simple format
an unknown key is a warning,
I don't see how this is any different from:
(key value)
On Fri, Jan 16, 2009 at 10:44 PM, Peter TB Brett pe...@peter-b.co.uk wrote:
Currently, Scheme is the only available extension language for
gEDA. However, in future it may be desirable to extend gEDA apps in
other languages, including possibly as native code loaded from .so
files.
Extending
Ales surprised me at the code sprint by calling me a heavy symbol
advocate. Let me try to make clear my real position.
The question is not light versus heavy, but where to put the
mass so it doesn't become a burden, especially for design reuse.
The more I use gEDA, the more this is an issue
hmmm, isn't problem info being logged. I would agree if during the
current run the logfile only included warnings.
how about if at the end of execution that if there was a problem of some
class detected that the user be asked if the log file should be
retained?
On Fri, 2009-01-16 at 18:32
On Jan 16, 2009, at 7:40 PM, Steve Meier wrote:
footprint and netlist
gschem (correctly IMNSHO) doesn't even know what these are, as they
depend on which flow you're using.
A program should do one thing well. Netlisting and layout are not
the charter of a schematic capture program.
A program should do one thing well. Netlisting and layout are not
the charter of a schematic capture program.
But 90% of the common users expect obvious things to work. Cutting
and pasting between applications should just work. The gEDA+pcb
flow should just work. Yes, there will be power
On Jan 16, 2009, at 7:43 PM, Steve Meier wrote:
hmmm, isn't problem info being logged. I would agree if during the
current run the logfile only included warnings.
how about if at the end of execution that if there was a problem of
some
class detected that the user be asked if the log
On Jan 16, 2009, at 7:52 PM, DJ Delorie wrote:
A program should do one thing well. Netlisting and layout are not
the charter of a schematic capture program.
But 90% of the common users expect obvious things to work. Cutting
and pasting between applications should just work. The gEDA+pcb
A program should do one thing well. Capturing circuit information
(regardless of what that is) and providing that to a layout system
(regardless of what *that* is) is that one thing here.
As stated by you, that's two things.
Sigh. I'll try to word it as one thing. Be a design capture
To me the idea of a app.log associated with a project is that if some
step in the project goes GAK I would like to know why.
For example I modified an altera project and built it and in doing
so generated a fubar.ptf file which I then put onto a memory stick and
moved fubar.ptf from a windo$e
DJ Delorie wrote:
Except that I *don't* drain it - that's the best part of CuCl is that
it's air regenerated, there's NO waste at all. The copper in solution
came from other boards I'd etched (you start with an HCl/H2O2 etchant
and slowly convert it).
Right. If you do enough CuCl etching
On Jan 16, 2009, at 8:48 PM, DJ Delorie wrote:
A program should do one thing well. Capturing circuit information
(regardless of what that is) and providing that to a layout system
(regardless of what *that* is) is that one thing here.
As stated by you, that's two things.
Sigh. I'll try
John,
For a simulator, wouldn't you want to select a section of a schematic
and say simulate this?
I think, thinking about scenarios leads to requirements. So to say be
able to select an area of a schematic and then transmute that schematic
section into the needs of the next application.
If the
On Jan 16, 2009, at 9:34 PM, Steve Meier wrote:
For a simulator, wouldn't you want to select a section of a schematic
and say simulate this?
I'd love it, but that's beyond the state of the art for AI. In
practice, simulation requires a lot of thought in the design of the
test fixture.
On Fri, 2009-01-16 at 21:37 -0700, John Doty wrote:
On Jan 16, 2009, at 9:09 PM, Steve Meier wrote:
To me the idea of a app.log associated with a project is that if some
step in the project goes GAK I would like to know why.
The basic problem is that the software's point of view is not
or will pcb support ASIC layouts in the future?
I don't expect so, but I don't see how that relates to what gschem is.
Furthermore, we want gschem to be a front-end for simulation
systems.
I'll lump simulator in with other layout systems then. If I had a
word that meant all those things
Frankly, I'm more than happy to remove local log files in the clean
targets of my per-project makefiles.
Normally, me too, but it puts them in the symbol directories if you
edit a symbol, and any script that uses gschem to print a schematic
leaves one behind, etc. They're messy.
On Saturday 17 January 2009 02:43:44 Steve Meier wrote:
hmmm, isn't problem info being logged. I would agree if during the
current run the logfile only included warnings.
99+% of the time, the log doesn't contain anything other than a
copywrite/no-warranty notice and a list of files loaded.
On Saturday 17 January 2009 01:24:52 r wrote:
On Fri, Jan 16, 2009 at 10:44 PM, Peter TB Brett pe...@peter-b.co.uk
wrote:
Currently, Scheme is the only available extension language for
gEDA. However, in future it may be desirable to extend gEDA apps in
other languages, including possibly
95 matches
Mail list logo
