Searched +full:meson +full:- +full:build (Results 1 – 25 of 222) sorted by relevance
123456789
| /third_party/skia/third_party/externals/freetype/ |
| D | .gitlab-ci.yml | 2 - build
4 # FIXME: Use --werror once warnings are fixed.
6 MESON_ARGS: --fatal-meson-warnings
7 MESON_ARGS_WINDOWS: ${MESON_ARGS} --force-fallback-for=zlib
9 .build windows common:
11 # https://gitlab.freedesktop.org/gstreamer/gst-ci/container_registry/213
12 image: 'registry.freedesktop.org/gstreamer/gst-ci/amd64/windows:v14-master'
13 stage: 'build'
15 - 'docker'
16 - 'windows'
[all …]
|
| /third_party/mesa3d/docs/ |
| D | meson.rst | 1 Compilation and Installation Using Meson
5 ---------------
7 For general information about Meson see the `Meson
10 **Mesa's Meson build system is generally considered stable and ready for
15 Mesa requires Meson >= 0.53.0 to build.
19 <https://mesonbuild.com/Getting-meson.html>`__ to install the
20 current version of Meson.
22 The Meson build of Mesa is tested on Linux, macOS, Windows, Cygwin,
25 Unix-like OSes
28 If Meson is not already installed on your system, you can typically
[all …]
|
| D | install.rst | 8 meson
11 -----------------------------
16 Build system
19 - `Meson <https://mesonbuild.com>`__ is required when building on \*nix
21 - Android Build system when building as native Android component. Meson
30 - GCC 4.2.0 or later (some parts of Mesa may require later versions)
31 - Clang - exact minimum requirement is currently unknown.
32 - Microsoft Visual Studio 2019 Version 16.11 or later and
38 - `Python <https://www.python.org/>`__ - Python 3.5 or newer is required.
39 - `Python Mako module <http://www.makotemplates.org/>`__ - Python Mako
[all …]
|
| D | android.rst | 5 into the Android OS using the Android.mk build system on older versions
6 of Android, or out-of-tree using the Meson build system and the
9 The Android.mk build system has proven to be hard to maintain, as one
10 needs a built Android tree to build against, and it has never been
11 tested in CI. The meson build system flow is frequently used by
15 ------------------------------
18 Then, create your meson cross file to use it, something like this
19 ``~/.local/share/meson/cross/android-aarch64`` file::
22 ar = 'NDKDIR/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android-ar'
23 c = ['ccache', 'NDKDIR/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android29-clang']
[all …]
|
| /third_party/skia/third_party/externals/harfbuzz/ |
| D | TESTING.md | 1 ## Build and Test
4 meson build
5 ninja -Cbuild
6 meson test -Cbuild
12 meson test -Cbuild --gdb testname
15 ## Build and Run
18 Values defined in `hb-debug.hh`.
21 CPPFLAGS='-DHB_DEBUG_SUBSET=100' meson setup build --reconfigure
22 meson test -C build
28 meson setup build -Db_sanitize=address --reconfigure
[all …]
|
| D | BUILD.md | 4 …sudo apt-get install meson pkg-config ragel gtk-doc-tools gcc g++ libfreetype6-dev libglib2.0-dev …
8 sudo dnf install meson pkgconfig gtk-doc gcc gcc-c++ freetype-devel glib2-devel cairo-dev
12 sudo pacman -Suy meson pkg-config ragel gcc freetype2 glib2 cairo
14 then use meson to build the project like `meson build && meson test -Cbuild`.
16 On macOS, `brew install pkg-config ragel gtk-doc freetype glib cairo meson` then use
17 meson like above.
19 On Windows, meson can build the project like above if a working MSVC's cl.exe (`vcvarsall.bat`)
20 or gcc/clang is already on your path, and if you use something like `meson build --wrap-mode=defaul…
23 Our CI configurations is also a good source of learning how to build HarfBuzz.
26 HarfBuzz like `g++ src/harfbuzz.cc -fno-exceptions` but there is not guarantee provided
|
| /third_party/mesa3d/.gitlab-ci/build/ |
| D | gitlab-ci.yml | 2 .build-common:
3 extends: .build-rules
10 - _build/meson-logs/*.txt
11 - _build/meson-logs/strace
12 - shader-db
15 .build-linux:
16 extends: .build-common
23 - !reference [default, before_script]
24 - export PATH="/usr/lib/ccache:$PATH"
25 - export CCACHE_BASEDIR="$PWD"
[all …]
|
| /third_party/skia/third_party/externals/harfbuzz/.circleci/ |
| D | config.yml | 4 win32-executor:
6 - image: cimg/base:edge-20.04
7 win64-executor:
9 - image: cimg/base:edge-20.04
10 autotools-executor:
12 - image: cimg/base:edge-20.04
16 macos-aat-fonts:
20 - checkout
21 …- run: HOMEBREW_NO_AUTO_UPDATE=1 brew install pkg-config ragel freetype glib cairo python3 icu4c g…
22 - run: pip3 install meson --upgrade
[all …]
|
| /third_party/lz4/build/meson/ |
| D | README.md | 1 Meson build system for lz4
4 Meson is a build system designed to optimize programmer productivity.
5 It aims to do this by providing simple, out-of-the-box support for
9 This Meson build system is provided with no guarantee.
11 ## How to build
13 `cd` to this meson directory (`contrib/meson`)
16 meson setup --buildtype=release -Ddefault_library=shared -Dprograms=true builddir
18 ninja # to build
28 To configure build options, use:
31 meson configure
[all …]
|
| /third_party/pulseaudio/ |
| D | .gitlab-ci.yml | 1 # The build has two stages. The 'container' stage is used to build a Docker
4 # effectively a no-op. All of this infrastructure is inherited from the
5 # freedesktop/ci-templates repository which is the recommended way to set up CI
8 # Once the container stage is done, we move on to the 'build' stage where we
9 # run meson build. Currently, tests are also run as part of the build stage as
14 - container
15 - build
22 FDO_DISTRIBUTION_TAG: '2023-08-13-00'
29 # break due to upstream changing things, so if you see unexpected build
31 - project: 'freedesktop/ci-templates'
[all …]
|
| /third_party/glib/ |
| D | README.win32.md | 1 Chun-wei Fan `<fanc999@yahoo.com.tw>`
17 To build GLib on Win32, you can use either GCC ("MinGW") or the Microsoft
21 You can also cross-compile GLib for Windows from Linux using the
22 cross-compiling mingw packages for your distro.
24 Note that to just *use* GLib on Windows, there is no need to build it
27 On Windows setting up a correct build environment is very similar to typing
28 `meson; ninja` like on Linux.
31 compilation related to Win32 in GLib-using code:
33 - `G_OS_WIN32` is defined when compiling for native Win32, without
37 - `G_WITH_CYGWIN` is defined if compiling for the Cygwin
[all …]
|
| /third_party/mesa3d/docs/relnotes/ |
| D | 19.2.1.rst | 1 Mesa 19.2.1 Release Notes / 2019-10-09
20 ---------------
24 4cc53ca1a8d12c6ff0e5ea44a5213c05c88447ab50d7e28bb350cd29199f01e9 mesa-19.2.1.tar.xz
27 ------------
29 - None
32 ---------
34 - meson.build:1447:6: ERROR: Problem encountered: libdrm required for
36 - Mesa doesn't build with current Scons version (3.1.0)
37 - libXvMC-1.0.12 breaks mesa build
38 - Meson can't find 32-bit libXvMCW in non-standard path
[all …]
|
| D | 19.1.8.rst | 20 ----------------
24 f0fe8289b7d147943bf2fc2147833254881577e8f9ed3d94ddb39e430e711725 mesa-19.1.8.tar.xz
27 ------------
32 ---------
34 - `Bug 111236 <https://bugs.freedesktop.org/show_bug.cgi?id=111236>`__
35 - VA-API radeonsi SIGSEGV \__memmove_avx_unaligned
36 - `Bug 111664 <https://bugs.freedesktop.org/show_bug.cgi?id=111664>`__
37 - [Bisected] Segmentation fault on FS shader compilation (mat4x3 \*
39 - `Issue
40 #121 <https://gitlab.freedesktop.org/mesa/mesa/-/issues/121>`__ -
[all …]
|
| D | 19.3.0.rst | 1 Mesa 19.3.0 Release Notes / 2019-12-12
21 ---------------
25 5fa0e4e9dca79560f6882e362f9db36d81cf96da16cf6a84e0ada7466a99a5d7 mesa-19.3.0.tar.xz
28 ------------
30 - GL_ARB_gl_spirv on i965, iris.
31 - GL_ARB_spirv_extensions on i965, iris.
32 - GL_EXT_demote_to_helper_invocation on iris, i965.
33 - OpenGL 4.6 on i965, iris.
34 - EGL_EXT_image_flush_external
35 - VK_ANDROID_external_memory_android_hardware_buffer on RADV.
[all …]
|
| D | 18.3.2.rst | 16 ----------------
20 1cde4fafd40cd1ad4ee3a13b364b7a0175a08b7afdd127fb46f918c1e1dfd4b0 mesa-18.3.2.tar.gz
21 f7ce7181c07b6d8e0132da879af1729523a6c8aa87f79a9d59dfd064024cfb35 mesa-18.3.2.tar.xz
24 ------------
29 ---------
31 - `Bug 106595 <https://bugs.freedesktop.org/show_bug.cgi?id=106595>`__
32 - [RADV] Rendering distortions only when MSAA is enabled
33 - `Bug 107728 <https://bugs.freedesktop.org/show_bug.cgi?id=107728>`__
34 - Wrong background in Sascha Willem's Multisampling Demo
35 - `Bug 108114 <https://bugs.freedesktop.org/show_bug.cgi?id=108114>`__
[all …]
|
| D | 18.0.1.rst | 15 ----------------
19 0c93ba892c0610f5dd87f2e2673b9445187995c395b3ddb33fd4260bfb291e89 mesa-18.0.1.tar.gz
20 b2d2f5b5dbaab13e15cb0dcb5ec81887467f55ebc9625945b303a3647cd87954 mesa-18.0.1.tar.xz
23 ------------
28 ---------
30 - `Bug 101408 <https://bugs.freedesktop.org/show_bug.cgi?id=101408>`__
31 - [Gen8+] Xonotic fails to render one of the weapons
32 - `Bug 102342 <https://bugs.freedesktop.org/show_bug.cgi?id=102342>`__
33 - mesa-17.1.7/src/gallium/auxiliary/pipebuffer/pb_cache.c:169]:
35 - `Bug 102542 <https://bugs.freedesktop.org/show_bug.cgi?id=102542>`__
[all …]
|
| /third_party/libinput/ |
| D | .gitlab-ci.yml | 9 # To change the gitlab CI, edit .gitlab-ci/ci.template and/or .gitlab-ci/config.yaml
10 # and run ci-fairy generate-template. For details, see
11 # https://freedesktop.pages.freedesktop.org/ci-templates/ci-fairy.html#templating-gitlab-ci-yml
14 # - we really want to run dnf/apt/... only once, updating on the test runner for
18 # This is handled by the ci-templates, ensuring containers are only rebuilt
21 # - GitLab only allows one script: set per job but we have a bunch of commands
22 # we need to re-run for each build (meson && ninja && etc). YAML cannot merge
27 # MESON_ARGS=-Denable-something=true
28 # NINJA_ARGS=dist ... to run 'ninja -C builddir dist'
35 # e.g. fedora:31@build-default
[all …]
|
| /third_party/skia/third_party/externals/harfbuzz/docs/ |
| D | usermanual-install-harfbuzz.xml | 2 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
3 "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
7 <chapter id="install-harfbuzz">
18 libharfbuzz DLL, hb-view.exe, hb-shape.exe, and all
32 compatibility-breaking way in any release. However, other,
45 <emphasis>(1)</emphasis> To build HarfBuzz on Linux, you must first install the
52 …mand>sudo apt install</command> <package>gcc g++ libfreetype6-dev libglib2.0-dev libcairo2-dev</pa…
53 On Fedora, RHEL, CentOS, or other Red-Hat–based systems, you would run:
54 …ting><command>sudo yum install</command> <package>gcc gcc-c++ freetype-devel glib2-devel cairo-dev…
68 From a shell in the top-level directory of the extracted source
[all …]
|
| /third_party/libinput/doc/user/ |
| D | building.rst | 4 libinput build instructions
12 Instructions on how to build libinput and its tools and how to build against
15 The build instruction on this page detail how to overwrite your
16 system-provided libinput with one from the git repository, see
21 ------------------------------------------------------------------------------
23 ------------------------------------------------------------------------------
30 correct, up-to-date and/or unmodified from the git branch. Due dilligence
33 The following repositories provide an up-to-date package for libinput:
35 - **Arch:** https://aur.archlinux.org/packages/libinput-git/
36 - **Fedora:** https://copr.fedorainfracloud.org/coprs/whot/libinput-git/
[all …]
|
| /third_party/libfuse/test/ |
| D | ci-build.sh | 3 set -e
5 TEST_CMD="python3 -m pytest --maxfail=99 test/"
13 # build and run tests in a temporary directory that we can set up to be world
15 SOURCE_DIR="$(readlink -f .)"
16 TEST_DIR="$(mktemp -dt libfuse-build-XXXXXX)"
21 cp -v "${SOURCE_DIR}/test/lsan_suppress.txt" .
26 # Standard build
27 for CC in gcc gcc-9 gcc-10 clang; do
29 mkdir build-${CC}; cd build-${CC}
36 if [ ${CC} == 'gcc-7' ]; then
[all …]
|
| /third_party/unity/examples/example_4/ |
| D | readme.txt | 5 to build this example run "meson setup <build dir name>".
7 Meson uses the Ninja build system to actually build the code. To start the
8 build, simply type the following command.
10 "ninja -C <build dir name>"
12 Meson provides native support for running tests. The command to do that is simple.
14 "meson test -C <build dir name>".
|
| /third_party/mesa3d/.github/workflows/ |
| D | ci.yml | 1 name: macOS-CI
8 macOS-CI:
12 runs-on: macos-11
15 MESON_EXEC: /Users/runner/Library/Python/3.11/bin/meson
17 - name: Checkout
19 - name: Install Dependencies
30 brew "pkg-config"
35 brew bundle --verbose
36 - name: Install Mako and meson
37 run: pip3 install --user mako meson
[all …]
|
| /third_party/unity/docs/ |
| D | MesonGeneratorRunner.md | 1 # Meson Generator - Test Runner
7 … have to run this by hand, a Meson generator is provided to generate the runner automatically for …
14 …to be a bug in how the paths work with subprojects in Meson. You can get the full path with `meson…
16 test_runner = meson.source_root() / 'test/test_example.c'
18 …Meson will create the test runner in a private directory for each build target. It's only meant to…
|
| /third_party/unity/examples/example_1/ |
| D | readme.txt | 6 Build and run with Make
7 ---
10 Build and run with Meson
11 ---
12 Run `meson setup build` to create the build directory, and then `meson test -C build` to build and …
|
| /third_party/skia/third_party/externals/freetype/tests/ |
| D | README.md | 7 Run the `tests/scripts/download-fonts.py` script, which will
10 ### Build the test programs
12 The tests are only built with the Meson build system, and
16 meson setup out -Dtests=enabled
17 meson compile -C out
21 meson test -C out
|
123456789