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

Compile mitsuba with VS2017 on win10 #143

Open
banbao990 opened this issue Apr 21, 2021 · 7 comments
Open

Compile mitsuba with VS2017 on win10 #143

banbao990 opened this issue Apr 21, 2021 · 7 comments

Comments

@banbao990
Copy link

When I follow the steps in #61, I meet the problems like following, I don't know how to fix it up, maybe someone can help me

(py27) D:\Code\mitsuba\mitsuba>scons
scons: Reading SConscript files ...
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc9 in position 9: ordinal not in range(128):
  File "D:\Code\mitsuba\mitsuba\SConstruct", line 12:
    'plugins', 'stubs', 'winstubs')
  File "D:\installed-application\Anaconda3\envs\py27\Scripts\..\Lib\site-packages\scons-2.5.1\SCons\Script\SConscript.py", line 602:
    env = self.factory()
  File "D:\installed-application\Anaconda3\envs\py27\Scripts\..\Lib\site-packages\scons-2.5.1\SCons\Script\SConscript.py", line 582:
    default_env = SCons.Defaults.DefaultEnvironment()
  File "D:\installed-application\Anaconda3\envs\py27\Scripts\..\Lib\site-packages\scons-2.5.1\SCons\Defaults.py", line 88:
    _default_env = SCons.Environment.Environment(*args, **kw)
  File "D:\installed-application\Anaconda3\envs\py27\Scripts\..\Lib\site-packages\scons-2.5.1\SCons\Environment.py", line 982:
    apply_tools(self, tools, toolpath)
  File "D:\installed-application\Anaconda3\envs\py27\Scripts\..\Lib\site-packages\scons-2.5.1\SCons\Environment.py", line 107:
    env.Tool(tool)
  File "D:\installed-application\Anaconda3\envs\py27\Scripts\..\Lib\site-packages\scons-2.5.1\SCons\Environment.py", line 1789:
    tool(self)
  File "D:\installed-application\Anaconda3\envs\py27\Scripts\..\Lib\site-packages\scons-2.5.1\SCons\Tool\__init__.py", line 190:
    self.generate(env, *args, **kw)
  File "D:\installed-application\Anaconda3\envs\py27\Scripts\..\Lib\site-packages\scons-2.5.1\SCons\Tool\default.py", line 41:
    SCons.Tool.Tool(t)(env)
  File "D:\installed-application\Anaconda3\envs\py27\Scripts\..\Lib\site-packages\scons-2.5.1\SCons\Tool\__init__.py", line 190:
    self.generate(env, *args, **kw)
  File "D:\installed-application\Anaconda3\envs\py27\Scripts\..\Lib\site-packages\scons-2.5.1\SCons\Tool\mslink.py", line 312:
    msvc_setup_env_once(env)
  File "D:\installed-application\Anaconda3\envs\py27\Scripts\..\Lib\site-packages\scons-2.5.1\SCons\Tool\MSCommon\vc.py", line 410:
    msvc_setup_env(env)
  File "D:\installed-application\Anaconda3\envs\py27\Scripts\..\Lib\site-packages\scons-2.5.1\SCons\Tool\MSCommon\vc.py", line 517:
    d = msvc_find_valid_batch_script(env,version)
  File "D:\installed-application\Anaconda3\envs\py27\Scripts\..\Lib\site-packages\scons-2.5.1\SCons\Tool\MSCommon\vc.py", line 467:
    d = script_env(vc_script, args=arg)
  File "D:\installed-application\Anaconda3\envs\py27\Scripts\..\Lib\site-packages\scons-2.5.1\SCons\Tool\MSCommon\vc.py", line 356:
    stdout = common.get_output(script, args)
  File "D:\installed-application\Anaconda3\envs\py27\Scripts\..\Lib\site-packages\scons-2.5.1\SCons\Tool\MSCommon\common.py", line 160:
    env['ENV'] = normalize_env(env['ENV'], vars, force=False)
  File "D:\installed-application\Anaconda3\envs\py27\Scripts\..\Lib\site-packages\scons-2.5.1\SCons\Tool\MSCommon\common.py", line 117:
    normenv[k] = copy.deepcopy(env[k]).encode('mbcs')
@merlinND
Copy link
Member

I have no specific experience with this problem, but looking at the stack trace, it might be because there's an environment variable containing non-ASCII characters. It looks like SCons has a problem with that.

@jakoaltrd
Copy link

I am compiling mitsuba in VS2017 as well. I clone the whole project and opened the solution in the build folder. when compiling it I got a different problem, it didn't generate the exe file. does this project from official site not complete or miss some files?

@banbao990
Copy link
Author

I am compiling mitsuba in VS2017 as well. I clone the whole project and opened the solution in the build folder. when compiling it I got a different problem, it didn't generate the exe file. does this project from official site not complete or miss some files?

Have you tried this method?
#61 (comment)

@banbao990
Copy link
Author

I have no specific experience with this problem, but looking at the stack trace, it might be because there's an environment variable containing non-ASCII characters. It looks like SCons has a problem with that.

thanks a lot, scons checks all my environment variables(not only path). as soon as I remove all variables with non-ascii character, it compiles well

@jakoaltrd
Copy link

yes, I tried that, but when I run mtsgui.exe , there is no response at all, I don't know whether it is because the Qt version doesn't match, I had Qt5.13 installed.

@banbao990
Copy link
Author

yes, I tried that, but when I run mtsgui.exe , there is no response at all, I don't know whether it is because the Qt version doesn't match, I had Qt5.13 installed.

I see the qt version is 5.9.1. "dependencies\include\QtCore\5.9.1"
I tried it, but the same question remains.

@banbao990
Copy link
Author

yes, I tried that, but when I run mtsgui.exe , there is no response at all, I don't know whether it is because the Qt version doesn't match, I had Qt5.13 installed.

If you change your Qt version to 5.9.1 and meet the same problem with me. you can see this. #52 (comment) The comment help me fix it out. Just use the Qt... files in your Qt installation path to overwrite the files in the same dir of mtsgui.exe.

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

3 participants