Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Because that's what we need, of course
|
|
This should have been supported before, but wasn't.
|
|
|
|
and use textwrap.dedent to make the very large messages more readable
and not break method folding.
|
|
|
|
This reverts commit 72365e6856e688054938f6055af66f0ac83d261e.
This is a vanity project that no longer exists.
See discussion at #8890, which still requires further thought but we can
at least start off by removing something clearly invalid.
|
|
Tests that we find something sensible for intl, capable of producing
binaries using gettext() to translate stuff.
No more need to manually check headers and *maybe* include the intl
library, which we were doing before; the new dependency actually
simplifies the existing test, and should simplify users' build files
too...
|
|
Checking how to aquire the *gettext family of symbols portably is
annoyingly complex, and may come from the libc, or standalone.
builtin dependency:
This detects if libintl is unneeded, because the *gettext family of
symbols is available in the libc.
system dependency:
This detects if libintl is installed as separate software, linkable via
-lintl; unfortunately, GNU gettext does not ship pkg-config files for
it.
Fixes #3929
|
|
Since we pass a method: 'foo' to every one of these
config-tool/pkg-config dependencies, we do not ever need to check which
type_name it has; change these to asserts instead.
In the process, we discover a bug! We kept checking for type
'configtool' instead of 'config-tool', so these tests all
short-circuited and checked nothing. Once moved to an assert, the
asserts failed.
Add a new lookup for a known system dependency and make it assert that
too.
|
|
mesonbuild.dependencies.__init__ exposes configtool, pkgconfig, cmake
and more in __init__.py, so there's no reason we should be tying
SystemDependency to the internal organization implementation of the
subpackage!
In the 2nd previous commit it took quite some effort to figure out that
the python module "does not exist" because of import errors while
refactoring something completely different.
|
|
For dependencies that on some systems are built into libc etc. and don't
need to be separately linked. This is distinct from "system"
dependencies which add linker args.
|
|
In accordance with review comments; it's small enough this seems fitting.
|
|
|
|
The dependency lookup is a lot of complex code. This refactor it all
into a single file/class outside of interpreter main class. This new
design allows adding more fallbacks candidates in the future (e.g. using
cc.find_library()) but does not yet add any extra API.
|
|
When no message is provided to assert(), it uses the ast printer to show
the condition that failed. In this case the 'not' is the first string
appended to the result, self.result[-1] would raise range error.
|
|
Rewrite the Qt module for type safety!
|
|
|
|
Which has been missing since the module was added in 0.57.0.
This also uses the include syntax
|
|
Insteadf of qt4 referencing the Qt5 page, include the same content in
both.
|
|
|
|
This really shouldn't be necissary, but fixing the typing annotations of
ModuleReturnValue is much harder than just returning the Holder
directly.
|
|
Remove an unused method (that didn't work before this series), and
remove the ability to pass a Generator to the GeneratedListHolder, it's
never used and it's weird and not the way Meson generally works now.
While we're here, finish the type annotations.
|
|
|
|
|
|
|
|
|
|
For generator.process_files. Just cleaner and nicer
|
|
It's really a property of the Generator what name to use, not something
that should be passed to each call to process files.
|
|
For qt we already have all of the necissary checking in place. Now in
the interpreter we have the same, the intrperter does all of the
checking, then passed the arguments to the Generator initializer, which
just assigns the passed values. This is nice, neat, and clean and fixes
the layering violatino between build and interpreter.
|
|
Do the type checking in a nice tidy way
|
|
This requires that the interpreter has done the validation, which it now
does at all callsites. This simplifies the Generator initializer.
|
|
This is an odd pattern, not the way most Holders work, and would be
problematic if a method wanted to return a Generator.
|
|
|
|
|
|
This just ignores the fact taht Generator is unchecked. Generator needs
some real love in terms of type checking.
|
|
|
|
|
|
|
|
This adds a number of missing type annotations to existing functions,
and makes a few members protected instead of public, as they were never
meant to be public
|