nativescript/android-v8

Contains the Google's V8 build used in android runtime.

NativeScript empowers you to access native APIs from JavaScript directly. Currently iOS, Android, and visionOS runtimes are provided for rich mobile development across a variety of diverse use cases.

Contribute

1. Setup your local development environment

2. Clone to contribute:

$ git clone https://github.com/NativeScript/NativeScript.git
$ cd NativeScript

# setup workspace for development
$ npm run setup

# list all available commands to run
$ npm start

We love you and your pull requests 🤗. Please follow our contributing guide and see our code of governance to become as involved as you want to be.

@nativescript/*

• @nativescript/core Singular primitives offering an easy-to-use API surface for diverse iOS/visionOS/Android APIs implemented with NativeScript.
• @nativescript/types Types for both iOS/Android below wrapped up as a convenience. Most commonly used.
• @nativescript/types-ios Types for iOS.
• @nativescript/types-android Types for Android.
• @nativescript/types-minimal A very minimal set of types for only the latest Android and iOS sdks. Most commonly used to optimize Web-based IDE's which auto load all type declarations from node_modules.
• @nativescript/ui-mobile-base UI mobile base native classes used by core.
• @nativescript/webpack Webpack build utilities and configs used by NativeScript apps.

Quick Links

• NativeScript Home
• NativeScript Tutorials
• NativeScript documentation
• JavaScript starter: https://nativescript.new/javascript
• TypeScript starter: https://nativescript.new/typescript
• Angular starter: https://nativescript.new/angular
• Vue starter: https://nativescript.new/vue
• Svelte starter: https://nativescript.new/svelte
• React starter: https://nativescript.new/react
• NativeScript on Twitter
• NativeScript on Discord
• NativeScript on Stack Overflow

Other source repos

Outside the source centralized in this repo, NativeScript consists of a few other source repos. Here are the major ones:

• iOS and visionOS Runtime Empowers JavaScript code to be executed on iOS and visionOS devices written in a mix of C++, Objective-C, and Swift.
• Android Runtime Empowers JavaScript code to be executed on Android devices written in a mix of C++, Java and Kotlin.
• CLI Command-line interface empowering you to create, build, and run apps using NativeScript.
• Docs Documentation available at http://docs.nativescript.org/ written in Markdown.
• Plugins Various TSC managed plugins. Also a good reference is the plugin marketplace with several additional plugins.
• Firebase Modular Firebase 🔥 implementation for supported platforms.
• ML Kit Google's ML Kit SDKs for supported platforms.
• Payments In-App Purchase, Subscriptions, Google Pay and Apple Pay.
• Artwork Want to use our logo or colors? Feel free to use any of our ready-to-use media material.

Copyright notice

Copyright OpenJS Foundation and NativeScript contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

The OpenJS Foundation | Terms of Use | Privacy Policy | OpenJS Foundation Bylaws | Trademark Policy | Trademark List | Cookie Policy

Made with ❤️

android-v8's Issues

5.1.xtimeline?

@jasssonpet - are we really thinking of jumping to the Canary v8 Engine? I'm all for running bleeding edge; but I can't imagine that running canary for my released application as this is the least tested versions of the v8's and if you are going to run canary; why are we picking .150 instead of 300ish you are missing about 150 potential fixes (& new bugs ).

So I guess the question is what is the time line for this engine being released for android; or are you going to wait until 5.1 gets moved into the beta channel and then upgrade to the current 5.1 at that point?

Could not find Ninja in the third_party of the current project

./scripts/setup-build.sh android
37>WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin" "2c2138e811487b13020eb331482fb991fd399d4e" "--no-tags"' in /home/11/android-v8/v8/third_party/requests failed; will retry after a short nap...
37>WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin" "2c2138e811487b13020eb331482fb991fd399d4e" "--no-tags"' in /home/11/android-v8/v8/third_party/requests failed; will retry after a short nap...
Syncing projects: 100% (42/42) v8/third_party/requests
v8/third_party/requests (ERROR)

[0:00:07] Started.
[0:00:07] Finished running: git rev-list -n 1 HEAD
[0:00:07] Finished running: git rev-parse --abbrev-ref=strict HEAD
error: RPC failed; HTTP 400 curl 22 The requested URL returned error: 400
[0:00:09] fatal: the remote end hung up unexpectedly
[0:00:12] error: RPC failed; HTTP 400 curl 22 The requested URL returned error: 400
[0:00:12] fatal: the remote end hung up unexpectedly

./scripts/build.android.sh
Done. Made 231 targets from 115 files in 219ms
Done. Made 231 targets from 116 files in 241ms
Done. Made 230 targets from 115 files in 226ms
Done. Made 230 targets from 116 files in 236ms
depot_tools/ninja.py: Could not find Ninja in the third_party of the current project, nor in your PATH.
Please take one of the following actions to install Ninja:

• If your project has DEPS, add a CIPD Ninja dependency to DEPS.
• Otherwise, add Ninja to your PATH after depot_tools.

*.o: No such file or directory

When i follow the md and build the v8 on macOS, i have this issue(as follow) ...

build finished in 1776 seconds /Documents/2nd_Project/dev/android-ndk-r20/toolchains/arm-linux-androideabi-4.9/prebuilt/darwin-x86_64/arm-linux-androideabi/bin/ar: creating ./dist//arm-release/libv8.a /Documents/2nd_Project/dev/android-ndk-r20/toolchains/arm-linux-androideabi-4.9/prebuilt/darwin-x86_64/arm-linux-androideabi/bin/ar: outgn/arm-release/obj/buildtools/third_party/libc++/libc++/*.o: No such file or directory
In the end i check the outgn dir and found mksnapshot under dist dir and no other items(.a static library) at all.
What did i missing? Thanks.

undefined reference to 'v8::platform::NewDefaultPlatform

I followed the README.md and build v8 successfully on linux, But when i added libv8.a and all the needed header to my own project, i have this issue(as follow):

JNI_OnLoad: error: undefined reference to 'v8::platform::NewDefaultPlatform(int, v8::platform::IdleTaskSupport, v8::platform::InProcessStackDumping, std::__ndkCr::unique_ptr<v8::TracingController, std::__ndkCr::default_deletev8::TracingController >)'
clang++: error: linker command failed with exit code 1 (use -v to see invocation)

Merge v4 branch back into Master.

The Real release version should be on master. The really outdated version is pointless on master.

Build Instructions?

Are their any specific build instructions for it for the NativeScript versions; or do we just follow the Android building instructions @ googles site. Which version of the Android runtimes are you building into the Android-runtimes?

These are the current valid v8 runtimes:
android_ia32
android_x64
android_arm
android_arm64
android_mipsel
android_x87

I assume it is ia32 & arm?
Any specific flags?