console plugins
Marcus Brinkmann <[email protected]>
| Newsgroups | gmane.os.hurd.devel.readers |
|---|---|
| Message-ID | <[email protected]> |
Hi,
I wrote plugin support, and tested it today. The current plan is as this:
/lib/hurd/VERSION/console/DRIVER.so
where VERSION is 0.3 right now and DRIVER is "vga", "pckbd" etc.
For this, it seems I need to hardcode the library search path in the
console-console executable with -Wl,-rpath=$(libdir)/hurd/$(hurd-version)/console.
Then I can use dlopen("DRIVER.so") without worrying about the details of the
path. Or should I use a full path in the binary?
The reason to not use $(libdir) is that those modules are private to the
console client, no other application can sensefully make use of it.
The reason to include a version number seems to be common practice, and
allows for better compatibility (or lack thereof) across versions. The use
of the one global Hurd version is as wrong as in libstore classes ;)
Is that setup fine, or do you have better suggestions?
Thanks,
Marcus
--
`Rhubarb is no Egyptian god.' GNU http://www.gnu.org [email protected]
Marcus Brinkmann The Hurd http://www.gnu.org/software/hurd/
[email protected]
http://www.marcus-brinkmann.de/