delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2016/07/06/08:39:38

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Wed, 6 Jul 2016 14:45:38 +0200 (CEST)
X-X-Sender: igor2 AT igor2priv
To: "James Battat (jbattat AT wellesley DOT edu) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From: gedau AT igor2 DOT repo DOT hu
Subject: Re: [geda-user] Exporting a design
In-Reply-To: <C1B27CB8-9811-4101-8166-F8E17D7026FF@wellesley.edu>
Message-ID: <alpine.DEB.2.00.1607061442400.7286@igor2priv>
References: <C1B27CB8-9811-4101-8166-F8E17D7026FF AT wellesley DOT edu>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
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


On Wed, 6 Jul 2016, James Battat (jbattat AT wellesley DOT edu) [via geda-user AT delorie DOT com] wrote:

> After completing a schematic and board layout, I?d like to distribute the full project to a colleague.  I?d like to send them a single file that is self-contained (meaning all .sch files, .pcb file, custom footprints and symbols), in a way that makes it easy on the recipient.  What is the recommended approach?
>
> At present, I have my design files (.sch, .pcb and config files) under version control.  I separately have my symbols and footprints in version control.  So a collaborator must check out the code for the board, and the code for the symbols/footprints, and then ensure that the symbol/footprint paths in the preference files align with their directory structure, etc.  In this approach, they also must get all of my custom symbols/footprints, not just the ones used in the current project.
>
> There must be a better way.  What do you do?

I keep my stuff in svn, and there I'd do this:

a directory in one of my repositories; it would contain an extern dir to 
the project dir, an extern dir to the symbol library and an extern dir to 
the pcb footprint library. One svn up and you svn upped all three.

It'd also contani a ghsc2pcb project file, a Makefile and gafrc.

The user may still need to make some tweaks and checks in pcb, gsch2pcb 
and gschem to make sure all three understood all footprint and/or sym lib 
dirs.

(btw, I'm adding better project file support in pcb-rnd mainly for this 
use case, see my mail from a few hours ago)

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019