On Tue, 2012-08-14 at 17:40 +0300, Vasily Khoruzhick wrote: > On Tue, Aug 14, 2012 at 5:37 PM, Bastien Nocera <had...@hadess.net> wrote: > > On Tue, 2012-08-14 at 17:31 +0300, Vasily Khoruzhick wrote: > >> On Tue, Aug 14, 2012 at 5:26 PM, Bastien Nocera <had...@hadess.net> wrote: > >> > > >> > I committed the first one, but worked around the udev problem in a > >> > slightly different way. > >> > > >> > Cheers > >> > >> Maybe it worth to disable udev rules generation by default in case of > >> cross compiling? > > > > I really want the rules files to be installed, as they're useful on > > embedded devices as well, and I'd like the developers that do that to be > > aware that things will break when cross-compiling from git, and the > > rules file doesn't already exist. > > > > Better ideas welcome obviously. > > Usually CC_FOR_BUILD (or HOST_CC) is used for building such kind of > binaries when cross compiling, > and that's what my 2nd patch did, it compiles fprint-list-udev-rules > with host compiler, so we can run it without any issues.
That would also mean compiling the library with the host compiler (and doing checks for the libraries being available in both the host build env, and the target build env). Pretty sure it wouldn't work as-is. > However it requires some testing for sure. Cheers _______________________________________________ fprint mailing list fprint@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/fprint
