Skip to content
Snippets Groups Projects
Commit 09494ab4 authored by Lennard Karger's avatar Lennard Karger
Browse files

Added PIO Projects in Sketches

parent 61003632
Branches
No related tags found
3 merge requests!4PIO Projekte in main-Branch implementieren,!3Vorbereitung Main merge PIO - Projektstrukturen,!1Test Merge
.pio
.vscode/.browse.c_cpp.db*
.vscode/c_cpp_properties.json
.vscode/launch.json
.vscode/ipch
{
// See http://go.microsoft.com/fwlink/?LinkId=827846
// for the documentation about the extensions.json format
"recommendations": [
"platformio.platformio-ide"
],
"unwantedRecommendations": [
"ms-vscode.cpptools-extension-pack"
]
}
This directory is intended for project header files.
A header file is a file containing C declarations and macro definitions
to be shared between several project source files. You request the use of a
header file in your project source file (C, C++, etc) located in `src` folder
by including it, with the C preprocessing directive `#include'.
```src/main.c
#include "header.h"
int main (void)
{
...
}
```
Including a header file produces the same results as copying the header file
into each source file that needs it. Such copying would be time-consuming
and error-prone. With a header file, the related declarations appear
in only one place. If they need to be changed, they can be changed in one
place, and programs that include the header file will automatically use the
new version when next recompiled. The header file eliminates the labor of
finding and changing all the copies as well as the risk that a failure to
find one copy will result in inconsistencies within a program.
In C, the usual convention is to give header files names that end with `.h'.
It is most portable to use only letters, digits, dashes, and underscores in
header file names, and at most one dot.
Read more about using header files in official GCC documentation:
* Include Syntax
* Include Operation
* Once-Only Headers
* Computed Includes
https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html
This directory is intended for project specific (private) libraries.
PlatformIO will compile them to static libraries and link into executable file.
The source code of each library should be placed in a an own separate directory
("lib/your_library_name/[here are source files]").
For example, see a structure of the following two libraries `Foo` and `Bar`:
|--lib
| |
| |--Bar
| | |--docs
| | |--examples
| | |--src
| | |- Bar.c
| | |- Bar.h
| | |- library.json (optional, custom build options, etc) https://docs.platformio.org/page/librarymanager/config.html
| |
| |--Foo
| | |- Foo.c
| | |- Foo.h
| |
| |- README --> THIS FILE
|
|- platformio.ini
|--src
|- main.c
and a contents of `src/main.c`:
```
#include <Foo.h>
#include <Bar.h>
int main (void)
{
...
}
```
PlatformIO Library Dependency Finder will find automatically dependent
libraries scanning project source files.
More information about PlatformIO Library Dependency Finder
- https://docs.platformio.org/page/librarymanager/ldf.html
; PlatformIO Project Configuration File
;
; Build options: build flags, source filter
; Upload options: custom upload port, speed and extra flags
; Library options: dependencies, extra library storages
; Advanced options: extra scripting
;
; Please visit documentation for the other options and examples
; https://docs.platformio.org/page/projectconf.html
[env:nano33ble]
platform = nordicnrf52
board = nano33ble
framework = arduino
upload_port = COM5
build_flags =
-DsmnDEFBYBUILD -DsmnNANOBLE33 -DsmnDEBUG ;-DSlaveACM3
lib_deps =
symlink://C:\Users\Lennard\Documents\Git_local\REP_STR\libraries\BlePoll
symlink://C:\Users\Lennard\Documents\Git_local\REP_STR\libraries\environment
symlink://C:\Users\Lennard\Documents\Git_local\REP_STR\libraries\ComRingBuf
symlink://C:\Users\Lennard\Documents\Git_local\REP_STR\libraries\LoopCheck
symlink://C:\Users\Lennard\Documents\Git_local\REP_STR\libraries\MidiNotes
symlink://C:\Users\Lennard\Documents\Git_local\REP_STR\libraries\Monitor
symlink://C:\Users\Lennard\Documents\Git_local\REP_STR\libraries\nRF52840Gpio
symlink://C:\Users\Lennard\Documents\Git_local\REP_STR\libraries\nRF52840Radio
symlink://C:\Users\Lennard\Documents\Git_local\REP_STR\libraries\nRF52840Ser
symlink://C:\Users\Lennard\Documents\Git_local\REP_STR\libraries\nRF52840Twi
symlink://C:\Users\Lennard\Documents\Git_local\REP_STR\libraries\SensorLSM9DS1
;symlink://C:\Users\Lennard\Documents\Git_local\REP_STR\libraries\SoaapComDue
symlink://C:\Users\Lennard\Documents\Git_local\REP_STR\libraries\SoaapMsg
symlink://C:\Users\Lennard\Documents\Git_local\REP_STR\libraries\StateMachine
This diff is collapsed.
This directory is intended for PlatformIO Test Runner and project tests.
Unit Testing is a software testing method by which individual units of
source code, sets of one or more MCU program modules together with associated
control data, usage procedures, and operating procedures, are tested to
determine whether they are fit for use. Unit testing finds problems early
in the development cycle.
More information about PlatformIO Unit Testing:
- https://docs.platformio.org/en/latest/advanced/unit-testing/index.html
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment