-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #5263 from Ericson2314/per-machine-cli-args
Per machine 'build_' and '' options
- Loading branch information
Showing
15 changed files
with
255 additions
and
146 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
## Specifying options per mer machine | ||
|
||
Previously, no cross builds were controllable from the command line. | ||
Machine-specific options like the pkg-config path and compiler options only | ||
affected native targets, that is to say all targets in native builds, and | ||
`native: true` targets in cross builds. Now, prefix the option with `build.` to | ||
affect build machine targets, and leave it unprefixed to affect host machine | ||
targets. | ||
|
||
For those trying to ensure native and cross builds to the same platform produced | ||
the same result, the old way was frustrating because very different invocations | ||
were needed to affect the same targets, if it was possible at all. Now, the same | ||
command line arguments affect the same targets everwhere --- Meson is closer to | ||
ignoring whether the "overall" build is native or cross, and just caring about | ||
whether individual targets are for the build or host machines. |
Oops, something went wrong.