Étienne Bersac wrote:
> Hi,
>
>> There is still one problem remaining for me with your build system. You
>> install ift-load in ${libdir}/udev, but then in the rule input
>> (isight.rule.in) you reference it by @prefix@/lib/. It should be
>> @libdir@/udev/ift-load in order to avoid conflicts. Also keep in mind
>> that some distributions use "lib64" instead of "lib" for 64bit.
>
> Right but, did you test the solution you propose ?
Yes with the patch I've managed to configure it properly for my 32bit
openSUSE:
./configure --prefix=/usr --libdir=/lib --bindir=/usr/bin
--sbindir=/sbin --datadir=/usr/share --datarootdir=/usr/share
--sysconfdir=/etc
To install as follows:
/etc/udev/rules.d/isight.rules
/lib/udev/ift-load
/usr/bin/ift-export
/usr/bin/ift-extract
/usr/share/doc/isight-firmware-tools/HOWTO
/usr/share/info/ift-export.info.gz
/usr/share/info/ift-extract.info.gz
/usr/share/locale/fr_FR/LC_MESSAGES/isight-firmware-tools.mo
/usr/share/man/man1/ift-export.1.gz
/usr/share/man/man1/ift-extract.1.gz
and the rule to be:
ACTION=="add", SYSFS{idVendor}=="05ac", SYSFS{idProduct}=="8300",
RUN+="/lib/udev/ift-load --firmware /lib/firmware/isight.fw"
> I remember configure substituting with shell variable … :/
>
Yes, because I used to set prefix to / in order to get the rule to have
the path to ift-load: /lib/udev/ and @prefix@/lib/udev/, where prefix ==
/ --> //lib/udev. The problem with prefix == / is that the prefix is
used for the translations and if prefix == / the translations are
installed in /share and not /usr/share. And if prefix == /usr (as it
should be) then the rule has the path /usr/lib/udev/ift-load/. So yeah
@libdir@ instead of @prefix@ works well for me in the rule.
Regards.
--
Ivan N. Zlatev
Web: http://www.i-nZ.net
"It's all some kind of whacked out conspiracy."
_______________________________________________
Linux-uvc-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
