You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 12, 2022. It is now read-only.
When I try to build my VS 2010 project with the default installation setup, compiles work but links fail with an error like
"Can't find C:/Program"
For some reason the part of VS that invokes the linker is confused by spaces in the path name in $EMSCRIPTEN. I tried both '/' and '' as path separators since when it first failed on XP I was using '' but it was working on Windows 7 which was using '/'. However it fails on XP with either.
My fix has been to set EMSCRIPTEN to the DOS short-form path which does not have spaces with
setx EMSCRIPTEN $(cygpath -d -m "$EMSCRIPTEN")
[You need cygwin to do the above. I have no idea how to obtain the DOS short-form with a Windows command.]
This gives a path like
C:/PROGRA1/EMSCRI1/EMSCRI1/172EFD1.8
The text was updated successfully, but these errors were encountered:
Perhaps the way could be to detect that the current OS is Windows XP and in that case, have python generate short paths for all env. vars that have spaces in them.
Did you have to fix this only for the EMSCRIPTEN env. var so that Visual Studio gets it right, or were there issues with other env. vars/invocations as well?
When I try to build my VS 2010 project with the default installation setup, compiles work but links fail with an error like
For some reason the part of VS that invokes the linker is confused by spaces in the path name in $EMSCRIPTEN. I tried both '/' and '' as path separators since when it first failed on XP I was using '' but it was working on Windows 7 which was using '/'. However it fails on XP with either.
My fix has been to set EMSCRIPTEN to the DOS short-form path which does not have spaces with
setx EMSCRIPTEN $(cygpath -d -m "$EMSCRIPTEN")
[You need cygwin to do the above. I have no idea how to obtain the DOS short-form with a Windows command.]
This gives a path like
C:/PROGRA
1/EMSCRI1/EMSCRI1/172EFD1.8The text was updated successfully, but these errors were encountered: