Are you one of those Amazon Echo users that have the house full of X10 devices and you’re sad you can’t use them with the Echo? There’s a way you can control them if you have a Linux server around, even if it’s something as simple and cheap like a Raspberry Pi!
It’s actually pretty easy to cross-compile qBittorrent on Linux for Windows targets using MXE, a cross environment based on the MinGW-w64 toolchain.
The MinGW-w64 project is an improvement on the original MinGW (Minimalist GNU for Windows) project to support 64-bits targets. Currently MXE supports two MinGW-w64 targets: i686-w64-mingw32 for 32-bits executables and x86_64-w64-mingw32 for 64-bits executables.
This is a guide to cross-compile qBittorrent on Linux for Windows 64-bits only. As usual we’ll use Debian for this.
The most popular questions about git always seem to be the same: When should I commit? How often should I commit? What exactly is a branch in my project? What is a tag?
Before getting into dirty grounds (and we’ll eventually get there) you should know a little about best practices when using git.
Note: If you haven’t read the post A Useful Git Tutorial – Part I you can check it here.
You know what I really hate about git? Calling working directories as repositories and real repositories as bare repositories. This is somehow confusing for people like me coming from older and outdated control version systems like CVS or SVN.
But if you keep in mind what I said above and give git a chance you’d realize is the most powerful control version system ever created.
There are tons of git tutorials out there but I’m pretty sure none of them cover how 90% of the people use git: clone an existing project, make their own changes and try to keep them updated with the original project. Eventually submit patches.