Jussi Pakkanen:
> On Sun, Sep 15, 2019 at 2:20 PM Niels Thykier <ni...@thykier.net> wrote:
>
>>>
>>> AFAICT, it would just be a question of doing:
>>>
>>> """
>>> /usr/share/meson/debcrossgen -a"$DEB_BUILD_ARCH"
>>> -o"$DIR/meson-native-file.conf"
>>> /usr/share/meson/debcrossgen -a"$DEB_HOST_ARCH"
>>> -o"$DIR/meson-cross-file.conf"
>>> meson --native-file "$DIR/meson-native-file.conf" --cross-file
>>> "$DIR/meson-cross-file.conf" ...
>>> """
>>>
>>> OR does it need a special case for cross-building vs. native?
>>>
>>> """
>>> /usr/share/meson/debcrossgen -a"$DEB_BUILD_ARCH"
>>> -o"$DIR/meson-native-file.conf"
>>> if (is_cross_compiling()) {
>>> /usr/share/meson/debcrossgen -a"$DEB_HOST_ARCH"
>>> -o"$DIR/meson-cross-file.conf"
>>> meson --native-file "$DIR/meson-native-file.conf" --cross-file
>>> "$DIR/meson-cross-file.conf" ...
>>> } else {
>>> meson --native-file "$DIR/meson-native-file.conf" ...
>>> }
>>> """
>
> The way Meson interprets things is that having a cross file means that
> you are cross compiling. Not having one means compiling natively. This
> has been under flux recently and might not work exactly like this
> currently due to bugs, but that is the intent. As this is not yet
> fully nailed down there may be policy changes, but I'd consider them
> unlikely. Thus the latter form is the one we should go for.
>
> I'm also not entirely sure if we can generate the native file with
> debcrossgen as it has slightly different syntax and it might need to
> handle envvars differently. But that is a question of me adding
> command line arguments or creating something like a "nativegen" or
> something like that.
>
> Sorry for the delay, had conference travel and other things.
>
Hi Jussi,
Any news on a "nativegen" command? :)
Thanks,
~Niels
