-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Rename 'linux' target to 'glfw' #3821
Comments
I think I'm 👎 on this. "linux" is the platform. The use of GLFW is an implementation detail of the test app for that platform. |
I actually got tripped up by |
@jfirebaugh there are two different things here, which are confusingly both named "linux": The |
Yeah -- I think we need to enforce some simplifications and abstractions to control the complexity of our build matrix and build system.
|
My take would be yes, since the OS X app adds a lot of complexity and weird UI and is more of an end user facing application, rather than a means to debug the renderer. I'm typically using the GLFW app to prototype new features and debug existing issues. There's nothing in GLFW that is Linux-specific; it's just the only app (until Qt lands) that runs on Linux. |
osxapp is intended to be as much an analogue to iosapp as possible, so it depends on the Mapbox OS X SDK just as iosapp depends on the iOS SDK. It isn't so much of an end user application, but its focus is definitely on SDK features like annotations and gesture recognition rather than renderer output. |
Fair enough; I'm 👍 on keeping both GLFW and the OSX app as supported targets on Mac OS. |
Heads up that #4498 will introduce an alternate headless rendering pipeline for |
Okay, we should move |
We've been able to build
linux
target in OS X for a while now. This target uses GLFW for rendering, and thus I feel havingglfw
target would be less confusing./cc @mapbox/gl
The text was updated successfully, but these errors were encountered: