Age | Commit message (Collapse) | Author | Files | Lines |
|
deps: Do not deepcopy internal libraries (fixes #7457)
|
|
want_output gives us the output file. We don't need the file. We just
need the compiler stderr, which is always stored.
|
|
|
|
In every other compilers level 0 maps to no argument at all.
|
|
Put it in the log file if necessary. Users don't need to know this.
It's very spammy.
|
|
|
|
* Add boost_root support to properties files
This commit implements `boost_root`, `boost_includedir`, and
`boost_librarydir` variable support to native and cross properties
files. The search order is currently environment variables, then
these variables, and finally a platform-dependent search.
* Add preliminary boost_root / boost_includedir tests
Each test contains a fake "version.hpp", as that's how boost detection is
currently being done. We look for this file relative to the root directory,
which probably shouldn't be allowed (it previously was for BOOST_LIBRARYDIR
but not for BOOST_ROOT). It also cannot help with breakage detection in
libraries, however it looks like this wasn't getting tested beforehand.
I've given the two unique version numbers that shouldn't be present in any
stock version of boost (001 and 002).
* Add return type to detect_split_root
* Return empty list when nothing found in BOOST_ROOT, rather than None
* Update boost_root tests
* Create nativefile.ini based on location of run_project_tests.py
* Add fake libraries to ensure boost_librarydir is being used
* Require all search paths for boost to be absolute
* Redo boost search ordering
To better match things like pkg-config, we now look through native/cross files,
then environment variables, then system locations for boost installations.
Path detection does not fall back from one method to the next for properties or
environment variables--if boost_root, boost_librarydir, or boost_includedir is
specified, they must be sufficient to find boost. Likewise for BOOST_ROOT and
friends. pkg-config detection is still optional falling back to system-wide
detection, for Conan.
(Also, fix a typo in test 33's nativefile)
* Correct return type for detect_roots
* Correct boost dependency search order in documentation
* Print debug information for boost library finding, to resolve CI issues
* Handle native/cross file templates in a more consistent way
All tests can now create a `nativefile.ini.in` if they need to use some
parameter that the testing framework knows about but they can't.
* Pass str--rather than PosixPath--to os.path.exists, for Python35
* Look for boost minor versions, rather than boost patch versions in test cases
* Drop fake dylib versions of boost_regex
* Prefer get_env_var to use of os.environ
* Correct error reporting for relative BOOST_ROOT paths
* Bump version this appears in. Also, change "properties file" to "machine file" as that appears to be the more common language.
|
|
When a list_sep is provided (e.g. ', ') all items are printed on the
same line, which gets ugly on very long lists (e.g. list of plugins
enabled).
|
|
This method aims to offer a simple way to 'substring'
an existing string with start and end values.
|
|
|
|
Co-authored-by: wb9688 <wb9688@users.noreply.github.com>
|
|
|
|
We have experimented with the module for about a year in a qemu
branch (https://wiki.qemu.org/Features/Meson), and we would like to
start moving the build system to meson. For that, keyval should have
the stability guarantees.
Cc: Paolo Bonzini <pbonzini@redhat.com>
|
|
Fixes:
NameError: name 'EnvironmentException' is not defined
Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
|
|
fixes #7404
|
|
This comment was added in 0fbd09609f4, where the case of a forward
slash was added for the case when cross compiling.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This avoid printing long backtrace by default, the user already has the
output of the git command printed for debugging purpose since we don't
redirect stdout/stderr.
|
|
This header erroneously referred to the dynamic linker while the paragraph talks about
the "link editor." Change the title to account for the difference.
|
|
Solaris fixes revisited
|
|
|
|
Python test upgrade
|
|
Add depfile support to generated targets for Qt >= 5.14.
Move warning into the module init itself, to check if the version is too
old before issuing. Also tweak the wording itself, to advise upgrading
to a suitable version of Qt5 instead of advising to wait for a Qt bug to
be fixed.
|
|
This was missed somehow when the feature was added a few years ago.
|
|
vc2017x64vs and vc2019x64vs sometimes timeout because they exceed the
60 min default limit.
|
|
I made the mistake of always selecting the debug CRT for compiler
checks on Windows 4 years ago:
https://github.com/mesonbuild/meson/pull/543
https://github.com/mesonbuild/meson/pull/614
The idea was to always build the tests with debugging enabled so that
the compiler doesn't optimize the tests away. But we stopped doing
that a while ago, and also the debug CRT has no relation to that.
We should select the CRT in the same way that we do for building
targets: based on the options.
On Windows ARM64, the debug CRT for ARM64 isn't always available, and
the release CRT is available only after installing the runtime
package. Without this, we will always try to pick the debug CRT even
when --buildtype=debugoptimized or release.
|
|
|
|
|
|
|
|
|
|
|
|
before this, tests were being skipped on Ubuntu 20.04 with Anaconda Python
Now, all 5 tests success
|
|
|
|
|
|
|
|
|
|
|
|
MyPy looks to .mypy.ini, reducing Meson top-level visual clutter
https://mypy.readthedocs.io/en/stable/config_file.html
|
|
|
|
|
|
|
|
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
|
|
As suggested by dcbaker in
https://github.com/mesonbuild/meson/pull/7370#discussion_r445145889
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
|
|
As suggested by dcbaker in
https://github.com/mesonbuild/meson/pull/7370#pullrequestreview-436872661
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
|
|
|