stau.space
Threads and Scheduling
docs: Update README.md with new build information. Signed-off-by: Sona Tau Estrada Rivera <sona@stau.space>
+17
-14
+17
-14
README.md
+17
-14
README.md
···
4
4
5
5
I am using a sockets library I developed mysel. For more information on how the
6
6
sockets library was developed, feel free to visit the repo:
7
-
- https://git.gay/sona/enchufe
7
+
- https://tangled.org/@stau.space/enchufe
8
+
9
+
This sockets library relies on having GNU's version of the POSIX utilities that
10
+
should be available on a POSIX compliant system. Additionally, I am using GNU's
11
+
implementation of semaphores, although they are not POSIX, they should be
12
+
available on most systems.
8
13
9
14
For threads, I am using a builtin library called `threads.h`. This library is
10
15
documented on [cppreference.com](https://cppreference.com) as:
···
23
28
## Cluster
24
29
25
30
```sh
26
-
make cluster.py
31
+
./build.sh cluster.py
27
32
```
28
33
29
34
This will simply run the cluster on the server's loopback `127.0.0.1` and on
30
35
port `42069`. If youu want to supply your own server and port, use:
31
36
32
37
```sh
33
-
make cluster.py ADDRESS=<server address> PORT=<server port>
38
+
./build.sh cluster.py server_address server_port
34
39
```
35
40
36
-
where `<server address>` is the IP address of the cluster, and `<server port>`
37
-
is the port number of the cluster. Remember that you must put the words
38
-
"`ADDRESS`" and "`PORT`" before the `<server address>` and `<server port>`. If
39
-
you don't `make` will not detect that you passed those arguments to the
40
-
executable.
41
+
where `server_address` is the IPv4 address of the cluster, and `server_port`
42
+
is the port number of the cluster.
41
43
42
44
## Embedded device
43
45
···
46
48
will let make know on which server and port you want to run it.
47
49
48
50
```sh
49
-
make edevice.py ADDRESS=<server address> PORT=<server port>
51
+
./build.sh edevice.py server_address server_port
50
52
```
51
53
52
-
where `<server address>` is the IP address of the cluster, and `<server port>`
54
+
where `server_address` is the IPv4 address of the cluster, and `server_port`
53
55
is the port number of the cluster.
54
56
55
57
# Building
···
69
71
To build the cluster. From these two executables, you can then run the programs
70
72
like,
71
73
```sh
72
-
./.build/cluster <server address> <server port>
73
-
./.build/edevice <server address> <server port>
74
+
./.build/cluster server_address server_port
75
+
./.build/edevice server_address server_port
74
76
```
75
77
76
78
# Contributions
77
79
78
-
I would like to thank Gabriel Romero and Anasofia Colon while developing this
79
-
project. Without them, this project would have been impossible.
80
+
I would like to thank Gabriel Romero, Pablo Torres, Sergio Rodriguez and
81
+
Anasofia Colon while developing this project. Without them, this project would
82
+
have been impossible.