Git-Mirrors/RetroShare
1
0
Fork 0
mirror of https://github.com/RetroShare/RetroShare.git synced 2024-12-14 10:24:31 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity
130d846e47
RetroShare/build_scripts/Android/prepare-toolchain-clang.sh

550 lines
18 KiB
Bash
Raw Normal View History

Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
#!/bin/bash
Improve license according to REUSE 3.0 FSFE licensing checking program lint is now happy $ reuse lint * Bad licenses: * Missing licenses: * Unused licenses: * Used licenses: AGPL-3.0-only, AGPL-3.0-or-later, Apache-2.0, CC-BY-SA-4.0, CC0-1.0, GPL-3.0-or-later, LGPL-3.0-or-later, MIT * Read errors: 0 * Files with copyright information: 6324 / 6324 * Files with license information: 6324 / 6324 Congratulations! Your project is compliant with version 3.0 of the REUSE Specification :-)
2019-12-18 11:57:20 -05:00
# Script to prepare RetroShare Android package building toolchain
#
Improve RetroShare Android tools and documentation
2020-03-19 19:10:11 -04:00
# Copyright (C) 2016-2020 Gioacchino Mazzurco <gio@eigenlab.org>
Improve license according to REUSE 3.0 FSFE licensing checking program lint is now happy $ reuse lint * Bad licenses: * Missing licenses: * Unused licenses: * Used licenses: AGPL-3.0-only, AGPL-3.0-or-later, Apache-2.0, CC-BY-SA-4.0, CC0-1.0, GPL-3.0-or-later, LGPL-3.0-or-later, MIT * Read errors: 0 * Files with copyright information: 6324 / 6324 * Files with license information: 6324 / 6324 Congratulations! Your project is compliant with version 3.0 of the REUSE Specification :-)
2019-12-18 11:57:20 -05:00
#
# This program is free software: you can redistribute it and/or modify it under
# the terms of the GNU Affero General Public License as published by the
# Free Software Foundation, version 3.
#
# This program is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
# FITNESS FOR A PARTICULAR PURPOSE.
# See the GNU Affero General Public License for more details.
#
# You should have received a copy of the GNU Affero General Public License along
# with this program. If not, see <https://www.gnu.org/licenses/>
#
# SPDX-FileCopyrightText: Retroshare Team <contact@retroshare.cc>
# SPDX-License-Identifier: AGPL-3.0-only
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
## Define default value for variable, take two arguments, $1 variable name,
## $2 default variable value, if the variable is not already define define it
## with default value.
function define_default_value()
{
VAR_NAME="${1}"
DEFAULT_VALUE="${2}"
Fix define_default_value in android scripts define_default_value wrongly reported error if the variable was already defined, causing the scripts to fail under bash -e, fix it by reporting corret exit value
2021-03-08 14:12:50 -05:00
[ -z "${!VAR_NAME}" ] && export ${VAR_NAME}="${DEFAULT_VALUE}" || true
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
}
## You are supposed to provide the following variables according to your system setup
define_default_value ANDROID_NDK_PATH "/opt/android-ndk/"
define_default_value ANDROID_NDK_ARCH "arm"
retroshare-service now build and runs fine on android (even older ones)
2018-10-05 16:29:49 -04:00
define_default_value ANDROID_PLATFORM_VER "16"
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
define_default_value NATIVE_LIBS_TOOLCHAIN_PATH "${HOME}/Builds/android-toolchains/retroshare-android-${ANDROID_PLATFORM_VER}-${ANDROID_NDK_ARCH}/"
define_default_value HOST_NUM_CPU $(nproc)
define_default_value BZIP2_SOURCE_VERSION "1.0.6"
define_default_value BZIP2_SOURCE_SHA256 a2848f34fcd5d6cf47def00461fcb528a0484d8edef8208d6d2e2909dc61d9cd
Update udp-discovery-cpp and android openssl
2019-08-29 09:50:26 -04:00
define_default_value OPENSSL_SOURCE_VERSION "1.1.1c"
define_default_value OPENSSL_SOURCE_SHA256 f6fb3079ad15076154eda9413fed42877d668e7069d9b87396d0804fdb3f4c90
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
define_default_value SQLITE_SOURCE_YEAR "2018"
define_default_value SQLITE_SOURCE_VERSION "3250200"
define_default_value SQLITE_SOURCE_SHA256 da9a1484423d524d3ac793af518cdf870c8255d209e369bd6a193e9f9d0e3181
retroshare-service support Android arm64 build
2019-07-18 05:11:42 -04:00
define_default_value SQLCIPHER_SOURCE_VERSION "4.2.0"
define_default_value SQLCIPHER_SOURCE_SHA256 105c1b813f848da038c03647a8bfc9d42fb46865e6aaf4edfd46ff3b18cdccfc
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
Fix compilation with libupnp-1.8.x
2019-04-24 17:36:40 -04:00
define_default_value LIBUPNP_SOURCE_VERSION "1.8.4"
define_default_value LIBUPNP_SOURCE_SHA256 976c3e4555604cdd8391ed2f359c08c9dead3b6bf131c24ce78e64d6669af2ed
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
define_default_value INSTALL_QT_ANDROID "false"
retroshare-service now build and runs fine on android (even older ones)
2018-10-05 16:29:49 -04:00
define_default_value QT_VERSION "5.12.0"
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
define_default_value QT_ANDROID_INSTALLER_SHA256 a214084e2295c9a9f8727e8a0131c37255bf724bfc69e80f7012ba3abeb1f763
Update udp-discovery-cpp and android openssl
2019-08-29 09:50:26 -04:00
define_default_value RESTBED_SOURCE_VERSION f74f9329dac82e662c1d570b7cd72c192b729eb4
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
Initial work on Broadcast Domain Discovery Discover peers on the same broadcast domain/LAN Implements own node announcement Implements others announcement listening Implements API to get notifiend when other nodes get discovered Implements API to get discovered nodes Add discovered peer locator to rsPeers if it is already friend Yet a bunch of things to do to take full advantage of this new implementation
2019-04-11 20:53:39 -04:00
define_default_value UDP_DISCOVERY_CPP_SOURCE "https://github.com/truvorskameikin/udp-discovery-cpp.git"
define_default_value UDP_DISCOVERY_CPP_VERSION "develop"
retroshare-service deep search support for Android
2018-10-05 19:23:08 -04:00
define_default_value XAPIAN_SOURCE_VERSION "1.4.7"
define_default_value XAPIAN_SOURCE_SHA256 13f08a0b649c7afa804fa0e85678d693fd6069dd394c9b9e7d41973d74a3b5d3
define_default_value RAPIDJSON_SOURCE_VERSION "1.1.0"
define_default_value RAPIDJSON_SOURCE_SHA256 bf7ced29704a1e696fbccf2a2b4ea068e7774fa37f6d7dd4039d0787f8bed98e
Add support to build with miniupnpc on Android Necessary to workaroud issues: https://github.com/RetroShare/RetroShare/issues/1649 https://github.com/mrjimenez/pupnp/issues/119
2019-09-28 07:54:16 -04:00
define_default_value MINIUPNPC_SOURCE_VERSION "2.1.20190625"
define_default_value MINIUPNPC_SOURCE_SHA256 8723f5d7fd7970de23635547700878cd29a5c2bb708b5e5475b2d1d2510317fb
retroshare-service deep search support for Android
2018-10-05 19:23:08 -04:00
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
## $1 filename, $2 sha256 hash
function check_sha256()
{
echo ${2} "${1}" | sha256sum -c &> /dev/null
}
## $1 filename, $2 sha256 hash, $3 url
function verified_download()
{
FILENAME="$1"
SHA256="$2"
URL="$3"
check_sha256 "${FILENAME}" "${SHA256}" ||
{
rm -rf "${FILENAME}"
wget -O "${FILENAME}" "$URL" ||
{
echo "Failed downloading ${FILENAME} from $URL"
exit 1
}
check_sha256 "${FILENAME}" "${SHA256}" ||
{
echo "SHA256 mismatch for ${FILENAME} from ${URL} expected sha256 ${SHA256} got $(sha256sum ${FILENAME} | awk '{print $1}')"
exit 1
}
}
}
retroshare-service support Android arm64 build
2019-07-18 05:11:42 -04:00
cArch=""
eABI=""
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
retroshare-service support Android arm64 build
2019-07-18 05:11:42 -04:00
case "${ANDROID_NDK_ARCH}" in
"arm")
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
cArch="${ANDROID_NDK_ARCH}"
eABI="eabi"
retroshare-service support Android arm64 build
2019-07-18 05:11:42 -04:00
;;
"arm64")
cArch="aarch64"
eABI=""
;;
"x86")
cArch="i686"
eABI=""
;;
esac
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
export SYSROOT="${NATIVE_LIBS_TOOLCHAIN_PATH}/sysroot/"
export PREFIX="${SYSROOT}/usr/"
export CC="${NATIVE_LIBS_TOOLCHAIN_PATH}/bin/${cArch}-linux-android${eABI}-clang"
export CXX="${NATIVE_LIBS_TOOLCHAIN_PATH}/bin/${cArch}-linux-android${eABI}-clang++"
export AR="${NATIVE_LIBS_TOOLCHAIN_PATH}/bin/${cArch}-linux-android${eABI}-ar"
export RANLIB="${NATIVE_LIBS_TOOLCHAIN_PATH}/bin/${cArch}-linux-android${eABI}-ranlib"
## More information available at https://android.googlesource.com/platform/ndk/+/ics-mr0/docs/STANDALONE-TOOLCHAIN.html
build_toolchain()
{
Update udp-discovery-cpp and android openssl
2019-08-29 09:50:26 -04:00
echo "build_toolchain()
################################################################################
################################################################################
################################################################################
"
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
rm -rf ${NATIVE_LIBS_TOOLCHAIN_PATH}
${ANDROID_NDK_PATH}/build/tools/make_standalone_toolchain.py --verbose \
--arch ${ANDROID_NDK_ARCH} --install-dir ${NATIVE_LIBS_TOOLCHAIN_PATH} \
--api ${ANDROID_PLATFORM_VER}
retroshare-service now build and runs fine on android (even older ones)
2018-10-05 16:29:49 -04:00
find "${PREFIX}/include/" -not -type d > "${NATIVE_LIBS_TOOLCHAIN_PATH}/deletefiles"
}
## This avoid <cmath> include errors due to -isystem and -I ordering issue
delete_copied_includes()
{
Update udp-discovery-cpp and android openssl
2019-08-29 09:50:26 -04:00
echo "delete_copied_includes()
################################################################################
################################################################################
################################################################################
"
retroshare-service now build and runs fine on android (even older ones)
2018-10-05 16:29:49 -04:00
cat "${NATIVE_LIBS_TOOLCHAIN_PATH}/deletefiles" | while read delFile ; do
rm "$delFile"
done
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
}
## More information available at https://gitlab.com/relan/provisioners/merge_requests/1 and http://stackoverflow.com/a/34032216
install_qt_android()
{
Update udp-discovery-cpp and android openssl
2019-08-29 09:50:26 -04:00
echo "install_qt_android()
################################################################################
################################################################################
################################################################################
"
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
QT_VERSION_CODE=$(echo $QT_VERSION | tr -d .)
QT_INSTALL_PATH=${NATIVE_LIBS_TOOLCHAIN_PATH}/Qt
QT_INSTALLER="qt-unified-linux-x64-3.0.2-online.run"
verified_download $QT_INSTALLER $QT_ANDROID_INSTALLER_SHA256 \
http://master.qt.io/archive/online_installers/3.0/${QT_INSTALLER}
chmod a+x ${QT_INSTALLER}
QT_INSTALLER_SCRIPT="qt_installer_script.js"
cat << EOF > "${QT_INSTALLER_SCRIPT}"
function Controller() {
installer.autoRejectMessageBoxes();
installer.installationFinished.connect(function() {
gui.clickButton(buttons.NextButton);
});
var welcomePage = gui.pageWidgetByObjectName("WelcomePage");
welcomePage.completeChanged.connect(function() {
if (gui.currentPageWidget().objectName == welcomePage.objectName)
gui.clickButton(buttons.NextButton);
});
}
Controller.prototype.WelcomePageCallback = function() {
gui.clickButton(buttons.NextButton);
}
Controller.prototype.CredentialsPageCallback = function() {
gui.clickButton(buttons.NextButton);
}
Controller.prototype.IntroductionPageCallback = function() {
gui.clickButton(buttons.NextButton);
}
Controller.prototype.TargetDirectoryPageCallback = function() {
gui.currentPageWidget().TargetDirectoryLineEdit.setText("$QT_INSTALL_PATH");
gui.clickButton(buttons.NextButton);
}
Controller.prototype.ComponentSelectionPageCallback = function() {
var widget = gui.currentPageWidget();
// You can get these component names by running the installer with the
// --verbose flag. It will then print out a resource tree.
widget.deselectComponent("qt.tools.qtcreator");
widget.deselectComponent("qt.tools.doc");
widget.deselectComponent("qt.tools.examples");
widget.selectComponent("qt.$QT_VERSION_CODE.android_armv7");
gui.clickButton(buttons.NextButton);
}
Controller.prototype.LicenseAgreementPageCallback = function() {
gui.currentPageWidget().AcceptLicenseRadioButton.setChecked(true);
gui.clickButton(buttons.NextButton);
}
Controller.prototype.StartMenuDirectoryPageCallback = function() {
gui.clickButton(buttons.NextButton);
}
Controller.prototype.ReadyForInstallationPageCallback = function() {
gui.clickButton(buttons.NextButton);
}
Controller.prototype.FinishedPageCallback = function() {
var checkBoxForm = gui.currentPageWidget().LaunchQtCreatorCheckBoxForm;
if (checkBoxForm && checkBoxForm.launchQtCreatorCheckBox)
checkBoxForm.launchQtCreatorCheckBox.checked = false;
gui.clickButton(buttons.FinishButton);
}
EOF
QT_QPA_PLATFORM=minimal ./${QT_INSTALLER} --script ${QT_INSTALLER_SCRIPT}
}
## More information available at retroshare://file?name=Android%20Native%20Development%20Kit%20Cookbook.pdf&size=29214468&hash=0123361c1b14366ce36118e82b90faf7c7b1b136
build_bzlib()
{
Update udp-discovery-cpp and android openssl
2019-08-29 09:50:26 -04:00
echo "build_bzlib()
################################################################################
################################################################################
################################################################################
"
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
B_dir="bzip2-${BZIP2_SOURCE_VERSION}"
rm -rf $B_dir
verified_download $B_dir.tar.gz $BZIP2_SOURCE_SHA256 \
Initial work on Broadcast Domain Discovery Discover peers on the same broadcast domain/LAN Implements own node announcement Implements others announcement listening Implements API to get notifiend when other nodes get discovered Implements API to get discovered nodes Add discovered peer locator to rsPeers if it is already friend Yet a bunch of things to do to take full advantage of this new implementation
2019-04-11 20:53:39 -04:00
http://distfiles.gentoo.org/distfiles/bzip2-${BZIP2_SOURCE_VERSION}.tar.gz
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
tar -xf $B_dir.tar.gz
cd $B_dir
sed -i "/^CC=.*/d" Makefile
sed -i "/^AR=.*/d" Makefile
sed -i "/^RANLIB=.*/d" Makefile
sed -i "/^LDFLAGS=.*/d" Makefile
sed -i "s/^all: libbz2.a bzip2 bzip2recover test/all: libbz2.a bzip2 bzip2recover/" Makefile
make -j${HOST_NUM_CPU}
make install PREFIX=${PREFIX}
# sed -i "/^CC=.*/d" Makefile-libbz2_so
# make -f Makefile-libbz2_so -j${HOST_NUM_CPU}
# cp libbz2.so.1.0.6 ${SYSROOT}/usr/lib/libbz2.so
cd ..
}
## More information available at http://doc.qt.io/qt-5/opensslsupport.html
build_openssl()
{
Update udp-discovery-cpp and android openssl
2019-08-29 09:50:26 -04:00
echo "build_openssl()
################################################################################
################################################################################
################################################################################
"
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
B_dir="openssl-${OPENSSL_SOURCE_VERSION}"
rm -rf $B_dir
verified_download $B_dir.tar.gz $OPENSSL_SOURCE_SHA256 \
https://www.openssl.org/source/$B_dir.tar.gz
tar -xf $B_dir.tar.gz
cd $B_dir
## We link openssl statically to avoid android silently sneaking in his own
## version of libssl.so (we noticed this because it had some missing symbol
## that made RS crash), the crash in some android version is only one of the
## possible problems the fact that android insert his own binary libssl.so pose
## non neglegible security concerns.
oBits="32"
[[ ${ANDROID_NDK_ARCH} =~ .*64.* ]] && oBits=64
ANDROID_NDK="${ANDROID_NDK_PATH}" PATH="${SYSROOT}/bin/:${PATH}" \
Update udp-discovery-cpp and android openssl
2019-08-29 09:50:26 -04:00
./Configure linux-generic${oBits} -fPIC --prefix="${PREFIX}" \
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
--openssldir="${SYSROOT}/etc/ssl"
# sed -i 's/LIBNAME=$$i LIBVERSION=$(SHLIB_MAJOR).$(SHLIB_MINOR) \\/LIBNAME=$$i \\/g' Makefile
# sed -i '/LIBCOMPATVERSIONS=";$(SHLIB_VERSION_HISTORY)" \\/d' Makefile
make -j${HOST_NUM_CPU}
make install
retroshare-service now build and runs fine on android (even older ones)
2018-10-05 16:29:49 -04:00
rm -f ${PREFIX}/lib/libssl.so*
rm -f ${PREFIX}/lib/libcrypto.so*
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
cd ..
}
build_sqlite()
{
Update udp-discovery-cpp and android openssl
2019-08-29 09:50:26 -04:00
echo "build_sqlite()
################################################################################
################################################################################
################################################################################
"
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
B_dir="sqlite-autoconf-${SQLITE_SOURCE_VERSION}"
Update Android build script to work with Qt 5.12.4 and NDK 18
2019-07-19 14:01:07 -04:00
rm -rf $B_dir
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
verified_download $B_dir.tar.gz $SQLITE_SOURCE_SHA256 \
https://www.sqlite.org/${SQLITE_SOURCE_YEAR}/$B_dir.tar.gz
tar -xf $B_dir.tar.gz
cd $B_dir
Update Android build script to work with Qt 5.12.4 and NDK 18
2019-07-19 14:01:07 -04:00
./configure --with-pic --prefix="${PREFIX}" --host=${cArch}-linux
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
make -j${HOST_NUM_CPU}
make install
rm -f ${PREFIX}/lib/libsqlite3.so*
# ${CC} -shared -o libsqlite3.so -fPIC sqlite3.o -ldl
# cp libsqlite3.so "${SYSROOT}/usr/lib"
cd ..
}
build_sqlcipher()
{
Update udp-discovery-cpp and android openssl
2019-08-29 09:50:26 -04:00
echo "build_sqlcipher()
################################################################################
################################################################################
################################################################################
"
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
B_dir="sqlcipher-${SQLCIPHER_SOURCE_VERSION}"
rm -rf $B_dir
T_file="${B_dir}.tar.gz"
verified_download $T_file $SQLCIPHER_SOURCE_SHA256 \
https://github.com/sqlcipher/sqlcipher/archive/v${SQLCIPHER_SOURCE_VERSION}.tar.gz
tar -xf $T_file
cd $B_dir
Improve SQLCipher/SQLite support When compiled with SQLCipher it is now capable of handling databases created by SQLite-only versions Add support for SQLCipher on Android arm64
2019-08-31 10:22:24 -04:00
case "${ANDROID_NDK_ARCH}" in
"arm64")
# SQLCipher config.sub is outdated and doesn't recognize newer architectures
rm config.sub
autoreconf --verbose --install --force
automake --add-missing --copy --force-missing
;;
esac
Update Android build script to work with Qt 5.12.4 and NDK 18
2019-07-19 14:01:07 -04:00
./configure --with-pic --build=$(sh ./config.guess) \
retroshare-service support Android arm64 build
2019-07-18 05:11:42 -04:00
--host=${cArch}-linux \
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
--prefix="${PREFIX}" --with-sysroot="${SYSROOT}" \
--enable-tempstore=yes \
--disable-tcl --disable-shared \
CFLAGS="-DSQLITE_HAS_CODEC" LDFLAGS="${PREFIX}/lib/libcrypto.a"
make -j${HOST_NUM_CPU}
make install
cd ..
}
build_libupnp()
{
Update udp-discovery-cpp and android openssl
2019-08-29 09:50:26 -04:00
echo "build_libupnp()
################################################################################
################################################################################
################################################################################
"
Fix compilation with libupnp-1.8.x
2019-04-24 17:36:40 -04:00
B_dir="pupnp-release-${LIBUPNP_SOURCE_VERSION}"
B_ext=".tar.gz"
B_file="${B_dir}${B_ext}"
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
rm -rf $B_dir
Fix compilation with libupnp-1.8.x
2019-04-24 17:36:40 -04:00
verified_download $B_file $LIBUPNP_SOURCE_SHA256 \
https://github.com/mrjimenez/pupnp/archive/release-${LIBUPNP_SOURCE_VERSION}${B_ext}
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
Fix compilation with libupnp-1.8.x
2019-04-24 17:36:40 -04:00
tar -xf $B_file
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
cd $B_dir
Fix compilation with libupnp-1.8.x
2019-04-24 17:36:40 -04:00
./bootstrap
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
## liupnp must be configured as static library because if not the linker will
## look for libthreadutils.so.6 at runtime that cannot be packaged on android
## as it supports only libname.so format for libraries, thus resulting in a
## crash at startup.
Update Android build script to work with Qt 5.12.4 and NDK 18
2019-07-19 14:01:07 -04:00
./configure --with-pic --enable-static --disable-shared --disable-samples \
Fix compilation with libupnp-1.8.x
2019-04-24 17:36:40 -04:00
--disable-largefile \
retroshare-service support Android arm64 build
2019-07-18 05:11:42 -04:00
--prefix="${PREFIX}" --host=${cArch}-linux
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
make -j${HOST_NUM_CPU}
make install
cd ..
}
build_rapidjson()
{
Update udp-discovery-cpp and android openssl
2019-08-29 09:50:26 -04:00
echo "build_rapidjson()
################################################################################
################################################################################
################################################################################
"
retroshare-service deep search support for Android
2018-10-05 19:23:08 -04:00
B_dir="rapidjson-${RAPIDJSON_SOURCE_VERSION}"
D_file="${B_dir}.tar.gz"
verified_download $D_file $RAPIDJSON_SOURCE_SHA256 \
https://github.com/Tencent/rapidjson/archive/v${RAPIDJSON_SOURCE_VERSION}.tar.gz
tar -xf $D_file
cp -r "${B_dir}/include/rapidjson/" "${PREFIX}/include/rapidjson"
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
}
build_restbed()
{
Update udp-discovery-cpp and android openssl
2019-08-29 09:50:26 -04:00
echo "build_restbed()
################################################################################
################################################################################
################################################################################
"
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
[ -d restbed ] || git clone --depth=2000 https://github.com/Corvusoft/restbed.git
cd restbed
Update udp-discovery-cpp and android openssl
2019-08-29 09:50:26 -04:00
# git fetch --tags
# git checkout tags/${RESTBED_SOURCE_VERSION}
git checkout ${RESTBED_SOURCE_VERSION}
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
git submodule update --init dependency/asio
git submodule update --init dependency/catch
git submodule update --init dependency/kashmir
cd ..
rm -rf restbed-build; mkdir restbed-build ; cd restbed-build
Update Android build script to work with Qt 5.12.4 and NDK 18
2019-07-19 14:01:07 -04:00
cmake \
Android reduce toolchain cross-compilation time No need to build restbed tests when cross-compiling the toolchain
2019-11-05 04:22:25 -05:00
-DCMAKE_POSITION_INDEPENDENT_CODE=ON BUILD_TESTS=OFF \
Update Android build script to work with Qt 5.12.4 and NDK 18
2019-07-19 14:01:07 -04:00
-DBUILD_SSL=OFF -DCMAKE_INSTALL_PREFIX="${PREFIX}" -B. -H../restbed
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
make -j${HOST_NUM_CPU}
make install
retroshare-service now build and runs fine on android (even older ones)
2018-10-05 16:29:49 -04:00
cp "${PREFIX}/library/librestbed.a" "${PREFIX}/lib/"
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
cd ..
}
Initial work on Broadcast Domain Discovery Discover peers on the same broadcast domain/LAN Implements own node announcement Implements others announcement listening Implements API to get notifiend when other nodes get discovered Implements API to get discovered nodes Add discovered peer locator to rsPeers if it is already friend Yet a bunch of things to do to take full advantage of this new implementation
2019-04-11 20:53:39 -04:00
build_udp-discovery-cpp()
{
Update udp-discovery-cpp and android openssl
2019-08-29 09:50:26 -04:00
echo "build_udp-discovery-cpp()
################################################################################
################################################################################
################################################################################
"
Initial work on Broadcast Domain Discovery Discover peers on the same broadcast domain/LAN Implements own node announcement Implements others announcement listening Implements API to get notifiend when other nodes get discovered Implements API to get discovered nodes Add discovered peer locator to rsPeers if it is already friend Yet a bunch of things to do to take full advantage of this new implementation
2019-04-11 20:53:39 -04:00
S_dir="udp-discovery-cpp"
[ -d $S_dir ] || git clone $UDP_DISCOVERY_CPP_SOURCE $S_dir
cd $S_dir
git checkout $UDP_DISCOVERY_CPP_VERSION
cd ..
B_dir="udp-discovery-cpp-build"
rm -rf ${B_dir}; mkdir ${B_dir}; cd ${B_dir}
Update Android build script to work with Qt 5.12.4 and NDK 18
2019-07-19 14:01:07 -04:00
cmake \
-DCMAKE_POSITION_INDEPENDENT_CODE=ON \
-DCMAKE_INSTALL_PREFIX="${PREFIX}" -B. -H../udp-discovery-cpp
Initial work on Broadcast Domain Discovery Discover peers on the same broadcast domain/LAN Implements own node announcement Implements others announcement listening Implements API to get notifiend when other nodes get discovered Implements API to get discovered nodes Add discovered peer locator to rsPeers if it is already friend Yet a bunch of things to do to take full advantage of this new implementation
2019-04-11 20:53:39 -04:00
make -j${HOST_NUM_CPU}
cp libudp-discovery.a "${PREFIX}/lib/"
cp ../$S_dir/*.hpp "${PREFIX}/include/"
cd ..
}
retroshare-service deep search support for Android
2018-10-05 19:23:08 -04:00
build_xapian()
{
Update udp-discovery-cpp and android openssl
2019-08-29 09:50:26 -04:00
echo "build_xapian()
################################################################################
################################################################################
################################################################################
"
retroshare-service deep search support for Android
2018-10-05 19:23:08 -04:00
B_dir="xapian-core-${XAPIAN_SOURCE_VERSION}"
D_file="$B_dir.tar.xz"
verified_download $D_file $XAPIAN_SOURCE_SHA256 \
https://oligarchy.co.uk/xapian/${XAPIAN_SOURCE_VERSION}/$D_file
rm -rf $B_dir
tar -xf $D_file
cd $B_dir
B_endiannes_detection_failure_workaround="ac_cv_c_bigendian=no"
B_large_file=""
[ "${ANDROID_PLATFORM_VER}" -lt "24" ] && B_large_file="--disable-largefile"
./configure ${B_endiannes_detection_failure_workaround} ${B_large_file} \
Update Android build script to work with Qt 5.12.4 and NDK 18
2019-07-19 14:01:07 -04:00
--with-pic \
retroshare-service deep search support for Android
2018-10-05 19:23:08 -04:00
--disable-backend-inmemory --disable-backend-remote \
--disable--backend-chert --enable-backend-glass \
retroshare-service support Android arm64 build
2019-07-18 05:11:42 -04:00
--host=${cArch}-linux --enable-static --disable-shared \
retroshare-service deep search support for Android
2018-10-05 19:23:08 -04:00
--prefix="${PREFIX}" --with-sysroot="${SYSROOT}"
make -j${HOST_NUM_CPU}
make install
}
Add support to build with miniupnpc on Android Necessary to workaroud issues: https://github.com/RetroShare/RetroShare/issues/1649 https://github.com/mrjimenez/pupnp/issues/119
2019-09-28 07:54:16 -04:00
build_miniupnpc()
{
echo "build_miniupnpc()
################################################################################
################################################################################
################################################################################
"
S_dir="miniupnpc-${MINIUPNPC_SOURCE_VERSION}"
B_dir="miniupnpc-${MINIUPNPC_SOURCE_VERSION}-build"
D_file="$S_dir.tar.gz"
verified_download $D_file $MINIUPNPC_SOURCE_SHA256 \
http://miniupnp.free.fr/files/${D_file}
rm -rf $S_dir $B_dir
tar -xf $D_file
mkdir $B_dir
cd $B_dir
cmake \
-DUPNPC_BUILD_STATIC=TRUE \
-DUPNPC_BUILD_SHARED=FALSE \
-DUPNPC_BUILD_TESTS=FALSE \
-DUPNPC_BUILD_SAMPLE=FALSE \
-DCMAKE_POSITION_INDEPENDENT_CODE=ON \
-DCMAKE_INSTALL_PREFIX="${PREFIX}" -B. -S../$S_dir
make -j${HOST_NUM_CPU}
make install
}
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
build_toolchain
[ "${INSTALL_QT_ANDROID}X" != "trueX" ] || install_qt_android
build_bzlib
build_openssl
build_sqlite
build_sqlcipher
build_libupnp
build_rapidjson
retroshare-service now build and runs fine on android (even older ones)
2018-10-05 16:29:49 -04:00
build_restbed
Initial work on Broadcast Domain Discovery Discover peers on the same broadcast domain/LAN Implements own node announcement Implements others announcement listening Implements API to get notifiend when other nodes get discovered Implements API to get discovered nodes Add discovered peer locator to rsPeers if it is already friend Yet a bunch of things to do to take full advantage of this new implementation
2019-04-11 20:53:39 -04:00
build_udp-discovery-cpp
retroshare-service deep search support for Android
2018-10-05 19:23:08 -04:00
build_xapian
Add support to build with miniupnpc on Android Necessary to workaroud issues: https://github.com/RetroShare/RetroShare/issues/1649 https://github.com/mrjimenez/pupnp/issues/119
2019-09-28 07:54:16 -04:00
build_miniupnpc
retroshare-service now build and runs fine on android (even older ones)
2018-10-05 16:29:49 -04:00
delete_copied_includes
Initial work on a RetroShare cross-platform service This doesn't need any interacion of the user at startup, unlike retroshare-nogui which requires the user to login on the shell this doesn't even need a TTY. At startup this just parse command line, read the PGP keyring, look for available locations, and start listening for JSON API requests. Another difference with retroshare-nogui is that this is capable to generate/import PGP identities, generate locations, and in general anything possible through the RetroShare API. retroshare-service is suitable also to run it as a system service, even in very constrained systems such as Android ot a Docker container. retroshare-service drop support for libresapi so only the new JSON API is exposed, it will completely obsolete retroshare-android-service once retroshare-qml-app is ported to the new JSON API.
2018-09-28 18:15:10 -04:00
echo NATIVE_LIBS_TOOLCHAIN_PATH=${NATIVE_LIBS_TOOLCHAIN_PATH}
Reference in New Issue Copy Permalink