Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitf2624d1

Browse files
committed
Adding URLs to dependencies, dependency installation procedure for Linux.
1 parent09a0dd4 commitf2624d1

File tree

1 file changed

+10
-5
lines changed

1 file changed

+10
-5
lines changed

‎README.md‎

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -52,13 +52,18 @@ To build and run locally:
5252

5353
**Dependencies**
5454

55-
* CMake
56-
* make
57-
* gcc
55+
*[CMake](https://cmake.org/)
56+
*[GCC](https://gcc.gnu.org/)
5857

59-
From the project root:
58+
On (Ubuntu) Linux run:
6059

60+
```bash
61+
sudo apt-get install build-essential cmake
6162
```
63+
64+
From the project root:
65+
66+
```bash
6267
cdtest&& mkdir build&&cd build
6368
cmake ..
6469
make&& bin/test-ArduinoCore-API
@@ -68,7 +73,7 @@ make && bin/test-ArduinoCore-API
6873

6974
In order to compile a core which is implementing ArduinoCore-API you'll need to copy/symlink the`api` directory to the target's`cores/arduino` directory as part of your development and release workflow. The most elegant and effective solution is to develop your core with`api` symlinked and produce the distributable archive by telling`tar` to follow symlinks. Example:
7075

71-
```
76+
```bash
7277
tar --exclude='*.git*' -cjhvf$yourcore-$version.tar.bz2$yourcore/
7378
```
7479

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp