User Tools
qcl:linux
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
qcl:linux [2020/04/24 17:31] kemal.oeztas |
qcl:linux [2020/11/27 14:10] (current) kemal.oeztas |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | =====nextnano.QCL on Linux===== | + | =====nextnano.NEGF on Linux===== |
| - | nextnano.QCL can be executed on Linux using the Wine compatibility layer. See below for the installation intstructions for several Linux distrubutions. | + | nextnano.NEGF can be executed on Linux using the Wine compatibility layer. See below for the installation intstructions for several Linux distrubutions. |
| - | ===Using nextnano.QCL with Wine=== | + | ===Using nextnano.NEGF with Wine=== |
| - | After having downloaded the nextnano.QCL zip file from [[https://www.nextnano.com/nextnano3/restricted/download/update/nextnano.QCL.zip|https://www.nextnano.com/nextnano3/restricted/download/update/nextnano.QCL.zip]], please extract it to your preferred path and copy (not just move!) the ''Native.dll'' file from the folder ''Bin64.1.0.0.74'' to the parent folder including ''nextnano.QCL.exe'' if needed. Having access to the material database ''Material_Database.xml'' and the license file ''License_nnQCL.lic'', one can run an input file as follows: | + | After having downloaded the nextnano.NEGF zip file from [[https://www.nextnano.com/nextnano3/restricted/download/update/nextnano.NEGF.zip|https://www.nextnano.com/nextnano3/restricted/download/update/nextnano.NEGF.zip]], please extract it to your preferred path. Having access to the material database **Material_Database.xml** and the license file **License_nnQCL.lic**, one can run an input file as follows: |
| <code> | <code> | ||
| - | wine /your_directory/nextnano.QCL.exe /your_directory/your_input_file.xml /your_directory/Material_Database.xml /your_directory/License_nnQCL.lic > test_input.log & | + | wine /your_directory/nextnano.NEGF.exe /your_directory/your_input_file.xml /your_directory/Material_Database.xml /your_directory/License_nnQCL.lic |
| </code> | </code> | ||
| - | ===Ubuntu 19.10=== | + | ===Ubuntu 20.10=== |
| - | On Ubuntu 19.10, the following commands will install the stable branch of Wine. | + | On Ubuntu 20.10, following commands will install the stable branch of Wine: |
| <code> | <code> | ||
| sudo dpkg --add-architecture i386 | sudo dpkg --add-architecture i386 | ||
| wget -nc https://dl.winehq.org/wine-builds/winehq.key | wget -nc https://dl.winehq.org/wine-builds/winehq.key | ||
| sudo apt-key add winehq.key | sudo apt-key add winehq.key | ||
| - | sudo apt-add-repository 'deb https://dl.winehq.org/wine-builds/ubuntu/ eoan main' | + | sudo add-apt-repository 'deb https://dl.winehq.org/wine-builds/ubuntu/ groovy main' |
| sudo apt update | sudo apt update | ||
| sudo apt install --install-recommends winehq-stable | sudo apt install --install-recommends winehq-stable | ||
| Line 69: | Line 69: | ||
| ===Configuring Wine=== | ===Configuring Wine=== | ||
| - | After installing Wine, if you encounter errors about Mono, a useful trick is to delete the folder **.Wine** and force Wine to download and install Gecko and Mono automatically. Normally, Wine will suggest installing these the first time it is used. Furthermore opening the ''wine uninstaller'' and removing interfering applications might solve some problems. In the end, we are able to use Wine without installing Winetricks or dotnet manually. If you are working on a remote machine, you might need to enable X11 forwarding to see the windows created during the Wine configuration. This is done by connecting via **ssh -X** and modifying the **ssh.config** file under **etc/ssh** accordingly. On RHEL/CentOS 8 some dependencies might need to be installed by the following command | + | After installing Wine, if you encounter errors about Mono, a useful trick is to delete the folder **.Wine** and force Wine to download and install Gecko and Mono automatically. Normally, Wine will suggest installing these the first time it is used. Furthermore, opening the ''wine uninstaller'' and removing interfering applications might solve some problems. In the end, we are able to use Wine without installing Winetricks or dotnet manually. If you are working on a remote machine, you might need to enable X11 forwarding to see the windows created during the Wine configuration. This is done by connecting via **ssh -X** and modifying the **ssh.config** file under **etc/ssh** accordingly. On RHEL/CentOS 8 some dependencies might need to be installed by the following command: |
| <code> | <code> | ||
| # dnf install xorg-x11-server-Xorg xorg-x11-xauth xorg-x11-apps -y | # dnf install xorg-x11-server-Xorg xorg-x11-xauth xorg-x11-apps -y | ||
| </code> | </code> | ||
qcl/linux.1587749495.txt.gz · Last modified: 2020/04/24 17:31 by kemal.oeztas
