-
|
Hi There! I am trying to compile and link raylib against Google's ANGLE so I can get better performance on Mac M1 Chips. With OpenGL being deprecated and being about 10 times slower than Metal on M1 Macs, the improved support for ANGLE, essentially giving raylib a Metal Backend is exciting! System
Folder Structure (up to 2 levels) λ ~/code/projects/raylib-cmake-starter/ angle* tree -L 2
.
├── CMakeLists.txt
├── README.md
├── bootstrap.sh
├── build
│ ├── CMakeCache.txt
│ ├── CMakeFiles
│ ├── CPackConfig.cmake
│ ├── CPackSourceConfig.cmake
│ ├── Makefile
│ ├── cmake_install.cmake
│ ├── raylib-starter
│ └── vendor
├── build.sh
├── build_with_angle.sh
├── run.sh
├── src
│ └── main.cpp
└── vendor
├── angle
└── raylib(All paths relative to root project directory unless absolute)
CMakeFiles.txt and output cmake_minimum_required(VERSION 3.16)
project(raylib-starter)
set(CMAKE_CXX_STANDARD 14)
file(GLOB_RECURSE SOURCES "src/*.cpp")
add_executable(${PROJECT_NAME} ${SOURCES})
# Set raylib and ANGLE include and library paths
set(RAYLIB_INCLUDE_DIR vendor/raylib/src)
set(RAYLIB_LIBRARY_DIR vendor/raylib/src)
set(ANGLE_INCLUDE_DIR vendor/angle/include)
set(ANGLE_LIBRARY_DIR vendor/angle/out/Release)
# Replace <path_to_angle_repository> with the actual path to your cloned ANGLE repository
target_include_directories(${PROJECT_NAME} PRIVATE
${RAYLIB_INCLUDE_DIR}
${ANGLE_INCLUDE_DIR}
)
# Find the raylib and ANGLE libraries
find_library(RAYLIB_LIBRARY libraylib.a PATHS ${RAYLIB_LIBRARY_DIR})
find_library(ANGLE_GLESv2_LIBRARY libGLESv2.dylib PATHS ${ANGLE_LIBRARY_DIR})
find_library(ANGLE_EGL_LIBRARY libEGL.dylib PATHS ${ANGLE_LIBRARY_DIR})
# Link required system frameworks for macOS
find_library(COCOA_LIBRARY Cocoa)
find_library(OPENGL_LIBRARY OpenGL)
find_library(IOKIT_LIBRARY IOKit)
find_library(CORE_FOUNDATION_LIBRARY CoreFoundation)
find_library(CORE_VIDEO_LIBRARY CoreVideo)
target_link_libraries(${PROJECT_NAME}
# Link raylib static library
${RAYLIB_LIBRARY}
# Link ANGLE libraries
${ANGLE_GLESv2_LIBRARY}
${ANGLE_EGL_LIBRARY}
# Link macOS system frameworks
${OPENGL_LIBRARY}
${COCOA_LIBRARY}
${IOKIT_LIBRARY}
${CORE_FOUNDATION_LIBRARY}
${CORE_VIDEO_LIBRARY}
)It compiles fine, but raylib gives a black screen: However in version of my cmake_minimum_required(VERSION 3.16)
project(raylib-starter)
set(CMAKE_CXX_STANDARD 14)
file(GLOB_RECURSE SOURCES "src/*.cpp")
add_executable(${PROJECT_NAME} ${SOURCES})
# Set raylib and ANGLE include and library paths
set(RAYLIB_INCLUDE_DIR vendor/raylib/src)
set(RAYLIB_LIBRARY_DIR vendor/raylib/src)
set(ANGLE_INCLUDE_DIR vendor/angle/include)
set(ANGLE_LIBRARY_DIR vendor/angle/out/Release)
# Replace <path_to_angle_repository> with the actual path to your cloned ANGLE repository
target_include_directories(${PROJECT_NAME} PRIVATE
${RAYLIB_INCLUDE_DIR}
${ANGLE_INCLUDE_DIR}
)
# Find the raylib and ANGLE libraries
find_library(RAYLIB_LIBRARY libraylib.a PATHS ${RAYLIB_LIBRARY_DIR})
find_library(ANGLE_GLESv2_LIBRARY libGLESv2.dylib PATHS ${ANGLE_LIBRARY_DIR})
find_library(ANGLE_EGL_LIBRARY libEGL.dylib PATHS ${ANGLE_LIBRARY_DIR})
# Link required system frameworks for macOS
find_library(COCOA_LIBRARY Cocoa)
# find_library(OPENGL_LIBRARY OpenGL)
find_library(IOKIT_LIBRARY IOKit)
find_library(CORE_FOUNDATION_LIBRARY CoreFoundation)
find_library(CORE_VIDEO_LIBRARY CoreVideo)
target_link_libraries(${PROJECT_NAME}
# Link raylib static library
${RAYLIB_LIBRARY}
# Link ANGLE libraries
${ANGLE_GLESv2_LIBRARY}
${ANGLE_EGL_LIBRARY}
# Link macOS system frameworks
# ${OPENGL_LIBRARY}
${COCOA_LIBRARY}
${IOKIT_LIBRARY}
${CORE_FOUNDATION_LIBRARY}
${CORE_VIDEO_LIBRARY}
)
I get the following errors: [ 50%] Linking CXX executable raylib-starter
Undefined symbols for architecture arm64:
"_glClearDepth", referenced from:
_rlglInit in libraylib.a(rcore.c.o)
"_glGetTexImage", referenced from:
_rlReadTexturePixels in libraylib.a(rcore.c.o)
"_glPolygonMode", referenced from:
_rlEnableWireMode in libraylib.a(rcore.c.o)
_rlDisableWireMode in libraylib.a(rcore.c.o)
ld: symbol(s) not found for architecture arm64Would appreciate it if anyone has anyone has any thoughts on this or knows how to get raylib working with ANGLE! |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 19 replies
-
|
@grplyler Did you manage to get it working? ANGLE support has been added recently and it's still quitte experimental, not sure if anyone has tried it with macOS M1 CPU just yet. Please, if you investigated it, let me know your progress! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @raysan5, I didn't quite get it working, but I took a break from it. I can take another stab at it in the next week or so. I'd like to get it working because Metal is capable of about 10x more draw calls than OpenGL on modern Macs. I'll let you know! Thanks for your time. |
Beta Was this translation helpful? Give feedback.
-
|
Nice! Thanks for testing! Take your time! Let me know if you get it working! :) |
Beta Was this translation helpful? Give feedback.
-
|
Update: After a few black screens, thanks to raylibs trace logs, I did manage to get it working on a small 2D project for work and went from about ~3000 FPS (optimized build without ANGLE) to ~7300 FPS with ANGLE! Without ANGLE (optimized build) With ANGLE (optimized build, dylib, 2021 Apple M1 Pro, 10 CPU Cores, 10 GPU Cores) Raylib Debug Tracing with ANGLE I plan on writing a proper guide for now to build and link ANGLE from scratch to raylib along with benchmarks, since this took a fair bit of googling, trial and error. The dynamic linking is convenient since people can just plop But these speed boosts on Mac could really make things interesting. For now, this is an easier solution than using something like I'll be back with a writeup/howto, CMakeLists.txt, and maybe update my raylib starter project when I get some more time! Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
WOW! This is really AMAZING! Congratulations! IT looks fantastic! A writeup or a simple guide or an update on raylib Wiki would be really appreciated! It could be REALLY useful for many macOS developers! Actually, I'm releasing my tools for macOS very soon and ANGLE could keep them alive if OpenGL gets removed at some point! Thanks again for such great news! 😄 |
Beta Was this translation helpful? Give feedback.
-
|
last time I looked at Angle on Linux I failed to even get it to compile, so well done, I look forward to the write up so I can have another go! |
Beta Was this translation helpful? Give feedback.
-
|
ah, I fixed it!!! diff --git a/src/external/glfw/src/egl_context.c b/src/external/glfw/src/egl_context.c
index bc5f3e60..4700e573 100644
--- a/src/external/glfw/src/egl_context.c
+++ b/src/external/glfw/src/egl_context.c
@@ -343,7 +343,7 @@ GLFWbool _glfwInitEGL(void)
#elif defined(__OpenBSD__) || defined(__NetBSD__)
"libEGL.so",
#else
- "libEGL.so.1",
+ "libEGL.so",
#endif
NULL
};Then after compiling raylib with GRAPHICS=GRAPHICS_API_OPENGL_ES2, I could use this command: I ran the executable with: changing the LD_LIBRARY_PATH is required, because otherwise glfw will still dlopen the mesa provided libEGL.so, despite that I was passing paths to them on the command line... I'm not really sure why, I guess I have more to learn about how shared libs work here. |
Beta Was this translation helpful? Give feedback.
-
I think it'd be best if all OS were just consolidated to a single page. |
Beta Was this translation helpful? Give feedback.
-
This is just conjecture, I haven't ran any actual benchmark, but I suspect there would not be such a disparity in performance between them, apple's opengl drivers are exceptionally terrible, I doubt such a difference would be observed on either windows or linux. |
Beta Was this translation helpful? Give feedback.
-
Might be able to change that with patchelf, but I would probably put it somewhere to where it's more portable. I know with Zig build system, can set the rpath in the build file itself. I'm not too good with make or cmake otherwises. Having said that, I still have a problem with the binary seeing it. Still segfaults looking for it, even though ldd is showing the correct path, so I dunno. |
Beta Was this translation helpful? Give feedback.
-
|
This is interesting. Apparently my issues to linking are due to I had setup for both X11 and Wayland, but when I compiled the library for just X11, everything linked as it should. I guess Angle must be setup for X11 and not Wayland or both. |
Beta Was this translation helpful? Give feedback.
-
|
Eyeing that iOS Metal translation that ANGLE seems to provide like 🕵️♀️🕵️🕵️♂️ |
Beta Was this translation helpful? Give feedback.
-
|
Nice. It can be merged into raylib and officially add support for macOS and iOS. |
Beta Was this translation helpful? Give feedback.
-
|
Linking with ANGLE is just a build option, no need to change anything on raylib side, afaik. iOS support requires a platform layer that is not implemented, that's the real work to do; the graphics layer is already implemented and probably working thanks to ANGLE. In any case, contributors are welcome to implement the iOS platform layer, I have no plans to do it and in 10 years nobody has done it. |
Beta Was this translation helpful? Give feedback.
-
|
Writeup on how to do this is out! Also got the source code at https://github.com/grplyler/raylib-articles if we want to collab, @Peter0x44 on adding it to the Raylib wiki. Medium post: https://medium.com/@grplyler/building-and-linking-googles-angle-with-raylib-on-macos-67b07cd380a3 |
Beta Was this translation helpful? Give feedback.
-
|
Update: I also added to my posts how to compile ANGLE with only the metal backend. No need for D3D, Vulkan, etc on mac. And when linking and running, its interesting, i get slightly different debug info on the renderer: Also, no matter what i did, I couldn't uncap the framerate with this build! It was limited somewhere in the implementation. Switching to the non-pruned versions of ANGLE and not changing my raylib code at all (not even recompiling) the framerate shot up to 11,000+ FPS. Idk if this is apple or google limiting this kind of GPU resource hogging. |
Beta Was this translation helpful? Give feedback.
-
|
AMAZING article! Thank you very much for writing it! And congratulations again for the accomplishment! It will be really useful for many raylib users! Thanks! 😄 |
Beta Was this translation helpful? Give feedback.
-
|
One question, did you check the differences in size/version between ANGLE from Chrome and ANGLE you build? |
Beta Was this translation helpful? Give feedback.
-
|
I couldn't readily find the actual version number I built, but it was from ANGLEs master repo: The size of my
Hope that helps! |
Beta Was this translation helpful? Give feedback.
-
|
@grplyler thanks for the article and research! I tried the one-line command you showed in the article. It compiles successfully, but I am not sure it's using the ANGLE in the end. This is the one-line command I am using to compile: I think the issue is that it doesn't choose the ANGLE library and defaults to openGL. I tried to add Log: I would appreciate any help, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
@andrei-zgirvaci Those are only cmake valid options. You need to define |
Beta Was this translation helpful? Give feedback.
-
|
Doesn't seems to make any difference in the logs. Not sure it's taking any effect. |
Beta Was this translation helpful? Give feedback.
-
|
You are using |
Beta Was this translation helpful? Give feedback.
-
|
I just tested ANGLE on Linux with my Go bindings. I used the I also had to symlink As for performance, it is actually a little better with plain OpenGL, around 2500FPS, with ANGLE it is around 2300, on intel GPU: And every time I close the window there is a segfault, that is on X11: |
Beta Was this translation helpful? Give feedback.
Update: After a few black screens, thanks to raylibs trace logs, I did manage to get it working on a small 2D project for work and went from about ~3000 FPS (optimized build without ANGLE) to ~7300 FPS with ANGLE!
Without ANGLE (optimized build)
With ANGLE (optimized build, dylib, 2021 Apple M1 Pro, 10 CPU Cores, 10 GPU Cores)
Raylib Debug Tracing with ANGLE