Re: gEDA-user: Blind and buried vias?
On Tue, Sep 29, 2009 at 05:21:16PM +, Kai-Martin Knaak wrote: On Tue, 29 Sep 2009 17:01:23 +, Michael Sokolov wrote: I'm told that the OMAP3430's Package-on-Package configuration requires at least six layers to get all the signals out. Ugh. OK, that explains the need for a lot of layers. But how does the need for blind/buried vias arise? The balls of the BGA occupy most of the real estate available on top layer. If all vias penetrate the hole stack, this occupation maps to all other layers too. Actually most often the top layer looks like a two interlaced grids: - one grid of pads to solder the balls, - one grid of vias that go allow to route the signals to other layers That's as long as you don't use exotic techniques like via-in-pad. Basically the two outermost rings of the BGA can be routed on the top layer (there is room for one trace between pads). The next two rings can be routed to the second copper layer with simple vias. But then every additional ring needs one layer if you don't have blind vias (buried vias are not necessary for BGA exit patterns), since there is only room for one trace between vias. With blind vias it is possible to route 2 rings per layer, and this adds up quite fast for large BGA. Of course there are also sometimes stupid packaging decisions by manufacturers, one example is the Spartan3A in BGA256 package where they decided to put some power connections on the second ring. The worst case: on the first ring it is easy to put a via just outside without blocking the exit for the second ring, from the third ring on you need a via anyway. Spartan2/2E in the same package did not have this stupid pinout. Therefore realistically blind vias for BGA exit patterns are only necessary for 20x20 matrices and larger (the center is often taken by power supplies which are easier to route). Gabriel ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Blind and buried vias?
I'm not sure why it's apparently irrelevant that the accepted predominant workflow is from gschem to pcb So what? What are all those other back ends for? Aren't they important? or that pcb is a member project of the geda project. If member projects and affiliated projects aren't considered part of gEDA then I'm curious as to what you define as gEDA and what topics you define as appropriate for this list. The issue isn't what topics are appropriate. The issue is keeping the interfaces clean and flexible. To do that, you have to remember what the interfaces are. What other backends? Are you referring to netlister and others? Most of them exist to modify schematic files to get it ready for a pcb. Otherwise I guess you could mean spice or other simulators. Either way, other backends are not particularly relevant to the discussion. The discussion was about why others consider pcb to be a part of gEDA. To keep the interfaces clean and flexible you have to remember what the interfaces are? I have no idea what you are trying to say. The OP said: What's the current and planned state of support for blind and/or buried vias in the gEDA system? That's like asking what's the state of support for driving Phillips head screws with a handsaw?. Another patronising analogy. I think last time you used a chainsaw. Pretty much everyone else on this list includes pcb in the geda name, those who don't know that others do. It's obvious from context what the question meant regardless of what your stance is on gEDA termi nology. I think that all things considered, your response was deliberately antagonistic. Currently, the gEDA project offers a mature suite of free softwareapplica tions for electronics design, including schematic capture, attribute management, bill of materials (BOM) generation, netlisting into over 20 netlist formats, analog and digital simulation, and printed circuit board (PCB) layout. I don't know who wrote that. gEDA and PCB are separate, independently developed projects. They have different source trees and conventions. They were not originally designed for each other. That they play well together is a testimony to the power of clean interface design. Let's not forget that, because if we do we will lose that power. It comes from the gEDA front page [1]http://www.gpleda.org/ That they play well is a testament to the fact that the netlister was written specifically for use with pcb and that the pcb project is affiliated with the gEDA project. [2]http://en.wikipedia.org/wiki/GEDA#History From the same wiki article: Loosely speaking, the term gEDA Suite refers to all [3]free software projects and applications that have voluntarily associated themselves with the gEDA Project via the geda-dev/geda-user mailing lists. These include: * gEDA/gaf - gschem and friends (the original project) * PCB - PCB layout program -- take note of this one * Gerbv - [4]Gerber file viewer * ngspice - a port of Berkeley [5]SPICE * GnuCap - A modern [6]electronic circuit simulation program * gspiceui - A [7]GUI front end for ngspice/GnuCap * gwave - An analog [8]waveform viewer * Icarus Verilog - A [9]Verilog simulator * GTKWave - A digital [10]waveform viewer * wcalc - [11]Transmission line and electromagnetic structure analysis Within the gEDA Suite, gEDA/gaf (gaf stands for gschem and friends) is the smaller subset of tools grouped together under the gEDA name and maintained directly by the gEDA project's founders. GEDA/gaf includes: * gschem - A [12]schematic capture program * gnetlist - A [13]netlist generation program * gsymcheck - A syntax checker for schematic symbols * gattrib - A [14]spreadsheet program for editing symbol attributes on a schematic. * libgeda - Libraries for gschem, gnetlist, and gsymcheck * gsch2pcb - Forward annotation from schematic to layout using pcb * Assorted utility programs Anyone who brings up a point about how geda/gaf/pcb could be more useful, more user friendly etc More useful and friendly to *what kind* of user? The kind that would prefer spending an hour mousing around to solve a problem once, or 15 minutes writing a script to solve it for all time? This is the line of argument I really have an issue with. I mean making it easier to use by someone who doesn't want to command line everything. For someone who likes to be able to use the program instead of spending all their time researching non-existent documentation. For someone who would like to have their program to have functions that are accessible, rather than have commands hidden away. You seem to assume that all users of gEDA are capable or want to write a script to solve a problem and that it takes an hour to find anything through a GUI interface. I
gEDA-user: Color PS output
Hi, I just tried to generate color Postscript output in both 1.5.2.20090328 and 1.5.4.20090830 and found that it won't work. Is anyone else having this problem? My gschemrc file has (output-color enabled) ; for color postscript output (image-color enabled) ; for color PNG output (enabled by default) copied from the wiki. Could someone please tell me what am I doing wrong here? -- http://evanfoss.googlepages.com/ ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Color PS output
On Sep 30, 2009, at 11:37 AM, evan foss wrote: I just tried to generate color Postscript output in both 1.5.2.20090328 and 1.5.4.20090830 and found that it won't work. Is anyone else having this problem? My gschemrc file has (output-color enabled) ; for color postscript output (image-color enabled) ; for color PNG output (enabled by default) copied from the wiki. Could someone please tell me what am I doing wrong here? Just a data point...I'm running 1.4.0.20080127 (still), and I get (beautiful!) color PS output with the above options. -Dave -- Dave McGuire Port Charlotte, FL ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Color PS output
Thank you. I will install that version too and run it to test my configuration. On Wed, Sep 30, 2009 at 3:58 PM, Dave McGuire mcgu...@neurotica.com wrote: On Sep 30, 2009, at 11:37 AM, evan foss wrote: I just tried to generate color Postscript output in both 1.5.2.20090328 and 1.5.4.20090830 and found that it won't work. Is anyone else having this problem? My gschemrc file has (output-color enabled) ; for color postscript output (image-color enabled) ; for color PNG output (enabled by default) copied from the wiki. Could someone please tell me what am I doing wrong here? Just a data point...I'm running 1.4.0.20080127 (still), and I get (beautiful!) color PS output with the above options. -Dave -- Dave McGuire Port Charlotte, FL ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user -- http://evanfoss.googlepages.com/ ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Color PS output
On Wed, 2009-09-30 at 15:37 +, evan foss wrote: Hi, I just tried to generate color Postscript output in both 1.5.2.20090328 and 1.5.4.20090830 and found that it won't work. Is anyone else having this problem? My gschemrc file has (output-color enabled) ; for color postscript output (image-color enabled) ; for color PNG output (enabled by default) copied from the wiki. Could someone please tell me what am I doing wrong here? Works fine for my Gentoo-Linux AMD64 test-installation 1.5.4. I have color for PNG output by default. After modifying the global gschemrc file I have color for eps and postscript output (print to file). Looks like screen display, black background. Tested with file examples/TwoStageAmp.sch. (I restarted gschem after I modified gschemrc) ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Color PS output
On Wed, Sep 30, 2009 at 10:07 AM, Stefan Salewski m...@ssalewski.de wrote: On Wed, 2009-09-30 at 15:37 +, evan foss wrote: Hi, I just tried to generate color Postscript output in both 1.5.2.20090328 and 1.5.4.20090830 and found that it won't work. Is anyone else having this problem? My gschemrc file has (output-color enabled) ; for color postscript output (image-color enabled) ; for color PNG output (enabled by default) copied from the wiki. Could someone please tell me what am I doing wrong here? Works fine for my Gentoo-Linux AMD64 test-installation 1.5.4. I have color for PNG output by default. After modifying the global gschemrc file I have color for eps and postscript output (print to file). Looks like screen display, black background. Tested with file examples/TwoStageAmp.sch. (I restarted gschem after I modified gschemrc) Is there a way to have the postscript output have a white background without changing the on-screen colors? Thanks, Matt ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Color PS output
On Wednesday 30 September 2009 16:37:52 evan foss wrote: Hi, I just tried to generate color Postscript output in both 1.5.2.20090328 and 1.5.4.20090830 and found that it won't work. Is anyone else having this problem? My gschemrc file has (output-color enabled) ; for color postscript output (image-color enabled) ; for color PNG output (enabled by default) copied from the wiki. Could someone please tell me what am I doing wrong here? As noted in the NEWS file (under 1.5.2 changes): * Major, *backwards-incompatible* changes to color handling in `libgeda' and `gschem'. - All colors are specified using hexadecimal `#RRGGBB' or `#RRGGBBAA' syntax. - The print and display color maps are now separate. - A new Scheme syntax is used to inspect and modify color maps. - If you wish to use a light background in `gschem', add the line: (load (build-path geda-rc-path gschem-colormap-lightbg)) to your personal or project gschemrc file. Changing the display colour map *intentionally* doesn't change the print colour map (so you can optimise the colours for each). Unfortunately, PNG output still uses the display colour map (this is due to the way PNG output is implemented). To change the colours printed, you should edit (or copy and edit) the 'print- colormap-lightbg' file, and then edit your gafrc file to load it. Look in the 'system-gafrc' to see how to do that. It should still be possible to swap between colour and BW printing using the same mechanisms as before 1.5.2. If this is broken, please file a bug report, including the gschemrc gafrc files you used. Thanks, Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre 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: Color PS output
On Wednesday 30 September 2009 19:35:06 Peter TB Brett wrote: On Wednesday 30 September 2009 16:37:52 evan foss wrote: Hi, I just tried to generate color Postscript output in both 1.5.2.20090328 and 1.5.4.20090830 and found that it won't work. Is anyone else having this problem? My gschemrc file has (output-color enabled) ; for color postscript output (image-color enabled) ; for color PNG output (enabled by default) copied from the wiki. Could someone please tell me what am I doing wrong here? It should still be possible to swap between colour and BW printing using the same mechanisms as before 1.5.2. If this is broken, please file a bug report, including the gschemrc gafrc files you used. Dang. It really is bust. *grumble* Thanks, Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre 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: Color PS output
On Wednesday 30 September 2009 20:00:52 Peter TB Brett wrote: On Wednesday 30 September 2009 19:35:06 Peter TB Brett wrote: On Wednesday 30 September 2009 16:37:52 evan foss wrote: Hi, I just tried to generate color Postscript output in both 1.5.2.20090328 and 1.5.4.20090830 and found that it won't work. Is anyone else having this problem? My gschemrc file has (output-color enabled) ; for color postscript output (image-color enabled) ; for color PNG output (enabled by default) copied from the wiki. Could someone please tell me what am I doing wrong here? It should still be possible to swap between colour and BW printing using the same mechanisms as before 1.5.2. If this is broken, please file a bug report, including the gschemrc gafrc files you used. Dang. It really is bust. *grumble* Okay, I managed to get it working by making sure that my (output-color enabled) line was in gschemrc rather than gafrc. Weird. Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre 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: Color PS output
On Wednesday 30 September 2009 19:14:18 Gareth Edwards wrote: 2009/9/30 Matt Ettus boysc...@gmail.com: Is there a way to have the postscript output have a white background without changing the on-screen colors? Thanks, Matt I couldn't get a white background even when I changed the on-screen colours - see my post from a week or two back. These black backgrounds are getting expensive to print Try adding the following to your gafrc: (load (build-path geda-rc-path print-colormap-lightbg)) As I mentioned in another e-mail, the print colours are *intentionall* decoupled from the display colours: what's comfortable to look at on-screen might not be as nice on paper. Regards, Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre 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: Color PS output
On Wed, 30 Sep 2009 20:32:43 +0100, Peter TB Brett wrote: Dang. It really is bust. *grumble* Okay, I managed to get it working by making sure that my (output-color enabled) line was in gschemrc rather than gafrc. Weird. May I suggest a GUI way to manage this kind of setting in the GUI? Preferably, as an overriding checkbox in the print dialog. In an environment with multiple printers, the color decision needs to be tuned on a case by case base. ---(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: Printing ps files
Is your printer capable of printing that close to the margins? Could you send me a copy of your .pcb file? ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Color PS output
On Wednesday 30 September 2009 21:23:06 Kai-Martin Knaak wrote: On Wed, 30 Sep 2009 20:32:43 +0100, Peter TB Brett wrote: Dang. It really is bust. *grumble* Okay, I managed to get it working by making sure that my (output-color enabled) line was in gschemrc rather than gafrc. Weird. May I suggest a GUI way to manage this kind of setting in the GUI? Can we just say, for setting in geda_settings: request_config_gui(setting, user=Kai-Martin Knaak) Look, we know it's a general problem -- it's just that no-one has the time and/or motivation to do the necessary work. Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre 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: Using the power instead of fighting it
On Sep 29, 2009, at 11:45 AM, Peter Clifton wrote: Ok, stop it guys, this is just too painful. pieces just don't work together very well. The mess of issues that arise between gschem and PCB are perhaps the most discussed, but all the parts I've had occasion to use feel more like a random collection of tools than a proper toolset - one size Phillips screwdriver, a couple of flat blades but none really small or really large, a hacksaw blade but you have to make your own frame for it... The individual parts are good quality, but... I just lost a whole toolbox full of lovely (high quality) new tools. They were on board the wave-rig I've spent the last 3 years working on - when it capsized last week... oops. (I was also on board some minutes before it went over!). Oh, sh*t. You have my sympathy. I know what it feels like. At some point the lost work and effort will dawn on me Been there. I've had two launch vehicle failures wreck years of work. But after awhile you realize that little has been lost, only hardware. The thinking that went into it is the real treasure, and that will inform your future work. Perhaps I'm still not that well adjusted on what matters though - I'm still more brothered about my lost tools than $scary_experience. ;) Well, by my standards that doesn't make you maladjusted. I'd feel pretty much the same. My close calls just become old war stories. It's my childrens' close calls that give me nightmares for awhile. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ j...@noqsi.com ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Color PS output
On Wed, Sep 30, 2009 at 8:30 PM, Peter TB Brett pe...@peter-b.co.uk wrote: On Wednesday 30 September 2009 21:23:06 Kai-Martin Knaak wrote: On Wed, 30 Sep 2009 20:32:43 +0100, Peter TB Brett wrote: Dang. It really is bust. *grumble* Okay, I managed to get it working by making sure that my (output-color enabled) line was in gschemrc rather than gafrc. Weird. May I suggest a GUI way to manage this kind of setting in the GUI? Can we just say, for setting in geda_settings: request_config_gui(setting, user=Kai-Martin Knaak) Look, we know it's a general problem -- it's just that no-one has the time and/or motivation to do the necessary work. I would be happy to have it stay text only. Otherwise the settings that get pulled in from the users .gschemrc and the projects .gschemrc will get confused with the global version. Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user -- http://evanfoss.googlepages.com/ ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Color PS output
On Wed, 30 Sep 2009 21:15:55 +, evan foss wrote: I would be happy to have it stay text only. Otherwise the settings that get pulled in from the users .gschemrc and the projects .gschemrc will get confused with the global version. That's why I suggested a temporary case-by-case override. The ~/pcb/preference vs ~/pcb/settings confusion is a warning example of what should better be avoided. ---(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
gEDA-user: Flexibility and capability
On Sep 30, 2009, at 2:29 AM, spuzzdawg wrote: I'm not sure why it's apparently irrelevant that the accepted predominant workflow is from gschem to pcb So what? What are all those other back ends for? Aren't they important? or that pcb is a member project of the geda project. If member projects and affiliated projects aren't considered part of gEDA then I'm curious as to what you define as gEDA and what topics you define as appropriate for this list. The issue isn't what topics are appropriate. The issue is keeping the interfaces clean and flexible. To do that, you have to remember what the interfaces are. What other backends? Are you referring to netlister and others? Most of them exist to modify schematic files to get it ready for a pcb. Yes and there are *many* ways to get from a set of gEDA schematics to a PCB. pcb is only one of them. The support for many paths is a great strength of gEDA, one of the things that make it superior to other toolkits. Otherwise I guess you could mean spice or other simulators. There are four working ASIC chip designs I created with gEDA. How do you suppose that happened? Either way, other backends are not particularly relevant to the discussion. No, they are *essential*, because they represent one of the things that makes gEDA special. And they give the lie to the notion that pcb limitations are gEDA limitations. The discussion was about why others consider pcb to be a part of gEDA. To keep the interfaces clean and flexible you have to remember what the interfaces are? I have no idea what you are trying to say. Don't treat gEDA/pcb as just another integrated tool. The world is infested with those. Remember that gEDA is better because, with its clean interfaces, it can work with other toolkits. To a lesser extent that true of pcb, too (as we have heard from an xcircuit user). The OP said: What's the current and planned state of support for blind and/or buried vias in the gEDA system? That's like asking what's the state of support for driving Phillips head screws with a handsaw?. Another patronising analogy. I think last time you used a chainsaw. Pretty much everyone else on this list includes pcb in the geda name, those who don't know that ^^^ That's almost certainly because pcb doesn't have its own list. I have the impression that users have a lot more questions about pcb than gEDA, so the list is dominated by pcb-centric concerns. others do. It's obvious from context what the question meant regardless of what your stance is on gEDA terminology. I think that all things considered, your response was deliberately antagonistic. *You* call *me* antagonistic? Come on, now. The question implied a limitation in gEDA. There is no such limitation. Is is good to allow such misinformation to tar gEDA's reputation? Currently, the gEDA project offers a mature suite of free softwareapplications for electronics design, including schematic capture, attribute management, bill of materials (BOM) generation, netlisting into over 20 netlist formats, analog and digital simulation, and printed circuit board (PCB) layout. I don't know who wrote that. gEDA and PCB are separate, independently developed projects. They have different source trees and conventions. They were not originally designed for each other. That they play well together is a testimony to the power of clean interface design. Let's not forget that, because if we do we will lose that power. It comes from the gEDA front page http://www.gpleda.org/ That they play well is a testament to the fact that the netlister was written specifically for use with pcb Nope. gsch2pcb was written for pcb, but gnetlist is a nice, clean, pretty neutral general-purpose tool. I see no pcb-specific code at all in gnetlist outside of the pcb back end. If anything, gnetlist is specialized for Verilog: there is some undocumented Verilog-specific code in the front end, and if we ever actually get around to refactoring gnetlist, that should be moved to the back end, and the back end data access limitations that pushed that stuff into the front repaired. and that the pcb project is affiliated with the gEDA project. http://en.wikipedia.org/wiki/GEDA#History If you look in the dictionary, affiliated does not mean the same or a part of. From the same wiki article: Loosely speaking, the term gEDA Suite refers to all free software projects and applications that have voluntarily associated themselves with the gEDA Project via the geda-dev/geda-user mailing lists. These include: gEDA/gaf - gschem and friends (the original project) PCB - PCB layout program -- take note of this one Gerbv - Gerber file viewer ngspice - a port of Berkeley SPICE GnuCap - A modern electronic circuit simulation program gspiceui - A GUI front
Re: gEDA-user: Flexibility and capability
John Doty j...@noqsi.com wrote: To a lesser extent that true of pcb, too (as we have heard from an xcircuit user). And a uEDA user too! My first PCB laid out by Ineiev in GNU PCB from my uschem schematics is currently being fabbed. MS ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Flexibility and capability
On Sep 30, 2009, at 10:05 PM, Michael Sokolov wrote: John Doty j...@noqsi.com wrote: To a lesser extent that true of pcb, too (as we have heard from an xcircuit user). And a uEDA user too! My first PCB laid out by Ineiev in GNU PCB from my uschem schematics is currently being fabbed. Cool! John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ j...@noqsi.com ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: [spicelib] how to run the tests ?
Probably you need to do this: edit scripts/geda-parts.scm and fix the path to your repository. If it still doesn't work, send me the output, both to the terminal and the html, of scripts/testlibrary -p indexfiles/nxp_diodes.index BAS116H_NXP01004 -Alan On 9/26/09, Bert Timmerman bert.timmer...@xs4all.nl wrote: Hi Werner and Alan, I just re-forked/re-cloned spicelib on github.com from Werners repository. Getting and installing the models with make all just seems to work. Running make test does run the test script, but all tests seem to fail. I think I need to do something in between make all and make test but can't find any clues in the README or doc/index.html. Can you give me any clues what to do ? Kind regards, Bert Timmerman. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Color PS output
On Wed, Sep 30, 2009 at 11:35 AM, Peter TB Brett pe...@peter-b.co.uk wrote: On Wednesday 30 September 2009 16:37:52 evan foss wrote: Hi, I just tried to generate color Postscript output in both 1.5.2.20090328 and 1.5.4.20090830 and found that it won't work. Is anyone else having this problem? My gschemrc file has (output-color enabled) ; for color postscript output (image-color enabled) ; for color PNG output (enabled by default) copied from the wiki. Could someone please tell me what am I doing wrong here? As noted in the NEWS file (under 1.5.2 changes): * Major, *backwards-incompatible* changes to color handling in `libgeda' and `gschem'. - All colors are specified using hexadecimal `#RRGGBB' or `#RRGGBBAA' syntax. - The print and display color maps are now separate. - A new Scheme syntax is used to inspect and modify color maps. - If you wish to use a light background in `gschem', add the line: (load (build-path geda-rc-path gschem-colormap-lightbg)) to your personal or project gschemrc file. Changing the display colour map *intentionally* doesn't change the print colour map (so you can optimise the colours for each). Unfortunately, PNG output still uses the display colour map (this is due to the way PNG output is implemented). To change the colours printed, you should edit (or copy and edit) the 'print- colormap-lightbg' file, and then edit your gafrc file to load it. Look in the 'system-gafrc' to see how to do that. It should still be possible to swap between colour and BW printing using the same mechanisms as before 1.5.2. If this is broken, please file a bug report, including the gschemrc gafrc files you used. Thanks, that worked perfectly. Matt ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
