Zen

Translation

Windows:
10/100 · 8

Sign in to save the translation.

English French Actions
CMake
 
Overte uses CMake to generate build files and project files for your platform.
 
Qt
 
CMake will download Qt 5.15.2 using vcpkg.
 
To override this - i.e., use an installed Qt configuration - you need to set a QT_CMAKE_PREFIX_PATH environment variable pointing to your Qt **lib/cmake** folder. This can either be entered directly into your shell session before you build or in your shell profile (e.g.: ~/.bash_profile, ~/.bashrc, ~/.zshrc - this depends on your shell and environment). The path it needs to be set to will depend on where and how Qt5 was installed.
 
For example, under Linux:
 
For example, under Windows:
 
For example, under OSX:
 
Note: You only need the following components checked under Qt 5.15.2 (select the "Custom Installation" option): "MSVC 2019 64-bit", "Qt WebEngine", and "Qt Script (Deprecated)".
 
Note: Installing the sources is optional but recommended if you have room for them (~3GB). You may also want the Qt debug information files (~7GB).
 
Note: Installing Qt Creator is optional but recommended if you will be editing QML files.
 
VCPKG
 
Overte uses vcpkg to download and build dependencies. You do not need to install vcpkg.
 
Building the dependencies can be lengthy and the resulting files will be stored in your OS temp directory. However, those files can potentially get cleaned up by the OS, so in order to avoid this and having to redo the lengthy build step, you can set an environment variable.
 
Linux:
 
Windows:
Windows MR
Where `/path/to/directory` is the path to a directory where you wish the build files to get stored.
 
Generating Build Files
 
Possible Environment Variables
 
Generate Files
Général
Create a build directory in the root of your checkout and then run the CMake build from there. This will keep the rest of the directory clean.
 
If CMake gives you the same error message repeatedly after the build fails, try removing `CMakeCache.txt`.
 
Generating a release/debug only vcpkg build
 
In order to generate a release or debug only vcpkg package, you could use the use the `VCPKG_BUILD_TYPE` define in your CMake generate command. Building a release only vcpkg can drastically decrease the total build time.
 
For release only vcpkg:
 
`cmake .. -DVCPKG_BUILD_TYPE=release`
 
For debug only vcpkg:
 
`cmake .. -DVCPKG_BUILD_TYPE=debug`
 
Variables
Vêtements
Any variables that need to be set for CMake to find dependencies can be set as ENV variables in your shell profile, or passed directly to CMake with a `-D` flag appended to the `cmake ..` command.
 
For example, to pass the QT_CMAKE_PREFIX_PATH variable (if not using the vcpkg'ed version) during build file generation:
 

Loading…

User avatar None

String updated in the repository

  1. Overte
  2. Overte Documentation
  3. French
Windows:
Windows MR
a year ago
Browse all string changes

Things to check

Mismatched colon

Source and translation do not both end with a colon

Reset

Glossary

English French
No related strings found in the glossary.

String information

Flags
check-glossary, rst-text
Source string location
../../source/developer/build/BUILD.md:95
String age
a year ago
Last updated
10 months ago
Source string age
a year ago
Translation file
source/locales/fr/LC_MESSAGES/overte-docs.po, string 1926