gEDA-dev: add-on dir name for pcb
Igor2
igor2 at inno.bme.hu
Sun Oct 1 11:08:57 EDT 2006
On Sun, 1 Oct 2006, DJ Delorie wrote:
>
>> I was originally thinking that they could go in $prefix/share/, but
>> I think for consistency with other apps, .so files ought to go in
>> $prefix/lib/appname/
>
>Technically, that would be $exec_prefix/...
>
>So...
>
>$exec_prefix/lib/pcb/*.so
>or
>$exec_prefix/lib/pcb/hids/*.so
>or
>$exec_prefix/lib/pcb/plugins/*.so ?
>
>As for $HOME, I think ~/.pcb/hids/ makes the most sense; we don't need
>the generic "lib/" subdir there.
>
>Although an optional platform-specific subdir in ~ might be useful, if
>you run pcb on multiple architectures with the same $HOME.
>
>That would be ~/.pcb/hids/i686-pc-linux-gnu/ on my machine.
>
$exec_prefix/lib/pcb/plugins sounds good. I think plugin is a better idea,
since later there could be plugins to perform operations on the pcb like
panelizing, and maybe for those name HID is not a good choice.
Two questions:
- Wouldn't it be better to have a config file (a list of file names) to
load instead of loading all hids found in specific dirs? That would allow
the user to load hids from non-default directories or to turn off loading
hids without renaming or deleting the lib files.
- Where do hid-specific data files go? I mean if a hid uses data files for
some reason, we should name default dir for them as well.
Regards,
Igor2
More information about the geda-dev
mailing list