OpenHarmony/third_party_mesa3d
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
c0c03f29e0b7680a5d62b151a92e1e66e456428c
third_party_mesa3d/src/gallium/targets/lavapipe/meson.build

34 lines
1.1 KiB
Meson
Raw Normal View History

lavapipe: rename vallium to lavapipe Just a cooler name, and a lot easier to search for. thanks Marek Acked-by: Marek Olšák <marek.olsak@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6921>
2020-09-30 05:29:04 +10:00
libvulkan_lvp = shared_library(
'vulkan_lvp',
vallium: initial import of the vulkan frontend This is the initial import of the vallium frontend for gallium. This is only good enough to run the triangle and the gears demo (wrongly) from Sascha demos. Improvements are mostly on the llvmpipe side after this. It contains an implementation of the Vulkan API which is mapped onto the gallium API, and is suitable only for SOFTWARE drivers. Command buffers are recordred into malloced memory, then later they are played back against the gallium API. The command buffers are mostly just Vulkan API marshalling but in some places the information is processed before being put into the command buffer (renderpass stuff). Execution happens on a separate "graphics" thread, againt the gallium API. There is only a single queue which wraps a single gallium context. Resources are allocated via the new resource/memory APIs. Shaders are created via the context and bound/unbound in the second thread. (No HW for reasons - memory management, sw paths for lots of paths, pointless CPU side queue) v2: drop mesa_icd, drop cpp_args, drop extra flags, change meson config (Eric) v2.1: use meson-gallium job meson pieces: Reviewed-by: Eric Engestrom <eric@engestrom.ch> overall: Acked-by: Roland Scheidegger <sroland@vmware.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6082>
2020-06-19 16:40:27 +10:00
[ 'target.c' ],
include_directories : [ inc_src, inc_util, inc_include, inc_gallium, inc_gallium_aux, inc_gallium_winsys, inc_gallium_drivers ],
lavapipe: rename vallium to lavapipe Just a cooler name, and a lot easier to search for. thanks Marek Acked-by: Marek Olšák <marek.olsak@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6921>
2020-09-30 05:29:04 +10:00
link_whole : [ liblavapipe_st ],
lavapipe: drop dri,dricommon deps. This would be a step towards building elsewhere. Reviewed-by: Eric Anholt <eric@anholt.net> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7019>
2020-10-06 16:31:11 +10:00
link_with : [libpipe_loader_static, libmegadriver_stub, libgallium, libwsw, libswdri, libws_null, libswkmsdri ],
vallium: initial import of the vulkan frontend This is the initial import of the vallium frontend for gallium. This is only good enough to run the triangle and the gears demo (wrongly) from Sascha demos. Improvements are mostly on the llvmpipe side after this. It contains an implementation of the Vulkan API which is mapped onto the gallium API, and is suitable only for SOFTWARE drivers. Command buffers are recordred into malloced memory, then later they are played back against the gallium API. The command buffers are mostly just Vulkan API marshalling but in some places the information is processed before being put into the command buffer (renderpass stuff). Execution happens on a separate "graphics" thread, againt the gallium API. There is only a single queue which wraps a single gallium context. Resources are allocated via the new resource/memory APIs. Shaders are created via the context and bound/unbound in the second thread. (No HW for reasons - memory management, sw paths for lots of paths, pointless CPU side queue) v2: drop mesa_icd, drop cpp_args, drop extra flags, change meson config (Eric) v2.1: use meson-gallium job meson pieces: Reviewed-by: Eric Engestrom <eric@engestrom.ch> overall: Acked-by: Roland Scheidegger <sroland@vmware.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6082>
2020-06-19 16:40:27 +10:00
gnu_symbol_visibility : 'hidden',
link_args : [ld_args_bsymbolic, ld_args_gc_sections],
dependencies : driver_swrast,
install : true,
)
lavapipe: configure suffix in icd json Acked-by: Jose Fonseca <jfonsec@vmware.com> Reviewed-by: Dave Airlie <airlied@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7341>
2020-10-18 19:55:21 +02:00
if with_platform_windows
module_dir = join_paths(get_option('prefix'), get_option('bindir'))
else
module_dir = join_paths(get_option('prefix'), get_option('libdir'))
endif
lavapipe: rename vallium to lavapipe Just a cooler name, and a lot easier to search for. thanks Marek Acked-by: Marek Olšák <marek.olsak@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6921>
2020-09-30 05:29:04 +10:00
lvp_icd = custom_target(
'lvp_icd',
input : 'lvp_icd.py',
output : 'lvp_icd.@0@.json'.format(host_machine.cpu()),
vallium: initial import of the vulkan frontend This is the initial import of the vallium frontend for gallium. This is only good enough to run the triangle and the gears demo (wrongly) from Sascha demos. Improvements are mostly on the llvmpipe side after this. It contains an implementation of the Vulkan API which is mapped onto the gallium API, and is suitable only for SOFTWARE drivers. Command buffers are recordred into malloced memory, then later they are played back against the gallium API. The command buffers are mostly just Vulkan API marshalling but in some places the information is processed before being put into the command buffer (renderpass stuff). Execution happens on a separate "graphics" thread, againt the gallium API. There is only a single queue which wraps a single gallium context. Resources are allocated via the new resource/memory APIs. Shaders are created via the context and bound/unbound in the second thread. (No HW for reasons - memory management, sw paths for lots of paths, pointless CPU side queue) v2: drop mesa_icd, drop cpp_args, drop extra flags, change meson config (Eric) v2.1: use meson-gallium job meson pieces: Reviewed-by: Eric Engestrom <eric@engestrom.ch> overall: Acked-by: Roland Scheidegger <sroland@vmware.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6082>
2020-06-19 16:40:27 +10:00
command : [
prog_python, '@INPUT@',
lavapipe: configure suffix in icd json Acked-by: Jose Fonseca <jfonsec@vmware.com> Reviewed-by: Dave Airlie <airlied@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7341>
2020-10-18 19:55:21 +02:00
'--lib-path', module_dir,
vallium: initial import of the vulkan frontend This is the initial import of the vallium frontend for gallium. This is only good enough to run the triangle and the gears demo (wrongly) from Sascha demos. Improvements are mostly on the llvmpipe side after this. It contains an implementation of the Vulkan API which is mapped onto the gallium API, and is suitable only for SOFTWARE drivers. Command buffers are recordred into malloced memory, then later they are played back against the gallium API. The command buffers are mostly just Vulkan API marshalling but in some places the information is processed before being put into the command buffer (renderpass stuff). Execution happens on a separate "graphics" thread, againt the gallium API. There is only a single queue which wraps a single gallium context. Resources are allocated via the new resource/memory APIs. Shaders are created via the context and bound/unbound in the second thread. (No HW for reasons - memory management, sw paths for lots of paths, pointless CPU side queue) v2: drop mesa_icd, drop cpp_args, drop extra flags, change meson config (Eric) v2.1: use meson-gallium job meson pieces: Reviewed-by: Eric Engestrom <eric@engestrom.ch> overall: Acked-by: Roland Scheidegger <sroland@vmware.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6082>
2020-06-19 16:40:27 +10:00
'--out', '@OUTPUT@',
lavapipe: configure suffix in icd json Acked-by: Jose Fonseca <jfonsec@vmware.com> Reviewed-by: Dave Airlie <airlied@redhat.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7341>
2020-10-18 19:55:21 +02:00
'--suffix', libvulkan_lvp.full_path().split('.')[-1],
vallium: initial import of the vulkan frontend This is the initial import of the vallium frontend for gallium. This is only good enough to run the triangle and the gears demo (wrongly) from Sascha demos. Improvements are mostly on the llvmpipe side after this. It contains an implementation of the Vulkan API which is mapped onto the gallium API, and is suitable only for SOFTWARE drivers. Command buffers are recordred into malloced memory, then later they are played back against the gallium API. The command buffers are mostly just Vulkan API marshalling but in some places the information is processed before being put into the command buffer (renderpass stuff). Execution happens on a separate "graphics" thread, againt the gallium API. There is only a single queue which wraps a single gallium context. Resources are allocated via the new resource/memory APIs. Shaders are created via the context and bound/unbound in the second thread. (No HW for reasons - memory management, sw paths for lots of paths, pointless CPU side queue) v2: drop mesa_icd, drop cpp_args, drop extra flags, change meson config (Eric) v2.1: use meson-gallium job meson pieces: Reviewed-by: Eric Engestrom <eric@engestrom.ch> overall: Acked-by: Roland Scheidegger <sroland@vmware.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6082>
2020-06-19 16:40:27 +10:00
],
lavapipe: rename vallium to lavapipe Just a cooler name, and a lot easier to search for. thanks Marek Acked-by: Marek Olšák <marek.olsak@amd.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6921>
2020-09-30 05:29:04 +10:00
depend_files : files('../../frontends/lavapipe/lvp_extensions.py'),
vallium: initial import of the vulkan frontend This is the initial import of the vallium frontend for gallium. This is only good enough to run the triangle and the gears demo (wrongly) from Sascha demos. Improvements are mostly on the llvmpipe side after this. It contains an implementation of the Vulkan API which is mapped onto the gallium API, and is suitable only for SOFTWARE drivers. Command buffers are recordred into malloced memory, then later they are played back against the gallium API. The command buffers are mostly just Vulkan API marshalling but in some places the information is processed before being put into the command buffer (renderpass stuff). Execution happens on a separate "graphics" thread, againt the gallium API. There is only a single queue which wraps a single gallium context. Resources are allocated via the new resource/memory APIs. Shaders are created via the context and bound/unbound in the second thread. (No HW for reasons - memory management, sw paths for lots of paths, pointless CPU side queue) v2: drop mesa_icd, drop cpp_args, drop extra flags, change meson config (Eric) v2.1: use meson-gallium job meson pieces: Reviewed-by: Eric Engestrom <eric@engestrom.ch> overall: Acked-by: Roland Scheidegger <sroland@vmware.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6082>
2020-06-19 16:40:27 +10:00
build_by_default : true,
install_dir : with_vulkan_icd_dir,
install : true,
)
Reference in New Issue Copy Permalink