Skip to content

Commit

Permalink
chore: force to use targetenv vs2022
Browse files Browse the repository at this point in the history
  • Loading branch information
kmruiz committed Dec 4, 2023
1 parent 036aafd commit 9be66bc
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 1 deletion.
1 change: 0 additions & 1 deletion .evergreen/InstallNode.ps1
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,6 @@ $url = "https://nodejs.org/download/release/v$version/node-v$version-win-x64.zip
$filename = "node.zip"
$node_zip = "$PSScriptRoot\$filename"
$node_dir = "$PSScriptRoot\node-v$version-win-x64"
$Env:target_env = "vs2022"

Write-Host "[NODE] downloading nodejs install"
Write-Host "url : $url"
Expand Down
1 change: 1 addition & 0 deletions .evergreen/compile-artifact.sh
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@ fi
# able to compile OpenSSL with assembly support,
# so we revert back to the slower version.
if [ "$OS" == "Windows_NT" ]; then
export target_env='vs2022'
export BOXEDNODE_CONFIGURE_ARGS='openssl-no-asm'
elif uname -a | grep -q 'Darwin.*x86_64'; then
export BOXEDNODE_CONFIGURE_ARGS='--openssl-no-asm'
Expand Down

0 comments on commit 9be66bc

Please sign in to comment.