| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
|
|
|
|
|
|
When run_command() first parameter is a compiler object, keep additional
exelist values as arguments.
|
|
Nix uses absolute paths to compilers in Nix store with Meson.
Those store paths contain a hash, which can contain short strings
like icl, resulting in incorrectly matching the compiler.
https://github.com/NixOS/nixpkgs/issues/73417#issuecomment-554077964
|
|
Probably dating back to the former mesonrewriter command?
Fixes commit d4fe805a51d5
In some corner cases, "rewriter" could be mistaken as a positional
argument.
|
|
|
|
|
|
|
|
|
|
Previously if a user tried to pass a command line build
option that contained a '%' character the command line
parser assumed that there was string interpolation to be
done. As there is no sense in such a scenario no code
provides any input for the interpolation. This then leads to
a failure.
In this commit we specifically override the defaults in
ConfigParser and set interpolation to None, which disables
command line build option interpolation.
Fixes #6157
|
|
This reverts commit 7b9c348102792030859ed0001a51416506a0a092.
Closes #6027.
|
|
A new Meson user may not realize how easy it is to get Ninja via
pip install ninja
|
|
Previously, warnings genereated in CMake were not logged because
CMake sends them to stderr alongside the trace information. With
this PR, only real trace lines are send to the trace parser and
all other lines in stderr are logged as warnings.
|
|
|
|
|
|
Added two new failing tests.
|
|
|
|
|
|
Fixes #5800
|
|
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
|
|
This way we can easily check that we only provide builtin targets such
as clang-format if the user has not provided their own.
|
|
The current state of this manual can best be described as... confusing.
The flow of the page jumps from one topic to the next without ever
actually telling you what you can do, so it's almost impossible to keep
track of what is supported, while instead going into involved derails
about why you'd want to use a wrap, and scattering some (but not all)
information throughout the promo material.
The most important changes this rewrite does (aside from turning
supported keys into a list of bullet points) is adding documentation for
the lead_directory_missing property, and mentioning that wrap-hg and
wrap-svn exist. I had to find out all of this by reading the source code
implementation, so let's try to save other people the effort.
Other miscellania: as per @jpakkane's comment, take the opportunity to
point out that wrap dependencies are also useful on Linux, in cases
where your distro doesn't have a new enough version of "$dependency".
It's a fairly common problem outside of select rolling-release distros,
so well worth mentioning.
|
|
In a large project, it can be hard to guess what meson "had in mind", when many different
warnings are added in different places. Let's make the message precise and specify the location.
WARNING: Consider using the built-in warning_level option instead of adding warning flags by hand.
â
meson.build:414: WARNING: Consider using the built-in warning_level option instead of using "-Wextra".
|
|
|
|
|
|
|
|
Make FAQ entry about linking failing on Windows with MSVC more easily discoverable by including keywords LNK1181 and linking.
|
|
|
|
|
|
|
|
fixes #6130
wrap: more error verbosity
|
|
correct syntax issues, missing imports revealed by type annotation checking
|
|
since 'cpo' is global, use `set` instead of `setlocal`.
Reported-By: Bram Moolenaar <Bram@vim.org>
Signed-off-by: Liam Beguin <liambeguin@gmail.com>
|
|
This means that when either cflags or libs lookup fails, this will be
logged always in the log, leading to much easier to debug messages
like:
Called `/usr/local/bin/pkg-config --cflags gnutls` -> 1
pkg-config error with 'gnutls': Could not generate cargs for gnutls:
Package nettle was not found in the pkg-config search path.
Perhaps you should add the directory containing `nettle.pc'
to the PKG_CONFIG_PATH environment variable
Package 'nettle', required by 'gnutls', not found
Run-time dependency gnutls found: NO (tried pkgconfig)
|
|
The stderr of pkg-config was never used, leading to no details about
failures at all in exception messages.
|
|
Previously even when meson failed to obtain cflags or libs for a
dependency it would lead to the dependency being found, causing very
confusing errors at build time.
|
|
|
|
|
|
- Typos were found by codespell v1.16.0
|
|
|
|
|
|
FreeBSD uses ${PREFIX}/libdata/pkgconfig as default pkgconf search path
for non-base libraries. This commit makes that directory the default
install_dir in the pkgconfig module on FreeBSD.
|
|
Under Windows, the colon ':' is used after the drive letter.
So, the colon should not be used as a list separator or for splitting,
otherwise it could lead to paths in CMAKE_PREFIX_PATH with a
semicolon ';' between the drive letter and the rest of the path, e.g:
-DCMAKE_PREFIX_PATH=C;/foo/bar
instead of
-DCMAKE_PREFIX_PATH=C:/foo/bar
Use os.pathsep instead of ':' to split the environmental variable
CMAKE_PREFIX_PATH
|
|
bugfix: fortran compiler assertionerror from 0c22798
|
|
|
|
|
|
|
