summaryrefslogtreecommitdiff
path: root/docs/markdown/Cross-compilation.md
AgeCommit message (Collapse)Author
2018-03-29docs: Expand on compiler vs compilee build host and target (#3308) [skip ci]John Ericson
2018-03-23docs: fix one 'target' that should be 'host' [skip ci]John Ericson
The target platform of cross compiler is the host platform of the project being built.
2018-03-11docs: update system cross file documentationJon Turney
Works on all non-Windows since cf98f5e3 (PR #3119)
2017-11-30cross: Implement support for loading cross files from system pathsDylan Baker
One thing that makes cross compiling with meson a pain is the need for cross files. The problem is not with cross files themselves (they're actually rather brilliant in that they allow for a much greater deal of flexibility than autotools hardcoded paths approach) but that each user needs to reimplement them themselves, when for most people what they really want is a cross file that could be provided by their distro, all they really want is the correct toolchain. This patch is the first stop to making it easier for distros to ship their own cross files (and for users to put their's somewhere safe so they don't get `git clean`ed. It allows the cross files (on Linux and *BSD) to be stored in home and system paths (~/.config/meson/cross, /usr/share/meson/cross, and /usr/local/share/meson/cross), and to be loaded by simply by specificying --cross-file. With this patch meson will check the locations its always checked first, (is cross file absolute, or is it relative to $PWD), then will check ~/.config/meson/cross, /usr/local/share/meson/cross, /usr/share/meson/cross, (or $XDG_CONFIG_PATH and $XDG_DATA_DIRS) for the files, raising an exception if it cannot find the specified cross file. Fixes #2283
2017-10-26docs: add pkgconfig to cross file exampleMike Gilbert
2017-08-21Rewrapped lines of a few more files.Jussi Pakkanen
2017-05-29environment: Add needs_exe_wrapper for overriding auto-detection.Ole André Vadla Ravnås
This is useful when build_machine appears to be compatible with host_machine, but actually isn't. For example when: - build_machine is macOS and host_machine is the iOS Simulator - the build_machine's libc is glibc but the host_machine libc is uClibc - code relies on kernel features not available on the build_machine
2017-05-03doc: Fix several minor typos.Elliott Sales de Andrade
2017-05-03docs: add a short description for all top pages in the ManualPeter Hutterer
2017-04-26docs: Import the website and wiki and build with hotdocThibault Saunier
This allows us to more easily have the documentation in sync with the source code as people will have to document new features etc right at the time where they implement it.