fad5d46d7d
|
||
|---|---|---|
| .. | ||
| tools | ||
| Build.bat | ||
| Clean.bat | ||
| CleanObjs.cmd | ||
| Find-WindowsSDKVersions.ps1 | ||
| Install-WindowsSDK.ps1 | ||
| Install-WindowsSdkISO.ps1 | ||
| README.md | ||
| Sign-Package.ps1 | ||
| SignClientSettings.json | ||
| StyleXaml.bat | ||
| UpdateHeaders.bat | ||
| build.cake | ||
| build.ps1 | ||
| header.txt | ||
| nuget.png | ||
README.md
Building Lottie-Windows
Prerequisites
- .NET Core 2.2 SDK or later
- Windows SDK May 2019 Update (18362) or later
- Visual Studio 2017 or later
As Azure DevOps does it
Open a VS2017 Developer Command Prompt and run build\build.bat. This will build everything in RELEASE configuration, run some checks, and produce nuget packages.
This is the slowest and most complete way to build. You should build this way to make sure your pull request can build on the official build system.
From Visual Studio
Open the Lottie-Windows.sln in Visual Studio and build as you normally would.
Use the Debug configuration to save a lot of time (the Release configuration of Lottie Viewer runs the .NET native compiler, which does a lot of slow optimization work).
Just LottieGen
Turbocharge your workflow with the smaller LottieGen\LottieGen.sln in Visual Studio. This solution does not include the Lottie Viewer code or the DLLs, but it does include all the source needed to translating Lottie .json files to Windows.UI.Composition.
This solution was added as a useful subset for use on slow laptops. It can even be built with Dotnet Build with no Visual Studio installed.