| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\
| |
| | |
project test junit schema + a few more uses
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This does a couple of nice things, one is that editors like vscode can
be configured to use this schema to provide auto completion and error
highlighting if invalid values are added or required values are missing.
It also allows us test that the format of the test matrix work in a unit
test, which I've added. It does require that the python jsonschema
package is installed.
|
| |
| |
| |
| |
| | |
Also note that meson doesn't use `el` on the end of the cpu_family to
mark endianness, that the endian field needs to be set appropriately.
|
|/ |
|
|
|
|
| |
Rather than the legacy cgit
|
| |
|
|
|
| |
Using meson version `0.53.2` prefix defaulted to `/usr/local`, not `/usr/local/` (not the trailing slash)
|
|
|
|
|
|
| |
It can happen that a server is temporaly down, tarballs often have
many mirrors available so we should be able to add at least one fallback
mirror in wrap files.
|
| |
|
|\
| |
| | |
Fix library(name_prefix: [])
|
| |
| |
| |
| |
| |
| |
| | |
Refine documentation of the default name_prefix, so people don't get the
impression they can write logic which uses 'lib' as the default, when
they should be defaulting to '[]', to let us take care of the
complexities.
|
| |
| |
| |
| | |
When set to **true** only the last component is used. And throw in two minor
grammatical fixes while we're there.
|
|/
|
| |
At https://mesonbuild.com/Reference-tables.html#compiler-and-linker-selection-variables, the table is broken and it seems that the only difference with other well-working tables on this page is the semi-column ":" that are present under Language.
|
|
|
|
|
| |
Very out of date instructions. We install `meson.exe` now and you
don't need to have `py` in PATH or use `/path/to/meson.py`.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
It is not always needed to test generated tarballs, for example when
they are generated by CI that already does its own testing.
|
| |
|
|
|
|
| |
Fixes #1949
|
|
|
|
|
|
| |
Rather than having two separate sections with duplicated information
lets just have one for the common settings, and only document sections
specific to each file in separately
|
| |
|
|
|
|
| |
This reverts commit 097dfc085e6a1bb3c670880134a52dcfca504be7.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Fix #3969
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
With Meson 0.53.1, this is now out of date. Updating to use the proper ld variables.
|
| |
|
| |
|
|
|
|
|
| |
We really should be documenting these in an easy to find and reference
place.
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Fix d compiler abstractions
|
| |
| |
| |
| |
| |
| | |
This is needed when mixing D and C code, as it's possible to end up
witha combination of linkers and compilres such that C produces pdb
files but D does not.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This allows the harness to apply the version correctly, putting it in the right
place, dropping the right amount of numbers, etc.
pdb taking a version allows it to be more easily copied from the
shared_lib type.
|
| |
| |
| |
| |
| | |
This allows fixing tests that produce .dylib's on macOS and .so's on elf
Unices.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
It may not be obvious to users that these two ways to set build-types
override each other and specifying both is redundant, and conflicts
are resolved based on whichever is specified later.
Closes https://github.com/mesonbuild/meson/issues/6742
|
| |
| |
| | |
Co-authored-by: Vedran Miletić <vedran@miletic.net>
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
[why]
Sometimes one want to set the 'Conflicts:' field in .pc files.
This is possible by using the 'conflicts' keyword argument in the
pkgconfig module. The feature is not documented on mesonbuild.org,
though.
But a warning is issued:
WARNING: Passed invalid keyword argument "conflicts".
WARNING: This will become a hard error in the future.
History:
It has been added along with kwarg 'url' with commit
309041918 pkgconfig: Add missing 'URL' and 'Conflicts' entries
Later the kwargs check has been introduced with
80d665e8d Converted some modules.
but both 'url' and 'conflicts' were missing.
With commit
2acf737b pkgconfig: Document url keyword
the 'url' kwarg has been added to the checks, but not 'conflicts'.
[how]
Add 'conflicts' to the allowed kwargs.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
|
|\ \
| | |
| | | |
Add add_languages(native:)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This improves the common case of a simple meson.build which doesn't
contain any 'native: true' targets to not require a native compiler when
cross-compiling, without needing any changes in the meson.build.
v2:
Do it the right way around!
|