16/02/2020 18:29, Ye Xiaolong: > On 02/16, Thomas Monjalon wrote: > >18/01/2020 06:48, Xiaolong Ye: > >[...] > >> + [binaries] > >> + c = 'x86_64-openwrt-linux-gcc' > >> + cpp = 'x86_64-openwrt-linux-cpp' > >> + ar = 'x86_64-openwrt-linux-ar' > >> + strip = 'x86_64-openwrt-linux-strip' > >> + > >> + meson builddir --cross-file openwrt-cross > > > >This is really a good example why meson should allow to override the > >toolchain prefix. > > Not sure whether I get your point or not, do you mean meson should support > something like "cross = 'x86_64-openwrt-linux-'" in config file (just like the > CROSS_COMPILE for make build system), so we don't need to override the build > tools one by one?
Yes, I think meson should support CROSS_COMPILE environment variable or a similar config option. I don't see the point of creating a new config file for each toolchain prefix. > >> + to /usr/lib64 in OpenWrt. > > > >libnuma is not packaged in OpenWrt? > > Unfortunately not, I guess the reason maybe OpenWrt is mainly focused on > low-end > embedded systems which don't have numa support. I would be nice to work on it in OpenWrt project then.