User Tag List

+ Trả lời chủ đề
Hiện kết quả từ 1 tới 2 của 2

Chủ đề: Dự án mã nguồn mở cho phần mềm thiết kế mạch điện tử gEDA (Unix- Linux Platform)

  1. #1
    Uỷ viên ban điều hành Box khoa ĐTVT Avatar của nothingtolose
    Tham gia ngày
    Sep 2004
    Bài gửi
    1.817

    Mặc định Dự án mã nguồn mở cho phần mềm thiết kế mạch điện tử gEDA (Unix- Linux Platform)

    General Frequently Asked Questions
    A. Introduction
    A1. What is gEDA?
    A2. What is gaf?
    A3. Why? What makes gEDA so different?
    A4. Where is this FAQ available and who maintains it?
    A5. What license does gEDA use?
    A6. Where can I get more information about and download gEDA?

    B. Tools
    B1. What tools are part of gEDA/gaf?
    B2. What other related tools are out there?
    B3. What are other planned tools?
    B4. What tools are frequently requested but are not going to be developed?

    C. OS and platform support?
    C1. What are the system requirements to run gEDA/gaf?
    C2. What Operating Systems has gEDA/gaf been tested on?
    C3. Does gEDA/gaf build under Win32?

    D. Common problems/questions when building gEDA
    D1. GTK+
    D2. GUILE
    D3. LibStroke
    D4. libgdgeda

    E. Common questions asked about gEDA development
    E1. Why C? Why not C++?
    E2. I have made some useful symbols. How do I submit them?
    E3. I want to write a conversion utility. What is the schematic/symbol file format?
    E4. A gEDA program just crashed. How do I help the maintainers find the problem?
    E5. Why does gEDA not become a GNOME/KDE application?
    E6. What is with all the ASCII file formats?


    ---------------------------------------------------------------------

    A. Introduction
    A1. What is gEDA?
    gEDA is a collection of tools which are used for electrical circuit design, simulation and prototyping/production. The gEDA project was started because of the lack of free EDA tools for UNIX. The tools are being developed mainly on GNU/Linux machines, but considerable effort is being made to make sure that gEDA runs on other UNIX variants.
    The original author of gEDA is Ales Hvezda but there are several other major contributers as well.

    It also important to note that the gEDA project has grown quite a bit, since the Spring of 1998. It is no longer one person producing tools. Instead, there are many people involved. A few people are contributing to the original tools, while others are doing their own development on their own tools. So, gEDA does not refer to the original tools anymore (those tools now stand on their own now), but instead it refers to all the projects which are free and are somehow associated with this webpage or the geda-dev/user mailing list. By associating with gEDA, free software authors do not give up any control over their tools, but they gain a community which cares about quality and free EDA tools.

    gEDA can be pronounced "gee-daahhh" (rhymes with cheetah) or "g-dahhh (short g).

    A2. What is gaf?
    gaf stands for "gschem and friends". gaf is the collection of tools which currently includes gschem, libgeda, gnetlist, gsymcheck, gattrib, and the utils. Even though gaf is very much a part of gEDA, the gEDA name does not necessarily only apply to gaf. gEDA refers to any GPLed EDA tool which decides to associate itself with the gEDA website/mailing list. gaf only refers to the above mentioned tools. On freshmeat.net gaf is known as the package gEDA.
    A3. Why? What makes gEDA so different?
    Tools in the gEDA suite and associated tools have the following characteristics:

    Free in the monetary sense (no cost).
    All the file formats and all the source codes are available via the GPL license. This license grants specific rights to the authors and users of GPLed software.
    Independence from any one vendor. All gEDA tools come with full source. You can change, improve, change, port, and even distribute (if you follow the terms of the GPL) the tools.
    No mechanism is used to restrict the use of the tools (like making use of hard disk ****** numbers or ethernet addresses to force the software to only run on one machine).
    Legacy design protection. Since the software will always run forever (because of above), gEDA tool design files will always be viewable/editable (with the right versions of the software).
    Open design flow. This means that the tools talk to each other via known and documented means (files / APIs). It is easy to replace a tool or augment the tools with something else if you so desire.
    Stability - Bugs which cause crashes are investigated immediately and fixed as soon as possible.
    Minimize bloat and unnecessary features.
    Run on as many platforms as possible. For gEDA/gaf: GNU/Linux, various other Unix systems.
    Developed in an open (no secrets) fashion.
    Strive to be documented.
    gEDA may not have all the latest cutting edge features found in other packages and may be viewed sometimes as being on the trailing edge of EDA technology, but the tools are becoming useful to a lot of people because the above mentioned reasons.

    A4. Where is this FAQ available and who maintains it?
    This FAQ is only available on the gEDA web site at http://www.geda.seul.org/docs/FAQ.html .
    The current maintainer is Ales Hvezda ahvezdaATgeda.seul.org. Updates, suggestion, corrections are welcome.

    A5. What license does gEDA use?
    All of the tools and associated files in gEDA will be released under the GNU General Public License version 2 (GPL), from Free Software Foundation
    From the license:
    When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.

    This cannot be stressed enough: gEDA is GPLed software. Therefore nothing proprietary can be distributed with gEDA like part libraries from proprietary EDA products. Conversion program for proprietary libraries will be available, but any converted files which are part of a proprietary product must never find their way into gEDA. Contributed files must be GPLable (or be places under another free license). Please keep this in mind if you wish to contribute something.

    A6. Where can I get more information about and download gEDA?
    Websites:
    The official website is http://www.geda.seul.org/ hosted by the SEUL Project.
    The official site is also mirrored at:

    http://ftp.sunet.se/geda/ hosted by Swedish University Network - Sweden, Nothern Europe. Many thanks!.

    There are two mailing list available. One is called geda-user which is for user related questions and the other is called geda-dev which is for developer related questions. To subscribe send an email to: majordomoATgeda.seul.org with:

    subscribe geda-user

    or
    subscribe geda-dev

    in the body.
    To unsubscribe send an email to: majordomoATgeda.seul.org with

    unsubscribe geda-user

    or
    unsubscribe geda-dev

    in the body.
    To send email to the list use the address: geda-userATgeda.seul.org or geda-devATgeda.seul.org

    Remember, geda-userATgeda.seul.org or geda-devATgeda.seul.org is for the actual list traffic.

    You must post to geda-user or geda-dev using the e-mail address that you subscribed with or your message might get lost.

    For administrative commands, use majordomoATgeda.seul.org




    B. Tools
    B1. What tools are part of gEDA/gaf?
    gschem : Schematic Capture. More information
    symbols : Symbol library. More information
    gnetlist : Netlist Generation and verification. More information
    gsymcheck: Symbol Checker. More information
    gattrib: Attribute Editor. More information
    utils: gEDA's Utilities (programs). More information


    B2. What other related tools are out there?
    GnuCap (formally know as ACS): GNU Circuit Analysis Package More information
    Icarus Verilog : A verilog compiler. More information | Official Homepage
    PCB : Printed Circuit Board layout tool. More information
    gerbv : Gerber viewer. More information
    gwave : Waveform viewer. More information
    GTKWave : Waveform viewer. More information
    For a complete list of freely available tools please be sure to visit Open Collector

    B3. What are other planned tools?
    gpcb: Printed Circuit Board (put on the long term back burner. Current replacement tool is PCB)
    gplace: stuff sheet layout
    gsim: design simulator
    gfpga / gpld: Compiling designs into these devices
    Progress on these tools is stalled, unless somebody steps up for the challenge.


    B4. What tools are frequently requested but are not going to be developed?
    These tools are frequently requested, but will not be developed unless somebody steps up for the challenge.

    IC/ASIC designer.
    A VHDL/Verilog simulator. The FreeHDL project will create a free VHDL simulator which gEDA will use.




    C. OS and platform support?
    C1. What are the system requirements to run gEDA/gaf?
    A computer:
    Processing equivalent (or more) to i486
    Enough RAM to make X happy (16 - 32 Mbytes)
    A mouse (two or three button)
    Anything else that X requires
    UNIX (see below for supported platforms)
    The X Window System
    Running at a minimum resolution of 800x600
    GTK+ version 2.4.x
    guile version 1.4.x or 1.6.x
    LibStroke (optional) for support for strokes
    libgdgeda (optional) for support PNG image writing
    libpng (required for above) PNG image writing library
    zlib (required for above) zlib library
    A C compiler (that supports ANSI C, like gcc)
    To be able to be build the CVS version you need (in addition to the usual autoconf et al) Noweb.
    C2. What Operating Systems has gEDA/gaf been tested on?
    Tested on the following platforms:
    Linux
    FreeBSD
    NetBSD
    HP-UX
    IRIX
    SunOS
    Solaris
    Unsupported Platforms

    Really old Unix platforms (let me know if you find one which does not work)



    C3. Does gEDA/gaf build under Win32?
    Yes, gEDA/gaf builds under Win32. Please get README.win32 in CVS for information on how to build it.



    D. Common problems/questions when building gEDA
    D1. GTK+
    gEDA requires the GTK+ and supporting libraries to build and run. GTK+ is the GIMP Toolkit.
    Recent versions of gEDA require GTK+ 1.2.x or GTK+ 2.4.x. Support for GTK+ 1.2.x will be dropped shortly so it is better to start using 2.4.x. GTK+ 1.1.x is NOT supported by gEDA anymore.

    Be sure to read the README/INSTALL file which comes with gEDA for more tips and tricks when compiling/installing gEDA.

    For issues building gtk+, be sure to visit the gtk+ homepage.

    D2. GUILE
    gEDA uses GUILE as its scripting engine. Why? Guile is a powerful scripting language and it was decided early on by the gEDA authors that inventing "yet another scripting language" was a waste of time.

    Guile is an implementation of the interpreted language Scheme. Guile is very nice in that it is easy embeddable in programs.

    Guile is used (at the moment) for parsing resource files, handle key mappings and as a "backend" for gnetlist. True scripting capabilities are being implemented right now. The first example of the scripting capabilities of gschem can be seen at the online symbol library which was created by gschem being driven by a guile script and Bourne shell scripts.

    At Scheme's Homepage can you find more information about Scheme, for example introductory texts. An example on a quite short introduction is "Teach Yourself Scheme in Fixnum Days". Also take a look at Scheme FAQs, Help, and Tutorials for even more info.

    D3. LibStroke
    gEDA uses LibStroke to provide "stroke" input in gschem. This is an optional library.
    D4. libgdgeda
    gEDA uses several support libraries to provide other functionality. libgdgeda is a hacked version of gd library to provide png output support. This library also requires libpng and zlib. libgdgeda is an optional library.



    E. Common questions asked about gEDA development
    E1. Why C? Why not C++?
    This question comes up from time to time on the gEDA mailing list. Manipulation of graphic objects (in schematic capture) would lend itself to an object oriented approach, however gschem and friends are written in C. Here are the reasons why gschem and friends are written in C:

    GTK+ is in written in C. When Ales started this project, the C++ GTK+ bindings were not stable.
    C++ is not as universal as C. Not everybody has a C++ compiler.
    g++ (the GNU C++ compiler) is not as mature as gcc (the GNU C compiler)
    An original goal was to take an object oriented like approach to gschem and friends, but it has deviated a bit from this. Hopefully the first rewrite will address some of the code organization problems.

    It is important to note that this should not discourage anybody who wants to code in C++, it is just that everything else is written in C. There are people writing EDA tools in other languages (Java and C++).

    I (Ales) have completely changed my opinion of C++. The above reasons were at one point valid, however, now (in the year 2000), none of these reasons are valid. I have been using C++ for years professionally and I am quite fond of the language. I am bouncing the idea around of using C++ in the first rewrite of gschem and friends (it is a long time away; I want to get the C version mostly done first).

    E2. I have made some useful symbols. How do I submit them?
    Most symbol libraries available in commercial EDA systems often have a copyright attached to them. This copyright makes it impossible to use them in gEDA. To get a decent library of symbols, that is as free as the rest of gEDA, the project is in great need of symbols.

    If you have made some symbols (following the guidelines available at the doc. page) you can submit them in several ways:


    1. Upload them via the web using the Online Symbol Contribution form. This is the preferred method of sending symbols.
    2. Attach them to an email and send them either to Ales ahvezdaATgeda.seul.org or to the mailing list geda-devATgeda.seul.org.

    3. Put them in the contrib directory on the gEDA ftp-site ftp://ftp.geda.seul.org/pub/geda/contrib/. Then send an email to either Ales ahvezdaATgeda.seul.org or to the mailing list geda-devATgeda.seul.org.

    4. Put them on a website that you have access to. If you want others to know that you have created a symbol, send an email to either Ales ahvezdaATgeda.seul.org or to the mailing list geda-devATgeda.seul.org.


    If/when you submit symbols, they will be released under the GPL. Please make sure that the symbols you are contributing are freely distributable. Be sure that the symbol representation is not proprietary (ie it is not under any NDA or any other copyright which forbids free distribution).

    E3. I want to write a conversion utility. What is the schematic/symbol file format?
    You can find the official gEDA file formats documented here.

    E4. A gEDA program just crashed. How do I help the maintainers find the problem?
    One of the programs in the gEDA tarball has just dumped core (or just seg faulted). Here are some things you can do to help find the problem:

    Send an email to either Ales ahvezdaATgeda.seul.org or to the mailing list geda-devATgeda.seul.org describing exactly what you did to cause the core dump.

    Most likely the above will be insufficient. If you have access to gdb (or an another debugger), please run that debugger against the binary. NOTE: the binaries which are reside in a newly built distributions are not binaries. Instead they are wrapper scripts around the actual binaries which reside in a .libs directory (ie gEDA-version/gschem/.libs). You will most likely need to set the following environment variable:

    setenv LD_LIBRARY_PATH gEDA-version/libgeda/.libs (csh/tcsh)
    or
    export LD_LIBRARY_PATH=gEDA-version/libgeda/.libs (sh/bash)

    where gEDA-version is the path to the gEDA untarred directory. These environment variables tell the loader where to find the libgeda shared library. If you do not want to bother with this or do not want shared libraries, you can configure gEDA not to build the shared libraries. Do this at configure time by supplying --disable-shared as a parameter to the ./configure script. Now you can run the debugger:

    gdb .libs/gschem

    (Assuming that you are in the gEDA-version/gschem directory.) Once the debugger starts up, run the program till it core dumps and then do a "where" (stack trace) and send that to the above mentioned persons. You might also have to rebuild the binaries with the -g flag (debugging symbols).
    E5.Why does gEDA not become a GNOME/KDE application?
    gEDA will most likely never come a pure GNOME/KDE application. The developers decided a long time ago that having too many dependencies on external libraries is not a good idea. Especially since gEDA is trying to achieve cross Unix platform portability. This philosophy does not exclude gEDA having support for GNOME/KDE (feel free to contribute code to achieve this), but this support will be a compile (./configure) time option.
    E6.What is with all the ASCII file formats?
    All file formats with gEDA must be pure ASCII. Why? Because ASCII is very portable and easy to deal with. A text file is so easy to parse and you get to use all those unix utilities to manipulate them. Binary files are highly non-portable. It might be easier to parse them (probably not) and they may be more space efficient, but they lack portability. This is too large a tradeoff. Plus I (Ales) say so, no binary formats. :-) All gEDA file formats are fully documented. If you find a gEDA file format which is not documented, let me know.


    Link : http://geda.seul.org/

  2. #2
    svBK's Newbie
    Tham gia ngày
    Aug 2005
    Bài gửi
    14

    Mặc định

    trời ơi, dài quá đọc bao giờ mới xong
    -bác cho em hỏi bác có phần mền gEDA nào ko?
    -có thể chia sẻ cho em được ko ?
    em đang dung Fedora Core 10

+ Trả lời chủ đề

Thông tin chủ đề

Users Browsing this Thread

Hiện có 1 người đọc bài này. (0 thành viên và 1 khách)

Chủ đề tương tự

  1. Bàn về Linux và phần mềm mã nguồn mở
    Gửi bởi Nistelrooy trong mục Hệ điều hành UNIX - Linux
    Trả lời: 37
    Bài cuối: 16-09-2013, 11:57 AM
  2. New File Added: The art of Unix programming
    Gửi bởi Nistelrooy trong mục Thế Giới Phần Mềm
    Trả lời: 2
    Bài cuối: 29-01-2007, 04:47 AM
  3. New File Added: Giao trinh UNIX.pdf
    Gửi bởi Mr.vulh_bk trong mục Thế Giới Phần Mềm
    Trả lời: 0
    Bài cuối: 25-01-2007, 05:17 AM
  4. Thiết kế web với các nguồn miễn phí
    Gửi bởi webforyou trong mục Lập Trình
    Trả lời: 8
    Bài cuối: 09-05-2006, 03:21 PM
  5. Knowledge Platform Researching Program
    Gửi bởi SkyMaster trong mục Giảng đường CNTT
    Trả lời: 0
    Bài cuối: 08-09-2004, 01:24 PM

Từ khóa (Tag) của chủ đề này

Quyền viết bài

  • Bạn không thể gửi chủ đề mới
  • Bạn không thể gửi trả lời
  • Bạn không thể gửi file đính kèm
  • Bạn không thể sửa bài viết của mình


About svBK.VN

    Bách Khoa Forum - Diễn đàn thảo luận chung của sinh viên ĐH Bách Khoa Hà Nội. Nơi giao lưu giữa sinh viên - cựu sinh viên - giảng viên của trường.

Follow us on

Twitter Facebook youtube