Skip to content
Snippets Groups Projects
Commit ed1f4dd4 authored by Jingwei Tang's avatar Jingwei Tang
Browse files

Update README.md

parent 9ccd96b4
No related branches found
No related tags found
No related merge requests found
......@@ -41,7 +41,7 @@ If you are using linux with a virtual machine on Windows, it is *strongly recomm
### Note for Windows users
`libigl` supports the **Microsoft Visual Studio 2015** compiler and later, in *64bit* mode. You can download *Visual Studio 2019 Community* for free from [here](https://visualstudio.microsoft.com/vs/).
The code depends on `libigl`. It supports the **Microsoft Visual Studio 2015** compiler and later, in *64bit* mode. You can download *Visual Studio 2019 Community* for free from [here](https://visualstudio.microsoft.com/vs/).
### Cloning the Exercise Repository
......@@ -49,11 +49,11 @@ Before you are able to clone your private exercise repository, you need to have
In the next step you need to clone it to your local hard drive:
```
git clone --recurse-submodules https://gitlab.ethz.ch/'Your_Git_Username'/engtool21.git
git clone https://gitlab.ethz.ch/'Your_Git_Username'/engtool21.git
```
`'Your_Git_Username'` needs to be replaced accordingly. This can take a moment.
Next, cd into the newly created folder, and run the following commands inside the relevant subfolder to setup the build folder:
Next, `cd` into the newly created folder, and run the following commands inside the relevant subfolder to setup the build folder:
```
cd engtool21; mkdir build
cd build
......@@ -84,4 +84,4 @@ Lastly, move to your `master` branch and merge updates into yours:
git checkout master
git merge upstream/master
```
Note that you need to run the first line *only once* for adding, and the following steps (cmake as well!) should be done again for new updates.
\ No newline at end of file
Note that you need to run the first line *only once* for adding, and the following steps (cmake as well!) should be done again for new updates.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment