| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[BugFix]Add check for env when adjustExternalMemory issue: m-6843521611 AutoLand:release/3.7 | 8 个月前 | |
[Optimize] Remove unnecessary `extern "C"` `quickjs.h` itself has already added `extern "C"` for C++ sources SkipChecks:macro | 3 个月前 | |
[Infra] Remove unused Mako binding generator - Remove the legacy bind_gen pipeline and its stale entry point and dependency manifest. - Remove the vendored Mako runtime and package metadata used only by that pipeline. - Keep the active Jinja2-based N-API generator unchanged. TEST: Ran tools/gen_bindings.py without site packages or Mako and generated the gen_test bindings successfully. AutoSubmit: true | 1 个月前 | |
[BugFix] Safely elevate NAPI object references - Move the elevated bridge reference into ObjectRef and recreate its weak reference while the wrapper is protected. - Add coverage for garbage collection and cloned object references. TEST: Built napi_binding_unittests_exec and passed all 7 tests. | 2 个月前 | |
[Optimize] Change gn path to relative path. Now there are lots of gn absolute path usage in our project, it brings the following problem: Affecting the parent directory of lynx: In order to make it possible to extend lynx project in other projects, we need to use //lynx gn absolute path in lynx project, so we should execute gn command in the parent directory of lynx. As a result, buildroot and other third_party libraries should be placed in parent directory of lynx. To solve the problem, we prefer to use relative path in lynx project, refering to the approach in skia and v8. In this change, we add a script named gn_relative_path_converter.py to help converting //lynx to relative path. But we still need to do some adaptions: Add rebase_path function for converting relative path to absolute path in template definition and variable definition in build_overrides, because the relative path is different with different gn target. | 1 年前 | |
initial commit | 1 年前 | |
initial commit | 1 年前 |
Directory mappings:
- /common -> common base interfaces for binding
- /idl-codegen -> idl code generator tools for NAPI
- /napi -> NAPI binding implementations