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

Port build from maven to gradle2.2 with support for AndroidStudio #91

Closed
k3b opened this Issue Jan 8, 2015 · 8 comments

Comments

Projects
None yet
5 participants
@k3b
Contributor

k3b commented Jan 8, 2015

Goals

  • Being able to build osmdroid (with its subprojects and with the demo app OpenStreetMapViewer) using gradle2.2ff and/or Androidstudio1.0ff.
  • Being able to create osm-based android apps that do not depend on non-free components to support fdroid (see osmdroid issue #71:Non-free libraries in dependencies )
  • Being able to easy create osm-based android apps where only gradle references to osmdroid and other libs are needed

Currently building osmdroid (with its subprojects) is mainly based on maven-pom-files.

I have startet doing this in my AndroidStudio-Branch. For details see current status

@ziem

This comment has been minimized.

Contributor

ziem commented Jan 8, 2015

👍

@neilboyd neilboyd added the enhancement label Jan 8, 2015

@k3b

This comment has been minimized.

Contributor

k3b commented Jan 10, 2015

Hello osmdroid core developper community

##status summary

  • AndroidStudio1+/gradle2.2+ project
    • works with sub-moduls OpenStreetMapViewer, osmdroid-android and osmdroid-third-party
    • does not work with sub-moduls osmdroid-android-it and OSMMapTilePackager
    • Risks
      • when using AndroidStuio with
        • making changes to supported modules may break sourcecode/functionality of non supportet modules
        • making changes to submodules/filenames may break maven build scripts

Should we integrate these changes into main osmdroid repository now and are we willing to accept the risks i mentioned?

What do you think?

Links to subproject and current status see first comment

Is there a non-google-forum where osmdroid-developpers discuss issues? (or a chat-group-channel?)

Is there a countinuous integration build server for osmdroid (i.e. jenkins) that can check the risks by doing a maven build with running the integrationstests?

@gaurav-fueled

This comment has been minimized.

gaurav-fueled commented Jun 12, 2015

+1

@k3b

This comment has been minimized.

Contributor

k3b commented Jun 12, 2015

I donot know how to gradle build "osmdroid-android-it" and "OSMMapTilePackager".

therefore i havent checked in my changes

@spyhunter99

This comment has been minimized.

Collaborator

spyhunter99 commented Jun 12, 2015

My two cents, avoid gradle. Maven has reasonable android support now.

@gaurav-fueled

This comment has been minimized.

gaurav-fueled commented Jun 12, 2015

Android officially supports android studio with gradle. So if we can port this library to gradle then we wont have a reasonable support

spyhunter99 added a commit that referenced this issue Oct 19, 2015

#91 adding grade build files. Note: this is only a partial solution, …
…but it will build osmdroid and the sample map app without a problem (and debug it)

spyhunter99 added a commit that referenced this issue Oct 24, 2015

@spyhunter99

This comment has been minimized.

Collaborator

spyhunter99 commented Jan 6, 2016

ok so most of the project now builds with both maven and gradle. only thing left is the tile packager.

@spyhunter99

This comment has been minimized.

Collaborator

spyhunter99 commented Jan 9, 2016

GoogleWrapperApp still needs conversion

spyhunter99 added a commit that referenced this issue Jan 15, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment