saucecontrol / PhotoSauce

MagicScaler high-performance, high-quality image processing pipeline for .NET
http://photosauce.net/
MIT License
569 stars 49 forks source link

Noob question: Having a hard time understanding the native codec binary build steps. #145

Closed futuremotiondev closed 6 months ago

futuremotiondev commented 6 months ago

I followed all of the steps:

git clone --recurse-submodules https://github.com/saucecontrol/PhotoSauce
git submodule update --init
git submodule update --remote
dotnet build src\MagicScaler -c Dist

And then the build succeeded:

Successfully created package 'D:\Dev\00 External Compile\PhotoSauce\build\..\out\nuget\PhotoSauce.MagicScaler.0.14.1.nupkg'.
Successfully created package 'D:\Dev\00 External Compile\PhotoSauce\build\..\out\nuget\PhotoSauce.MagicScaler.0.14.1.snupkg'.

But I'm now confused about this:

Native codec binaries are built with vcpkg. See azure-pipelines.yml in the repo root for a working setup. Alternatively, pre-built native binaries can be retrieved from a recent CI run and extracted to [reporoot]\out\vcpkg\install Once native binaries are built or downloaded, the native codec plugin packages can be built as normal with dotnet build

I downloaded all of the artifacts from here: https://dev.azure.com/saucecontrol/PhotoSauce/_artifacts/feed/photosauce_ci And here: https://dev.azure.com/saucecontrol/PhotoSauce/_artifacts/feed/photosauce_vcpkg

Am I supposed to place all of the .nupkg files in PhotoSauce\out\vcpkg\install\ and then rebuild with dotnet build? Should I run dotnet build src\MagicScaler -c Dist again?

I just want to make sure that all of the native codec plugins are installed / working before I use the library.

Any guidance would be greatly appreciated!