libgdx / libgdx-gradle-template Goto Github PK

Gradle template for libgdx projects that hopefully works on the CLI, Eclipse, Netbeans and Intellij IDEA

License: Apache License 2.0

Groovy 33.29% Java 12.10% Shell 54.61%

libgdx-gradle-template's Introduction

Cross-platform Game Development Framework

libGDX is a cross-platform Java game development framework based on OpenGL (ES), designed for Windows, Linux, macOS, Android, web browsers, and iOS. It provides a robust and well-established environment for rapid prototyping and iterative development. Unlike other frameworks, libGDX does not impose a specific design or coding style, allowing you the freedom to create games according to your preferences.

Open Source, Feature Packed, and Fostering a Large Third-Party Ecosystem

libGDX is released under the Apache 2.0 License, offering unrestricted usage in both commercial and non-commercial projects. While not mandatory, we appreciate any credit given to libGDX when you release a game or app using it. Check out our showcase for a selection of popular libGDX-powered games. With libGDX, you gain access to a comprehensive set of tools and features to develop multi-platform 2D and 3D games using Java.

Moreover, libGDX boasts a vibrant third-party ecosystem, with numerous tools and libraries that streamline development tasks. Explore the awesome-libgdx repository for a curated list of libGDX-centered libraries, serving as an excellent starting point for newcomers in the libGDX community.

An example game created with libGDX: Pathway by Robotality. Discover more captivating games in our Showcase.

Getting Started with libGDX / Documentation

Thanks to Gradle, you can easily set up libGDX without the need to download the framework itself. Your favorite build tool can handle everything for you. Additionally, we offer a convenient setup tool that automates project creation and downloads all the necessary components. Check out our website for instructions on getting started or refer to our comprehensive wiki.

We provide the libGDX javadocs online for easy reference. Additionally, the javadocs are bundled with every libGDX distribution, ensuring smooth integration with your preferred IDE.

Community & Contribution

Stay up to date with the latest libGDX news by following our blog. For engaging discussions and support, join our official libGDX Discord.

Reporting Issues

Use the Issue Tracker here on GitHub to report any issues you encounter. Before submitting, please read our Getting Help guide, which walks you through the process of reporting an issue effectively.

Contributing to the Codebase

libGDX benefits greatly from contributions made by our dedicated developer community. We appreciate any assistance in making libGDX even better. Check out the CONTRIBUTING.md file for details on how to contribute. Note that contributing involves working directly with libGDX's source code, a process that regular users do not typically undertake. Refer to the Working with the Source article for guidance.

You can also support our infrastructure (build server, web server, test devices) by contributing financially through our Patreon!

libgdx-gradle-template's People

Contributors

Stargazers

Watchers

libgdx-gradle-template's Issues

Build breaks with Gradle 1.8

Execution of "gradle clean" command fails with Gradle version 1.8 (the wrapper is set tu use 1.7 at the moment) with the following stack trace:

Where:
Build file 'C:\HomeSpace\gradle\libgdx-gradle-template-master\libgdx-gradle-temp
late-master\android\build.gradle' line: 37
What went wrong:
A problem occurred evaluating project ':android'.

Could not expand ZIP 'C:\Users\ob.gradle\caches\artifacts-26\filestore\com.ba
dlogicgames.gdx\gdx-platform\0.9.9-SNAPSHOT\jar\f4d6af8931ecb83354d9ccdc51a238d9
49da06ef\gdx-platform-0.9.9-SNAPSHOT-natives-armeabi.jar'.

Using Gradle 1.7 works Ok.

Android Studio 0.4.0 and Android Build Tools 0.7.+ incompatibility...

The template has the following lines in it:

// needed to add JNI shared libraries to APK when compiling on CLI
tasks.withType(com.android.build.gradle.tasks.PackageApplication) { pkgTask ->
    println pkgTask
    pkgTask.jniDir new File(projectDir, 'libs')
}

Unfortunately, the latest Android tools break this functionality, so builds at the command-line seem not to have the JNI libraries present in the APK. Any ideas?

Feature: TexturePacker integration

Some magical hook for generating texture atlases with TexturePacker would be awesome.

Question: Android SDK Versions

Foreword: I'm a complete Android newb so forgive my ignorance on this.

Trying to track down all the SDK versioning and what means what is driving me up the wall. From what I can tell, there's settings in the following places that refer to android-sdk stuff (omitting all lines I THINK are not relevant)...

android/build.gradle

android {
buildToolsVersion "17.0"
compileSdkVersion 17
}

android/project.properties

target=android-18

android/AndroidManifest.xml

    <uses-sdk
        android:minSdkVersion="8"
        android:targetSdkVersion="19" />

Can someone either enlighten me as to the purpose of these different settings or point me towards the info? Do any of these things need to be kept in sync? (From my perspective they look out of sync[ie 17, 18, 19])

Side Note: It seems like the buildTools versioning does not have a 1-1 relationship with the actual SDK version, is this true? As in, is it perfectly reasonable to continue to update your buildtools version while remaining on an old SDK?

Thanks!

To Do's

Anywhere we can go to see what other big ticket tasks need to be accomplished? kanban board or anything? I'd love to help and have some of my own ideas but I'd rather help with predetermined goals if there are any already.

Can not import the gradle-template to IDEA because of inter-module reference

When I try to import the template to IDEA as a gradle project I get following error:

[  30793]   WARN - .plugins.gradle.util.GradleLog - java.lang.IllegalArgumentException: Can't register given path of type 'SOURCE' because it's out of content root.
Content root: '/tmp/libgdx-gradle-template/desktop'
Given path: '/tmp/libgdx-gradle-template/android/assets'
    at org.jetbrains.plugins.gradle.model.gradle.GradleContentRoot.storePath(GradleContentRoot.java:66)
    at org.jetbrains.plugins.gradle.remote.impl.GradleProjectResolverImpl.populateContentRoot(GradleProjectResolverImpl.java:200)
    at org.jetbrains.plugins.gradle.remote.impl.GradleProjectResolverImpl.populateContentRoots(GradleProjectResolverImpl.java:171)
    at org.jetbrains.plugins.gradle.remote.impl.GradleProjectResolverImpl.populateModule(GradleProjectResolverImpl.java:142)
    at org.jetbrains.plugins.gradle.remote.impl.GradleProjectResolverImpl.populateModules(GradleProjectResolverImpl.java:133)
    at org.jetbrains.plugins.gradle.remote.impl.GradleProjectResolverImpl.doResolveProjectInfo(GradleProjectResolverImpl.java:82)
    at org.jetbrains.plugins.gradle.remote.impl.GradleProjectResolverImpl.access$000(GradleProjectResolverImpl.java:36)
    at org.jetbrains.plugins.gradle.remote.impl.GradleProjectResolverImpl$1.fun(GradleProjectResolverImpl.java:51)
    at org.jetbrains.plugins.gradle.remote.impl.GradleProjectResolverImpl$1.fun(GradleProjectResolverImpl.java:47)
    at org.jetbrains.plugins.gradle.remote.impl.RemoteGradleServiceHelper.execute(RemoteGradleServiceHelper.java:132)
    at org.jetbrains.plugins.gradle.remote.impl.GradleProjectResolverImpl.resolveProjectInfo(GradleProjectResolverImpl.java:47)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at org.jetbrains.plugins.gradle.remote.impl.GradleApiFacadeImpl$1.invoke(GradleApiFacadeImpl.java:116)
    at com.sun.proxy.$Proxy3.resolveProjectInfo(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322)
    at sun.rmi.transport.Transport$1.run(Transport.java:177)
    at sun.rmi.transport.Transport$1.run(Transport.java:174)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.rmi.transport.Transport.serviceCall(Transport.java:173)
    at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:553)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:808)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:667)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:722)

Maybe it would be an option to extract assets to separate subproject?