Add android build on travis

[Bjoe]

Add android build on travis.

[obiltschnig]

It seems all other builds are commented out?

[Bjoe]

@obiltschnig This is only to get faster an result. After android build is working I will comment all in and squash all commits.

[obiltschnig]

Wouldn't it be faster to set up Travis for your fork?

[obiltschnig]

I guess we don't need to merge this for now, as Travis builds your PR anyway ;-)

[Bjoe]

Wouldn't it be faster to set up Travis for your fork?

Would be better, but travis is not building on my fork... but maybe I should create a pull request in my own fork?

[Bjoe]

... but maybe I should create a pull request in my own fork?

No sorry. Travis is not building in my fork. Only when I create a pull request to poco, travis builds my branch.

[zosrothko]

@Bjoe "Travis is not building in my fork.".. Yes Travis is building your fork, but you have before to add your github repository to the travis workflow. Go on Travis and open you account. Then add your poco's fork

[Bjoe]

@zosrothko Ok thank you! Now it works.

@obiltschnig Ok I cleanup/enable all builds in travis.yml and squashed my commits.
Unfortunately the android emulator is not yet running :-( I will figured out.
As test name I add here "android API level 19", but this should be changed or?

At the moment the android build will fail because we have two issues in android. These are fixed in #1983 and #1975

[Bjoe]

Ok, done. Now it is ready to be merged, after review is done :-)

I added two android builds. I think POCO should support as minimum API level 19 and as newest 24. These are the most distributed android platform versions. See Platform Versions

There are still some open issues:

• Failing tests: Failing tests are fixed in pull request Set pthread min stack size in android #2035
• Build for android API level 19 is crashing in android emulator for API level 19 with following output:

Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 1690 (Foundation-test)
backtrace:
#00 pc 00000000
#1 pc 00049d63 /data/local/tmp/lib/libCppUnitd.so (std::__ndk1::__stdinbuf::imbue(std::__ndk1::locale const&)+26)
#2 pc 00049a71 /data/local/tmp/lib/libCppUnitd.so (std::__ndk1::__stdinbuf::__stdinbuf(__sFILE*, mbstate_t*)+72)

I think the problem has something to do with the standard C++ library. I will figure out what is the problem. For the first time, I decided to use the android API level 24 at runtime.

• Unfortunately the android NDK didn't provide any OpenSSL version, so all crypto tests are not running. But I think POCO should have this.

For the develop branch, should I create also a pull request?

[zosrothko]

@aleks-f From my point of view, all change requests are ok. BTW, it is nice to have Poco on Android. Thanks to @Bjoe for this contribution.

[aleks-f]

@Bjoe this pull should go to poco-1.9.0

[Bjoe]

@aleks-f Yep, I know. But I will fix first the review findings... then test should be back to green and then I will merge or better squash and rebase to poco-1.9.0. Too many changes at once could be difficult to find the problem if the build fails. So when I'm ready I will inform you. Btw. how can I requested a review?

[aleks-f]

how can I requested a review?

[Bjoe]

@aleks-f I didn't have this "button" on the right site of "Reviewers".

[aleks-f]

I'm not sure why, you are a member of developers team and I think you should be able to:

https://help.github.com/articles/requesting-a-pull-request-review/

@zosrothko can you request reviews on poco pulls with your permissions?

[Bjoe]

@aleks-f I have read this article about "Requesting a pull request review" before and I didn't have this buttons or can search for a person. I think this is the problem:

Note: Pull request authors can't request reviews unless they are either a repository owner or collaborator with write access to the repository.

[Bjoe]

@zosrothko I used first POCO_ANDROID instead of POCO_OS_ANDROID, because it is not only to add POCO_OS_ANDROID in Poco/Platfrom.h... see my pull request #2186

It's fixed

[obiltschnig]

Will temporarily remove/disable in 1.9.0 due to failing tests.