vcpkg, emscripten, and powershell

[nolan-yoo-miris]

I bumped into the following issue:
#48317

The thing that's striking me as odd here:
I'm invoking this from a PowerShell environment. I've also used emsdk.ps1 to activate the Emscripten environment. Under these circumstances, I don't expect an The command line is too long. error.

I'm under the impression that vcpkg should be finding and invoking em++.ps1, but instead:

Detecting compiler hash for triplet x64-windows...
Compiler found: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.44.35207/bin/Hostx64/x64/cl.exe
Detecting compiler hash for triplet wasm32-emscripten-release...
Compiler found: C:/Users/nolan/gitarea/aqua/build-output/emsdk/upstream/emscripten/em++.bat

vcpkg also seems to be invoking emar.bat, emranlib.bat, etc instead of the provided ps1 files.

Am I doing something wrong on my end?

[dg0yt]

I bumped into the following issue: #48317

#48317 is a port bug which is already fixed in the current version of the port.

The thing that's striking me as odd here: I'm invoking this from a PowerShell environment. I've also used emsdk.ps1 to activate the Emscripten environment. Under these circumstances, I don't expect an The command line is too long. error.

I'm under the impression that vcpkg should be finding and invoking em++.ps1, but instead:

Detecting compiler hash for triplet x64-windows...
Compiler found: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.44.35207/bin/Hostx64/x64/cl.exe
Detecting compiler hash for triplet wasm32-emscripten-release...
Compiler found: C:/Users/nolan/gitarea/aqua/build-output/emsdk/upstream/emscripten/em++.bat

vcpkg also seems to be invoking emar.bat, emranlib.bat, etc instead of the provided ps1 files.

Am I doing something wrong on my end?

vcpkg's wasm32-emscripten community triplet relies on what is emscripten chooses in its ${EMSCRIPTEN_ROOT}/cmake/Modules/Platform/Emscripten.cmake toolchain file.

There is no universal fix for the command line length limitations: Any tool in the call stack can still have limitations.