chore(docs): 6.4-build on cloud - gitpod
@@ -75,6 +75,7 @@ Use the [installer](https://github.com/metacall/install) and try [some examples]
- [6.1 Build Options](#61-build-options)
- [6.2 Coverage](#62-coverage)
- [6.3 Debugging](#63-debugging)
+ - [6.4 Build on Cloud - Gitpod](#64-build-on-cloud---gitpod)
- [7. Platform Support](#7-platform-support)
- [7.1 Docker Support](#71-docker-support)
- [7.1.1 Docker Development](#711-docker-development)
@@ -612,16 +613,6 @@ In order to end this section, here's a list of ideas that are not completely imp
## 6. Build System
----
-Instead of configuring a local setup, you can also use [Gitpod](https://www.gitpod.io/), an automated cloud dev environment.
-
-Click the button below. A workspace with all required environments will be created.
-
-[![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/metacall/core)
-
-> To use it on your forked repo, edit the 'Open in Gitpod' button url to `https://gitpod.io/#https://github.com/<your-github-username>/core`
----
-
Follow these steps to build and install **METACALL** manually.
``` sh
@@ -736,6 +727,18 @@ ctest
For running other Valgrind's tools like helgrind or similar, I recommend running them manually. Just run one test with `ctest -VV -R metacall-node-port-test`, copy the environment variables, and configure the flags by yourself.
+
+### 6.4 Build on Cloud - Gitpod
+
+Instead of configuring a local setup, you can also use [Gitpod](https://www.gitpod.io/), an automated cloud dev environment.
+
+Click the button below. A workspace with all required environments will be created.
+
+[![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/metacall/core)
+
+> To use it on your forked repo, edit the 'Open in Gitpod' button url to `https://gitpod.io/#https://github.com/<your-github-username>/core`
+
+
## 7. Platform Support
The following platforms and architectures have been tested an work correctly with all plugins of **METACALL**.
