docs/BuildSource.md
If you are building from source for non-development purposes
(i.e., you want to run TimescaleDB, not submit a patch), you should
always use a release-tagged commit and not build from main.
See the Releases tab for the latest release.
Prerequisites:
postgresql-server-dev-17 package
for Linux, Postgres.app for MacOS)git clone [email protected]:timescale/timescaledb.git
cd timescaledb
# Find the latest release and checkout, e.g. for 2.15.0:
git checkout 2.15.0
# Bootstrap the build system
./bootstrap
# To build the extension
cd build && make
# To install
make install
Note, if you have multiple versions of PostgreSQL installed you can specify the path to pg_config
that should be used by using ./bootstrap -DPG_CONFIG=/path/to/pg_config.
Please see our additional configuration instructions.
If you are building from source for non-development purposes
(i.e., you want to run TimescaleDB, not submit a patch), you should
always use a release-tagged commit and not build from main.
See the Releases tab for the latest release.
Prerequisites:
pg_config and cmakeIf using Visual Studio 2017 with the CMake and Git components, you should be able to simply clone the repo and open the folder in Visual Studio which will take care of the rest.
If you are using an earlier version of Visual Studio, then it can be built in the following way:
git clone [email protected]:timescale/timescaledb.git
cd timescaledb
# Find the latest release and checkout, e.g. for 2.15.0:
git checkout 2.15.0
# Bootstrap the build system
bootstrap.bat
# To build the extension from command line
cmake --build ./build --config Release
# To install
cmake --build ./build --config Release --target install
# Alternatively, build in Visual Studio via its built-in support for
# CMake or by opening the generated build/timescaledb.sln solution file.