Bug 103442 - Can't build android viewer with recent NDK
Summary: Can't build android viewer with recent NDK
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Android Viewer (show other bugs)
Version:
(earliest affected)
5.2.3.1 rc
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-23 21:21 UTC by MTest31
Modified: 2017-06-21 09:17 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description MTest31 2016-10-23 21:21:22 UTC
When I try to compile the android viewer with a recent android NDK, the build errors with the message:

configure: error: Unrecognized Android NDK. Missing RELEASE.TXT file in /home/vagrant/android-ndk/r12b.
Error running configure at ./autogen.sh line 281.

Only Android r10e works.

The version I tested was 5.2.3.1 or git commit 01ec8f357e651ca9656837b783cf7e6a32ee4d92, but it looks like current master still has this problem.

This is a problem I discovered when building libreoffice for f-droid (Bug 103067).
Comment 1 David Heidelberg 2016-11-02 21:39:53 UTC
Hello LibreOffice guys,

first I'd like to say I really appreciate effort on developing LibreOffice.

Second, I'd like to ask, as F-Droid user, if you could give a hand for people who building LibreOffice for F-Droid. It would make process much easier and faster :)

Also it would reduce number of bugreports about outdated LO in F-Droid.

Thank you
Comment 3 MTest31 2017-02-01 15:03:37 UTC
I confirm its fixed for 5.3.0.3.
Comment 4 Christian Lohmaier 2017-02-01 16:34:13 UTC
to answer backport: Android viewer isn't in a stage of maturity to warrant maintaining it in release branches. In other words: all releases thus far have been prepared from master branch.
Comment 5 MTest31 2017-02-01 21:25:44 UTC
About the recent 5.3 release. I've tried to package 5.3.0.3 for F-Droid, and got a build error which looks like another bug, without any idea how to work around it. Can I file an issue for it? Do you think I should avoid packaging it?

Also, could you make it more transparent which git commits you use for Android builds? Like giving them special git tags for example, or maintaining a public document with git commits.
Comment 6 David Heidelberg 2017-06-21 09:17:14 UTC
@MTest31 please open new issue, it's not likely that anyone notice comment in already closed issue :)