Unified executable (for CPU-only, OpenCL and CUDA)
Re: Unified executable (for CPU-only, OpenCL and CUDA)
Windows never stop to amaze me (a limited stack size in 2020...), I should have fixed the problem in the latest sources.
Re: Unified executable (for CPU-only, OpenCL and CUDA)
OSX works fine NVIDIA and APPLE drivers. Using LUXRAYS_ENABLE_OPENCL and LUXRAYS_ENABLE_CUDA .
Also a sidenote compilation time
CUDA 3min
NV OPENCL 6min
APPLE OPENCL 14min
Will test on APPLE AMD drivers this evening.
Also a sidenote compilation time
CUDA 3min
NV OPENCL 6min
APPLE OPENCL 14min
Will test on APPLE AMD drivers this evening.
check out my newest stuff http://q3de.com/research/
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
Re: Unified executable (for CPU-only, OpenCL and CUDA)
Defining symbols should be not required any more. Binaries will have now always the potential ability to work with CUDA and OpenCL if the drivers are available when run.
You can use LUXRAYS_DISABLE_OPENCL and LUXRAYS_DISABLE_CUDA if you really want to produce binaries that can not support GPUs (but it should be never required).
Re: Unified executable (for CPU-only, OpenCL and CUDA)
Well then i will have to find out how to compile with cuda on a system that does not support cuda...
But it is files and libs after all ..
luxcoreui seems to be liked against
Does cuda get linked in statically ???
there does not seem to be a dynamic dependency anymore ??
But it is files and libs after all ..
luxcoreui seems to be liked against
Does cuda get linked in statically ???
Code: Select all
MacBook-Pro:LuxCore drquader$ otool -L build/Release/luxcoreui
build/Release/luxcoreui:
@rpath/libomp.dylib (compatibility version 5.0.0, current version 5.0.0)
/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 23.0.0)
/System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL (compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1560.12.0)
/System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo (compatibility version 1.2.0, current version 1.5.0)
@rpath/libembree3.3.dylib (compatibility version 3.0.0, current version 3.0.0)
@rpath/libOpenImageDenoise.0.dylib (compatibility version 0.0.0, current version 1.2.0)
@rpath/libtbb.dylib (compatibility version 0.0.0, current version 0.0.0)
@rpath/libtiff.5.dylib (compatibility version 11.0.0, current version 11.0.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.11)
@rpath/libOpenImageIO.1.8.dylib (compatibility version 1.8.0, current version 1.8.13)
/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 400.9.4)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1252.200.5)
/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit (compatibility version 45.0.0, current version 1671.10.106)
/System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics (compatibility version 64.0.0, current version 1247.4.1)
/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 1560.12.0)
/usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)
check out my newest stuff http://q3de.com/research/
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
Re: Unified executable (for CPU-only, OpenCL and CUDA)
You don't need any OpenCL or CUDA header or library to compile the code, it is the magic of dynamic loading of DLLs.
Re: Unified executable (for CPU-only, OpenCL and CUDA)
which files are needed by lux then ??? only the installed driver ?So i will not have to add any .dylib files ?? And no patching That sounds unbelievable
This will make things alot easier ...
This will make things alot easier ...
check out my newest stuff http://q3de.com/research/
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
Re: Unified executable (for CPU-only, OpenCL and CUDA)
I think that the NVRTC DLLs are still needed, they are not shipped with the drivers.
Re: Unified executable (for CPU-only, OpenCL and CUDA)
The unified executables seem to work fine on Windows, both standalone and in blender.
Defining LUXRAYS_DISABLE_CUDA and LUXRAYS_DISABLE_OPENCL seems to have no effect: LuxCoreUI still allows to choose OCL render engines. I'll try to check why this happens.
Defining LUXRAYS_DISABLE_CUDA and LUXRAYS_DISABLE_OPENCL seems to have no effect: LuxCoreUI still allows to choose OCL render engines. I'll try to check why this happens.
Re: Unified executable (for CPU-only, OpenCL and CUDA)
What is so bad about that ? On Linux you can use NVIDIA and AMD GPU together ... i plan to do that ...
What dlls do you need to copy ??
check out my newest stuff http://q3de.com/research/
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
Re: Unified executable (for CPU-only, OpenCL and CUDA)
Well, nothing so bad I guess...
Only, it's not the expected behaviour...
The needed DLLs on Windows are nvrtc64_101_0.dll and nvrtc-builtins64_101.dll.
They are not included in drivers, they come with the SDK and Nvidia allows to redistribute them.
If they are missing, the unified executable does not find CUDA.