| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
When building for iOS, the Qt binaries only contain static libraries
and headers. No framework.
With this, Meson can successfully compile and link to Qt on iOS
|
|
This is a regression from previous releases and breaks existing build
files, such as GStreamer. The proper fix is in master (#4857), but we
cannot backport that since it is a complete rewrite of the framework
detection.
|
|
See: https://github.com/mesonbuild/meson/pull/4630#issuecomment-459235498
|
|
When using pkg.generate(mylib, library : publicdep) it is pretty clear
we don't want to associate publicdep to this generated pkg-config file.
This is a small behaviour break in theory, but also fixes real bug in
the case publicdep is later used to generate another pkg-config file
that does not depend on mylib, that would write a wrong `Requires:
mylib` in the genarated pkg-config file.
This fix unavoidable deprecation warning when glib is cross built
for Android. Glib does `pkg.generate(libglib, libraries : [libintl],
...)` which wrongly associates libintl to the generated glib-2.0.pc, so
when later it generates gio-2.0.pc file that depends on libglib, it will
warn about libintl being associated with libglib. This does not happen
in normal glib build because libintl is usually provided by glibc and is
only an internal library when it fallbacks to a subproject.
|
|
|
|
|
|
Our builddir ABI is stable across minor (stable) releases, so there is
no need to force a wipe. We already release pretty often, no need to
force people to wipe twice as often.
|
|
Since `_process_libs` appends the lib's dependencies this list already,
the final return value of `_process_libs` will end up after its
dependencies, which is the wrong way around. (The lib must come first,
then its dependencies)
The easiest solution is to simply pre-pend the return value of
`_process_libs` rather than appending it, so that its dependencies come
after the library itself.
Closes #4091.
|
|
Because we need to store those as well.
|
|
If the coredata file has been truncated, that's pretty much the same as
being corrupt, handle that via the same path.
|
|
Which can happen due to internal refactorings, such as the removal of
the ConfData class between 0.49 and 0.50
|
|
Otherwise Python gets all confused and it makes testing difficult.
Also minimally emulate the behaviour of the normal object to make the rest
of the code happy.
|
|
When python sees an invalid character in a filename for the current locale,
instead of clobbering it, it saves is as an invalid codepoint called a
surrogate. We need to explicitly instruct the encoder to write those out
as-is. In the JSON file, we replace them instead to produce valid json.
|
|
On OpenBSD, the main PowerPC machine is known as macppc, while the processor
family is powerpc:
$ uname -{m,p}
macppc powerpc
$ echo 'import platform; print (platform.machine())' | python3
macppc
$ echo 'import platform; print (platform.processor())' | python3
powerpc
This allows for e.g. GLib configure to properly detect that cpu:
Build machine cpu family: ppc
Build machine cpu: macppc
While it failed before with: WARNING: Unknown CPU family 'macppc' <snip>
|
|
This is a regression introduced by 2cbf7caf5, generated pkg-config files
have many duplicated '-pthread' flags.
|
|
|
|
This seems to be related to deleting the current working directory.
Simply deleting all of the trees inside the build directory instead
seems to fix it. This only appears with some combination of generated
targets, running the test case against say "1 trivial" doesn't show the
bug.
See this mesa bug: https://bugs.freedesktop.org/show_bug.cgi?id=109071
|
|
Fixes #4641
|
|
Since 0.46.1 pkg-config detection has been broken using the qt from homebrew,
due to a bug in homebrew (I think). Tested with qt 5.12.0 on Mojave.
|
|
|
|
As would happen if someone tried to manually call meson --wipe on a
directory configured with a version < 0.49.0
|
|
We previously didn't require it so we shouldn't silently start doing so.
Fixes #4654
|
|
|
|
This reinstates 2256e6314b610b8f6645d0c5384536001ddeccf9, which was
lost in refactoring in 9f9cfd21396db5cd5eb1711916c8b0c6e433c702.
|
|
|
|
|
|
If you change only some project in meson.build,
only that .vcxproj file will be updated and reloaded.
If you change something not related to VS solution and projects
or simply touch the meson.build file, nothing will be reloaded.
|
|
Yo dawg! We heard U don't like kwargs in kwargs, so we made it
impossible to put kwargs in your kwargs so now you can't kwargs with
your kwargs.
|
|
|
|
None is not iterable so it would trigger a TypeError later when link_args are
passed on to CompilerArgs.extend_direct().
|
|
|
|
This is the same case as 32-bit x86 on x86_64.
Closes https://github.com/mesonbuild/meson/issues/4586
|
|
Use a single point of exit for the detect_cpu* functions, and factor
out the compiler define code into a helper function.
|
|
Starting with VS 2017, `Platform` is not always set (f.ex., if you use
VsDevCmd.bat directly instead of vcvars*.bat), but `VSCMD_ARG_HOST_ARCH`
is always set, so try that first.
|
|
|
|
Try to guess which VS Command Prompt was used for the Meson call.
If one is chosen invoke it before calling Meson in REGEN command.
|
|
- Add libraries from InternalDependency.libraries
- Deprecate association of libraries from the "libraries" keyword
argument to the generated pkg-config file.
|
|
|
|
After we make this work consistently, we can try to abstract the new pattern.
|
|
|
|
If a project generates a single pc file but multiple shared libraries
with dependencies on each other, the generated pc name will be used to
generate a Requires.private dependency, which means the project will
depend on itself. This breaks at least some versions of pkg-config
(0.27 in RHEL7) which cannot handle the recursion and error out.
When adding the dependency using the pc name, check that it's not
on the project itself.
Fixes #4583
|
|
Add 'meson subprojects update' command
|
|
summary from stdout is often used by Automated builds to show build details
The --print-summary option was added to gcovr in v3.2, since html output
was added only in 3.1, limitting support to 3.2 wonât be a big deal.
--print-summary is not enabled for text/xml report generation as it will
result in meson not supporting any gcovr version less than 3.2.
|
|
|
|
|
|
This is inspired by gst-build's git-update script.
|
|
Fix 'meson introspect --target-files' for a custom target
|
|
|
|
mintro: Allow introspect --projectinfo without build directory
|
