During cross compilation, base_options are being applied from native compiler class instead of cross compiler class

[sompen]

It seems like the base_options are being applied from native compiler class only and the cross compiler's base_options are being ignored during cross compilation. Is this intended? What should be done to use the base_options of cross compiler only?

In interpreter.py:

`def add_languages(self, args, required):
..
..
self.add_base_options(comp)`

Thanks,
Sompen

[nirbheek]

@xclaesse did this change with your PR to rework this code?

[xclaesse]

I think we always used native compiler base options. Even before my PR, add_languages() was already doing self.add_base_options(comp). I think this is the same type of issue than #3669, there is a massive confusion in meson about what apply to native or cross compiler.

[xclaesse]

As far as I understand it takes base options from the native compiler and use them for both native and cross compilers. Can it happen that they are from different class? Should we duplicate all base options so we can set different values for native and cross compilers? like b_asneeded and b_native_asneeded, etc... ?

If we got that path, I guess we should also have c_args and c_native_args etc...

[Ericson2314]

Can we test this again? I wouldn't be surprised if it is fixed. If it is not #4010 should fix it.

[Ericson2314]

Can somebody write a test? I'll take care of fixing things so the test passes.

[marc-h38]

Can somebody write a test? I'll take care of fixing things so the test passes.

Would something like #6362 work ?