代码拉取完成，页面将自动刷新
Currently an officially supported host OS for development, building and testing is Ubuntu 18.04 and Ubuntu 20.04.
The full list of packages required for building and testing the project is specified in
scripts/deps-lists files. These packages can be installed either manually or by running
a bootstrap script:
$ sudo ./scripts/install-deps-ubuntu
For more bootstrapping options, run:
$ sudo ./scripts/install-deps-ubuntu --help
E.g. for development purposes you should run:
$ sudo ./scripts/install-deps-ubuntu -i=dev
If you want additionally to install python dependencies for running tests add a parameter -i=test:
$ sudo ./scripts/install-deps-ubuntu -i=dev -i=test
It creates a virtual environment .venv-panda in your home directory with all required dependencies.
Later, tests python scripts can activate this environment. If you already have run with the parameter -i=test
the second time it might be skipped.
Panda uses third party libraries. To install the libraries and apply patches, run:
$ ./scripts/install-third-party --force-clone
Assuming your system is bootstrapped, please run the following commands in the root of the project:
$ mkdir panda-build
$ cd panda-build
$ cmake /path/to/panda/repository -GNinja
$ ninja
This will build Panda in debug mode with your default C++ compiler. All supported compilers can be
found in cmake/toolchain. E.g., to build with Clang 14, pass a path to the corresponding toolchain
file during configuration:
$ cmake -DCMAKE_TOOLCHAIN_FILE=/path/to/panda/repository/cmake/toolchain/host_clang_14.cmake /path/to/panda/repository
Recommended way to build Panda is to set CMAKE_BUILD_TYPE variable explicitly during configurations. Supported values are:
| Mode | Assertions | Optimizations | Debug info |
|---|---|---|---|
Debug |
Yes | None (CMake default) |
-g (CMake default) |
Release |
No |
-O3 (CMake default) |
None (CMake default) |
FastVerify |
Yes | -O2 |
-ggdb3 |
Notes:
RelWithDebInfo, MinSizeRel, DebugDetailed) should work but they are not tested in CI.RelWithDebInfo, FastVerify preserves assertions (and provides more verbose debug information).
Use this build type for running heavy test suites when you want both fast-running code and debuggability.DebugDetailed gives more debug information than Debug, it can be usefull for debugging unit tests for example.Example:
$ cmake -DCMAKE_BUILD_TYPE=Release ...
Recommended QEMU version for running testst is 6.2.0 (but 5.1+ should be ok, too). By default, it is downloaded and installed during environment bootstrap. Any system-installed package is left intact. If recommened QEMU version is not accessible via $PATH it can be specified during configuration time:
# If QEMU is available as /opt/qemu-6.2.0/bin/qemu-aarch64
$ cmake -DQEMU_PREFIX=/opt/qemu-6.2.0 ...
$ git clone https://gn.googlesource.com/gn
$ cd gn
$ python build/gen.py
$ ninja -C out
ark_asm, ark_disasm, ark_aot, ark_aotdump, c2abc, ark_bin, es2panda, verifier_bin and ark targets are supported)$ cd /path/to/panda/repository
$ /path/to/gn/repository/out/gn gen out
$ ninja -C out ark
When standard system, use
$ cd /path/to/panda/repository
$ /path/to/gn/repository/out/gn --args=-is_standard_system=true gen out
$ ninja -C out <target name>
For testing, the following umbrella targets that guarantee building prior to running may be used:
tests, for running all testing suites.tests_full, for running all testing suites and various code linters.clang-format and clang-tidy checks are integrated into build system and can be called by target of build system:
$ ninja code-style-check # clang-format
$ ninja clang-tidy-check # clang-tidy
In order to measure bytecode optimizer coverage, configure your build with -DENABLE_BYTECODE_OPTIMIZER_COVERAGE=true. Then run:
$ ninja bytecode_optimizer_coverage
To build and run benchmarks, please use the umbrella target benchmarks or any of its
dependencies. Please see the root CMakeLists.txt for more details.
NB! Make sure that you configure your build with -DCMAKE_BUILD_TYPE=Release, otherwise
your run will most likely be dead slow.
Assuming that you are in panda-build directory, please run:
$ ./bin/ark_asm /path/to/panda-assembly.pa /path/to/binary/output.abc
Assuming that your main function is defined as .function main(...) in the assembly listing,
and /path/to/binary/output.abc is the result of the assembler, please run:
$ ./bin/ark /path/to/binary/output.abc _GLOBAL::main
此处可能存在不合适展示的内容，页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容，可点击提交进行申诉，我们将尽快为您处理。