New Version of OSMand~?

[phouuupeMember]

Hi folks,

 

will there be another version of OSMand~ within the next weeks? Its awesome!

 

Thx.

P

[daithib8Member]

There may be. It is a complicated app and requires trickery to build and trickery to find the correct position to do the build from, at least when using ant. Until somebody with the necessary skill and knowledge has time to make a new build version line for the recipe, we can’t do it.

[phouuupeMember]

Hey, thats cool, because the app is 1.x now and it is wonderful 🙂

[pfalconMember]

Ok, latest versions consist of multiple components and use Google “repo” tool to fetch project (prooflink: http://code.google.com/p/osmand/wiki/InstallDevelopmentEnvironment). Do we want to to support “repo” repository type in F-Droid? I’m not sure how many projects would use it, but may be more than 1. It’s of course possible to work it around and fetch extra git repos “manually”.

Other problem is the same as before – they now have per-version branches, but don’t tag specific release revisions still, and repo manifests provided by them don’t reference specific revisions for reproducible builds. So, we’d need to maintain our manifests anyway.

Otherwise, I was able to build current HEAD without too much magic (but the build downloads/fetches lot of stuff and takes few hours, mostly because it builds for 4 archs).

[daithib8Member]

pfalcon: are you able to make a build version of it latest osmand?

[pfalconMember]

So, as I wrote, I was able to build it outside F-Droid, but was unsure how to proceed with adding it to F-Droid. Ideally, we’d add “repo” repo type support, and ability to specify repo type and url on package-version level. So, lot of blockers. Lately, I considered to just go ahead and do adhoc build with bunch of git clone’s in prebuild, but didn’t get to it either.

[daithib8Member]

It’s hard to guess what’s required (WP8?): https://github.com/osmandapp/OsmAnd-manifest/blob/master/current_release.xml. We can use git clone , although srclibs are more efficient . At least git is secure, unlike wget over http. The approach I usually adopt is to get out a build with git clone then put in a merge request for srclibs and do the subsequent build with those.We already have srclibs for osmand core and osmand tools anyway

[pfalconMember]

Yes, I found that to build just the android app, not all git repos are needed, their default manifests just checks out complete devel env with all components.

[daithib8Member]

I’ve made a WIP recipe by using srclibs so that their tree is replicated i.e. android core tools. I’m not sure where to go from here since I don’t understand the scripts. It builds fine without native code anyway with one small change to build.xml on branch r1.4.

[ColegotaMember]

Hi Friends!

Sorry to bump this post. I’ve also read the one called OsmAnd and OsmAnd+
http://f-droid.org/forums/topic/update-osmand-and-osmand/#
but not sure about situation. Will use OSMAnd after a lot of time and noticed that FDroid has an old version 0.8.2 while current it’s 1.4.1 and not sure if understood the problem.

Seems to be a hard to build application but not sure if this is the question about not to be continued.

It’s there a problem with Google maps and api at OSMAnd that not recommends to install from FDroid due to Google tracking policies?

Will be newer versions of OSMAnd in FDroid?

Any answers and help will be appreciated. Sorry if my message it’s not too clear. And of course, thank you a lot for providing us FDroid! 🙂

Best regards!
Colegota

[daithib8Member]

We can nearly build it, but have a strange permissions error for a build script when building with our build server. So no other problem, but it seems that future versions will use Google Analytics, though hopefully that will be easier to remove. I just hope they won’t use new Google location APIs.

[ColegotaMember]

Thanks for your answer!

If they start using any kind of tracking or location API then I will no use it, if not, I can wait for. 🙂

[PyroDevilMember]

I build OsmAnd 1.4 alpha out of the github repository yesterday:
https://dl.dropboxusercontent.com/u/1512554/OsmAnd-release.apk
(I singed it with my signature, so you may have to deinstall your existing version to use it)

[daithib8Member]

Thanks for the merge request PyroDevil (https://gitorious.org/f-droid/fdroiddata/merge_requests/142)! However, an alpha release isn’t ideal and the error we are having on the build server (https://f-droid.org/wiki/page/net.osmand.plus/lastbuild) doesn’t appear to be tackled in your build. I didn’t have any special problems myself with targets.

[fgiffMember]

As you know, there aren’t any tags to indicate what version is what, so I just built for master/HEAD, which describes itself in res/values/no-translate.xml as 1.4 alpha. In the previous build this version string was the same, but sed was used to rewrite it depending on the architecture being built.

The error on the build server is avoided by not calling the ndk-build at all. I got a quite usable apk without it. If you know what it does and why we need it, I can put it back in.

The targets thing wasn’t necessary for the older releases, but more recently there’s a dependency on ICS or newer SDKs to get the updated look-and-feel. This doesn’t affect backwards compatibility: I quite happily ran the generated apk on a Froyo device.

[Author]

Posts