| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Fixes #8605
|
|
They behave slightly differently than other env vars, so have a test for
them as well.
|
|
They are supposed to have different behavior. The environment variables
apply to both the compiler and linker when the compiler acts as a
linker, but the command line ones do not.
Fixes #8345
|
|
1. use `locale.getpreferredencoding()` to get encoding name.
`bytes.decode()` assumes `encoding='utf-8'` by default. It is incorrect on my
Windows setup, and causes `UnicodeDecodeError`.
2. use `errors='replace'`.
`bytes.decode()` assumes `errors='strict'` by default. Meson shouldn't crash
if subprocess outputs some garbage that can't be decoded.
`surrogateescape` doesn't work as expected on Windows. On Linux, default
`errors` for `sys.stdout` is `strict`, so `surrogateescape` can't be used there
too (at least until `sys.stdout` is reconfigured).
Fixes https://github.com/mesonbuild/meson/issues/8480
|
|
|
|
|
|
Otherwise user cannot understand which wrap file is missing or wrong
|
|
When using --reset we should guarantee that next reconfigure will pick
the latest code. For wrap-file we have no way to know if the revision
changed, so we have to delete the source tree and extract again.
It is unlikely that user has local changes in non-git subprojects, and
--reset is known to be dangerous.
|
|
The host cache had BUILD, which is wrong.
|
|
Fixed version of #8527
|
|
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.
|
|
Closes #8523.
|
|
No coverage, no tests, unreadable, unused, likely premature
optimization.
|
|
Makes command-line more readable.
|
|
|
|
Some variables are reserved because meson set them automatically. But we
are not setting them for dataonly pc files, so there is no reason to
reserve them.
Fixes: #8583.
|
|
It is not documented and does not seems to be used anywhere.
|
|
They are not used anywhere.
|
|
|
|
It looks like when Windows media scanner holds files we can't change
their permission neither.
|
|
SInce the build directory is `builddir/` it should be
`builddir/meson-logs/testlog.txt` to be uploaded.
|
|
QT: use a proper dependency factory
|
|
|
|
|
|
Fix spurious sandbox violation warning
|
|
If the installed files don't have suitable file permissions depfixer
will fail to process it. Temporarily lax file permissions to work around
this.
|
|
* compilers: clang-cl: Also accept .s files
clang-cl has support for gas-compatible assembly files.
* Add clang-cl to '128 generated assembly' test
|
|
|
|
|
|
Instead of using qmake, use config-tool. This is no different than when
we deprecated the other per-dependency config-tool types (sdl2-config,
llvm-config, etc) for just config-tool
|
|
Currently the Qt Dependencies still use the old "combined" method for
dependencies with multiple ways to be found. This is problematic as it
means that `get_variable()` and friends don't work, as the dependency
can't implement any of those methods. The correct solution is to make
use of multiple Dependency instances, and a factory to tie them
together. This does that.
To handle QMake, I've leveraged the existing config-tool mechanism,
which allows us to save a good deal of code, and use well tested code
instead of rolling more of our own code.
The one thing this doesn't do, but we probably should, is expose the
macOS ExtraFrameworks directly, instead of forcing them to be found
through QMake. That is a problem for another series, and someone who
cares more about macOS than I do.
|
|
We don't always have qmake installed (and it's good to test failure
paths too!) so we can't expect this to succeed in all cases. With the
following commit we'll use a test.json to test both pkg-config and
qmake, so we need to be able to skip.
|
|
When doing include_directories('.') at the root of the subproject we
should not warn about sandboxing violation.
|
|
By default expected line must be matched in order. When an expected line
is matched it does not matter if it's matched again later or not.
When defining "count", it means that line must be matched exactly that
many times before matching the next expected line. Once all occurences
have been matched for an expected line, it not must appear any more in
all next lines.
|
|
|
|
|
|
* environment(): Allow stacking append() and prepend()
* Update docs/markdown/Reference-manual.md
Co-authored-by: Elliott Sales de Andrade <quantum.analyst@gmail.com>
Co-authored-by: Elliott Sales de Andrade <quantum.analyst@gmail.com>
|
|
RFC: logs: Prepend current subproject name to all messages
|
|
|
|
It already contains the full callstack and it's more visible when it's
standing on its own line.
|
|
|
|
|
|
|
|
Meson used to prepend '|' for each nested subproject to distinguish in
the logs where a subproject start and ends. It is more useful to print
the current subproject name.
Also print the call stack when starting a new subproject to better see
which subproject chain leads to to.
|
|
It's a method on the QtDependeny that exists purely for the consumption
of the qt module (in the form, return some stuff the module makes into
an instance variable). So put it where it actually belongs, and pass the
qt dependency into it.
|
|
As we break these classes up we're going to need this.
|
|
This code is really old, and it might be fine to delete this altogether,
but for now lets do this.
|
|
It's static anyway, and never overwritten.
|
|
Since Compiler is actually useful now as a base class, unlike when this
code was written.
|
|
And fix some style and correctness issues
|
