| www.delorie.com/archives/browse.cgi | search |
| X-Authentication-Warning: | delorie.com: mail set sender to geda-user-bounces using -f |
| Date: | Wed, 25 Mar 2015 14:15:00 -0400 |
| Message-Id: | <201503251815.t2PIF0i0015341@envy.delorie.com> |
| From: | DJ Delorie <dj AT delorie DOT com> |
| To: | geda-user AT delorie DOT com |
| In-reply-to: | |
| <CAGYR9vcjq9DRWkZ2xJDUmUhUeUyvy4OfTsiYeeYtaLMiEqiHbw AT mail DOT gmail DOT com> | |
| (message from Bernhard Kraft on Wed, 25 Mar 2015 16:23:54 +0100) | |
| Subject: | Re: [geda-user] Export filters |
| References: | <CAGYR9vcjq9DRWkZ2xJDUmUhUeUyvy4OfTsiYeeYtaLMiEqiHbw AT mail DOT gmail DOT com> |
| Reply-To: | geda-user AT delorie DOT com |
> How are the export filters of PCB currently implemented? PCB has a shared library hook for runtime-loadable actions and exporters, although the common ones are built into pcb. If you look at one of my plugins you'll see how to add an action at runtime: http://www.delorie.com/pcb/teardrops/ more at http://www.delorie.com/pcb/ For exporters, PCB looks for a function called "hid_<filename>_init()" (i.e. frob.so -> hid_frob_init()) or, more easily, a function called pcb_plugin_init(). This function may call any of the same functions that built-in hids call, including hid_register_hid().
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |