update readme

readme.md

@@ -0,0 +1,25 @@
+# Build ed esecuzione
+
+## Build a due fasi
+Creazione del file .wasm con l'immagine di emcc e creazione del container con supporto wasm.
+`docker build --platform wasi/wasm -t main-wasm .`
+
+## Run
+Esecuzione container con platform wasm.
+`docker run --runtime=io.containerd.wasmedge.v1 --platform=wasi/wasm main-wasm`
+
+# TODO
+## Studio
+
+- studio wasm
+- compilare c++ con wasm
+- creazione container con wasm runtinme
+- definizione tag per codice
+
+## Python module
+- divide il codice in diverse task
+- aggrega le task in base al target
+
+## Build e run
+- container che builda tutti i task
+- run del container con wasm

task-splitter/readme.md

@@ -5,7 +5,6 @@ Tha annotation must tell the splitter how to aggregate and where to send each ta
 
 The code will be processed and splitted into possible modules. Inside the path /build will be created a directory for each module. Inside there will be the wasm compiled bytecode, a file scheduler.config that will list all the information that schedule could need to schedule the module.
 
-
 ## Targets
 Possible devices that run the task:
 - Cloud device, prossibly the same cloud that runs the scheduler
@@ -19,4 +18,4 @@ List of possible annotations:
 - `@TaskGeneric` defines a generic task that can run everywere
 - `@CloudSpecific` runs only on cloud
 - `@EdgeSpecific` runs only on edge
-- `@EndDeviceSpecific` runs only on end device, in particular the device can be specified with `@EndDeviceSpecific(device_name)`
+- `@EndDeviceSpecific` runs only on end device, in particular the device can be specified with `@EndDeviceSpecific(device_name)`

todo.md

@@ -1,14 +0,0 @@
-# Studio
-
-- studio wasm
-- compilare c++ con wasm
-- creazione container con wasm runtinme
-- definizione tag per codice
-
-# Python module
-- divide il codice in diverse task
-- aggrega le task in base al target
-
-# Build e run
-- container che builda tutti i task
-- run del container con wasm