PerconaFT is built using CMake >= 2.8.9. Out-of-source builds are
PerconaFT is built using CMake >= 2.8.9. Out-of-source builds are
recommended. You need a C++11 compiler, though only GCC >= 4.7 and
recommended. You need a C++11 compiler, though only some versions
Apple's Clang are tested. You also need zlib development packages
of GCC >= 4.7 and Clang are tested. You also need zlib development
(`yum install zlib-devel` or `apt-get install zlib1g-dev`).
packages (`yum install zlib-devel` or `apt-get install zlib1g-dev`).
You will also need the source code for jemalloc, checked out in
You will also need the source code for jemalloc, checked out in
`third_party/`.
`third_party/`.
...
@@ -42,16 +40,16 @@ CC=gcc47 CXX=g++47 cmake \
...
@@ -42,16 +40,16 @@ CC=gcc47 CXX=g++47 cmake \
cmake --build.--targetinstall
cmake --build.--targetinstall
```
```
This will build `libtokudb.so` and `libtokuportability.so` and install it,
This will build `libft.so` and `libtokuportability.so` and install it,
some header files, and some examples to `percona-ft/prefix/`. It will also
some header files, and some examples to `percona-ft/prefix/`. It will also
build jemalloc and install it alongside these libraries, you should link
build jemalloc and install it alongside these libraries, you should link
to that if you are planning to run benchmarks or in production.
to that if you are planning to run benchmarks or in production.
### Platforms
### Platforms
PerconaFT is supported on 64-bit Centos, should work on other 64-bit linux
PerconaFT is supported on 64-bit Centos, Debian, and Ubuntu and should work
distributions, and may work on OSX 10.8 and FreeBSD. PerconaFT is not
on other 64-bit linux distributions, and may work on OSX 10.8 and FreeBSD.
supported on 32-bit systems.
PerconaFT is not supported on 32-bit systems.
[Transparent hugepages][transparent-hugepages] is a feature in newer linux
[Transparent hugepages][transparent-hugepages] is a feature in newer linux
kernel versions that causes problems for the memory usage tracking
kernel versions that causes problems for the memory usage tracking
...
@@ -97,16 +95,9 @@ We have two publicly accessible mailing lists for TokuDB:
...
@@ -97,16 +95,9 @@ We have two publicly accessible mailing lists for TokuDB:
- tokudb-dev@googlegroups.com is for discussion of the development of
- tokudb-dev@googlegroups.com is for discussion of the development of
TokuDB.
TokuDB.
and two for TokuMX:
- tokumx-user@googlegroups.com is for general and support related
questions about the use of TokuMX.
- tokumx-dev@googlegroups.com is for discussion of the development of
TokuMX.
All source code and test contributions must be provided under a [BSD 2-Clause][bsd-2] license. For any small change set, the license text may be contained within the commit comment and the pull request. For larger contributions, the license must be presented in a COPYING.<feature_name> file in the root of the PerconaFT project. Please see the [BSD 2-Clause license template][bsd-2] for the content of the license text.
All source code and test contributions must be provided under a [BSD 2-Clause][bsd-2] license. For any small change set, the license text may be contained within the commit comment and the pull request. For larger contributions, the license must be presented in a COPYING.<feature_name> file in the root of the PerconaFT project. Please see the [BSD 2-Clause license template][bsd-2] for the content of the license text.
// I know that Barry prefers the single-return case, but writing the code this way means that the compiler will complain if I forget something in the enum. -Bradley
// I know that Barry prefers the single-return case, but writing the code this way means that the compiler will complain if I forget something in the enum. -Bradley
// I know that Barry prefers the single-return case, but writing the code this way means that the compiler will complain if I forget something in the enum. -Bradley
// I know that Barry prefers the single-return case, but writing the code this way means that the compiler will complain if I forget something in the enum. -Bradley