| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
There's starting to be a lot of things including coredata that coredata
needs to itself include. putting it in mesonlib makes more sense
|
| | |
|
| |
|
|
|
|
| |
Most options don't use language prefaced options (std vs c_std)
internally, as we don't need that due to namespacing. Let's do that
across the board
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
So that every subclass doesn't have to reimplement it. Especially since
the Gnu implementation moved out of the CCompiler and into the
GnuLikeCompiler mixin
|
| | |
|
| |
|
|
| |
Every language had the exact same implementation
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
Fixes #4027
|
| | |
|
| |
|
|
|
|
|
|
| |
Currently this is done at the instance level, but we need it at the
class level to allow compiler "lang" args to be gotten early enough.
This patch also removes a couple of instance of branch/leaf classes
providing their own implementation that is identical to the Compiler
version.
|
| |
|
|
|
| |
We know that if a compiler class inherits CCompiler it's language will
be C, so doing this at the class level makes more sense.
|
| | |
|
| |
|
|
| |
- Typos were found by codespell v1.16.0
|
| | |
|
| |
|
|
|
|
| |
Now that the linkers are split out of the compilers this enum is
only used to know what platform we're compiling for. Which is
what the MachineInfo class is for
|
| | |
|
| |
|
|
|
| |
Since they are laways paired there is no need to "search" for the cuda
linker.
|
| |
|
|
| |
Fixes issue #5870
|
| |
|
|
|
|
|
|
|
|
|
|
| |
class
Instead of the DynamicLinker returning a hardcoded value like
`-Wl,-foo`, it now is passed a value that could be '-Wl,', or could be
something '-Xlinker='
This makes a few things cleaner, and will make it possible to fix using
clang (not clang-cl) on windows, where it invokes either link.exe or
lld-link.exe instead of a gnu-ld compatible linker.
|
| |
|
|
|
| |
Most of the cuda code is from Olexa Bilaniuk.
Most of the PGI code is from Michael Hirsc
|
| | |
|
| |
|
|
|
| |
Even with the check (for extra safety) string.replace is more than twice
as fast.
|
| |
|
|
|
| |
I debated a bit whether both classes really belong in the same module,
and decided that they do because the share a number of helpers.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
In most cases instead pass `for_machine`, the name of the relevant
machines (what compilers target, what targets run on, etc). This allows
us to use the cross code path in the native case, deduplicating the
code.
As one can see, environment got bigger as more information is kept
structured there, while ninjabackend got a smaller. Overall a few amount
of lines were added, but the hope is what's added is a lot simpler than
what's removed.
|
| | |
|
| | |
|
| |
|
|
| |
Partially addresses #4961.
|
| |
|
|
|
|
|
| |
PArtially addresses #4961.
Also make the sanity check do double duty as a GPU architecture
detection test.
|
| | |
|
| |
|
|
|
|
|
| |
Also adds test case for shared library linking.
Closes #4912, at least on Linux. The future 0.50.0 does not yet claim to
support CUDA on systems other than Linux and backends other than Ninja.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
