aboutsummaryrefslogtreecommitdiff
path: root/docs/markdown/howtox.md
AgeCommit message (Collapse)AuthorFilesLines
2021-03-28docs: Provide working instructions for scan-build [skip ci]Patryk Obara1-3/+17
Replace `meson compile scan-build` with `ninja -C dir scan-build`, because scan-build target does not work with `meson compile`. Note about SCANBUILD env variable was not precise enough to describe how to pass arguments to scan-build - provide an example to make it clear. Fixes: #7644.
2021-02-04Introduce `fs.read` to read a file as a stringLuke Drummond1-0/+17
Following #7890, this patch introduces the ability to read the contents of a file to the fs module. This patch introduces the ability to read files at configure time, but has some restrictions: - binary files are not supported (I don't think this will prove a problem, and if people are wanting to do something with binary files, they should probably be shelling out to their own script). - Only files outside the build directory allowed. This limitation should prevent build loops. Given that reading an arbitrary file at configure time can affect the configuration in almost arbitrary ways, meson should force a reconfigure when the given file changes. This is non-configurable, but this can easily be changed with a future keyword argument.
2021-01-31Capitalize "Meson" consistently as it is a proper name. [skip ci]Jussi Pakkanen1-1/+1
2021-01-30Rewrap long text lines in docs. [skip ci]Jussi Pakkanen1-27/+35
2020-07-14Replace `dynamic linker` with `linker` [skip ci]Nathan Lanza1-1/+1
This header erroneously referred to the dynamic linker while the paragraph talks about the "link editor." Change the title to account for the difference.
2020-06-30Replaced `ninja` with `meson` [skip ci]TheQwertiest1-3/+3
2020-06-18Merge pull request #7196 from cconverse711/llvm-covJussi Pakkanen1-2/+1
coverage: llvm-cov support
2020-06-18docs: replaced `ninja` with appropriate `meson` commands [skip ci]TheQwertiest1-5/+5
2020-06-17coverage: llvm-cov supportCary Converse1-2/+1
2020-05-14Docs: Make the suggested use for the not-found dependency better [skip ci]Dylan Baker1-4/+6
2020-05-14docs: Add a Howto about the null dependency [skip ci]Dylan Baker1-0/+23
2020-03-23Revert "Naturally use env vars a bit more to match Autoconf"Jussi Pakkanen1-8/+7
This reverts commit 097dfc085e6a1bb3c670880134a52dcfca504be7.
2020-03-23Naturally use env vars a bit more to match AutoconfJohn Ericson1-7/+8
PR #6363 made it so our interpretation of env vars no longer clashed with Autoconf's: if both Meson and Autoconf would read and env var, both would do the same things with the value they read. However, there were still cases that autoconf would read an env var when meson wouldn't: - Autoconf would use `CC` in cross builds too - Autoconf would use `CC_FOR_BUILD` in native builds too. There's no reason Meson can't also do this--if native cross files overwrite rather than replace env vars, cross files can also overwrite rather than replace env vars. Because variables like `CC` are so ubiquitous, and because ignoring them in cross builds just makes those builds liable to break (and things more complicated in general), we bring Meson's behavior in line with Autoconf's.
2020-03-23Fix legacy env var support with crossJohn Ericson1-13/+9
Fix #3969
2020-03-17envconfig: Make compiler and linker environment variables matchDylan Baker1-0/+6
2020-02-14docs: Update documentation about linker selectionNirbheek Chauhan1-2/+2
We missed this in https://github.com/mesonbuild/meson/pull/6457
2020-01-27docs: small cleanups and clarifications to setting the dynamic linker [skip ci]Dylan Baker1-3/+5
Fixes #6510
2020-01-22environment: Replace LD with <LANG>LDDylan Baker1-11/+23
The rust code is ugly, because rust is annoying. It doesn't invoke a linker directly (unless that linker is link.exe or lld-link.exe), instead it invokes the C compiler (gcc or clang usually) to do it's linking. Meson doesn't have good abstractions for this, though we probably should because some of the D compilers do the same thing. Either that or we should just call the c compiler directly, like vala does. This changes the public interface for meson, which we don't do unless we absolutely have to. In this case I think we need to do it. A fair number of projects have already been using 'ld' in their cross/native files to get the ld binary and call it directly in custom_targets or generators, and we broke that. While we could hit this problem again names like `c_ld` and `cpp_ld` are far less likely to cause collisions than `ld`. Additionally this gives a way to set the linker on a per-compiler basis, which is probably in itself very useful. Fixes #6442
2019-12-02docs: Update docs for LD and ld entriesDylan Baker1-2/+23
2019-11-10Document lack of clang support [skip ci]mayl1-0/+3
Meson doesn't currently provide a very helpful message when trying to generate a coverage report with clang, and in fact just silently fails for 2 of the 3 reports. Ideally Meson would support coverage with llvm-cov, or provide a more helpful error message. Until then, it seems it would be helpful to at least put a warning in the documentation
2019-02-01CMake: Added support for CMAKE_MODULE_PATH and extra CMake args (closes #4779)Daniel Mensinger1-0/+17
2019-01-08docs: further specify that CFLAGS and friends are only for distro packagers ↔Dylan Baker1-1/+3
[skip ci]
2018-06-24Update documentation about compiler envvars and cross files. [skip ci]Jussi Pakkanen1-11/+46
2018-03-20Docs: Correct env variable SCAN_BUILD to SCANBUILDMarvin Scholz1-2/+2
2017-11-19Documentation: Add note about SCAN_BUILDChristoph Behle1-0/+6
When running ninja scan-build you can use the environment variable SCAN_BUILD to choose the right executable.
2017-10-23Update references from mesonconf to meson configureKevin Anderson1-2/+2
Fixes #2372
2017-10-23docs: Markdown headers don't need trailing hash signsLuis Menina1-1/+1
This is a cosmetic change because github seems to interpret those correctly. Nonetheless, it adds unnecessary noise and makes people modifying the pages think it might be needed. See syntax guide at https://guides.github.com/features/mastering-markdown/
2017-07-04doc: Mention that C/C++ language versions can be set per-targetGabrĂ­el ArthĂșr PĂ©tursson1-0/+6
2017-05-04Use American English - 'ise' -> 'ize' where applicablePeter Hutterer1-1/+1
2017-05-04Use American English: behaviour -> behaviorPeter Hutterer1-1/+1
2017-05-03doc: Use https links wherever possible.Elliott Sales de Andrade1-1/+1
2017-05-03doc: Fix several minor typos.Elliott Sales de Andrade1-1/+1
2017-05-03doc: Capitalize things more consistently.Elliott Sales de Andrade1-1/+1
Upper or lower case depending on the official spelling, or the more consistent usage.
2017-04-28howtox.md: fix header hierarchyMathieu Duponchelle1-11/+7
.. and remove an obsolete wiki home link at the bottom of the page
2017-04-26docs: Import the website and wiki and build with hotdocThibault Saunier1-0/+160
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.