+4
-0
@@ -0,1 +1,5 @@ | ||
| # v7.4.0 - 14/11/25 | ||
| - feat(windows): support msvc 2026 (Thanks to @Norgerkaj) | ||
| # v7.3.1 - 17/04/25 | ||
@@ -2,0 +6,0 @@ |
@@ -122,3 +122,3 @@ 'use strict' | ||
| async findVisualStudio2019OrNewerFromSpecifiedLocation() { | ||
| return this.findVSFromSpecifiedLocation([2019, 2022]) | ||
| return this.findVSFromSpecifiedLocation([2019, 2022, 2026]) | ||
| } | ||
@@ -165,3 +165,3 @@ | ||
| async findVisualStudio2019OrNewerUsingSetupModule() { | ||
| return this.findNewVSUsingSetupModule([2019, 2022]) | ||
| return this.findNewVSUsingSetupModule([2019, 2022, 2026]) | ||
| } | ||
@@ -223,3 +223,3 @@ | ||
| async findVisualStudio2019OrNewer() { | ||
| return this.findNewVS([2019, 2022]) | ||
| return this.findNewVS([2019, 2022, 2026]) | ||
| } | ||
@@ -387,2 +387,6 @@ | ||
| } | ||
| if (ret.versionMajor === 18) { | ||
| ret.versionYear = 2026 | ||
| return ret | ||
| } | ||
| this.log.silly('- unsupported version:', ret.versionMajor) | ||
@@ -457,2 +461,4 @@ return {} | ||
| return 'v143' | ||
| } else if (versionYear === 2026) { | ||
| return 'v145' | ||
| } | ||
@@ -459,0 +465,0 @@ this.log.silly('- invalid versionYear:', versionYear) |
+1
-1
@@ -24,3 +24,3 @@ { | ||
| "main": "lib", | ||
| "version": "7.3.1", | ||
| "version": "7.4.0", | ||
| "author": "Gábor Mező aka unbornchikken", | ||
@@ -27,0 +27,0 @@ "maintainers": [ |
+14
-10
@@ -103,4 +103,2 @@ # CMake.js (MIT) | ||
| In a nutshell. _(For more complete documentation please see [the first tutorial](https://github.com/unbornchikken/cmake-js/wiki/TUTORIAL-01-Creating-a-native-module-by-using-CMake.js-and-NAN).)_ | ||
| - Install cmake-js for your module `npm install --save cmake-js` | ||
@@ -113,5 +111,5 @@ - Put a CMakeLists.txt file into your module root with this minimal required content: | ||
| add_compile_definitions(-DNAPI_VERSION=4) | ||
| add_compile_definitions(NAPI_VERSION=4) | ||
| file(GLOB SOURCE_FILES "your-source files-location-here") | ||
| file(GLOB SOURCE_FILES "your-source-files-location-here") | ||
@@ -351,3 +349,3 @@ add_library(${PROJECT_NAME} SHARED ${SOURCE_FILES} ${CMAKE_JS_SRC}) | ||
| That's it. There is nothing else to do either on the application's or on the module's side, CMake.js modules are compatible with NW.js out-of-the-box. For more complete documentation please see [the third tutorial](https://github.com/unbornchikken/cmake-js/wiki/TUTORIAL-03-Using-CMake.js-based-native-modules-with-nw.js). | ||
| That's it. There is nothing else to do either on the application's or on the module's side, CMake.js modules are compatible with NW.js out-of-the-box. | ||
@@ -379,9 +377,15 @@ #### Heroku | ||
| ## Tutorials | ||
| ## Using external C/C++ libraries | ||
| - [TUTORIAL 01 Creating a native module by using CMake.js and NAN](https://github.com/unbornchikken/cmake-js/wiki/TUTORIAL-01-Creating-a-native-module-by-using-CMake.js-and-NAN) | ||
| - [TUTORIAL 02 Creating CMake.js based native addons with Qt Creator](https://github.com/unbornchikken/cmake-js/wiki/TUTORIAL-02-Creating-CMake.js-based-native-addons-with-QT-Creator) | ||
| - [TUTORIAL 03 Using CMake.js based native modules with NW.js](https://github.com/unbornchikken/cmake-js/wiki/TUTORIAL-03-Using-CMake.js-based-native-modules-with-nw.js) | ||
| - [TUTORIAL 04 Creating CMake.js based native modules with Boost dependency](https://github.com/unbornchikken/cmake-js/wiki/TUTORIAL-04-Creating-CMake.js-based-native-modules-with-Boost-dependency) | ||
| Because you are using CMake, there are many ways to load libraries in your CMakeLists.txt. | ||
| Various places on the internet and in the CMake docs will suggest various approaches you can take. Common ones are: | ||
| * [conan](https://conan.io/) (This may not work properly currently; we hope to improve support in a future release) | ||
| * [vcpkg](https://vcpkg.io/) (This may not work properly currently; we hope to improve support in a future release) | ||
| * [hunter](https://github.com/cpp-pm/hunter) | ||
| * [CMake ExternalProject](https://cmake.org/cmake/help/latest/module/ExternalProject.html) | ||
| * If on linux, using system libraries from the system package-manager | ||
| * Importing as a git submodule | ||
| We aim to be agnostic about how to use CMake, so it should be possible to use whatever approach you desire. | ||
| ## Real examples | ||
@@ -388,0 +392,0 @@ |
Shell access
Supply chain riskThis module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.
Found 1 instance in 1 package
Debug access
Supply chain riskUses debug, reflection and dynamic code execution features.
Found 1 instance in 1 package
Dynamic require
Supply chain riskDynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
Found 1 instance in 1 package
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
Found 7 instances in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 2 instances in 1 package
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
Found 1 instance in 1 package
Major refactor
Supply chain riskPackage has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.
Found 1 instance in 1 package
Shell access
Supply chain riskThis module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.
Found 1 instance in 1 package
Debug access
Supply chain riskUses debug, reflection and dynamic code execution features.
Found 1 instance in 1 package
Dynamic require
Supply chain riskDynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.
Found 1 instance in 1 package
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
Found 7 instances in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 2 instances in 1 package
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
Found 1 instance in 1 package
1982
0.3%404
1%3
-25%104940
-0.06%