git submodule deinit <path_to_submodule>
git rm <path_to_submodule>
rm -rf .git/modules/
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/** | |
* (c) Ark Ecosystem <[email protected]> | |
* | |
* For the full copyright and license information, please view the LICENSE | |
* file that was distributed with this source code. | |
**/ | |
/** | |
* ESP32 Post Data Example Sketch | |
* |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#if defined(ESP8266) | \ | |
defined(ARDUINO_SAMD_MKRZERO) | \ | |
defined(ARDUINO_SAMD_ZERO) | \ | |
defined(ARDUINO_SAM_DUE) | \ | |
defined(ARDUINO_ARCH_ARC32) | \ | |
defined(__TC27XX__) | \ | |
(defined(TEENSYDUINO) && (TEENSYDUINO < 139)) | |
#undef pgm_read_ptr | |
#define pgm_read_ptr(addr) (*(const void **)(addr)) | |
#endif |
git fetch upstream && git checkout master && git rebase upstream/master
In your local clone of your forked repository, you can add the original GitHub repository as a "remote". ("Remotes" are like nicknames for the URLs of repositories - origin is one, for example.) Then you can fetch all the branches from that upstream repository, and rebase your work to continue working on the upstream version. In terms of commands that might look like:
git remote add upstream https://github.com/whoever/whatever.git
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# - run: | |
# name: Install OpenSSL | |
# command: | | |
# wget https://github.com/openssl/openssl/archive/OpenSSL_1_1_1.tar.gz | |
# tar -xf OpenSSL_1_1_1.tar.gz | |
# cd openssl-OpenSSL_1_1_1 | |
# ./config | |
# make | |
# sudo make install | |
# - run: |
brew install llvm
ln -s "/usr/local/opt/llvm/bin/clang-format" "/usr/local/bin/clang-format"
ln -s "/usr/local/opt/llvm/bin/clang-tidy" "/usr/local/bin/clang-tidy"
use cmake
file
find_program(CLANG_TIDY_BIN clang-tidy)
find_program(RUN_CLANG_TIDY_BIN /usr/local/Cellar/llvm/10.0.0_3/share/clang/run-clang-tidy.py)
Appends , MODE="0660", GROUP="plugdev"
to the subsystem udev rules from github/LedgerHQ/udev-rules.
Solution found at github/LedgerHQ/udev-rules/issues/#4.
Nano S version >=1.5.5
Steps:
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/******************************************************************************* | |
* Ark Wallet | |
* (c) 2017 Ledger | |
* | |
* Licensed under the Apache License, Version 2.0 (the "License"); | |
* you may not use this file except in compliance with the License. | |
* You may obtain a copy of the License at | |
* | |
* http://www.apache.org/licenses/LICENSE-2.0 | |
* |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
## Install Development Environment | |
There are two options for setting up our environment | |
**Option 1**: Using Ledger Vagrant | |
- Clone ledger-vagrant | |
> `git clone https://github.com/fix/ledger-vagrant` | |
- Connect to the vagrant machine | |
> `vagrant ssh` | |
- Move to the app |