On Mon, 4 May 2020 at 13:27, Helmut Grohne <[email protected]> wrote:
> When one passes --libdir and --cross-file to meson, meson thinks it > knows better than the user and overrides the libdir with plain "lib". > Setting a libdir from the crossfile does not work either. It gets > ignores in the same way. There is something stranger going on in here. I tried to replicate this by running the following command: ./meson.py --cross-file cross/ubuntu-armhf.txt test\ cases/common/8\ install build --libdir=foo Running meson configure immediately after this lists its value as "foo", as it should and running install places the files in their correct locations. This happens both on trunk and 0.54.1.
