Replies: 2 comments 7 replies
-
You can define your toolchain in a native file: https://mesonbuild.com/Machine-files.html. But that still requires the user to run |
Beta Was this translation helpful? Give feedback.
7 replies
-
#10938 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi.
I've found the very old thread about that
subject: #1752 but it ended inconclusively.
Today we have multiple tool-chains,
each with its own set of bugs and features.
My project represents a very complex system,
that can only be built using clang++ (not g++)
as a compiler, GNU ld (and not lld) as a linker,
and a customly patched version of nasm
(and not, say, yasm).
I realize that the intention of meson is to
allow the user to select the preferable tool-chain
when he builds the code. But today's tool-chains
are so complex and the new features are added
so rapidly to them, that the assumption that
"every tool-chain suits", is basically no longer valid.
So my question is: does meson allow me to
configure the needed tool-chain for my project
(by selecting the components from multiple
tool-chains and adding custom tools), without
asking the user to please set CC/CXX/LD/NASM
variables on his own?
Beta Was this translation helpful? Give feedback.
All reactions