-
Notifications
You must be signed in to change notification settings - Fork 44
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
Scala 2.11 compatibility #78
Comments
aginiewicz
added a commit
to aginiewicz/libgdx-sbt-project.g8
that referenced
this issue
Jul 7, 2014
This big commit updates Scala to 2.11.1 and SBT to 0.13.5. It was possible because of new Android plugin. This template now uses https://github.com/pfn/android-sdk-plugin plugin. Directory layout of project was changed to mirror those of official gdx-setup.jar, though proguard rules are different - they are merge of rules from old project, gdx-setup.jar template rules and official android rules from proguard-android.txt. Proguard rules might still need some polishing, there are warnings, but they seem not influence normal working of Libgdx, so they are ignored for now. If something does not work due to bad proguard rule, open ticket and it will be fixed in template. Last, but not least, I disabled iOS code for now, due to few reasons: - ajhager#78 - roboscala/sbt-robovm#10 - default template from gdx-setup.jar looks different (it has three files) - I don't have iOS nor Mac to test/fix this stuff That's why I decided to remove those files and publish what I already got, and wait for patches from someone who has iOS or Mac and can test/fix iOS support in new template.
This was referenced Jul 7, 2014
See #80 for follow up on iOS. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there,
I tried building my prototype with Scala 2.11.0-RC4. As for iOS, I kept initial project layout and haven't modified anything from template yet. I was able to compile whole project with 2.10, but now I get:
Have you seen it before?
The text was updated successfully, but these errors were encountered: