You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Goal: Fast, reliable, and simply-configured continuous integration for a STLab compiled for Android ABI(s).
STLab will be linked into an executable with our testing framework (presently, Boost.Test) which should be executed in an environment analogous to an Android Phone.
Configuration
Android has a significant number of configurations one may wish to support:
Android supports four ABIs, with a total of 14 instruction sets among them.
armeabi-v7a (32 bit ARM) (3 instruction sets)
arm64-v8a (64 bit ARM) (1 instruction set)
x86 (32 bit x86) (4 instruction sets)
x86_64 (64 bit x86) (6 instruction sets)
Building & Testing
To reduce setup and maintenance costs, any solution proposed should integrate with cmake and be invokable from the command line.
We allow installing dependencies (including libraries, compilers, emulators, and system images) but these must be installable from the command line.
Are there exemplar projects in this space? (C++ library with efficient Android CI support)
This Stack Overflow post suggests that .mk (makefile) files are used on Android to specify build configurations for executables. It contains fields like LOCAL_SRC_FILES := a.cpp b.cpp c.cpp etc.cpp.
Android CI for STLab
Goal: Fast, reliable, and simply-configured continuous integration for a STLab compiled for Android ABI(s).
STLab will be linked into an executable with our testing framework (presently, Boost.Test) which should be executed in an environment analogous to an Android Phone.
Configuration
Android has a significant number of configurations one may wish to support:
Android supports four ABIs, with a total of 14 instruction sets among them.
Building & Testing
To reduce setup and maintenance costs, any solution proposed should integrate with
cmake
and be invokable from the command line.We allow installing dependencies (including libraries, compilers, emulators, and system images) but these must be installable from the command line.
Our workflow should look very close to this:
Open Questions
What ABIs do we need to support for Adobe? What instruction sets do we need to support?
Is it possible to transpile an executable Android binary which is not an APK?
What is the minimum set of dependencies necessary to accomplish this?
Are there exemplar projects in this space? (C++ library with efficient Android CI support)
This Stack Overflow post suggests that
.mk
(makefile) files are used on Android to specify build configurations for executables. It contains fields likeLOCAL_SRC_FILES := a.cpp b.cpp c.cpp etc.cpp
.Reference
Native Executable on Android
Add C and C++ code to your [Android] project
Start the [Android] emulator from the command line
C++ Android Project in Android Emulator | Visual Studio 2019
To Read
http://www.hoseinjamshidi.com/compile-c-c-for-android-and-make-a-native-executable/
https://community.rti.com/static/documentation/connext-dds/5.2.0/doc/manuals/connext_dds/getting_started_extras/html_files/RTI_ConnextDDS_CoreLibraries_GettingStarted_AndroidAddendum/Content/AndroidAddendum/Building_and_Running_a__C_C___Applicatio.htm
The text was updated successfully, but these errors were encountered: