Qt
Internal/Contributor docs for the Qt SDK. Note: These are NOT official API docs; those are found at https://doc.qt.io/
Loading...
Searching...
No Matches
qtquick3d-cmake-macros.qdoc
Go to the documentation of this file.
1
// Copyright (C) 2025 The Qt Company Ltd.
2
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only
3
4
/*!
5
\page qtquick3d-cmake-qt6-add-lightprobe-images.html
6
\ingroup cmake-commands-qtquick3d
7
8
\title qt6_add_lightprobe_images
9
\keyword qt6_add_lightprobe_images
10
11
\section1 Description
12
13
\c {.hdr -> .ktx} baker. Somewhat similar to \l {qt6_add_shaders()}.
14
15
For example, the following autogenerates the lightprobe map at build time and
16
includes it in the executable under \c {:/maps/OpenfootageNET_garage-1024.ktx}:
17
18
\badcode
19
qt6_add_lightprobe_images(principledmaterial "ibl_assets"
20
PREFIX
21
"/"
22
FILES
23
"maps/OpenfootageNET_garage-1024.hdr" )
24
\endcode
25
26
In addition to \c PREFIX, \c BASE is available, and works like in
27
\c {qt6_add_resources}:
28
Adding \c {BASE "maps"} in the above example would lead to getting
29
\c {:/OpenfootageNET_garage-1024.ktx}
30
31
\c OUTPUTS works like in \c qt6_add_shaders, which allows you to specify an
32
alternative name for the resource system for each entry in \c FILES. For
33
example, adding \c {OUTPUTS "alt/er/native/image.abc"} to the above example
34
would generate \c {:/alt/er/native/image.abc}
35
36
In short, the actual file name in the resource system is either
37
\c {:/PREFIX/FILES[i]-BASE-".hdr"+".ktx"} or \c {:/PREFIX/OUTPUTS[i]}
38
39
\sa {Pre-generating IBL cubemap}
40
*/
qtquick3d
src
quick3d
doc
src
qtquick3d-cmake-macros.qdoc
Generated on
for Qt by
1.14.0