X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Sat, 9 Jan 2016 14:31:43 -0500
Message-Id: <201601091931.u09JVh2M007971@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to:
	<CAC4O8c_tFOOXCA5ABEMuSU8BnXMZWauV+uJYy-TJO7nJYBS9+A AT mail DOT gmail DOT com>
	(geda-user AT delorie DOT com)
Subject: Re: [geda-user] (features: layers stack, padstack/vias)
References: <1512221837 DOT AA25291 AT ivan DOT Harhan DOT ORG>
	<20160106091006 DOT 5F67B809D7A1 AT turkos DOT aspodata DOT se>
	<CACwWb3CcsYJ9KgDFAa5pZqDzfTewhvbuatbxoKUp6PtHRCoa+w AT mail DOT gmail DOT com>
	<20160106133049 DOT 5A0E9809D79B AT turkos DOT aspodata DOT se>
	<CACwWb3Cyk4yLwt3=V1Mu5C4RieOQEjYH3ej5MXZSNnLPbshqDg AT mail DOT gmail DOT com>
	<20160106143629 DOT 4D39D809D79B AT turkos DOT aspodata DOT se>
	<CACwWb3BXbnQXs+DwVVzmC8DrhwOYxPgVyUhZTPL9bM9cJbHimw AT mail DOT gmail DOT com>
	<20160106164022 DOT D0D4E809D79B AT turkos DOT aspodata DOT se>
	<20160106180912 DOT 42ddf4079d91384f206b7c35 AT gmail DOT com>
	<20160106191433 DOT 5dc5cb59 AT jive DOT levalinux DOT org>
	<20160106202817 DOT 56197b2c539d426a1b724c9e AT gmail DOT com>
	<568E09ED DOT 1080508 AT m0n5t3r DOT info>
	<CACwWb3AhSh-+NNu--bVMGZBfjaoA+hHg7gbXnoyNv3oMq=e17g AT mail DOT gmail DOT com>
	<568E6354 DOT 80302 AT m0n5t3r DOT info>
	<20160108002640 DOT 03233b24 AT jive DOT levalinux DOT org>
	<20160108175259 DOT 127a3f073616758434f7edff AT gmail DOT com>
	<20160109020345 DOT 1e07cb84 AT jive>
	<CAC4O8c-nqs2+9rgsD-Gsks-wSmJ1eCkJ9PFMi3XqMrYE2FO3Ew AT mail DOT gmail DOT com>
	<20160109112851 DOT 1129dc38 AT wind DOT levalinux DOT org> <CAC4O8c_tFOOXCA5ABEMuSU8BnXMZWauV+uJYy-TJO7nJYBS9+A AT mail DOT gmail DOT com>
Reply-To: geda-user AT delorie DOT com


> > Another idea came in my mind to separate the exporter HIDs from
> > the main pcb.  For example, the gerber exporter would be a
> > separate piece of program (using shared libraries).
> 
> I haven't looked at how export works yet so I don't know about this.  But I
> think there's some consensus that moving things like this from apps (pcb,
> gschem) to libgeda is generally a good idea.

First off, libgeda has nothing to do with pcb, it really should be
libgaf but it's not worth renaming or bikeshedding.

Second, pcb does support loading shared objects at runtime, so you
already *can* have a separate exporter object which is pulled into a
batch-pcb to act as a "separate program" in a build flow.