Fiddling arround for a long time

Author: tobixdev

ReadMe.md

@@ -1,32 +1,31 @@
 # Acknowledgements
 
-Thanks to [dinfuehr](https://gist.github.com/dinfuehr) for providing [cacao-jvm-dockerfile](https://gist.github.com/dinfuehr/ab83ad825cd24be0e816588d0465a7fb), which is the core of this repository.
+Thanks to [dinfuehr](https://gist.github.com/dinfuehr) for providing [cacao-jvm-dockerfile](https://gist.github.com/dinfuehr/ab83ad825cd24be0e816588d0465a7fb), on which this guide is based.
 
 # What is this?
 
-This guide summarizes the setup of a [cacaojvm](http://www.cacaojvm.org/) dev container using Windows 10 with docker. In theory a similar approach should work on Linux based systems, if you want to isolate your cacao-dev environment from your day-to-day system.
+This guide summarizes the setup of a [cacaojvm](http://www.cacaojvm.org/) dev container using Windows 10 with docker.
 
-This repository solely extends the gist provided by [dinfuehr](https://gist.github.com/dinfuehr) with an "Getting Started" installation guide.
+In theory a similar approach should work on Linux based systems, if you want to isolate your cacao-dev environment from your day-to-day system.
 
 Tools used in this guide:
 * Windows 10 Pro
 * docker for Desktop
 * Visual Studio Code
- * [Remote - Containers Extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers)
+    * [Remote - Containers Extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers)
 
 # Getting Started
 
 * Fork the repository using your BitBucket account. [Further information](http://c1.complang.tuwien.ac.at/cacaowiki/Draft/CodeSubmissionProcess?action=show&redirect=Contributing) on the code submission process.
-* Clone the forked repository into a well known location (e.g. `C:\Development`)
+* Change the mercurial repository link in the docker file (`RUN hg clone https://bitbucket.org/cacaovm/cacao-staging`) to your forked repository.
 * Open VS Code
-* Open the cacao folder in the dev container
- * Press F1 to open the command palette.
- * Execute the command `Remove-Containers: Open Folder in Container`
- * Select the folder created through cloning this repository in Step #1.
-* Let VS Code do the rest
- * VS Code will setup the container for you
+* Create the dev container
+    * Press F1 to open the command palette.
+    * Execute the command `Remove-Containers: Reopen in Container`
+* VS Code/docker will setup the container for you
 * Verify the installation
- * Toggle the integrated terminal
- * Open a new bash shell
- * Try to locate the `cacao-staging` repository under `/code/cacao-staging`
-* You should now be able to use the `Open Folder` command to open the folder `/code` in the container
+    * Toggle the integrated terminal
+    * Open a new bash shell
+    * Try to locate the `cacao-staging` repository under `/code/cacao-staging`
+* You should now be able to use the `Open Folder` command to open the folder `/code` in the container
+* Validate the environment by invoking `make check` in the `/code/build` directory

dockerfile

@@ -1,8 +1,6 @@
 FROM ubuntu:16.04
-MAINTAINER [email protected]
 
-RUN apt-get update \
-    && apt-get install -y \
+RUN  apt-get install -y \
         mercurial \
         wget \
         unzip \
@@ -15,10 +13,16 @@ RUN apt-get update \
         libiberty-dev \
         fastjar \
         zlib1g-dev \
-
-        # for add-apt-repository
         software-properties-common
 
+RUN apt update \
+    && apt-get install -y software-properties-common \
+    && add-apt-repository ppa:ubuntu-toolchain-r/test \
+    && apt update \
+    && apt install gcc-9 g++-9 -y \
+    && update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-9 90 --slave /usr/bin/g++ g++ /usr/bin/g++-9 --slave /usr/bin/gcov gcov /usr/bin/gcov-9 \\
+    && update-alternatives --config gcc
+
 RUN add-apt-repository ppa:openjdk-r/ppa -y \
     && apt-get update \
     && apt-get install -y openjdk-7-jdk
@@ -27,10 +31,13 @@ RUN mkdir -p /code/tools
 WORKDIR /code
 
 RUN cd tools \
-    && wget http://search.maven.org/remotecontent\?filepath\=junit/junit/4.10/junit-4.10.jar \
-      -O junit-4.10.jar \
+    && wget https://repo1.maven.org/maven2/junit/junit/4.12/junit-4.12.jar -O junit-4.12.jar \
     && mkdir -p /usr/share/java \
-    && cp junit-4.10.jar /usr/share/java/junit4.jar
+    && cp junit-4.12.jar /usr/share/java/junit4.jar
+
+RUN cd tools \
+    && wget https://repo1.maven.org/maven2/org/hamcrest/hamcrest-all/1.3/hamcrest-all-1.3.jar -O hamcrest-1.3.jar \
+    && cp hamcrest-1.3.jar /usr/share/java/hamcrest.jar
 
 RUN cd tools \
     && wget http://ufpr.dl.sourceforge.net/project/jasmin/jasmin/jasmin-2.4/jasmin-2.4.zip \
@@ -41,7 +48,11 @@ RUN cd tools \
     && wget ftp://ftp.gnu.org/gnu/classpath/classpath-0.99.tar.gz \
     && tar xzf classpath-0.99.tar.gz
 
-RUN hg clone https://bitbucket.org/cacaovm/cacao-staging
+RUN cd tools \
+    && wget https://sourceforge.net/projects/boost/files/boost/1.61.0/boost_1_61_0.tar.gz \
+    && tar xzf boost_1_61_0.tar.gz
+
+RUN hg clone https://bitbucket.org/tobixdev/cacao-staging/
 
 RUN cd tools/classpath-0.99 \
     && sh autogen.sh \
@@ -53,6 +64,6 @@ RUN cd cacao-staging && sh autogen.sh
 
 RUN mkdir build \
     && cd build \
-    && ../cacao-staging/configure --enable-disassembler \
-    && make \
-    && make check
+    && ../cacao-staging/configure --enable-debug --enable-compiler2 --enable-replacement --enable-logging --with-java-runtime-library=gnuclasspath --with-java-runtime-library-prefix=/usr/local/classpath --with-junit-jar=/usr/share/java/junit4.jar:/usr/share/java/hamcrest.jar
+
+ENV CPATH=/code/tools/boost_1_61_0/