Harry van der Wolf <[email protected]> writes:
> openjdk8 is fine. I use that as well (just as openjdk11 by the way as java8
> is officially no longer supported).
When you say "java8 is officially no longer supported", do you mean Java
8 the language flavor, or openjdk8, or jdk8 from Oracle, or ?
I also have openjdk11 installed, so I could use that, but it seems like
that is not my problem.
> You do not only need git, you also need the google repo tool. either
> download it or install it from your package manager.
Thanks for the hint. It would be really nice if someone caused the
README.md or a BUILDING.md in these repos to have build instructions.
Thank you very much for the scripts. Obviously I have some things to
work through, so I will not quote most of it and only when I have a
question.
> ${curpath}/android/OsmAnd-java/collect_legacy_libs.sh
>
> # Copy the libraries in
> LIBDIR="${libpath}/lib"
> cd ${curpath}/tools/java-tools/OsmAndMapCreator/
> cp -v ${LIBDIR}/libOsmAndCoreWithJNI_standalone.so lib-native/
> cp -v ${LIBDIR}/libOsmAndCore_ResourcesBundle_shared.so lib-native/
> cp -v ${LIBDIR}/OsmAndCore_jni.jar lib-gl/OsmAndCore_jni.jar
> rm lib-native/OsmAndCore_jni.jar
Do these .so files get built somehow by the previous steps? If so, I'll
figure things out.
> - From my "software build scripts folder", I cd into "OsmAnd-all" where I
> build everything, but there is a very nasty detail. It is very important
> (!) to have a folder "lib" next to "OsmAnd-all" (not inside) where you
> have all the jars AND "libOsmAndCore_ResourcesBundle_shared.so" and
> "libOsmAndCoreWithJNI_standalone.so", which you can take from a nightly
> build from OsmandMapCreator (lib versions are actually already quite old).
But I have different native ELF format and have to build these, not copy
some long-ago-built Linux binary.
> Without these you will not be able to build a correct OsmAndMapCreator.
> Inside my script another script is called that is part of the OsmAnd-tools
> repo, but that script already assumes you have the necessary stuff
> available, which you normally don't have. And that script actually has an
> error as well, that's why my follow-up copying steps are in my script.
> (- I use a comparable, but more complex, script for OsmAnd and OsmAnd+ WITH
> the same symlink to the libraries, otherwise OsmAnd does not build either).
Wow. This is more complicated than I expected. I wonder if there is
any chance of getting these fixes pushed upstream?
> In the end a zip will be created containing "everything" in the folder one
> level above "OsmAnd-all" . The zip is approx. 80Mb. If it is around 67MB
> (or so), you did something wrong with the libraries mentioned in remark 1.
Thanks very much for the detailed hints!
--
You received this message because you are subscribed to the Google Groups
"OsmAnd" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/osmand/rmid0adjf2y.fsf%40s1.lexort.com.
