-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting started on macOS and Maven #56
Comments
@jzy3d Hey! I'm guessing you deleted the test that includes the POM. If you haven't, you should begin by going to https://lwjgl.org/customize to get the POM for your project. Copy it in, and make sure you select all platforms you support. The error you're getting is informing you that a LWJGL module can't find the LWJGL core. It is a headache to solve, but making sure the POM is right is the first step. LWJGL extracts the native libraries itself and cleans up after itself—you don't need to manually do anything. Let me know if you have further issues (sorry I'm two months late). |
Hi @SWinxy, thank you a lot for the suggestions! Generating pom file parts with LWJGL Customize solved my path issue, what a great tool! |
I was able to locate most of Could you help me to locate packages GLU and GLUT in LWJGL? I am interested if you have links to share about making GL context current to non AWT thread (which was necessary with JOGL when invoking GL out of the display loop). Hints about text rendering similar to JOGL would be appreciated as well! |
GLU and GLUT are not supported by LWJGL (i.e., it does not provide Java bindings to those native libraries). I don't know any OpenGL, but here are what my buddies have informed me: GLU is deprecated, and GLUT is for making windows. AWT is a windowing and UI library, so in a way it can serve as a replacement to GLUT. But to implement such a conversion, you'd either migrate all the code over to AWT, or maintain both AWT and GLUT in parallel. It's sorta like, why force yourself to use GLUT, when AWT is right here for the picking. Working with OpenGL and its past libraries is a complicated dance. But, if you must use GLU and/or GLUT, there is a way. LWJGL can work with most native C libraries, but you will have to both provide the native library yourself as well as write code to interface with the native library. You can read up on how LWJGL generates the bindings here. If you decide that you must use GLU and/or GLUT, open an issue at LWJGL/lwjgl3, and Spasi might help you. I am happy to answer more questions that you have. |
GLUT was indeed written first for Windows but was then made available for linux under the name Freeglut. It does not only provide tools for the UI but also has useful methods for rendering, e.g. glutBitmapString is handy for drawing text, glutSolidSphere, glutSolidCube for drawing shapes. JOGL's GLUT seams to be written in pure java rather than binded, so this could be picked there. GLU as a lot of crucial methods for computing 3D to 2D or vice-versa, e.g. gluProject, gluUnproject, gluOrtho2d, gluLookAt and gluPickMatrix. (It also has useful methods for rendering : gluSphere, gluDisk, gluSphere, gluCylinder but these are less important to me). I found that GLU existed in previous version of LWJGL in pure Java (see GLU relying on Project). I probably can copy this. However JOML seams to be the place where to find GLU for LWJGL 3 nowadays. Another useful set of links. |
I can get a basic chart working, thanks again for your help! I started by simply copying previous LWJGL GLU source code in my project and simply add to rename I'll make my progress visible here. |
I am giving a try to lwjgl-awt as an alternative OpenGL binding to JOGL in Jzy3D.
I am simply trying to run the AWTTest sample but am getting the message
I wrote my pom file by looking at the project main pom and forced the import on macOS to start.
I print my classpath and get
with
lwjgl-opengl-3.3.1-natives-macos.jar
containingliblwjgl_opengl.dylib
, but not the expectedliblwjgl.dylib
.Is there anything missing in my maven dependencies to LWJGL?
I would prefer not to extract the natives in a local temporary dir and avoid defining the path through java.library.path.
The text was updated successfully, but these errors were encountered: