Does anyone know if Eagle can write out and import EDIF, either
directly or by way of an opensource tool? Or perhaps a
vector-graphics format like SVG?
If it can then that might be the way to share the schematics side of things with a conventional text-based source-code revision control system. It would also open up the option to use the files with other software tools.
Thanks for speaking up and airing your situation.
All I can think of is that there must be some way to
get the damned schematics into an ASCII format that
*can* be version controlled. Not saying that is going
to be obvious or non-trivial. I'll try to do some
research on this one, since it is in my own best
Thank you for a great and cool product, BTW.
Michael A. Hobson
--- Gordon Kruberg < email@example.com> wrote:
> It has been a while since I actually responded to
> anything-- sorry for
> being so heads down into the workings that I may
> seem to be ignoring
> this list. Really, I'm not.
> As far as I can tell, I owe you **at least** an
> Eagle library file, but
> I'd like to do this right.
> I have a large set of Eagle schematics that I use to
> cut and paste them
> to make the buddy boards, and have a set of ulp's
> that reposition
> components into specific positions and orientations
> (scripts to draw the
> gumstix outline and lay down holes in the right
> place). I have spent a
> lot of time recently refining this so that
> ultimately I can distribute
> them under the Creative Commons.
> Here's the set of challenges-- I really want to
> release them so we can
> all share edits. I strongly prefer SVN for version
> control; however,
> there is no diff for Eagle libraries or schematics
> because they're in
> Eagle's proprietary format. Since ulp and scr are
> text files, these are
> So-- any ideas how to release these so that I can
> help without creating
> a mess of conflicting versions? It could be as
> simple as
> 1) abandoning version control on the Hirose library
> components by
> pushing out just the 2, and
> 2) versioning the scripts and ulps so they "set up"
> a daughtercard with
> the correct holes, connector position, and a few key
> This solves nothing for the schematics and PCB
> layouts, but it might
> help a lot anyway.
> Comments or ideas?
> >I forgot to add that one wants all of the Schematic
> >CAD / PCB data in a part library file or files, so
> >that the Schematic CAD program can do automated
> >checking for various kinds of errors, and so that
> >PCB Auto-Router can automatically generate most of
> >PCB foil pattern for you.
> >Cadsoft Eagle, Mentor Graphics PADS PCB, ORCAD and
> >other packages need these part libraries or you end
> >having to make them yourself.
> >Michael A. Hobson
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's
> Geronimo App Server. Download
> it for free - -and be entered to win a 42" plasma tv
> or your very own
> Sony(tm)PSP. Click here to play:
> gumstix-users mailing list
Yahoo! Mail - PC Magazine Editors' Choice 2005
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
gumstix-users mailing list