> > Would anyone be opposed to having the netlister assume a :1 for net=
> > attributes without a colon?
> There was a patch for this available, but it did not make it in the
> official code.
I would love it if I didn't need the :1 on netlist names. Right now I
do not have :1 on my net names, and
plete
without the dreaded "Gtk-WARNING **: cannot open display". In my case
I am trying to do the above on a machine I don't have root access on,
where there's already a display server running on :0, so I just picked
a random other display to run Xvfb on.
- Miles
On Tue, May 2
I have this same problem, because I automate my build with makefiles,
and I'd like to have a build machine (that doesn't run X) be able to
build everything (mostly software, but also PNGs and PDFs of my
schematics, along with running DRC, making a netlist, etc.)
I did a search for an alternate way
I have 1.4.1.20080929, that's the only version I've tried to build.
- Miles
On Wed, May 20, 2009 at 7:26 AM, Alberto Maccioni
wrote:
> Has anyone been able to compile gEDA v1.4.3 with cygwin?
> I can only build 1.4.2, but not 1.4.1
> What about v1.5.x? It needs GTK 2.8 but unfortynately cygwin o
I agree it's a waste of time to port gEDA to windows, and that a
cross-platform library is the way to go. I've used SDL a bit, but I
wouldn't pick it for this. I'd (personally) pick Qt, and recommend
porting gEDA to Qt, so there'd be one unified code base, instead of a
separate codebase for unix+
>> For software to be truly expert friendly, it must use languages
>> that are meaningful in the application domain, and lots of
>> extendability. To a circuit designer, that is not C, Scheme,
>> M4, or XML.
>
> The ones I know circuit designers use are verilog, perl and python.
> and then there a
I think the file you are missing is "attribs"
http://www.geda.seul.org/wiki/geda:faq-gnetlist
mine:
$ cat attribs
device
value
manufacturer
manufacturer_part_number
footprint
On Thu, Apr 30, 2009 at 1:59 PM, Rob Butts wrote:
>
> I'm trying to use gnetlist -g bom -o... to generate a bill of
>
On Thu, Apr 9, 2009 at 9:40 AM, John Doty wrote:
>
>>
>> Where is the problem by this simple approach?
>>
>
> Cognitive dissonance in the minds of users and developers, whose
> minds actually work hierarchically, but who expect, based on
> traditional practices, that component management is flat.
John wrote:
> Huh? Not the way it works for me (currently using gEDA/gschem version
> 1.4.3.20081231). Unpromoted visible attributes from the sym are
> visible in the schematic, you just can't edit them. Are you sure
> you've marked them visible?
Yes, absolutely sure. This happens on 1.4.1.2008092
> > I have attributes in my symbol files that I mark as "visible". This
> > makes them visible when editing the .sym file, but NOT when editing
> > the .sch file.
>
> I don't think so. I think if I add visible attributes to a symbol, they
> are visible (and edible) in the schematic.
>
> I th
I have attributes in my symbol files that I mark as "visible". This
makes them visible when editing the .sym file, but NOT when editing
the .sch file. I do not want them "promoted" (which I think will copy
the text of them to the contents of my .sch files, when a symbol is
inserte
11 matches
Mail list logo
