You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> There is not yet a published package on JFrog and you will need to build the package manually using `conan create . --version=latest`. This will be fixed soon.
4
+
> No cross compiler profiles have been created yet, to use develop using this you currently need develop with the same archtecture and operating system as your build target. A Dockerfile has been provided for arm64 linux development. (Raspberry Pis and alike)
Git History for implementations of output_pin, input_pin, i2c, and serial can be seen [here](https://github.com/PhazonicRidley/libhal-linux-alpha)
10
15
11
16
## Contributing
12
17
@@ -18,161 +23,35 @@ Apache 2.0; see [`LICENSE`](LICENSE) for details.
18
23
19
24
---
20
25
21
-
## Making a new platform driver (Delete section below)
22
-
23
-
Use [libhal/libhal-lpc40](https://github.com/libhal/libhal-lpc40/) as an
24
-
example of the sections a README should have.
25
-
26
-
To make your own libhal library:
27
-
28
-
1. Press the green "Use this Template" button then.
29
-
2. Press the "Create a new repository".
30
-
3. Name it `libhal-<insert_platform_name>` and replace `<insert_platform_name>`
31
-
with the name of the device's family. For exmaple, if you want to make a
32
-
library for the stm32f103 which is in the stm32f1 series of MCUs then call
33
-
it `libhal-stm32f1`.
34
-
4. Choose where to put the repo under.
35
-
5. Go to `settings` > `Pages` > `Build and deployment` > `Source` and set the
36
-
source to `Github Actions`.
37
-
6. Go to `Pull Requests` and merge the library rename pull request.
38
-
7. Done!
39
-
40
-
## About the libhal-platform template
41
-
42
-
The `libhal-linux` repository is a template for creating platform
43
-
libraries in the libhal ecosystem. It provides a structured layout and a set of files to help you get started with creating your own platform library.
44
-
45
-
## .github/workflows
46
-
47
-
This directory contains GitHub Actions workflow files for continuous integration
48
-
(CI) and other automated tasks. The workflows currently included are:
49
-
50
-
-`ci.yml`: This workflow runs the CI pipeline, which includes
51
-
building the project, running tests, and deploying the library to the
52
-
`libhal-trunk` package repository.
53
-
-`take.yml`: This workflow is responsible for the "take" action, which assigns
54
-
commits to
55
-
-`deploy-version.yml`: A helper CI workflow that builds the library for each
56
-
target architecture/os/etc.
57
-
-`0.0.1.yml`: A launch file. This file is used to manually release a version
58
-
of the project via the "work dispatch" function of github actions.
59
-
-`update_name.yml`: This workflow updates the name of the repository when it's
60
-
used as a template for a new repository.
26
+
## 📚 Software APIs & Usage
27
+
To learn about available kernel APIs, documentation will be be made available soon.
61
28
62
-
## conanfile.py
29
+
To see some example code on how various APIs are used, see the programs inside the `demos` folder.
63
30
64
-
This is a [Conan](https://conan.io/) recipe file. Conan is a package manager for
65
-
C and C++ that helps manage dependencies in your project. This file defines how
66
-
Conan should build your project and its dependencies.
0 commit comments