Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

On Windows, --output-dir does not work if path contains a space #1208

Open
sapetnioc opened this issue Nov 21, 2024 · 0 comments
Open

On Windows, --output-dir does not work if path contains a space #1208

sapetnioc opened this issue Nov 21, 2024 · 0 comments

Comments

@sapetnioc
Copy link

I installed rattler-build 0.31.0 via Pixi.
I used the recipe located here

In PowerShell, the following command fail:

 rattler-build.exe build -r 'C:\Users\Me Myself\dev\neuro-forge\recipes\libminc' --output-dir 'C:\Users\Me Myself\dev\output'

But the following one is working:

rattler-build.exe build -r 'C:\Users\Me Myself\dev\neuro-forge\recipes\libminc' --output-dir 'C:\Users\me\dev\output'

Looking at the output, I suspect that rattler-build generates a build_env.bat script and use call on it without appropriate quotes:

 │ ╭─ Running build script
 │ │ %SRC_DIR%>IF "" == "" (
 │ │ 'C:\Users\Me' n’est pas reconnu en tant que commande interne
 │ │ ou externe, un programme exécutable ou un fichier de commandes.
 │ │
 │ │  call %SRC_DIR%\build_env.bat
 │ │ )

The french sentence says that C:\Users\Me is not recognized as an executable. Probably %SRC_DIR%\build_env.bat is interpreted as "C:\Users\Me" "Myself\dev\output\...\build_env.bat" instead of "C:\Users\Me Myself\dev\output\...\build_env.bat". But I am not familiar at all with Windows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant