Eyal Kalderon

Results 126 comments of Eyal Kalderon

Well, the specific error I'm hitting is at the 90% mark from linking `librenderdoc.so`: ``` /usr/bin/ld: cannot find -lrenderdoc_libentry collect2: error: ld returned 1 exit status make[2]: *** [renderdoc/CMakeFiles/renderdoc.dir/build.make:1364: bin/librenderdoc.so]...

I already did try with a fresh `build` folder and no dice. However, calling `make renderdoc_libentry` by hand before invoking `make` solved the problem for me. Oh, that's interesting! I...

Whatever changes you made to the CMake scripts fixed the `renderdoc_libentry` issue for me! Thank you for that. I'm recompiling RenderDoc with OpenGL ES enabled as I type this. I...

Good news! Compiling RenderDoc with `ENABLE_GLES` works surprisingly well on Wayland. Calling `Start`/`EndFrameCapture` (passing the EGL context as a `DevicePointer` and a null pointer for the `WindowHandle`) works as expected....

Thank you so much for all the information! As you requested, I've created all the CMake and `globalconfig.h` infrastructure for detecting and linking to `libwayland-client` and `libwayland-egl` in a new...

So, it turns out that the most common way to detect a Wayland session over an X11 session is to simply check for the existence of a `DISPLAY` environment variable...

Usually, Wayland applications use the `wayland-egl.h` header to abstract over EGL. Thankfully, a simple C-style cast to `EGLNativeWindowType` seems to compile correctly for me, so no issues there. The real...

I've been looking further into how applications detect X11 and Wayland sessions at run-time, and I can't find any other way except for checking for `DISPLAY` and `WAYLAND_DISPLAY` at startup...

Also, it looks like `Keyboard::{Add,Remove}InputWindow` isn't being called consistently for all drivers when I use the *Launch Application* tab. Despite adding the function calls into `RenderDoc::{Add,Remove}FrameCapturer`, they don't seem to...

Okay, I'll remove those `Keyboard` functions from `{Add,Remove}FrameCapturer`. But it's very difficult for me to tell from reading the source where the keyboard input is supposed to occur, since doesn't...