Gradle build
See original GitHub issueIs this considered/going to be considered?
I think it’s the fastest way of getting LWJGL3 to be used by other projects without the current LWJGL2 hassle of generating POMs separated from the main build. It can be used to compile without ant
at all, or it can be mixed.
I started adding support and got the kotlin plugin to compile all the sources, but got confused about the Generator.kt
If you’re not planning on adding this, please close as wont fix so I don’t spend any more time on it 😄
Issue Analytics
- State:
- Created 9 years ago
- Comments:71 (20 by maintainers)
Top Results From Across the Web
Gradle Build Tool
Accelerate developer productivity. Gradle helps teams build, automate and deliver better software, faster.
Read more >Getting Started | Building Java Projects with Gradle - Spring
This guide walks you through using Gradle to build a simple Java project. What you'll build. You'll create a simple app and then...
Read more >Gradle - Build a JAVA Project - Tutorialspoint
This chapter explains how to build a java project using Gradle build file. First of all, we have to add java plugin to...
Read more >The Gradle build system- Tutorial - Vogella.com
Gradle builds are described via a or multiple build.gradle files. At least one build file is typically located in the root folder of...
Read more >Gradle build command - Tom Gregory
Running the Gradle build command builds your Gradle project, including assembling your application and running tests.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have already experimented with porting the build process to Gradle in the past and had a look at it again quite recently. I might publish my progress later this week to give you an idea of what it could look like.
However, one issue that’s stopping me from cleanly transitioning to Gradle remains: There are circular dependencies between templates of some modules (e.g. OpenGL and OpenCL). While it is possible to compile all templates together this eliminates some of Gradle’s benefits and I’d rather see those circular dependencies removed (if this is reasonable without too much duplication).
I pushed another commit, the whole linux workflow can be considered complete now