<html><head></head><body>No no, I'm suggesting that there should *not* be a dedicated option to turn pkg-config in non-native builds.<br><br><div class="gmail_quote">Le 3 février 2020 10:02:32 GMT+02:00, Steve Lhomme <robux4@ycbcr.xyz> a écrit :<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On 2020-02-02 13:13, Rémi Denis-Courmont wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Le dimanche 2 février 2020, 14:02:16 EET Alexandre Janniaux a écrit :<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;">There are no valid reasons to disable pkg-config if it is correctly set<br>(i.e., to the correct platform/directories). It won't find what's nowhere<br>to be found. To take the extreme, if you wanted to compile VLC for bare<br>(which won't work as is), you would anyway have the dedicated<br>arm-none-... triplets, and you wouldn't hit any "wrong" packages.<br></blockquote>For instance, I build for (linaro-)aarch64-linux-gnu which<br>might become the same triplet name as raspberry one day,<br>and have /usr/aarch64-linux-gnu/ on my machine.<br></blockquote>And then what? If you need a different SDK with the same triplet, you have th<br>same cross-tool names, so you need a different directories prefix. pkg-config<br>makes no difference here: first and foremost, you need to point to the correct C<br>compiler and C headers and run-time libraries.<br><br>Just like if you *natively* build for a different distro.<br><br>Point being, this has nothing to do with pkg-config and nothing to do with<br>cross-compilation, and thus I don't see why there should be a cross-<br>compilation-specific pkg-config-specific flag for that.<br></blockquote><br>Are you suggesting to use TRIPLET-pkg-config even when not cross <br>compiling ? That could work (with the same fallback to pkg-config + <br>custom PKG_CONFIG_LIBDIR if not found).<br><br>We should also make sure we use the same PKG_CONFIG (and its <br>environment) between the contribs and VLC, as said earlier in the <br>thread. For example as I mentioned autotools uses <br>x86_64-w64-mingw32-pkg-config when cross compiling for Win64. Except, <br>this pkg-config doesn't work and will never find anything on the system. <br>It would have been better to use a working pkg-config with proper <br>PKG_CONFIG_LIBDIR, if the user wants to provide pre-compiled things.<hr>vlc-devel mailing list<br>To unsubscribe or modify your subscription options:<br><a href="https://mailman.videolan.org/listinfo/vlc-devel">https://mailman.videolan.org/listinfo/vlc-devel</a></pre></blockquote></div><br>-- <br>Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.</body></html>