/dports/www/firefox-legacy/firefox-52.8.0esr/mobile/android/docs/ |
H A D | bouncer.rst | 9 Fennec-like "bouncer" APK that redirects (bounces) a potential Fennec user to the marketplace of 11 APK. 13 The real APK should install seamlessly over top of the bouncer APK. Care is taken to keep the 14 bouncer and application APK <permission> manifest definitions identical, and to have the bouncer APK 15 <activity> manifest definitions look similar to the application APK <activity> manifest definitions. 18 redirecting to the marketplace. The application APK recognizes the installed distribution and 21 The motivation is to allow partners to pre-install the very small bouncer APK on shipping devices 22 and to have a smooth path to upgrade to the full application APK, with a partner-specific 28 To build the bouncer APK, define ``MOZ_ANDROID_PACKAGE_INSTALL_BOUNCER``. To pack a distribution 29 into the bouncer APK (and *not* into the application APK), add a line like:: [all …]
|
/dports/x11-clocks/xdaliclock/xdaliclock-2.44/android/ |
H A D | Makefile | 17 APK = $(TARGET)-$(VERSION_NUM).apk macro 122 mv ../$(TARGET)/app/build/outputs/apk/app-release-unsigned.apk ./$(APK); \ 124 $(APK) $(TARGET2); \ 133 mv $(APK) ../$(APK); \ 135 $(ZIPALIGN) -v 4 $(APK) $(APK).aligned; \ 136 mv $(APK).aligned ../$(APK) ; \ 140 mv $(APK) ../archive/"$(APK)" ; \
|
/dports/x11-clocks/xdaliclock/xdaliclock-2.44/ |
H A D | Makefile | 167 APK="$$HEAD3.apk" ; \ 179 if [ ! -f archive/$$APK ]; then \ 180 echo "archive/$$APK does not exist! Did you forget to \`make apk'?" ; \ 185 chmod a-w archive/$$APK ; \ 203 if [ -f $$DEST/$$APK ]; then \ 204 /bin/echo -n "WARNING: $$DEST/$$APK already exists! Overwrite? "; \ 219 cp -p archive/$$APK $$DEST/$$APK ; \ 220 chmod u+w $$DEST/$$APK ; \ 254 git add index.html updates.xml $$TAR $$DMG $$APK ; \
|
/dports/www/chromium-legacy/chromium-88.0.4324.182/tools/binary_size/libsupersize/testdata/ |
H A D | Archive_Apk.golden | 141 .dex@0(size_without_padding=1792,padding=0,full_name=org,object_path=$APK/org,source_path=,flags={}… 142 .dex@0(size_without_padding=975347,padding=0,full_name=org.chromium,object_path=$APK/org/chromium,s… 143 .dex@0(size_without_padding=44714,padding=0,full_name=org.chromium.chrome,object_path=$APK/org/chro… 144 …dding=2522400,padding=0,full_name=org.chromium.chrome.browser,object_path=$APK/org/chromium/chrome… 145 …86,padding=0,full_name=org.chromium.chrome.browser.compositor,object_path=$APK/org/chromium/chrome… 146 …ng=0,full_name=org.chromium.chrome.browser.compositor.layouts,object_path=$APK/org/chromium/chrome… 147 …ull_name=org.chromium.chrome.browser.compositor.layouts.phone,object_path=$APK/org/chromium/chrome… 148 …me=org.chromium.chrome.browser.compositor.layouts.phone.stack,object_path=$APK/org/chromium/chrome… 220 …rowser.compositor.layouts.phone.stack.StackAnimationLandscape,object_path=$APK/org/chromium/chrome… 557 …padding=4194304,padding=0,full_name=smalltest.so,object_path=,source_path=$APK/smalltest.so,flags=… [all …]
|
H A D | Archive_MinimalApks.golden | 142 .dex@0(size_without_padding=1792,padding=0,full_name=org,object_path=$APK/org,source_path=,flags={}… 143 .dex@0(size_without_padding=975347,padding=0,full_name=org.chromium,object_path=$APK/org/chromium,s… 144 .dex@0(size_without_padding=44714,padding=0,full_name=org.chromium.chrome,object_path=$APK/org/chro… 145 …dding=2522400,padding=0,full_name=org.chromium.chrome.browser,object_path=$APK/org/chromium/chrome… 146 …86,padding=0,full_name=org.chromium.chrome.browser.compositor,object_path=$APK/org/chromium/chrome… 147 …ng=0,full_name=org.chromium.chrome.browser.compositor.layouts,object_path=$APK/org/chromium/chrome… 148 …ull_name=org.chromium.chrome.browser.compositor.layouts.phone,object_path=$APK/org/chromium/chrome… 149 …me=org.chromium.chrome.browser.compositor.layouts.phone.stack,object_path=$APK/org/chromium/chrome… 221 …rowser.compositor.layouts.phone.stack.StackAnimationLandscape,object_path=$APK/org/chromium/chrome… 558 …padding=4194304,padding=0,full_name=smalltest.so,object_path=,source_path=$APK/smalltest.so,flags=… [all …]
|
/dports/devel/axmldec/axmldec-1.2.0/ |
H A D | README.md | 6 [`AndroidManifest.xml`][Android App Manifest] in an [APK file][APK] is binary 9 decoded `AndroidManifest.xml` directly from an APK file. 13 Tools such as [Apktool] are designed to process the whole APK file including 16 many APK files just to get the XML information. In contrast, axmldec is 59 ### 3.2 Decoding `AndroidManifest.xml` in an APK File 61 If an APK file is specified, axmldec automatically extracts and decodes 71 the package name from an APK file using xmllint: 90 You can specify `-DENABLE_APK_LOADING=NO` to disable APK loading. In this 106 [APK]: https://en.wikipedia.org/wiki/Android_application_package
|
/dports/www/chromium-legacy/chromium-88.0.4324.182/testing/android/docs/ |
H A D | components_for_testing.md | 8 - the test APK instruments the app APK 19 > the test APK. 22 described above: app code is in one APK (the _APK under test_), test code is 23 in another APK (the _test APK_), and auxiliary code, when necessary, is in 28 able to access code defined in the app APK's .dex file(s). Test components, 30 test APK. While test components referencing app code will build without issue, 86 using a support APK or using sharedUserIds. 88 ### Use a support APK 92 support APK runs in the same package or process as the test or app code. 125 The support APK must depend on this target. The target containing your test [all …]
|
/dports/deskutils/syncthingtray/qtutilities/cmake/modules/ |
H A D | AndroidApk.cmake | 52 CACHE STRING "user visible name for the APK") 100 # make subdirectory to store build artefacts for APK 124 CACHE STRING "toolchain version for making APK file") 158 CACHE STRING "path to standard library for making APK file") 250 CACHE STRING "name of the sysroot for making APK file") 333 # add rules to make APK 391 COMMENT "Preparing build dir for Android APK" 408 COMMENT "Android APK" 415 # add install target for APK 434 # add deploy target for APK [all …]
|
/dports/www/chromium-legacy/chromium-88.0.4324.182/android_webview/docs/ |
H A D | how-does-loading-work.md | 18 APK in L. All the core framework code is automatically present in every app at 24 In N, we made it possible for the Chrome APK to also provide a WebView 29 you can assume all references to "the APK" or "the WebView APK" refer to the 35 The APK contains three categories of "stuff": compiled Java code (one or more 78 versions of the APK. 81 process would always be using the currently installed APK to provide its 104 as the replacement APK will have been installed to a new location by 117 the same code that is used when the framework loads an APK "normally". 131 load the class in the WebView APK which implements the framework's 244 main WebView APK. It will not be found if it's in a split APK or library APK. [all …]
|
H A D | channels.md | 3 Since the introduction of WebView as an updatable APK in Android L, WebView has 28 APK with the highest `versionCode` among eligible tracks. 30 Google publishes an APK of Android System WebView to the beta track based on the 57 receive the beta APK (Play Store delivers the APK with the higher `versionCode` 58 value) even if a stable APK from the same build is available (such as when we 66 WebView stable APK to Standalone WebView beta (since they share the same package 71 For Android versions N - P, WebView is built as a part of the Chrome APK. Since 93 only APK of this package that gets published to the beta track is Standalone
|
H A D | aosp-system-integration.md | 15 (Lollipop) the WebView implementation has been provided by a separate APK. This 16 APK is preinstalled on the device and can be updated in the same ways as an 76 The standalone WebView is a single APK which contains the entire WebView 77 implementation. The prebuilt APK provided in AOSP is a standalone WebView APK. 91 Monochrome is a single APK which contains both the entire WebView 94 much smaller than having a separate WebView APK and browser APK. 107 Trichrome is composed of three APK/AABs: 159 of the WebView APK, or about a class called 387 packageName (required): The Android package name of the APK. 411 to the private key used to sign the APK, encoded as base64. --> [all …]
|
/dports/lang/spidermonkey60/firefox-60.9.0/mobile/android/tests/browser/robocop/ |
H A D | README.rst | 20 To deploy the robocop APK to your device and start the robocop test 30 robocop APK built by ``build/mobile/robocop``. If you modify Java files 31 in ``mobile/android/tests/browser/robocop``, you need to rebuild the robocop APK 38 APK -- these changes are always 'live', since they are served by the 41 ``mach package`` does build and sign a robocop APK, but ``mach 42 robocop`` does not use it. (This signed APK is used to test
|
/dports/www/firefox-legacy/firefox-52.8.0esr/mobile/android/tests/browser/robocop/ |
H A D | README.rst | 20 To deploy the robocop APK to your device and start the robocop test 30 robocop APK built by ``build/mobile/robocop``. If you modify Java files 31 in ``mobile/android/tests/browser/robocop``, you need to rebuild the robocop APK 38 APK -- these changes are always 'live', since they are served by the 41 ``mach package`` does build and sign a robocop APK, but ``mach 42 robocop`` does not use it. (This signed APK is used to test
|
/dports/www/chromium-legacy/chromium-88.0.4324.182/chrome/browser/android/examples/partner_browser_customizations_provider/ |
H A D | README | 1 An example app for partner customizations. When this APK is installed, Chrome 16 * Build an example customizations content provider APK. 19 * [LEGACY non-GN] Build an example customizations content provider APK. 23 * Buid the APK 28 * Install the compiled APK.
|
/dports/www/chromium-legacy/chromium-88.0.4324.182/third_party/skia/tools/skqp/ |
H A D | test_apk.sh | 8 APK="$1" 11 if ! [ -f "$APK" ]; then 38 sh "$THIS/run_apk.sh" "$APK" "$TDIR"
|
H A D | run_apk.sh | 16 APK="$1" 19 printf '\n\nAPK = "%s"\nDST = "%s"\n\n' "$APK" "$DST" 29 adb install "$APK" || exit 1
|
/dports/www/qt5-webengine/qtwebengine-everywhere-src-5.15.2/src/3rdparty/chromium/third_party/skia/tools/skqp/ |
H A D | test_apk.sh | 8 APK="$1" 11 if ! [ -f "$APK" ]; then 38 sh "$THIS/run_apk.sh" "$APK" "$TDIR"
|
H A D | run_apk.sh | 16 APK="$1" 19 printf '\n\nAPK = "%s"\nDST = "%s"\n\n' "$APK" "$DST" 29 adb install "$APK" || exit 1
|
/dports/lang/spidermonkey60/firefox-60.9.0/taskcluster/docs/ |
H A D | pushapk.rst | 1 APK publication 20 …xtremely important because Google Play is vigilant about APK signatures and will refuse any APK fo… 22 …ectures. We have already had one big crash on these devices because an x86 APK was overseeded by i… 26 * they ensure the APK buildIds (called "version code") are higher than the last ones they have on f… 27 * they check whether the APKs are zipaligned (meaning, the APK archive has been optimized). 38 …s to pushapkscript. The latter validates APKs signatures, makes sure every APK architecture is pre…
|
/dports/games/emptyepsilon/EmptyEpsilon-EE-2021.06.23/cmake/ |
H A D | android.toolchain | 1 # Android APK build toolchain file. 22 # Signing key to use to sign the APK. You can generate one with: 24 set(ANDROID_SIGN_KEY_NAME "Android" CACHE STRING "Which key to use to sign the final APK for androi… 135 set(APK "${APK_ALIGNED}.unaligned") 141 OUTPUT "${APK}" 142 …Manifest.xml" -S "${CMAKE_CURRENT_SOURCE_DIR}/android/res" -I "${ANDROID_PLATFORM_JAR}" -F "${APK}" 143 COMMAND "${AAPT}" ARGS add "${APK}" 153 COMMAND "${AAPT}" ARGS add "${APK}" ${ASSETS} 154 …g SHA1withRSA -digestalg SHA1 -storepass "${ANDROID_SIGN_KEY_PASSWORD}" "${APK}" "${ANDROID_SIGN_K… 161 COMMAND "${ZIPALIGN}" ARGS 4 "${APK}" "${APK_ALIGNED}" [all …]
|
/dports/audio/kid3-kf5/kid3-3.8.6/android/qt-android-cmake/ |
H A D | readme.md | 37 …to call the ```add_qt_android_apk``` macro to create a new target that will create the Android APK. 46 And that's it. Your APK can now be created by running "make" (or "cmake --build ." if you don't wan… 57 **IMPORTANT** ```JAVA_HOME``` must be defined when you compile the APK too. 86 The first two arguments of the macro are the name of the APK target to be created, and the target i… 88 …ation of these arguments is valid, so that you can customize the generated APK according to your o… 134 …nerated from the ```AndroidManifest.xml.in``` template and automatically used for building the APK. 146 The path to a keystore file and an alias, for signing the APK. If not provided, the APK won't be si… 171 A list of dependencies (libraries) to be included into the APK. All the dependencies of the applica… 183 If this option is given, the created APK will be deployed to a connected Android device. By default…
|
/dports/audio/kid3-qt5/kid3-3.8.6/android/qt-android-cmake/ |
H A D | readme.md | 37 …to call the ```add_qt_android_apk``` macro to create a new target that will create the Android APK. 46 And that's it. Your APK can now be created by running "make" (or "cmake --build ." if you don't wan… 57 **IMPORTANT** ```JAVA_HOME``` must be defined when you compile the APK too. 86 The first two arguments of the macro are the name of the APK target to be created, and the target i… 88 …ation of these arguments is valid, so that you can customize the generated APK according to your o… 134 …nerated from the ```AndroidManifest.xml.in``` template and automatically used for building the APK. 146 The path to a keystore file and an alias, for signing the APK. If not provided, the APK won't be si… 171 A list of dependencies (libraries) to be included into the APK. All the dependencies of the applica… 183 If this option is given, the created APK will be deployed to a connected Android device. By default…
|
/dports/devel/corrade/corrade-2020.06/toolchains/modules/ |
H A D | UseAndroid.cmake | 15 # install the APK directly from the IDE / command-line. 23 # the APK. 90 COMMENT "Copying stripped ${target} for an APK build" 108 # Align the APK 114 # Sign the APK 121 # Make the APK dependency of an "always build" target so it gets built by 132 # projects that only ever have just one APK output -- have it as an option?
|
/dports/graphics/magnum-examples/magnum-examples-2019.10/toolchains/modules/ |
H A D | UseAndroid.cmake | 15 # install the APK directly from the IDE / command-line. 23 # the APK. 88 COMMENT "Copying stripped ${target} for an APK build" 106 # Align the APK 112 # Sign the APK 119 # Make the APK dependency of an "always build" target so it gets built by 130 # projects that only ever have just one APK output -- have it as an option?
|
/dports/graphics/magnum-extras/magnum-extras-2019.10/toolchains/modules/ |
H A D | UseAndroid.cmake | 15 # install the APK directly from the IDE / command-line. 23 # the APK. 88 COMMENT "Copying stripped ${target} for an APK build" 106 # Align the APK 112 # Sign the APK 119 # Make the APK dependency of an "always build" target so it gets built by 130 # projects that only ever have just one APK output -- have it as an option?
|