DHP wallet application for Ledger devices.
You can quickly setup a convenient environment to build and test your application by using Ledger's VSCode developer tools extension which leverages the ledger-app-dev-tools docker image.
It will allow you, whether you are developing on macOS, Windows or Linux to quickly build your apps, test them on Speculos and load them on any supported device.
- Install and run Docker.
- Make sure you have an X11 server running :
- Install VScode and add Ledger's extension.
- Open a terminal and clone
app-dHealth
withgit clone [email protected]:dhealthproject/app-dHealth.git
. - Open the
app-dHealth
folder with VSCode. - Use Ledger extension's sidebar menu or open the tasks menu with
ctrl + shift + b
(command + shift + b
on a Mac) to conveniently execute actions :- Build the app for the device model of your choice with
Build
. - Test your binary on Speculos with
Run with Speculos
. - You can also run functional tests, load the app on a physical device, and more.
- Build the app for the device model of your choice with
ℹ️ The terminal tab of VSCode will show you what commands the extension runs behind the scene.
The ledger-app-dev-tools docker image contains all the required tools and libraries to build, test and load an application.
You can download it from the ghcr.io docker repository:
sudo docker pull ghcr.io/ledgerhq/ledger-app-builder/ledger-app-dev-tools:latest
You can then enter this development environment by executing the following command from the directory of the application git
repository:
Linux (Ubuntu)
sudo docker run --rm -ti --user "$(id -u):$(id -g)" --privileged -v "/dev/bus/usb:/dev/bus/usb" -v "$(realpath .):/app" ghcr.io/ledgerhq/ledger-app-builder/ledger-app-dev-tools:latest
macOS
sudo docker run --rm -ti --user "$(id -u):$(id -g)" --privileged -v "$(pwd -P):/app" ghcr.io/ledgerhq/ledger-app-builder/ledger-app-dev-tools:latest
Windows (with PowerShell)
docker run --rm -ti --privileged -v "$(Get-Location):/app" ghcr.io/ledgerhq/ledger-app-builder/ledger-app-dev-tools:latest
The application's code will be available from inside the docker container, you can proceed to the following compilation steps to build your app.
To easily setup a development environment for compilation and loading on a physical device, you can use the VSCode integration whether you are on Linux, macOS or Windows.
If you prefer using a terminal to perform the steps manually, you can use the guide below.
Setup a compilation environment by following the shell with docker approach.
From inside the container, use the following command to build the app :
make DEBUG=1 # compile optionally with PRINTF
You can choose which device to compile and load for by setting the BOLOS_SDK
environment variable to the following values :
BOLOS_SDK=$NANOS_SDK
BOLOS_SDK=$NANOX_SDK
BOLOS_SDK=$NANOSP_SDK
BOLOS_SDK=$STAX_SDK
By default this variable is set to build/load for Nano S.
This step will vary slightly depending on your platform.
ℹ️ Your physical device must be connected, unlocked and the screen showing the dashboard (not inside an application).
Linux (Ubuntu)
First make sure you have the proper udev rules added on your host :
# Run these commands on your host, from the app's source folder.
sudo cp .vscode/20-ledger.ledgerblue.rules /etc/udev/rules.d/
sudo udevadm control --reload-rules
sudo udevadm trigger
Then once you have opened a terminal in the app-builder
image and built the app for the device you want, run the following command :
# Run this command from the app-builder container terminal.
make load # load the app on a Nano S by default
Setting the BOLOS_SDK environment variable will allow you to load on whichever supported device you want.
macOS / Windows (with PowerShell)
ℹ️ It is assumed you have Python installed on your computer.
Run these commands on your host from the app's source folder once you have built the app for the device you want :
# Install Python virtualenv
python3 -m pip install virtualenv
# Create the 'ledger' virtualenv
python3 -m virtualenv ledger
Enter the Python virtual environment
- macOS :
source ledger/bin/activate
- Windows :
.\ledger\Scripts\Activate.ps1
# Install Ledgerblue (tool to load the app)
python3 -m pip install ledgerblue
# Load the app.
python3 -m ledgerblue.runScript --scp --fileName bin/app.apdu --elfFile bin/app.elf
The dHealth app comes with functional tests implemented with Ledger's Ragger test framework.
To test your app on macOS or Windows, it is recommended to use Ledger's VS Code extension to quickly setup a working test environment.
You can use the following sequence of tasks and commands (all accessible in the extension sidebar menu) :
Select build target
Build app
Then you can choose to execute the functional tests :
- Use
Run tests
.
Or simply run the app on the Speculos emulator :
Run with Speculos
.
On Linux, you can use Ledger's VS Code extension to run the tests. If you prefer not to, open a terminal and follow the steps below.
Install the tests requirements :
pip install -r tests/requirements.txt
Then you can :
Run the functional tests (here for nanos but available for any device once you have built the binaries) :
pytest tests/ --tb=short -v --device nanos
Or run your app directly with Speculos
speculos --model nanos build/nanos/bin/app.elf
High level documentation such as APDU, commands and transaction serialization are included in developer documentation which can be generated with doxygen
doxygen .doxygen/Doxyfile
the process outputs HTML and LaTeX documentations in doc/html
and doc/latex
folders.
The flow processed in GitHub Actions is the following:
- Ledger guidelines enforcer which verifies that an app is compliant with Ledger guidelines. The successful completion of this reusable workflow is a mandatory step for an app to be available on the Ledger application store. More information on the guidelines can be found in the repository ledger-app-workflow
- Code formatting with clang-format
- Compilation of the application for all Ledger hardware in ledger-app-builder
- Unit tests of C functions with cmocka (see tests/unit-tests/)
- End-to-end tests with Speculos emulator and ragger (see tests/functional)
- Code coverage with gcov/lcov and upload to codecov.io
- Documentation generation with doxygen
It outputs 3 artifacts:
compiled_app_binaries
within binary files of the build process for each devicecode-coverage
within HTML details of code coveragedocumentation
within HTML auto-generated documentation
For a smooth and quick integration:
- See the developers’ documentation on the Developer Portal, and
- Go on Discord to chat with developer support and the developer community.