-
Notifications
You must be signed in to change notification settings - Fork 148
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
build win32 version error #196
Comments
that is an odd unicode error. what tools did you use to check out the sources? did you edit the sources? as a workaround to see if it helps can you try installing https://gitforwindows.org/ and checking out the sources with that git? |
I didn't edit anything.
but i just run |
didn’t understand your last statement. i have had many people build on windows. i am guessing it is something about your configuration. |
try https://gitforwindows.org/ as an experiment... what git are you using? |
i use this: |
I had this problem as well, but it disappeared somehow. There was a problem with the SDK pathes as well, but this batch file works fine for me since then:
It's even working when executed outside the Developer Command Prompt (maybe VS 2019 automatically added some stuff to the PATH). |
If someone can give me the exact recipe that generates the issue, I can try to reproduce it locally. |
|
Install non-english Visual Studio. My Cyrillic installation emits errors in 866 code page by default. |
Can you run this command and tell me what it returns: python3 -c "import locale; print(locale.getpreferredencoding())" or python2 instead of python3. I have a guess that mbuild's hardcoded use of utf-8 is problematic for some languages. Easy to change (I have a patch locally), just wanted to get more data for my hunch |
C:\VS>python3 -c "import locale; print(locale.getpreferredencoding())" C:\VS>python -c "import locale; print(locale.getpreferredencoding())" C:\VS>where python |
so I pushed a patch to the mbuild git repo that might address this issue. Please give it a shot and let me know. |
works for me with no hacks applied |
cool. (And my dreams of getting a job as unicode consultant continue to thrive :-) ) |
run :
The text was updated successfully, but these errors were encountered: