Yep. You're right. I'll update the patch with the fix.<br><br><div>Roshan Pius</div><br><div class="gmail_quote">On Fri Dec 19 2014 at 10:10:06 AM Aleksander Morgado <<a href="mailto:aleksander@aleksander.es">aleksander@aleksander.es</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Dec 19, 2014 at 6:53 PM, Roshan Pius <<a href="mailto:rpius@chromium.org" target="_blank">rpius@chromium.org</a>> wrote:<br>
> +<br>
> +#Install udev rules only if configured with --enable-qmi-username<br>
> +if INSTALL_QMI_UDEV_RULES<br>
> +udevrulesdir = $(UDEV_BASE_DIR)/rules.d<br>
> +udevrules_DATA = 76-qmi-proxy-device-ownership.<u></u>rules<br>
> +<br>
> +EXTRA_DIST = \<br>
> +       $(udevrules_DATA)<br>
> +endif<br>
<br>
Just realized this; shouldn't EXTRA_DIST include the<br>
<a href="http://76-qmi-proxy-device-ownership.rules.in" target="_blank">76-qmi-proxy-device-ownership.<u></u>rules.in</a> file, instead of the<br>
76-qmi-proxy-device-ownership.<u></u>rules one? The rules file will be<br>
generated during configure, so the dist tarball needs the .in file.<br>
<br>
--<br>
Aleksander<br>
<a href="https://aleksander.es" target="_blank">https://aleksander.es</a><br>
</blockquote></div>