[Buildroot] [PATCH] package/pkg-meson: ensure the global cross-compilation.conf file is correct

Arnout Vandecappelle arnout at mind.be
Fri Dec 6 08:58:15 UTC 2019



On 06/12/2019 08:59, Thomas Petazzoni wrote:
> Hello,
> 
> On Thu, 5 Dec 2019 23:13:42 +0100
> Arnout Vandecappelle <arnout at mind.be> wrote:
> 
>>> -TOOLCHAIN_POST_INSTALL_STAGING_HOOKS += PKG_MESON_INSTALL_CROSS_CONF
>>> +TOOLCHAIN_TARGET_FINALIZE_HOOKS += PKG_MESON_INSTALL_CROSS_CONF  
>>
>>  Note that this essentially reverts [1].
> 
> Yes, true.
> 
>>  The case for that patch was not terribly strong, so it should be OK. But then
>> again, the case for this patch is not that strong either.
> 
> Well, the case for my patch is that it allows to produce a meson
> cross-compilation.conf that has correct and usable values at the end of
> the build.
> 
>>  Note that pkg-cmake has the same issue.

 Now that I'm awake again (<grin>) I see that it actually doesn't, because that
one uses relative paths. I don't suppose that meson's cross-compilation.conf can
use a similar trick? (Adding meson "experts" in Cc...)

>> And a number of other packages as well,
>> e.g. the Python sysconfig refers to the Python per-package dirs.
> 
> For sysconfig, I have a pending patch that I will submit soon to fix
> the problem. It is in fact worse for sysconfig because if you don't
> tweak it during the build, the build simply fails. While for the global
> meson cross-compilation.conf, it is less dramatic as it is not used by
> Buildroot itself, just provided as a convenience.

 Just to be entirely clear: it actually works as long as you keep the build
directory around, it just doesn't work in the context of the SDK, right?

 Regards,
 Arnout



More information about the buildroot mailing list