- unpack OpenMesh
- go to OpenMesh folder and create a folder called "build" inside
- open qt-cmd-prompt as administrator (needed to install)
cmake-gui
- fill in path to source and build-directory
- click Configure and choose mingw-makefiles
- click Generate
- close CMake-Gui and switch back to cmd-prompt
- navigate to build folder
#!/bin/bash | |
# .local/bin zu PATH hinzufügen, automatisch bei öffnen des Terminals | |
# an ~/.bashrc anhängen | |
echo "export PATH=\$PATH:~/.local/bin" >> ~/.bashrc | |
#bashrc neu laden | |
source ~/.bashrc | |
# setuptools laden und für user installieren | |
wget https://bootstrap.pypa.io/ez_setup.py -O - | python - --user | |
#bashrc neu laden |
# revert ALL changes recursively | |
svn revert -R . | |
# undo multiple commits | |
svn merge -c -REV_X,-REV_Y,-REV_Z . | |
svn commit -m "reverted revisions x, y, z" |
sudo apt-get install xzdec | |
tlmgr init-usertree | |
tlmgr install sourcesanspro |
#!/bin/bash | |
# Script for installing tmux on systems where you don't have root access. | |
# tmux will be installed in $APP_DIR/bin. | |
# It's assumed that wget and a C/C++ compiler are installed. | |
# exit on error | |
set -e | |
TMUX_VERSION=2.2 |
#!/usr/bin/env python3 | |
# -*- coding: utf-8 -*- | |
import multiprocessing as mp | |
from time import sleep | |
def task(exit_evt, id): | |
while not exit_evt.is_set(): | |
pass |
npx eslint src -f compact | awk -F ":" '{print $1}' | uniq | head -n -2 | xargs code -r |
A Virtual Environment is a tool to keep the dependencies required by different projects in separate places, by creating virtual Python environments for them. It solves the “Project X depends on version 1.x but, Project Y needs 4.x” dilemma, and keeps your global site-packages directory clean and manageable. - The Hitchhiker’s Guide to Python!
Virtual Environments werden also dazu genutzt um verschiedene Softwareprojekte und ihre Abhängigkeiten voneinander zu isolieren. Ein netter nebeneffekt ist, das Installation aus dem Python Package Index (pip) ohne Administratorrechte erfolgen können, weil die Pakete im Verzeichnis des Virtual Environments installiert werden.
Jedes Virtual Environment hat seine eigenen site-packages
sowie pip
- und python
-Kommandos. Dabei wird der Interpreter nicht jedes neu installiert, sondern über Symlinks verknüpft.