... | ... | @@ -2,11 +2,13 @@ |
|
|
|
|
|
WSL Version 2 provides a Linux environment on top of your Windows System via virtual Windows environments named Hyper-V. The Linux-kernel which is started inside this environment is equipped with a special driver set to use the provided set of functions of Hyper-V instead of real hardware devices like a disc-drive. This technique is known para-virtualization.
|
|
|
|
|
|
The typical most basic user-interface to WSL is a terminal-window which runs a linux-shell, if not changed by the user this is for Ubuntu a program named bourne again shell (bash).
|
|
|
The typical most basic user-interface to WSL is a **terminal-window** which runs a linux-shell, if not changed by the user this is for Ubuntu a program named bourne again shell (bash).
|
|
|
|
|
|
For using and programming with Dumux we keep with that setting. But the Linux-distribution like Ubuntu inside the WSL has to be equipped with all the tools to fetch and compile the code and you will likely need install some native Windows applications to edit or browsing the code, debug or handle the produced data of simulations.
|
|
|
For using and programming with Dumux we keep with that setting. But the Linux-distribution like Ubuntu inside the WSL has to be equipped with all the tools to fetch and compile the code and you will likely need install some **native Windows applications** to edit or browsing the code, debug or handle the produced data of simulations.
|
|
|
|
|
|
Usually one first checks out the code with tools like **git** directly or indirectly started with python-scripts like **installdumux.py** or **installexternal.py**. You find hints to that when follwing [getting started](https://dumux.org/gettingstarted/) or the [\[DuMux\]-course](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux-course/-/blob/master/README.md)
|
|
|
You also have to be familiar with methods how to access files within the WSL from Windows, and sometimes also the other way around, i.e. accessing your windows drives from the Linux commandline in the terminal-window.
|
|
|
|
|
|
Usually one first checks out the code with tools like **git** directly or indirectly started with python-scripts like **installdumux.py** and for other parts with **installexternal.py**. You find hints to that when follwing [getting started](https://dumux.org/gettingstarted/) or the [DuMux-course](https://git.iws.uni-stuttgart.de/dumux-repositories/dumux-course/-/blob/master/README.md).
|
|
|
|
|
|
**Code editing** can be done either
|
|
|
|
... | ... | @@ -15,11 +17,13 @@ Usually one first checks out the code with tools like **git** directly or indire |
|
|
|
|
|
**Compiling Dumux** is done via **shell-commands** which can be entered in WSL **terminal-window**.
|
|
|
|
|
|
**Visualizing** data-files is done with a **native Windows application** like paraview for Windows
|
|
|
**Visualizing** data-files is done with a **native Windows application** like paraview for Windows.
|
|
|
|
|
|
Running the integrated development (IDE) **Visual Studio Code** natively for Windows with an extension for working with code living inside of a WSL.
|
|
|
|
|
|
Working this way has the advantage that you do not need to run any Linux application with graphical output, so you do not have to care about making graphics work for it.
|
|
|
Working this way has the advantage that you do not need to run any Linux application with graphical output, so you do not have to care about making graphics work for it.
|
|
|
|
|
|
Note if your system has limited resources, do not consider to run the IDE. Also setting up and learning an IDE can be time consuming, so just doing the tasks of Dumux-course this can be to much in the beginning. You can always browse the code with the file-manager Explorer and text-editors and also online with by browsing the online [doxygen-documentation](https://dumux.org/docs/).
|
|
|
|
|
|
# Installation
|
|
|
|
... | ... | |