1f28470cf4
Further reading: * https://forum.qt.io/topic/78540/qstringliteral-vs-qlatin1string/2 * https://woboq.com/blog/qstringliteral.html * https://www.qt.io/blog/2014/06/13/qt-weekly-13-qstringliteral tl;dr: QLatin1Literal uses less memory than QStringLiteral; however, since most Qt APIs require a QString argument, there's extra runtime cost of converting QLatin1Strings to QStrings. QStringLiteral uses a little more memory but constructs its QStrings at compile time. ok, the `prefer-qstringliteral` branch is getting out of control: the secondary goal of fixing a .clang-tidy issue is causing more diffs than the primary goal. So, I'm breaking it into two separate PRs. |
||
|---|---|---|
| .tx | ||
| Transmission.xcodeproj | ||
| cli | ||
| cmake | ||
| daemon | ||
| dist/msi | ||
| docker/code_style | ||
| extras | ||
| gtk | ||
| libtransmission | ||
| m4 | ||
| macosx | ||
| po | ||
| qt | ||
| release/windows | ||
| third-party | ||
| utils | ||
| web | ||
| .gitignore | ||
| .gitmodules | ||
| .jsbeautifyrc | ||
| AUTHORS | ||
| CMakeLists.txt | ||
| COPYING | ||
| ChangeLog | ||
| Makefile.am | ||
| NEWS.md | ||
| README.md | ||
| appveyor.yml | ||
| autogen.sh | ||
| code_style.sh | ||
| configure.ac | ||
| docker-compose.yml | ||
| transmission-gtk.spec.in | ||
| uncrustify.cfg | ||
| update-version-h.sh | ||
README.md
About
Transmission is a fast, easy, and free BitTorrent client. It comes in several flavors:
- A native Mac OS X GUI application
- GTK+ and Qt GUI applications for Linux, BSD, etc.
- A headless daemon for servers and routers
- A web UI for remote controlling any of the above
Visit https://transmissionbt.com/ for more information.
Command line interface notes
Transmission is fully supported in transmission-remote, the preferred cli client.
Three standalone tools to examine, create, and edit .torrent files exist: transmission-show, transmission-create, and transmission-edit, respectively.
Prior to development of transmission-remote, the standalone client transmission-cli was created. Limited to a single torrent at a time, transmission-cli is deprecated and exists primarily to support older hardware dependent upon it. In almost all instances, transmission-remote should be used instead.
Different distributions may choose to package any or all of these tools in one or more separate packages.
Building
Transmission has an Xcode project file (Transmission.xcodeproj) for building in Xcode.
For a more detailed description, and dependencies, visit: https://github.com/transmission/transmission/wiki
Building a Transmission release from the command line
$ tar xf transmission-2.92.tar.xz
$ cd transmission-2.92
$ mkdir build
$ cd build
$ cmake ..
$ make
$ sudo make install
Building Transmission from the nightly builds
Download a tarball from https://build.transmissionbt.com/job/trunk-linux/ and follow the steps from the previous section.
If you're new to building programs from source code, this is typically easier than building from Git.
Building Transmission from Git (first time)
$ git clone https://github.com/transmission/transmission Transmission
$ cd Transmission
$ git submodule update --init
$ mkdir build
$ cd build
$ cmake ..
$ make
$ sudo make install
Building Transmission from Git (updating)
$ cd Transmission/build
$ make clean
$ git pull --rebase --prune
$ git submodule update
$ cmake ..
$ make
$ sudo make install
Contributing
Code Style
You would want to setup your editor to make use of uncrustify.cfg and .jsbeautifyrc configuration files located in the root of this repository.
If for some reason you are unwilling or unable to do so, there is a shell script which you could run either directly or via docker-compose:
$ ./code_style.sh
or
$ docker-compose build --pull
$ docker-compose run --rm code_style