commit | 01b92188f54056859f09501440b1b780ff929060 | [log] [tgz] |
---|---|---|
author | mjtalbot <hello@rive.app> | Fri Nov 03 17:13:47 2023 +0000 |
committer | mjtalbot <hello@rive.app> | Fri Nov 03 17:13:47 2023 +0000 |
tree | 66556fde93a976ca27cbf269fef65f2e51a1e43c | |
parent | 06d553a123a4417e27c545f67943a6d30e8663c5 [diff] |
Fix follow path 6070 fixes #6070 thank you @philter for sorting out the path mess, i got myself extra confused with `addToRawPath` (i thought we were simply passing the variables along and one of them got corrupted, i didnt notice that it was just down to a bad static cast when we were a path!) vid of this behaving in dart & cpp Added a rive-flutter test to this. one interesting thing, essentially follow path currently follows the "first" path in a shape. https://github.com/rive-app/rive/assets/1216025/d59026f6-c901-439c-aff2-2214a021ee75 Diffs= ef8a4e7f7 Fix follow path 6070 (#6182) Co-authored-by: Maxwell Talbot <talbot.maxwell@gmail.com> Co-authored-by: Phil Chung <philterdesign@gmail.com>
Rive C++ is a runtime library for Rive, a real-time interactive design and animation tool.
The C++ runtime for Rive provides these runtime features:
We use premake5. The Rive dev team primarily works on MacOS. There is some work done by the community to also support Windows and Linux. PRs welcomed for specific platforms you wish to support! We encourage you to use premake as it's highly extensible and configurable for a variety of platforms.
In the rive-cpp
directory, run build.sh
to debug build and build.sh release
for a release build.
If you've put the premake5
executable in the rive-cpp/build
folder, you can run it with PATH=.:$PATH ./build.sh
Rive makes use of clang vector builtins, which are, as of 2022, still a work in progress. Please use clang and ensure you have the latest version.
cd skia/dependencies ./make_skia.sh // this will invoke get_skia.sh
To build viewer (plus you'll needed CMake installed)
./make_viewer_dependencies.sh
Uses the Catch2 testing framework.
cd dev ./test.sh
In the dev
directory, run test.sh
to compile and execute the tests.
(if you've installed premake5
in rive-cpp/build
, you can run it with PATH=../../build:$PATH ./test.sh
)
The tests live in rive/test
. To add new tests, create a new xxx_test.cpp
file here. The test harness will automatically pick up the new file.
There's a VSCode command provided to run tests
from the Tasks: Run Task command palette.
rive-cpp uses clang-format, you can install it with brew on MacOS: brew install clang-format
.
Note that if you‘re on MacOS you’ll want to install valgrind, which is somewhat complicated these days. This is the easiest solution (please PR a better one when it becomes available).
brew tap LouisBrunner/valgrind brew install --HEAD LouisBrunner/valgrind/valgrind
You can now run the all the tests through valgrind by running test.sh memory
.
If you want to examine the generated assembly code per cpp file, install Disassembly Explorer in VSCode.
A disassemble
task is provided to compile and preview the generated assembly. You can reach it via the Tasks: Run Task command palette or you can bind it to a shortcut by editing your VSCode keybindings.json:
[ { "key": "cmd+d", "command": "workbench.action.tasks.runTask", "args": "disassemble" } ]