Add powershell support

[wolfv]

Maybe we could add powershell support by implementing a activate.psm1 similar to this:

https://www.powershellgallery.com/packages/EnterDeveloperPowerShell/1.0.12/Content/EnterDeveloperPowerShell.psm1

[mjcarroll]

Ran into this today. Would be greatly appreciated, so I may get a few cycles to take a look here this week.

[mjcarroll]

Is this still relevant? I just got back to building a workspace with vs2022_win-64 installed and things seemed to work without issue.

[i2w3]

try this :)

1. Use PowerShell to activate your virtual environment and create vs2022_compiler_vars.ps1
2. Copy the following content to vs2022_compiler_vars.ps1

# PowerShell script to activate VS2022 MSVC compiler
# This is the PowerShell equivalent of vs2022_compiler_vars.bat

Write-Host "Activating Visual Studio 2022 MSVC environment..."

# Set environment variables
$env:CC  = "cl.exe"
$env:CXX = "cl.exe"

# Find Visual Studio installation
$vsInstallDir = ""

# Try to find VS2022 using vswhere
try {
    $vsPath = & vswhere.exe -nologo -products * -version "[17.0,18.0)" -property installationPath 2>$null
    if ($vsPath) {
        $vsInstallDir = $vsPath.Trim() + "\"
    }
} catch {
    Write-Warning "vswhere.exe not found or failed"
}

if (-not $vsInstallDir -or -not (Test-Path $vsInstallDir)) {
    Write-Warning "Visual Studio 2022 not found. MSVC compiler may not be available."
    return
}

Write-Host "Found Visual Studio at: $vsInstallDir"

# Set up include and lib paths
$env:INCLUDE = "$env:CONDA_PREFIX\Library\include;$env:INCLUDE"
$env:LIB = "$env:CONDA_PREFIX\Library\lib;$env:LIB"
$env:CMAKE_PREFIX_PATH = "$env:CONDA_PREFIX\Library;$env:CMAKE_PREFIX_PATH"

# Use Launch-VsDevShell.ps1 (the correct PowerShell way)
$launchVsDevShellPath = Join-Path $vsInstallDir "Common7\Tools\Launch-VsDevShell.ps1"
if (Test-Path $launchVsDevShellPath) {
    Write-Host "Loading MSVC environment using: $launchVsDevShellPath"
    
    try {
        # Use Launch-VsDevShell.ps1 with appropriate parameters
        & $launchVsDevShellPath -Arch amd64 -HostArch amd64 -SkipAutomaticLocation
        
        Write-Host "MSVC environment activated successfully!"
        
        # Test if cl.exe is now available
        $clPath = Get-Command cl.exe -ErrorAction SilentlyContinue
        if ($clPath) {
            Write-Host "MSVC compiler found at: $($clPath.Source)"
        } else {
            Write-Warning "cl.exe not found in PATH"
        }
    } catch {
        Write-Warning "Failed to execute Launch-VsDevShell.ps1: $($_.Exception.Message)"
    }
} else {
    Write-Warning "Launch-VsDevShell.ps1 not found at: $launchVsDevShellPath"
}

3. copy it to the path $env:CONDA_PREFIX\etc\conda\activate.d

Copy-Item "vs2022_compiler_vars.ps1" "$env:CONDA_PREFIX\etc\conda\activate.d\" -Force

[traversaro]

Is this still relevant? I just got back to building a workspace with vs2022_win-64 installed and things seemed to work without issue.

I think this is solved when using rattler-build/pixi, as there on Windows the .bat activation scripts are always used, regardless of the shell, to extract the change in the environments, that is then applied for all shells.