gEDA-dev: [pcb] patch: export some compile-time options (for external HIDs)

Igor2 igor2 at inno.bme.hu
Tue Oct 10 00:20:06 EDT 2006


On Tue, 10 Oct 2006, DJ Delorie wrote:

>
>> My external HID has data (the actual scripts), which is stored in
>> pcb-gpmi/, near the .so, in the plugins dir.
>
>They wouldn't be binaries, so they'd go in $prefix, not $exec_prefix.
>Then they'd be shared across cpu/os combinations.
>
>> However there are more then one plugins dir and PCB does a search
>> which I have to reproduce in my HID.
>
>Well, you need to replicate the places that are searched (cwd, home,
>install) but not the exact directories.  You'd want to store scripts
>in a cpu-independent directory ($prefix), not the cpu-specific one the
>.so goes in ($exec_prefix).

It's a bit more problematic since they might be scripts or data files; I
also need to store config files. But you are right, the current scheme is
not the best. It's very hard to find where to put these kind of mixed
stuff. The current scheme is that the exteral HID looks for pcb-gpmi.conf
on all the paths the HID's so could be and load the modules listed in that
file. If the module is a script module, it's param is a script name.





More information about the geda-dev mailing list