meson: add native-file #291
Conversation
jkloetzke
left a comment
jkloetzke
left a comment
There was a problem hiding this comment.
I'm wondering why we need to add cmake to the cross file? Would be good to add this reasoning to the commit message...
classes/meson.yaml
Outdated
| c_args = [$(meson_join_list "${MESON_CFLAGS[@]}")] | ||
| cpp_args = [$(meson_join_list "${MESON_CXXFLAGS[@]}")] | ||
| c_link_args = [$(meson_join_list "${MESON_LDFLAGS[@]}")] | ||
| cpp_link_args = [$(meson_join_list "${MESON_LDFLAGS[@]}")] |
There was a problem hiding this comment.
This looks odd. When cross-compiling, both a cross- and a native-file are passed. Does it mean we're using the flags same flags for host and target?
There was a problem hiding this comment.
AFAIU this providing both is valid?
We do not have separate environment variables for host and target toolchain, but I see that using the target flags for the native tools might also break. Maybe this should be set to some safe defaults instead?
I feared you'll ask this. I have this commit since a few years and missed to add details... I'll remove it and see what breaks.. |
The native file is used to specify the tools to be used for building native binaries. Without this file meson uses the system toolchain in /usr/bin if available.
rhubert
force-pushed
the
meson-native-file
branch
from
9ae640f to
01561be
Compare
2 participants
The native file is used to specify the tools to be used for building native binaries. Without this file meson uses the system toolchain in /usr/bin if available.