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
- fix install.alpine.packages.sh chmod +x
- refactor nodejs.py sub-commands (git-CLI style)
- add j2v8-cli convenience scripts with command aliases (for win32/linux/macos)
- do not run NodeJsTest when native lib was not compiled with node features included
- add check in CMake node js lib scripts if all njs lib files exist, exit with error if any is missing
- add node 7.9.0 patch file (works for linux, but not windows currently)
- j2v8jni build-step is now called j2v8cpp
- j2v8jni is a new build-step using javah to regenerate J2V8 JNI header files
- j2v8jni build-step is skipped if the required V8.class file does not yet exist
- implement basic unit-testing for build-system
- centralize maven build-steps logic and also just run maven pre-build actions once per build-process
(e.g. copy native J2V8 libs to the Java directories)
Copy file name to clipboardexpand all lines: BUILDING.md
+22-5
Original file line number
Diff line number
Diff line change
@@ -41,6 +41,9 @@ Override build-steps ? (leave empty to run pre-configured steps): j2v8
41
41
42
42
The J2V8 build-system performs several build steps in a fixed order to produce the final J2V8 packages for usage on the designated target platforms. What follows is a short summary for what each of the executed build-steps does and what output artifacts are produced by each step.
Generate the JNI glue header file from the native method definitions of the Java `V8` class.
85
+
86
+
__Inputs__:
87
+
- Java V8.class file
88
+
-`./target/classes/com/eclipsesource/v8/V8.class`
89
+
90
+
__Artifacts:__
91
+
- J2V8 C++ JNI header file
92
+
-`./jni/com_eclipsesource_v8_V8Impl.h`
93
+
---
94
+
## C++
79
95
80
-
Compile and link the J2V8 C++ shared libraries (.so/.dylib/.dll), which provide the JNI bridge to interop with the C++ code of Node.js / V8.
96
+
Compile and link the J2V8 native shared libraries (.so/.dylib/.dll), which contain the C++ JNI bridge code to interop with the embedded Node.js / V8 parts.
81
97
82
98
__Inputs__:
83
99
- CMake generated Makefiles / IDE Project-files
100
+
- Node.js / V8 static link libraries & C++ header files
Copy file name to clipboardexpand all lines: build_system/build_constants.py
+2-1
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,8 @@
19
19
CLIStep(c.build_node_js, " Builds the Node.js & V8 dependency artifacts that are later linked into the J2V8 native bridge code.\n"+
20
20
" (only works if the Node.js source was checked out into the J2V8 ./node directory)"),
21
21
CLIStep(c.build_j2v8_cmake, " Uses CMake to generate the native Makefiles / IDE project files to later build the J2V8 C++ native bridge shared libraries."),
22
-
CLIStep(c.build_j2v8_jni, " Compile and link the J2V8 C++ shared libraries (.so/.dylib/.dll), which provide the JNI bridge to interop with the C++ code of Node.js / V8."),
22
+
CLIStep(c.build_j2v8_jni, " Generate the J2V8 JNI C++ Header files."),
23
+
CLIStep(c.build_j2v8_cpp, " Compile and link the J2V8 C++ shared libraries (.so/.dylib/.dll), which provide the JNI bridge to interop with the C++ code of Node.js / V8."),
23
24
CLIStep(c.build_j2v8_optimize, " The native J2V8 libraries are optimized for performance and/or filesize by using the available tools of the target-platform / compiler-toolchain."),
24
25
CLIStep(c.build_j2v8_java, " Compiles the Java source code and packages it, including the previously built native libraries, into the final package artifacts.\n"+
25
26
" For the execution of this build-step Maven (Java) or Gradle (Android) are used for the respective target platforms."),
0 commit comments