X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.6
X-Exmh-Isig-CompType: repl
X-Exmh-Isig-Folder: inbox
From: karl AT aspodata DOT se
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] Re: Project file
In-reply-to: <FA1472EC-713E-4A14-A881-6404E527998C@noqsi.com>
References: <CAGqyy=bsRdbA8r8q1MTX7pG9ASZiqpsw1-kbj=geTwLoWaz1sA AT mail DOT gmail DOT com> <20180723152807 DOT 13d27cadcd023b63aa3fd9c0 AT gmail DOT com> <CAGqyy=ZC68vU+8vpM4oai5=Mrfq_=QpyojzDwwW-50EV6P4q3A AT mail DOT gmail DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1807231832560 DOT 8169 AT igor2priv> <20180723174658 DOT 32979841DEBA AT turkos DOT aspodata DOT se> <alpine DOT DEB DOT 2 DOT 00 DOT 1807232013250 DOT 8169 AT igor2priv> <20180723195942 DOT 605CB841DEBA AT turkos DOT aspodata DOT se> <alpine DOT DEB DOT 2 DOT 00 DOT 1807240343390 DOT 8169 AT igor2priv> <20180724132731 DOT 76074841DEBC AT turkos DOT aspodata DOT se> <20180724161712 DOT f0082dda1044e41179fa82f0 AT gmail DOT com> <20180724145644 DOT 122BA841DEC5 AT turkos DOT aspodata DOT se> <FA1472EC-713E-4A14-A881-6404E527998C AT noqsi DOT com>
Comments: In-reply-to John Doty <jpd AT noqsi DOT com>
   message dated "Tue, 24 Jul 2018 11:58:26 -0400."
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Message-Id: <20180724162454.21C6C841DEC5@turkos.aspodata.se>
Date: Tue, 24 Jul 2018 18:24:54 +0200 (CEST)
X-Virus-Scanned: ClamAV using ClamSMTP
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

John:
> Large projects can be quite complex.
> 
> You may have different symbol libraries for prototype and production.
> 
> You may have partial implementations: test boards and the like.
> One recent project of mine had two production board variants,
> where which board you made depended on which subset of the top
> level schematics you chose.
> 
> You often simulate fragments of the system, so each simulation
> is its own subproject based on its own subset of the schematics.
> 
> You may need to support multiple layout systems.
> 
> Projects often contain parts outside the EDA toolkit, like LaTeX
> documents, C code, VHDL code, etc.
> 
> The general-purpose tool for handling this kind of thing is “make”.

Yes, after a while in my projects, makefiles tend to creap in,
and in a way the Makefile is the project file, it tells how things
are glued together.

///

Currently I do the test/prototype boards and another guy does the final
layout in another tool (kicad, he doesn't like kicad but don't want to
learn yet another eda tool).

Unfortunately kicad isn't good att automation, like export to pdf,
which works wery well in geda. I'm trying to build solutions to bind
the systems together, and that goes for pcb-rnd and lepton also.

Regards,
/Karl Hammar

-----------------------------------------------------------------------
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden