Changeset View
Standalone View
release/scripts/modules/sys_info.py
| Context not available. | |||||
| else: | else: | ||||
| output.write("Blender was built without FFmpeg support\n") | output.write("Blender was built without FFmpeg support\n") | ||||
| if bpy.app.build_options.sdl: | |||||
| output.write("\nSDL\n") | |||||
| output.write(lilies) | |||||
| output.write("Version: %s\n" % bpy.app.sdl.version_string) | |||||
| if bpy.app.build_options.sdl_dynload: | |||||
| output.write("Loading method: dynamically loaded by Blender (WITH_SDL_DYNLOAD=ON)\n") | |||||
| else: | |||||
| output.write("Loading method: linked (WITH_SDL_DYNLOAD=OFF)\n") | |||||
| if not bpy.app.sdl.available: | |||||
| output.write("WARNING: Blender could not load SDL library\n") | |||||
sergey: I can't follow this logic. There is no difference in dynamic linking and dynamic loading, you… | |||||
Not Done Inline ActionsThere are three ways to configure SDL support: "dynamic loading" - Blender loads the lib with dlopen(). "ldd blender" doesn't show the SDL library. This is the behaviour you'd get with WITH_SDL_DYNLOAD=yes. "dynamic linking" - GCC links the lib, and the OS loads it when loading Blender. "ldd blender" does show the SDL library. This is the behaviour you'd get with WITH_SDL_DYNLOAD=no. This is still dynamic, as the library is not statically linked with Blender. The third option is simply not supporting SDL, i.e. WITH_SDL=no sybren: There are three ways to configure SDL support:
"dynamic loading" - Blender loads the lib with… | |||||
Not Done Inline ActionsI know the technical aspects of difference between dynamic linking and dynamic loading. I don't see difference for handling both cases and showing exact version in the system info. Meaning, IMO, you can always show relevant SDL version, optionally maybe also mentioning if it's dynload or not. sergey: I know the technical aspects of difference between dynamic linking and dynamic loading. I don't… | |||||
| output.write("\nOther Libraries:\n") | output.write("\nOther Libraries:\n") | ||||
| output.write(lilies) | output.write(lilies) | ||||
| ocio = bpy.app.ocio | ocio = bpy.app.ocio | ||||
| Context not available. | |||||
| else: | else: | ||||
| output.write("Blender was built without Cycles support\n") | output.write("Blender was built without Cycles support\n") | ||||
| if not bpy.app.build_options.sdl: | |||||
| output.write("SDL: Blender was built without SDL support\n") | |||||
| if bpy.app.background: | if bpy.app.background: | ||||
| output.write("\nOpenGL: missing, background mode\n") | output.write("\nOpenGL: missing, background mode\n") | ||||
| else: | else: | ||||
| Context not available. | |||||
I can't follow this logic. There is no difference in dynamic linking and dynamic loading, you should just be able to query SDL version via it's API.
Also, if dynamic loading is not used, you know for sure if it's SDL1.2 or SDL2.0.
So to me it seems reporting here could be improved a lot.