|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Ip2region||14,065||38||57||8 days ago||11||February 05, 2023||40||apache-2.0||Go|
|Ip2region (2.0 - xdb) is a offline IP address manager framework and locator, support billions of data segments, ten microsecond searching performance. xdb engine implementation for many programming languages|
|Neon||7,399||184||267||20 days ago||44||May 23, 2022||86||apache-2.0||Rust|
|Rust bindings for writing safe and fast native Node.js modules.|
|Node Serialport||5,536||4,102||1,689||14 hours ago||174||July 27, 2023||126||mit||TypeScript|
|Native Node bindings to Git.|
|Node Opencv||4,275||307||63||8 months ago||31||March 10, 2020||126||mit||C++|
|OpenCV Bindings for node.js|
|Puerts||4,160||5 days ago||174||other||C++|
|PUER(普洱) Typescript. Let's write your game in UE or Unity with TypeScript.|
|Web scraper for NodeJS|
|Node Webrtc||2,588||320||353||10 months ago||87||January 10, 2021||118||other||C++|
|node-webrtc is a Node.js Native Addon that provides bindings to WebRTC M87|
|Node.js bindings for Argon2 hashing algorithm|
|Nut.js||1,665||32||3 days ago||263||July 14, 2023||32||apache-2.0||TypeScript|
|Native UI testing / controlling with node|
Core library which will be used by Ledger applications.
If you’re a developer and want to contribute, please refer to our contribution guidelines specific documentation.
git clone --recurse-submodules https://github.com/LedgerHQ/lib-ledger-core.git
If you had already forked / cloned the repository before issuing that command, it’s okay. You can initiate the submodules with the following commands:
cd lib-ledger-core git submodule init git submodule update
This project is based on cmake as a build system so you should install it before starting (at least version 3.7).
cmake is building out of source, you should create a build directory (e.g.
. # Directory where clone command was launched ├── lib-ledger-core # Source files directory ├── lib-ledger-core-build # Build directory
If you respect this folder structure (and naming), after
cd lib-ledger-core-build, you can build the library by running:
cmake -DSYS_OPENSSL=ON -DOPENSSL_ROOT_DIR=<path-to-openssl-root-dir> -DOPENSSL_INCLUDE_DIR=<path-to-openssl-include-files> -DOPENSSL_SSL_LIBRARIES=<path-to-openssl-libraries> -DOPENSSL_USE_STATIC_LIBS=TRUE ../lib-ledger-core && make
NB. if you want to build on
Windows with Visual Studio by adding the argument
-G "Visual Studio 16 2019" in the above cmake command, instead of using
make to build the project, you should open the 'ledger-core.sln' solution file with Visual Studio and build the solution with it
If you struggle with how openssl is installed, for example, on
opensslcan be installed with
brew install openssl
you can then use the argument
-DOPENSSL_ROOT_DIR=/usr/local/opt/openssl in the above cmake command
"DOPENSSL_INCLUDE_DIR" and "DOPENSSL_SSL_LIBRARIES" are not necessary on mac.
apt-get install libssl-dev
you can then use the argument
-DOPENSSL_SSL_LIBRARIES=/usr/lib/x86_64-linux-gnu -DOPENSSL_INCLUDE_DIR=/usr/include/openssl in the above cmake command
"DOPENSSL_ROOT_DIR" is not necessary on linux.
Windows, Openssl can be downloaded and installed from https://slproweb.com/products/Win32OpenSSL.html "DOPENSSL_ROOT_DIR" is then the installed path of Openssl in the above cmake command "DOPENSSL_INCLUDE_DIR" and "DOPENSSL_SSL_LIBRARIES" are not necessary on windows.
Several CMake arguments might interest you there:
-DCMAKE_BUILD_TYPE=Debug: you should always set that when testing as you will get DWARF debug symbols and debugging instruments support.
-DCMAKE_EXPORT_COMPILE_COMMANDS=YES: useful when you’re using a C++ linter, such as cquery.
-G "Visual Studio 16 2019": build libcore with Visual Studio on Windows
-G Xcode: build libcore with Xcode on Mac
-DBUILD_TESTS=OFF: build libcore without unit tests. In this case, openssl arguments are not needed
Building with JNI (Java Native Interface), allows you to use the library with Java based software. In order to enable JNI mode use
This will add JNI files to the library compilation and remove tests. You need at least a JDK 7 to build for JNI (OpenJDK or Oracle JDK)
Make sure that your have
PostgreSQL installed on your machine, otherwise the
find_package(PostgreSQL REQUIRED) will fail during configuration.
To compile libcore with PostgreSQL support, you should add
-DPG_SUPPORT=ON to your
CMake configuration command.
You also need to add
-DPostgreSQL_INCLUDE_DIR=path/to/include/dir in your configuration
as a hint for headers' location (e.g.
To use with libcore, simply set value of the key
to the database's URL connection and set it in the pool's configuration.
It is also possible to configure the size of the connection pool and read-only connection pool when instantiating the
api::DatabaseBackend::getPostgreSQLBackend(int32_t connectionPoolSize, int32_t readonlyConnectionPoolSize).
If you don't build the library with PostgreSQL, sqlite3 shall be used as Database.
If you build the library with PostgreSQL, make sure to have a running PostgreSQL server or PostgreSQL docker container
As an example, if you are running it on
test_db as database name,
database's name forwarded to the pool (through configuration key
should look like :
In order to run local tests
ctest -C Debug -VV
if you want to run only one specific unit test. (e.g. the test case
BitcoinLikeWalletSynchronization.MediumXpubSynchronization in the test project
You can generate the Doxygen documentation by running the
doc target (for instance,
The library can be compiled and integrated as an node module in a pretty straightforward way. You will be interested in either using it, or making a new version of the node module.
The lib-ledger-core-node-bindings repository contains the node.js bindings you will need to
lib-ledger-core. You can either clone the git repository or simply install from
npm i @ledgerhq/ledger-core
Generating bindings is a several steps process:
lib-ledger-coreand generate a fresh version of
package.jsonfile in order to remove or comment the
lib-ledger-core, run the
tools/generateBindings.shscript by giving it the path to the bindings (i.e. where you cloned lib-ledger-core-node-bindings) and as second argument the path to the directory where you built the
lib-ledger-core— it should be something like
get fetch origin --prune && git rebase origin/master.
java8for a complete, working install.
lib-ledger-core— if any — with a
git checkout .and/or
git reset ..
yarnto generate the bindings.
build/Release/ledgerapp_nodejs.nodein the bindings project.
npm ishould install your own version.
Libcore can be built for following OSes:
macOS 9.0, with
MSVC(starting from Visual Studio 15), 32-bit is built with
arm64architectures are supported, minimum supported version is
arm64-v8aarchitectures are supported, minimum supported version is
Android 7 (API 24)(Java 8 is needed).
<9.0.0(other versions are not tested (yet)),
You are advised to link your GitHub account to both CircleCI and Appveyor by signing-in. Because we are using shared runners and resources, we have to share CI power with other teams. It’s important to note that we don’t always need to run the CI. Example of situations when we do not need it:
In those cases, please include the
[skip ci] or
[ci skip] text in your commit message’s
title. You could tempted to put it in the body of your message but that will not work with
Finally, it’s advised to put it on every commit and rebase at the end to remove the
[skip ci] tag
from your commits’ messags to have the CI re-enabled, but some runners might be smart enough to do
it for all commits in the PR.
Rebasing is done easily. If your PR wants to merge
feature/stuff -> develop, you can do something
like this — assuming you have cloned the repository with a correctly set
git checkout feature/stuff git rebase -i origin/develop
reword at the beginning of each lines without changing the text of
the commits — this has no effect. Save the file and quit. You will be prompted to change the
commits’ messages one by one, allowing you to remove the
[skip ci] tag from all commits.
Currently, interface files (headers, .hpp) are not linked by copied directly into the test directory. That means that every time you make a change in the interface that is tested by any code in core/test/, you need to update the copy.
Just run this command:
cd $your_build_folder rm -rf CMakeFiles CMakeCache.txt
Especially if you’ve upgraded to Mojave for which there are some breaking changes, you will need to perform some manual tasks — here, for macOSX Mojave:
xcode-select --install open /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg