blender/intern/cycles
Sergey Sharybin 21f31e6054 Fix T47856: Cycles problem when running from multi-byte path
This is a mix of regression and old unsupported configuration.

Regression was caused by some checks added on Blender side which was
checking whether python function returned error or not. This made it
impossible to enable Cycles when running from a file path which can't
be encoded with MBCS codepage.

Non-regression issue was that it wasn't possible to use pre-compiled
CUDA kernels when running from a path with non-ascii multi-byte
characters.

This commit fixes regression and CUDA parts, but OSL still can't be
used from a non-ascii location because it uses non-widechar API to
work with file paths by the looks of it. Not sure we can solve this
just from our side by using some codepage trick (UTF-16?) since even
oslc fails to compile shader when there are non-ascii characters in
the path.
2016-03-23 13:58:31 +01:00
..
app Fix compilation of cycles standalone and network device 2016-03-11 10:00:47 +01:00
blender Fix T47856: Cycles problem when running from multi-byte path 2016-03-23 13:58:31 +01:00
bvh Fix (harmless) assert in BVH spatial splits with Visual Studio debug builds. 2016-02-17 00:07:35 +01:00
cmake CMake: Fix typo in CUDA dynload commit 2016-01-14 12:48:14 +05:00
device Cycles: Some typo fixes 2016-03-12 15:01:20 +05:00
doc
kernel Cycles: Support parallel convergence mode for spherical stereo 2016-03-12 15:01:20 +05:00
render Fix T47856: Cycles problem when running from multi-byte path 2016-03-23 13:58:31 +01:00
subd Cycles: Correction to asserts, they will never trigger before 2016-02-03 15:01:26 +01:00
test Cycles: Add some utility tests using GTests 2016-02-06 19:19:20 +01:00
util Fix T47856: Cycles problem when running from multi-byte path 2016-03-23 13:58:31 +01:00
CMakeLists.txt Fix compilation of cycles standalone and network device 2016-03-11 10:00:47 +01:00