* Original Node.js files
* Implement N-API for V8 with unit tests
* Update Node.js files, add more tests, and add comments
* Address PR feedback
* Format code with 120 columns per row
* (1) Robust tracing in V8Runtime and Inspector (2) Inspector fixes including sampling profiler
* Enabling inspector, profiles, diagnostics by default
* Fixing build and turn enableInspector flag to be of by default
* Incorporating feedbacks and fixing build
* Missed adding tracing.cpp into build definition
Use windows-2019
Update
Use absolute path for other YML
User relative path for other YAML
Use expression to evaluate $(RunUnitTests)
Update
Update
Update
Update
Update
Update
Update
Update
Update
Update
Update
Update
Update
Update
Update
Shorten job description
Add variable-verifying task
Clean up pull-request.yml
Disable PR validation until merging
Use dependencies to pass NuGetId
Update
Use matrix for NuGet job
Remove parameter runUnitTests
Uncomment triggers
* Add .editorconfig
* Use DirectoryInfo for folder paths
* Use non-interpolable literals in ValidateSet
* Add NuGet config and packages
* Add NuGet config and packages
* Obtain Boost version from packages.config'
* Add UseOldGn param.
* Drop old GN download
* Fix JSI implementation to pass unit tests. Include windbg extension
* Add support for Symbol
* Don't try to run ARM unit tests
* Don't build debug extension in uwp
* pipeline syntax
* You can't use parameters in conditions
* yaml syntax
* timeout
* Add a debug line
* Try a separate boolean parameter
* Update to v8.6
* small build fix
* Fix ARM64 build
* Fix JSI implementation to pass unit tests. Include windbg extension
* Add support for Symbol
* Don't try to run ARM unit tests
* Don't build debug extension in uwp
* pipeline syntax
* You can't use parameters in conditions
* yaml syntax
* timeout
* Add a debug line
* Try a separate boolean parameter
* Keep experimenting with PublishSymbols
* Try to create a separate NuGet for UWP
* Remove PublishSymbols task
* Different nuspec and targets files
* bump version
* Start branching for RN (JSI) compatibility
* Create versioning scheme for master branch
* Synchronize JSI headers from RN master
* Save JSI headers in a different location to avoid conflicts
Now that upstream dependents upgraded form v15 to v16 toolset, we can remove the hardcoded version pinning (which will reduce CI loop time significantly).
* Fix basic debugging support. Upgrade to V8 8.4
* Try a new way to install VS components
* try different arguments for vs installer
* try to collect logs for VSInstall failures
* try to capture vslogs
* syntax fix
* add an update step
* always download bootstrapper to update installer
* Inspector cleanup; shutdown per-platform support (exp.)
* Address some CR comments; update boost to 1.72
Co-authored-by: tudorm <tudorm@microsoft.com>
* Hardcode 14.24 VC tools due to FH4 regression
* Initial UWP support work; support clang+stdlib builds; include version information in DLL
* Fix copyright string
Co-authored-by: tudorm <tudorm@microsoft.com>
This is required due to the convoluted build system in React Native Windows that has no way to distinguish between UWP and WIN32 builds in shared projects.
The V8JSI_NODLLCOPY MsBuild property will skip the ReferenceCopyLocalPaths step if set.
* Reenable some V8 disabled warnings. Fix some warnings in adapter code. Turn on CFG.
* Add waitForDebugger flag and use default debugger port
* Ignore line endings when applying patches. Also turn on CI coverage for PRs
* V8 does not support external UTF-8 strings (only ASCII and 2-byte), so we need to copy the data.
* Rev package version
* GClient is using Python 3 by default as of today
Co-authored-by: tudorm <tudorm@microsoft.com>
- reenable some V8 disabled warnings;
- fix some warnings in adapter code;
- turn on CFG (Control Flow Guard);
- add waitForDebugger flag and use default debugger port;
* update to version 8.1 of V8;
* convert JS errors into C++ jsi::JSError exceptions;
* update JSI headers to latest Hermes AP;
* remove some console logging;
* delay load the dll by default (so that consumers can have a run-time / optional dependency on v8jsi.dll without needing to distribute it if unused);
* the Platform must be process-singleton to match v8 internals (V8 is not embedder-friendly and makes several assumptions about objects that are initialized once per process - we're matching that design with our V8Platform to avoid crashes if multiple contexts are created / shut down during a process' lifetime);
* Switch back to V8 8.0 (with disabled FH4 support for 141 toolset compatibility);
* Reduce unnecessary dependencies on Boost libraries;
* Use NuGet for bringing in Boost ASIO headers (much faster than downloading the whole zip from boostorg);
* Misc fixes (include v8 version / ref number in NuGet, etc.);
This includes all work previously done for the V8 Jsi implementation, partially cleaned up, plus build scripts and requisite licensing / comment changes in preparation for public OSS release.