I'm starting to dig through the PCB source - just a quick survey for
those who hack on the source code: what do you use for debugging and
development of the project?
Same as any other program I'm hacking on: gdb (and/or printfs) for
debugging, usually my favourite text editor (a non-GNU emacs,
Thanks DJ. I will look into this. If I go the scripting route would
Python be ok? For the plug-in route are there some pointers to show how
to go about creating a plug-in?
On Thu, 2009-02-05 at 00:21 -0500, DJ Delorie wrote:
Nothing at the moment, but if it's a documented text file, you could
If I go the scripting route would Python be ok?
Use whatever you want.
For the plug-in route are there some pointers to show how to go
about creating a plug-in?
Search the mail archives for plugin and you should find a number of
examples.
Am Mittwoch, den 04.02.2009, 23:30 +0100 schrieb Levente Kovacs:
I would like to print labels. For this I'd generate N times some labels, with
slight different content. Then I have N *.eps file.
Question. How do I merge them into one A4 postscript page?
Options I have so far.
* LaTex.
I'm pleased to announce the release of an update to Gwave, a viewer for
analog waveform data such as that produced by gnucap and other spice-like
simulators.
Downloads available from:
http://sourceforge.net/project/showfiles.php?group_id=211903package_id=261599release_id=655985
This update
Oliver Lehmann wrote:
Stefan Salewski wrote:
My one, shipped with gEDA 1.4.3 is tragesym version 0.0.12
and dist-license and use-license is supported.
FreeBSD ports come with geda 20070216 which is probably a
svn/cvs/whatever ;) checkout. And yeah - sounds old
I've added the license
6 matches
Mail list logo
