Docker #38

.devcontainer/Dockerfile

@@ -0,0 +1,25 @@
+# See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.177.0/containers/javascript-node/.devcontainer/base.Dockerfile
+
+# [Choice] Node.js version: 16, 14, 12
+ARG VARIANT="16-buster"
+FROM mcr.microsoft.com/vscode/devcontainers/javascript-node:0-${VARIANT}
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+#     && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment if you want to install an additional version of node using nvm
+# ARG EXTRA_NODE_VERSION=10
+# RUN su node -c "source /usr/local/share/nvm/nvm.sh && nvm install ${EXTRA_NODE_VERSION}"
+
+# [Optional] Uncomment if you want to install more global node modules
+# RUN su node -c "npm install -g <your-package-list-here>"
+
+RUN cd /home/node
+RUN apt-get -y install git
+RUN mkdir -p /home/node/emsdk
+RUN cd /home/node/emsdk
+RUN git clone https://github.com/emscripten-core/emsdk.git /home/node/emsdk
+
+RUN /home/node/emsdk/emsdk install latest
+RUN /home/node/emsdk/emsdk activate latest

.devcontainer/devcontainer.json

@@ -0,0 +1,37 @@
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the README at:
+// https://github.com/microsoft/vscode-dev-containers/tree/v0.177.0/containers/javascript-node
+{
+    "name": "Node.js",
+    "build": {
+        "dockerfile": "Dockerfile",
+        // Update 'VARIANT' to pick a Node version: 12, 14, 16
+        "args": { "VARIANT": "16" }
+    },
+
+    // Set *default* container specific settings.json values on container create.
+    "settings": {
+        "terminal.integrated.profiles.linux": {
+            "zsh (login)": {
+                "path": "zsh",
+                "args": ["-l"]
+            }
+        }
+    },
+
+    // Add the IDs of extensions you want installed when the container is created.
+    "extensions": [
+        "dbaeumer.vscode-eslint",
+        "esbenp.prettier-vscode",
+        "eamodio.gitlens",
+        "pflannery.vscode-versionlens"
+    ],
+
+    // Use 'forwardPorts' to make a list of ports inside the container available locally.
+    "forwardPorts": [80],
+
+    // Use 'postCreateCommand' to run commands after the container is created.
+    "postCreateCommand": "npm install",
+
+    // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+    "remoteUser": "node"
+}

.gitignore

@@ -46,4 +46,4 @@ debug_output
 .bin
 build
 *.log
-node_modules
+node_modules

.vscode/extensions.json

@@ -0,0 +1,12 @@
+{
+  "recommendations": [
+    "eamodio.gitlens",
+    "pflannery.vscode-versionlens",
+    "esbenp.prettier-vscode",
+    "ms-azuretools.vscode-docker",
+    "github.vscode-pull-request-github",
+    "ms-vscode-remote.remote-containers",
+    "dbaeumer.vscode-eslint",
+    "msjsdiag.debugger-for-chrome"
+  ]
+}

README.md

@@ -44,17 +44,23 @@ ifcApi.CloseModel(modelID);
 
 The WASM library is built through emscripten, please see [the emscripten installation guide](https://emscripten.org/docs/getting_started/downloads.html) for information on how to set up emscripten. Afterwards both `setup-env` and `em++` need to be in your path.
 
+* For docker with vscode use `clone repository` to get more speed. First build will take more time.
+
 ### WASM library
 
 Run `npm install` to install all dependencies.
+* This is executed by default in the docker rebuild
 
 Run `npm run setup-env` whenever you open a new terminal, this will set up the required emscripten environment variables for you to compile code.
+* If you are using docker then run 
+  * `source /home/node/emsdk/emsdk_env.sh` instead for every new terminal
+  * `export EM_NODE_JS=/home/node/emsdk/node/14.15.5_64bit/bin/node`
+    * You might be able to skip this later, but atm you need it due to error you get with EM_NODE_JS
 
 Run `npm run build-release` to build a release version of the wasm binary and the accompanying web-ifc api. It will be placed in `./dist`.
 
 Run `npm run dev` to launch a development server with a basic ifc file viewer.
 
-
 ### Stand alone C++ executable
 
 Compiling the library to a standalone executable requires use of CMAKE. For visual studio code, the easiest way is by installing [cmake-tools](https://marketplace.visualstudio.com/items?itemName=ms-vscode.cmake-tools).