Repository navigation
Enhancement - Update build.ps1/build.netcore.ps1 to allow for building/packaging for subset of architectures #3706
Description
Activity
- added a commit that references this issue
on Oct 12, 2021 Tests are now failing when run via
AppVeyorhttps://ci.appveyor.com/project/cefsharp/cefsharp/builds/41113154
It looks like the cef dependencies aren't copied to the output directory anymore (I can reproduce it by deleting the
bin/objfolders before duing a build).Adding the following lines to https://github.com/cefsharp/CefSharp/blob/master/CefSharp.Test/CefSharp.Test.csproj fixes it:
<Target Name="CefCopy" AfterTargets="Build"> <CallTarget Targets="CefRedist32CopyResources" Condition="'$(Platform)' == 'x86'"/> <CallTarget Targets="CefRedist64CopyResources" Condition="'$(Platform)' == 'x64'"/> </Target>
Looks like this got removed here:
67a08c4#diff-b6fc1d6d9c3d3eff95f339ef0f4455fbf23bf9bcb59d53500632de453f4f676dL11-L13
67a08c4#diff-b6fc1d6d9c3d3eff95f339ef0f4455fbf23bf9bcb59d53500632de453f4f676dL16-L19- added a commit that references this issue
on Oct 12, 2021 I'll fix the errors shortly.
The chromiumembeddedframework.runtime package is now used internally. Tests should now be passing again.
- added 2 commits that reference this issue
on Oct 13, 2021 It should now be possible to compile only a subset of architectures
.\build.ps1 -BuildArches "x64" .\build.ps1 -BuildArches "x64 x86" .\build.ps1 -BuildArches "x64" -TargetFramework NetCore .\build.ps1 -BuildArches "x64 x86" -TargetFramework NetCore
- added a commit that references this issue
on Oct 15, 2021
When building custom version of
CefSharpit maybe desirable to only build/package a subset of thex86/x86/arm64architectures. e.g. You may only wish to buildx86/x64for your custom version.The
nupkgprocess will fail if the files don't exist, so we need to perform some modifications dynamically.Nuspecfiles to exclude any arch that isn't required. e.g.remove arm64.BrowserSubProcesshasTSAwareandLargeAddressAwareattributes set.To simplify this issue #3444 should likely be resolved first. I'm adding the
breaking-changelabel, whilst this change in itself isn't breaking, the changes in #3444 will be.Related issue cefsharp/cef-binary#98