| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
this should help users specify leading `~` in various Meson options and variables
without refactoring lots of places inside Meson itself.
|
|
fs: make exception specify method name
fs: actually raise exceptions
fs: resolve path e.g. /opt/foo/.. => /opt/foo
fs: correct behavior of is_symlink
|
|
The documentation of "order-only" dependencies is limited and their
various purposes are especially not clear. See issue #6391 for a recent
example, search the internet for many more. So mention the particular
purpose here while making the documentation barely longer.
|
|
|
|
|
|
|
|
This allows Meson native-file [properties] to be used.
This avoids the need to call meson from a script file or have a
long command line invocation of `meson setup`
The method meson.get_native_property('prop', 'fallback') is added.
The native file can contain properties like
```
[properties]
myprop1 = 'foo'
mydir2 = 'lib/custom'
```
Then from within `meson.build`
```meson
x1 = meson.get_native_property('myprop1')
thedir = meson.get_native_property('mydir2', 'libs')
```
fallback values are optional
|
|
Add new Meson sample templates
|
|
Closes: #3472.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixes #6510
|
|
Add ability to set and query arbitrary variables on declare_dependency objects
|
|
|
|
|
|
Fixes #6456
|
|
|
|
|
|
|
|
Fixes #6492
|
|
The rust code is ugly, because rust is annoying. It doesn't invoke a
linker directly (unless that linker is link.exe or lld-link.exe),
instead it invokes the C compiler (gcc or clang usually) to do it's
linking. Meson doesn't have good abstractions for this, though we
probably should because some of the D compilers do the same thing.
Either that or we should just call the c compiler directly, like vala
does.
This changes the public interface for meson, which we don't do unless we
absolutely have to. In this case I think we need to do it. A fair number
of projects have already been using 'ld' in their cross/native files to
get the ld binary and call it directly in custom_targets or generators,
and we broke that. While we could hit this problem again names like
`c_ld` and `cpp_ld` are far less likely to cause collisions than `ld`.
Additionally this gives a way to set the linker on a per-compiler basis,
which is probably in itself very useful.
Fixes #6442
|
|
In order to unify the use of sysroot in the cross-file,
the pkg_config_libdir can now be passed directly in the file.
|
|
|
|
|
|
Commit 1404f404 (#4744) introduced this typo, making the link not jump to the correct section when clicked.
|
|
It's worth to list a meson project building a firmware.
|
|
|
|
|
|
Remove "(not the default yet)" from Glib, Orc and Pango
|
|
Fixes #6411
|
|
|
|
In declare_dependency() and dependency.get_variables().
|
|
Requested by scivision@
|
|
Most of the OSes Meson supports actually do have package managers,
and at least some of them are not harder to use than Linux ones.
|
|
|
|
|
|
This fixes an issue with generated sources and object libraries, as
well as an issue on windows with the `link` linker and the vs backend.
The last issue is resolved by building the source files multiple times
to avoid extracting object files in meson.
|
|
Fixes: #6372.
|
|
this can be useful for if/elif where linker behaviors must be
considered.
For example, clang with "link" vs gcc with "ld.bfd" etc.
ci for compiler.get_linker_id() method
doc
add @FeatureNew check
Co-Authored-By: Daniel Mensinger <daniel@mensinger-ka.de>
|
|
is_samepath better reflects the nature of this function--that files
and directories can be compared.
Also, instead of raising exceptions, simply return False when one
or both .is_samepath(path1, path1) don't exist. This is more
intuitive behavior and avoids having an extra if fs.exist() to go
with every fs.is_samepath()
|
|
|
|
Add a summary() function for configuration summarization
|