Skip to main content

Building: TinyORM

Introduction​

Stability: 2 - Stable

The build systems supported out of the box are CMake and qmake.

info

All examples below assume that pwsh runs on Windows and bash runs on Linux.

Common Prerequisites​

Install the required dependencies before starting.

warning

The QSqlDatabase depends on QCoreApplication from Qt v6.5.3 so you must create the QCoreApplication instance before you will call anything from the TinyORM library. 🫤 The change was made here.

Windows Prerequisites​

Build environment scripts​

The Visual Studio does not provide vcvars scripts for pwsh, you can use vcvars64.ps1 provided by TinyORM in the tools/ folder. Place them on the $env:Path user/system path and they will be available system-wide.

The same is true for the Qt Framework, it doesn't provide qtenv scripts for pwsh too. You can create your own script, place it on the $env:Path user/system path and it will be available system-wide.

Here is one simple example for pwsh and bash on Linux.

qtenv6.ps1
#!/usr/bin/env pwsh

Set-StrictMode -Version 3.0

Write-Host 'Setting up environment for Qt 6.7.2 usage...' -ForegroundColor Magenta
Write-Host

$Script:QtRoot = $env:TINY_QT_ROOT ?? 'C:\Qt'

$env:Path = "$Script:QtRoot\6.7.2\msvc2019_64\bin;" + $env:Path

. vcvars64.ps1
info

These scripts consider the TINY_QT_ROOT environment variable that should point to the Qt installation folder, you can define this environment variable globally in your OS.

info

You can't execute these qtenvX scripts, they have to be sourced like source qtenvX or . qtenvX.

Open Local Security Policy, go to Local Policies - User Rights Assignment, open Create symbolic links and add your user account or user group, restart when it doesn't apply immediately.

Folders structure​

All tinyorm.org examples are based on the following folders structure. The tom folder will contain a migrations console application.

tip

You can set the root and application folder paths in the form below and they will be used across the whole www.tinyorm.org website. 🥳 The pwsh shell is supposed to use on Windows and the bash shell on Linux, but it is not a requirement.

Current pwsh path 




├──
│   ├── HelloWorld/
│   |   ├── HelloWorld/
│   |   ├── HelloWorld-builds-cmake/
│   |   |   └── build-debug/
│   |   └── HelloWorld-builds-qmake/
│   |       └── build-debug/
│   ├── TinyORM/
│   |   ├── TinyORM/
│   |   ├── TinyORM-builds-cmake/
│   |   │   ├── build-gcc-debug/
│   |   │   ├── build-gcc-release/
│   |   │   └── build-clang-debug/
│   |   └── TinyORM-builds-qmake/
│   |       ├── build-debug/
│   |       ├── build-TinyORM-Desktop_Qt_6_7_2_MSVC2019_64bit-Debug/
│   |       └── build-TinyORM-Desktop_Qt_6_7_2_MSYS2_UCRT64_64bit-Release/
│   └── tom/
│       ├── tom/
│       │   └── database/
│       │       ├── migrations/
│       │       ├── seeders/
│       │       ├── migrations.pri
│       │       └── seeders.pri
│       ├── tom-builds-cmake/
│       │   └── build-TinyORM-Desktop_Qt_6_7_2_MSVC2019_64bit-Debug/
│       └── tom-builds-qmake/
│           ├── build-TinyORM-Desktop_Qt_6_7_2_MSYS2_UCRT64_64bit-Release/
│           └── build-TinyORM-Desktop_Qt_6_7_2_MSVC2019_64bit-Debug/
├── tmp/
└── vcpkg/
danger

Avoid paths with spaces with the qmake build system, it will not compile.

tip

You can force the QtCreator to generate a build folders structure as is described above.

To generate the required folders structure set the Settings - Build & Run - Default Build Properties - Default build directory to:
../%{Project:Name}-builds-%{BuildSystem:Name}/%{JS: Util.asciify("build-%{Project:Name}-%{Kit:FileSystemName}-%{BuildConfig:Name}")}

Getting started​

Prepare compilation environment, we need to put the Qt Framework and Visual Studio MSVC compiler on the path on Windows. The compiler is already on the path on Linux and you can export PATH and LD_LIBRARY_PATH for Qt Framework, or use our qtenvX scripts described above.

mkdir 
cd 
$env:Path = 'C:\Qt\6.7.2\msvc2019_64\bin;' + $env:Path
vcvars64.ps1
tip

You can also use the tools/Add-FolderOnPath.ps1 pwsh script to quickly prepend a path or pwd on the system PATH.

vcpkg​

Installing the vcpkg is highly recommended, it simplifies installation of the range-v3 and tabulate dependencies.

git clone git@github.com:microsoft/vcpkg.git
cd vcpkg
.\bootstrap-vcpkg.bat

Add vcpkg on the system path, add the following to the .bashrc or .zshrc on Linux.

export PATH=/vcpkg${PATH:+:}$PATH

On Windows, open the Environment variables dialog and add vcpkg on the user PATH.

Or you can export it for the current session only.

$env:Path = "\vcpkg;" + $env:Path

Set up vcpkg environment​

To export vcpkg environment variables globally, add it to the .bashrc or .zshrc on Linux, and you can use the Environment variables dialog on Windows.

Linux
export VCPKG_DEFAULT_TRIPLET=x64-linux
#export VCPKG_DEFAULT_HOST_TRIPLET=x64-linux
export VCPKG_MAX_CONCURRENCY=11
export VCPKG_OVERLAY_PORTS="$HOME/.local/share/vcpkg/ports"
export VCPKG_OVERLAY_TRIPLETS="$HOME/.local/share/vcpkg/triplets"
export VCPKG_ROOT="$HOME/Code/c/vcpkg"
info

It is recommended to define these variables globally because the CMake and qmake build system are able to detect the vcpkg installation from them so you don't have to configure them manually to detect the vcpkg installation.

tip

On Windows, it's always better to create these types of variables as user variables instead of system variables in the Environment variables dialog.

C preprocessor macros​

The following table summarizes all the C preprocessor macros defined in the TinyORM library. These C macros are configured by CMake or qmake build systems. They are not sorted alphabetically, but they are sorted by how significant they are.

In the CMake build system, all the C macros are auto-detected / auto-configured or controlled by CMake build options, so you don't have to care too much about them.

In the qmake build is important whether you are building TinyORM library or you are building your application and linking against TinyORM library. When you are building the TinyORM library, all the C macros are auto-detected / auto-configured or controlled by qmake build options, so you don't have to care too much about them.

But a special situation is when you are building your application / library and you are linking against TinyORM library. In this particular case, you must configure all these C macros manually! For this reason, the TinyOrm.pri has been created, so that's not a big deal either. Little more info here.

C Macro NameDescription
TINYORM_LINKING_SHAREDMust be defined when you are linking against TinyORM shared build (dll library), exported classes and functions will be tagged with __declspec(dllimport) on msvc and visibility("default") on GCC >= 4.
TINYORM_BUILDING_SHAREDDefined when TinyORM is built as a dll library (shared build).
TINYORM_DEBUGDefined in the debug build.
TINYORM_NO_DEBUGDefined in the release build.
TINYORM_DEBUG_SQLDefined in the debug build.
TINYORM_NO_DEBUG_SQLDefined in the release build.
TINYORM_MYSQL_PINGEnable Orm::MySqlConnection::pingDatabase() method.
Defined when mysql_ping (qmake) / MYSQL_PING (cmake) configuration build option is enabled.
TINYORM_DISABLE_ORMControls the compilation of all ORM-related source code, when this macro is defined, then only the query builder without ORM is compiled. Also excludes ORM-related unit tests.
Defined when disable_orm (qmake) / ORM (cmake) configuration build option is enabled (qmake) / disabled (cmake).
TINYORM_EXTERN_CONSTANTSDefined when extern constants are used. Extern constants are enabled by default for shared builds and disabled for static builds.
Described at qmake / CMake how it works.
TINYORM_INLINE_CONSTANTSDefined when global inline constants are used.
Defined when inline_constants (qmake) / INLINE_CONSTANTS (cmake) configuration build option is enabled.
TINYORM_TESTS_CODEEnable code needed by unit tests, eg. connection overriding in the Orm::Tiny::Model.
Defined when build_tests (qmake) / BUILD_TESTS (cmake) configuration build option is enabled.
TINYORM_DISABLE_THREAD_LOCALRemove all thread_local storage duration specifiers, it disables multi-threading support.
Defined when disable_thread_local (qmake) / DISABLE_THREAD_LOCAL (cmake) configuration build option is enabled.
TINYTOM_MIGRATIONS_DIRDefault migrations path for the make:migration command, can be an absolute or relative path (to the pwd).
Default value: database/migrations (relative to the pwd)
Defined by TOM_MIGRATIONS_DIR (cmake) configuration build option.
(qmake note) You can use DEFINES += TINYTOM_MIGRATIONS_DIR="\"database/migrations\"" on the command-line or set it in the main conf.pri file.
TINYTOM_MODELS_DIRDefault models path for the make:model command, can be an absolute or relative path (to the pwd).
Default value: database/models (relative to the pwd)
Defined by TOM_MODELS_DIR (cmake) configuration build option.
(qmake note) You can use DEFINES += TINYTOM_MODELS_DIR="\"database/models\"" on the command-line or set it in the main conf.pri file.
TINYTOM_SEEDERS_DIRDefault seeders path for the make:seeder command, can be an absolute or relative path (to the pwd).
Default value: database/seeders (relative to the pwd)
Defined by TOM_SEEDERS_DIR (cmake) configuration build option.
(qmake note) You can use DEFINES += TINYTOM_SEEDERS_DIR="\"database/seeders\"" on the command-line or set it in the main conf.pri file.
TINYORM_USING_PCHDefined if building with precompiled headers.
Controlled by qmake / CMake.
TINYORM_USING_UBSANDefined if building with UBSan.
Defined when ubsan (qmake) / CMake not supported.

Building with CMake​

tip

If something is not clear, you can still look at GitHub Action workflows how the build is done.

First, create a basic folder structure and then clone the TinyORM project.

cd 
mkdir /TinyORM/TinyORM-builds-cmake/build-debug

cd /TinyORM
git clone git@github.com:silverqx/TinyORM.git

Configure & Build (cmake)​

Now you are ready to configure the TinyORM library.

cd TinyORM-builds-cmake/build-debug
cmake.exe `
-S "/TinyORM/TinyORM" `
-B "/TinyORM/TinyORM-builds-cmake/build-debug" `
-G 'Ninja' `
-D CMAKE_BUILD_TYPE:STRING='Debug' `
-D CMAKE_TOOLCHAIN_FILE:FILEPATH="/vcpkg/scripts/buildsystems/vcpkg.cmake" `
-D CMAKE_CXX_SCAN_FOR_MODULES:BOOL=OFF `
-D CMAKE_INSTALL_PREFIX:PATH="/tmp/TinyORM" `
-D BUILD_TESTS:BOOL=OFF `
-D MATCH_EQUAL_EXPORTED_BUILDTREE:BOOL=ON `
-D MYSQL_PING:BOOL=OFF `
-D TOM:BOOL=ON `
-D TOM_EXAMPLE:BOOL=OFF `
-D VERBOSE_CONFIGURE:BOOL=ON
CMake STRICT_MODE option​

The STRICT_MODE CMake configuration option was added in TinyORM v0.38.1. This option was added to avoid the propagation of aggressive strict warning compiler/linker options and Qt definitions from the TinyORM library to user code through the TinyOrm::CommonConfig interface library.

TinyORM uses the strictest warning level options, virtually anything that can be enabled is enabled to produce a better code. I highly recommend enabling this option to produce better code and to follow good practices. It also helps to follow the ISOCPP C++ Core Guidelines standards.

If you want to enable these strict warning options in your code, you can enable the STRICT_MODE CMake configuration option and they will be propagated to your code. You can also enabled it globally using the TINYORM_STRICT_MODE environment variable, and the value of this environment variable will be picked up during initial CMake configuration as the default value for the STRICT_MODE CMake configuration option.

You can achieve the same result by manually linking against the TinyOrm::CommonConfig interface library when the STRICT_MODE is set to OFF.

target_link_libraries(<target> PRIVATE TinyOrm::CommonConfig)
info

The recommended way is to set the TINYORM_STRICT_MODE environment variable to 1 or ON.

Build TinyORM​

And build. You don't have to install it, you can use the build tree directly if you want.

cmake --build . --target all
cmake --install .

Or build and install in one step.

cmake --build . --target install
info

CMake multi-config generators like Ninja Multi-Config or Visual Studio 16 2019 are also supported.

CMake build options​

Option NameDefaultDescription
BUILD_DRIVERSOFFBuild TinyDrivers SQL database drivers (core/common code; replaces QtSql module).
BUILD_MYSQL_DRIVEROFFBuild TinyDrivers MySQL database driver.
Available when: BUILD_DRIVERS
BUILD_SHARED_LIBSONBuild as a shared/static library.
BUILD_TESTSOFFBuild TinyORM unit tests.
BUILD_TREE_DEPLOYONCopy TinyDrivers and TinyMySql libraries to the root of the build tree.
DRIVERS_TYPESharedHow to build and link against TinyDrivers SQL database drivers.
The Static value will be select by default when the BUILD_SHARED_LIBS is OFF.
Supported values: Shared, Loadable, and Static
Available when: BUILD_DRIVERS AND BUILD_SHARED_LIBS
INLINE_CONSTANTSOFFUse inline constants instead of extern constants in the shared build.
OFF is highly recommended for the shared build;
is always ON for the static build.
Available when: BUILD_SHARED_LIBS
MSVC_RUNTIME_DYNAMICONUse MSVC dynamic runtime library (-MD) instead of static (-MT), also considers a Debug configuration (-MTd, -MDd).
Available when: MSVC AND NOT TINY_VCPKG AND NOT DEFINED VCPKG_CRT_LINKAGE AND NOT DEFINED CMAKE_MSVC_RUNTIME_LIBRARY
MYSQL_PINGOFFEnable Orm::MySqlConnection::pingDatabase() method.
ORMONControls the compilation of all ORM-related source code, when this option is disabled, then only the query builder without ORM is compiled. Also excludes ORM-related unit tests.
STRICT_MODEOFFControls propagation of strict compiler/linker options and Qt definitions using the TinyOrm::CommonConfig interface library to the user code.
(highly recommended; can also be set with the TINYORM_STRICT_MODE environment variable; described here).
TOMONControls the compilation of all Tom-related source code, when this option is disabled, then it also excludes Tom-related unit tests.
TOM_EXAMPLEOFFBuild the tom console application example.
TOM_MIGRATIONS_DIR-Default migrations path for the make:migration command, can be an absolute or relative path (to the pwd).
Default value: database/migrations (relative to the pwd)
TOM_MODELS_DIR-Default models path for the make:model command, can be an absolute or relative path (to the pwd).
Default value: database/models (relative to the pwd)
TOM_SEEDERS_DIR-Default seeders path for the make:seeder command, can be an absolute or relative path (to the pwd).
Default value: database/seeders (relative to the pwd)
VERBOSE_CONFIGUREOFFShow information about PACKAGES_FOUND / PACKAGES_NOT_FOUND in the CMake configure output.

Advanced TinyORM options.

Option NameDefaultDescription
DISABLE_THREAD_LOCALOFFRemove all thread_local storage duration specifiers, it disables multi-threading support.
MATCH_EQUAL_EXPORTED_BUILDTREEOFFExported package configuration from the build tree is considered to match only when the build type of application/library that is linking against the TinyORM library is equal.
Available when:
CMAKE_EXPORT_PACKAGE_REGISTRY AND NOT TINY_IS_MULTI_CONFIG

Important CMake options.

Option NameDefaultDescription
CMAKE_DISABLE_PRECOMPILE_HEADERSOFFDisable precompiled headers.
CMAKE_CXX_COMPILERautoThe full path to the C++ compiler.
CMAKE_CXX_COMPILER_LAUNCHER-Default compiler launcher to use for the C++ compiler.
Can be used to enable ccache, eg. ccache.exe on MinGW or /usr/bin/ccache on Linux.
CMAKE_EXPORT_PACKAGE_REGISTRYOFFEnable the export(TinyOrm) command.
TinyORM doesn't set this variable by default. Its initial value is taken from the TINYORM_EXPORT_PACKAGE_REGISTRY environment variable if not already defined.
CMAKE_INTERPROCEDURAL_OPTIMIZATIONOFFEnable Link time code optimization (LTO).
Works on all Supported Compilers.
CMAKE_VERBOSE_MAKEFILEOFFEnable verbose output from Makefile builds.

CMake build environment variables​

The following are environment variables that are affecting the TinyORM CMake build system.

These environment variables have lower priority than CMake -D compile definitions and they are used if the -D compile definitions are not DEFINED.

Option NameDescription
TINYORM_EXPORT_PACKAGE_REGISTRYEnvironment variable for CMAKE_EXPORT_PACKAGE_REGISTRY.
Used if: NOT DEFINED CMAKE_EXPORT_PACKAGE_REGISTRY
TINYORM_STRICT_MODEEnvironment variable for STRICT_MODE CMake feature option.
It's passed as the initial value [value] for the CMake option command.
VCPKG_ROOTAuto-detect the CMAKE_TOOLCHAIN_FILE from the VCPKG_ROOT environment variable.
Used if: NOT DEFINED CMAKE_TOOLCHAIN_FILE
VCPKG_INSTALLATION_ROOTAuto-detect the CMAKE_TOOLCHAIN_FILE from the VCPKG_INSTALLATION_ROOT environment variable. The VCPKG_INSTALLATION_ROOT environment variable is set on GitHub hosted runners.
Used if: NOT DEFINED CMAKE_TOOLCHAIN_FILE
VCPKG_DEFAULT_TRIPLETDefault value for the VCPKG_TARGET_TRIPLET.
Used if: NOT DEFINED VCPKG_TARGET_TRIPLET

Consume TinyOrm library (cmake)​

In your application or library CMakeLists.txt file add following find_package() call.

CMakeLists.txt
find_package(TinyOrm 0.38.1 CONFIG REQUIRED)

If the TinyORM build tree is not exported to the CMake's User Package Registry then also add the TinyORM build tree or CMAKE_INSTALL_PREFIX folder to the CMAKE_PREFIX_PATH, so CMake can find TinyORM's package configuration file during find_package(TinyOrm) call.

# build tree
list(APPEND CMAKE_PREFIX_PATH "/TinyORM/TinyORM-builds-cmake/build-debug")

# installation folder - CMAKE_INSTALL_PREFIX
list(APPEND CMAKE_PREFIX_PATH "/tmp/TinyORM")

Or as an alternative, you can set CMAKE_PREFIX_PATH environment variable.

As the last thing, do not forget to add TinyOrm0d.dll on the path on Windows and on the LD_LIBRARY_PATH on Linux, so your application can find it during execution.

$env:Path = "\TinyORM\TinyORM-builds-cmake\build-debug;" + $env:Path

Now you can try the HelloWorld CMake example.

info

You can also try the FetchContent method to quickly link against the TinyORM library.

Building with qmake​

First, create a basic folder structure and then clone the TinyORM project.

cd 
mkdir /TinyORM/TinyORM-builds-qmake

cd /TinyORM
git clone git@github.com:silverqx/TinyORM.git

Install dependencies​

With the qmake build system, you have to install TinyORM dependencies manually. We will use the vcpkg package manager.

cd ../../vcpkg

vcpkg search range-v3
vcpkg search tabulate
vcpkg install range-v3 tabulate
vcpkg list

On Linux, you can install the range-v3 library and some other dependencies with the package manager.

Configure & Build (qmake)​

Open QtCreator IDE​

tip

I recommend creating a new Session in the QtCreator, this way you will have all the examples in one place and as a bonus, everything will be in the same place when you close and reopen QtCreator IDE. You can name it tinyorm.org or TinyORM examples, it is up to you.

tip

If you are using sessions, you can use a single clangd instance for all projects in this session in the QtCreator IDE. One significant advantage of this method is that the .qtc_clangd/ folder will not be created in the build folder, but will be stored globally in the Roaming profile. You can enable it in the Settings - C++ - Clangd - Sessions with a single clangd instance.

Configure TinyORM​

Now you are ready to configure the TinyORM library. There are two ways how to configure the TinyORM library and it's the new Auto-configure feature added in TinyORM v0.34.0 using the .env files and the old way using the conf.pri files.

Auto-configuration and tiny_dotenv​

This is the new recommended method to auto-configure TinyORM's qmake build system and also the dependencies, it was added in TinyORM v0.34.0. You need to copy the prepared .env.(win32|unix|mingw).example file to the .env.(win32|unix|mingw). One .env example file is prepared for each supported platform.

All prepared .env.(win32|unix|mingw).example files are simple and clear. You can also create a common .env file that is included before the platform-specific .env.(win32|unix|mingw) files.

cd /TinyORM/TinyORM

cp .env.win32.example .env.win32

And that is all, if you have correctly set all qmake variables in this .env.(win32|unix|mingw) file or you have correctly set environment variables, then the qmake build system should be able to auto-detect all dependencies . 🔥

info

The Auto-configuration and Environment files internals are described at the end to make this section more clear.

tip

The Auto-configuration feature can be turned off using the disable_autoconf qmake configuration option (eg. CONFIG*=disable_autoconf).

tip

The tiny_dotenv feature can be turned off using the disable_dotenv qmake configuration option (eg. CONFIG*=disable_dotenv).

Manual configuration (conf.pri)​

This is the old method used before TinyORM v0.34.0. You need to copy the conf.pri.example files to conf.pri (there are four, one for every project or sub-project) and manually update the INCLUDEPATH and LIBS to configure TinyORM's qmake build dependencies. This way you can override any qmake build options or variables.

To disable the Auto-configuration feature you must define the disable_autoconf qmake configuration option (eg. CONFIG*=disable_autoconf) because from TinyORM v0.34.0 is the Auto-configuration feature enabled by default.

You can also remove all .env files or turn off the tiny_dotenv feature using CONFIG*=disable_dotenv. You can use them all at once if you want, .env and also conf.pri files.

conf.pri files are nicely commented on, so you can see what needs to be modified.

cd /TinyORM/TinyORM

cp conf.pri.example conf.pri
cp tests/conf.pri.example tests/conf.pri
cp tests/testdata_tom/conf.pri.example tests/testdata_tom/conf.pri
cp examples/tom/conf.pri.example examples/tom/conf.pri
info

The Manual configuration internals are described at the end to make this section more clear.

note

The Manual configuration is still relevant if you have any non-standard installation of the vcpkg or MySQL and the Auto-configuration feature fails.

Opening TinyORM.pro (main project file)​

Now you can open the TinyORM.pro project in the QtCreator IDE.

This will open the Configure Project tab, select some kit and update build folder paths to meet our folders structure or like you want.

TinyORM - QtCreator - Configure Project
tip

You can force the QtCreator to generate a build folders structure as is described above.

You are ready to configure build options, hit Ctrl+5 to open Project Settings tab and select Build in the left sidebar to open the Build Settings, it should look similar to the following picture.

Disable QML debugging and profiling and Qt Quick Compiler, they are not used.

TinyORM - QtCreator - Build Settings

If you want to change some TinyORM build options, you can pass them to the Build Steps - qmake TinyORM.pro - Additional arguments input field. It can look like this.

TinyORM - QtCreator - Build Settings - Additional arguments

Build TinyORM​

Everything is ready for build, you can press Ctrl+b to build the project.

qmake build options​

CONFIG Option NameDefaultDescription
build_loadable_driversOFFBuild TinyDrivers as a shared library and SQL database drivers (eg. TinyMySql) as shared libraries (Loadable modules) that are loaded at runtime using LoadLibrary() on Windows or dlopen() on Linux.
build_mysql_driverOFFBuild TinyDrivers MySQL database driver.
It's enabled by default when build_shared_drivers, build_loadable_drivers, or build_static_drivers is enabled.
Available when: build_shared_drivers OR build_loadable_drivers OR build_static_drivers
build_shared_driversOFFBuild TinyDrivers as a Shared library.
build_static_driversOFFBuild TinyDrivers as a Static library archive.
The build_static_drivers qmake configuration option will be select by default when the CONFIG*=static is enabled.
build_testsOFFBuild TinyORM unit tests.
ccacheONEnable compiler cache. Homepage
It works on Windows and Unix systems. This option overrides qmake's ccache option. It internally calls qmake's ccache option on Unix and tiny_ccache_win32 on Windows.
Reason: It allows using the same option on both OS-es.
See Ccache support for more information.
disable_autoconfOFFDisable the Auto-configuration feature (auto-configuration is enabled by default from TinyORM v0.34.0).
disable_dotenvOFFDisable the tiny_dotenv feature (environment files are enabled by default from TinyORM v0.34.0).
disable_thread_localOFFRemove all thread_local storage duration specifiers, it disables multi-threading support.
disable_ormOFFControls the compilation of all ORM-related source code, when this option is enabled, then only the query builder without ORM is compiled. Also excludes ORM-related unit tests.
disable_tomOFFControls the compilation of all Tom-related source code, when this option is disabled, then it also excludes Tom-related unit tests.
extern_constantsONUse extern constants instead of inline constants in the shared build.
ON is highly recommended for the shared build (by default);
is always OFF for the static build.
Available when: CONFIG(shared|dll):!inline_constants
inline_constantsOFFUse inline constants instead of extern constants in the shared build.
OFF is highly recommended for the shared build;
is always ON for the static build.
mysql_pingOFFEnable Orm::MySqlConnection::pingDatabase() method.
tiny_ccache_win32ONEnable compiler cache. Homepage
It works only on Windows systems. It works well with the MSYS2 g++, clang++, msvc, and clang-cl with msvc. It replaces the -Zi and -ZI compiler options with the -Z7 for debug builds as the -Zi and -ZI compiler options are not supported (link to the issue) and disables precompile_header if ccache <4.10 as they are not supported on Windows.
tom_exampleOFFBuild the tom console application example.

Advanced TinyORM options.

Option NameDefaultDescription
ubsanOFFAllows to enable UBSan sanitizer (Clang only)
Defines: TINYORM_USING_UBSAN

Important qmake options.

CONFIG Option NameDefaultDescription
ccacheOFFEnable compiler cache. Homepage
It works only on the Unix systems. It works well with g++ and clang++ and also supports precompiled headers. TinyORM overrides this qmake option with the ccache option.
See Ccache support for more information.
ltcgOFFEnable Link time code optimization (LTO).
Works on all Supported Compilers.
precompile_header-Enable precompiled headers, you can disable them with:
CONFIG-=precompile_header.
The precompile_header is enabled by default on msvc, g++, clang++, clang-cl on Windows and disabled by default on linux.
static
staticlib		OFFBuild as a static library (lib only).
If you want to build all libraries in the TinyORM project as static library archives and link against static libraries use the CONFIG += static. Don't use the CONFIG += staticlib.
See NOTES.txt for more information (search static vs staticlib).
static_runtimeOFFLink against the shared (dynamic) or static run-time library.
The -MD becomes -MT and -MDd becomes -MTd. It works only on MSVC and MinGW or MSYS2.
Please don't use this option.
Available when: msvc or mingw

Consume TinyOrm library (qmake)​

The TinyOrm.pri file is available to simplify the integration of the TinyORM library into your application. It sets up and configures the CONFIG and DEFINES qmake variables, adds the TinyORM, tom, and vcpkg header files on the system INCLUDEPATH (cross-platform using the -isystem or -imsvc), links against the TinyORM shared or static library using the LIBS.

You can use it to configure the TinyORM library when you are linking against it. It does a very similar thing like the CMake's Find Modules feature.

Requirements​

It has a few requirements, you need to:

  • specify path to the TinyORM qmake features (.prf files) using the QMAKEFEATURES variable that can only be set in the .qmake.conf file
  • specify qmake or environment variables to find the vcpkg installation (TINY_VCPKG_ROOT and TINY_VCPKG_TRIPLET)
  • specify path to the TinyORM build folder (TINYORM_BUILD_TREE)
  • build your application with the same CONFIG qmake variables that were used when building the TinyORM library

Let's explain one by one.

QMAKEFEATURES​

Create the .qmake.conf file in your application root folder with the following content.

.qmake.conf
# Path to the PARENT folder of the TinyORM source folder
TINY_MAIN_DIR = $$clean_path(<your_path>)
# To find .env and .env.$$QMAKE_PLATFORM files in YOUR project
TINY_DOTENV_ROOT = $$PWD

# Path to the TinyORM build folder (specified manually)
TINYORM_BUILD_TREE = $$quote($$TINY_MAIN_DIR/TinyORM-builds-qmake/build-TinyORM-Desktop_Qt_6_7_2_MSVC2019_64bit-Debug/)
# vcpkg - range-v3 and tabulate
TINY_VCPKG_ROOT = $$quote(<your_path>/vcpkg/)
#TINY_VCPKG_TRIPLET = x64-windows

# To find .prf files, needed by eg. CONFIG += tiny_system_headers inline/extern_constants
QMAKEFEATURES *= $$quote($$TINY_MAIN_DIR/TinyORM/qmake/features)

You can move all qmake variables that are part of the qmake configuration process to the .env file if you want (recommended), this is possible because the TinyOrm.pri enables the Environment files feature by default.

You can look at the Auto-configure using .qmake.conf and .env example for Hello world project of what must stay in the qmake.conf file and what can be moved to the .env files.

tip

You can use the Partial guessing of the TINYORM_BUILD_TREE if you don't like to specify it manually.

Variables affecting TinyOrm.pri​

You must define the following variables before the TinyOrm.pri is included:

Variable NameDescription
TINYORM_BUILD_TREEPath to the TinyORM build folder.
TINY_VCPKG_ROOTPath to the vcpkg installation folder.
If not defined, then it tries to use the VCPKG_ROOT environment variable.
TINY_VCPKG_TRIPLETThe vcpkg triplet to use (vcpkg/installed/$$TINY_VCPKG_TRIPLET/).
If not defined, then it tries to guess the vcpkg triplet based on the current compiler and OS (based on the QMAKESPEC), and as the last thing, it tries to use the VCPKG_DEFAULT_TRIPLET environment variable.

These variables will be set after the configuration is done:

Variable NameDescription
TINY_BUILD_SUBFOLDERFolder by release type if CONFIG+=debug_and_release is defined (/debug, /release, or an empty string).
TINY_CCACHE_BUILDTo correctly link ccache build against a ccache build (_ccache or an empty string).
TINY_MSVC_VERSIONThe MSVC compiler string (MSVC2022 or MSVC2019).
TINY_QT_VERSION_UNDERSCOREDUnderscored Qt version (eg. 6_7_2).
TINY_RELEASE_TYPE_CAMELBuild type string (Debug, Profile, or Release).
TINY_VCPKG_INCLUDEPath to the vcpkg include folder (vcpkg/installed/<triplet>/include/).

Then you simply include the TinyOrm.pri in your project file.

AnyProject.pro
include($$TINY_MAIN_DIR/TinyORM/qmake/TinyOrm.pri)

And that is all, now you should be able to link against the TinyORM library. 👌

Manual configuration examples​

Frankly, there is no reason to use the Manual configuration (define the variables described below before the TinyOrm.pri inclusion), the only reason to use it is when you want more control over this process or want to define everything yourself. I'll leave this section here to show how things work.

You will have to link against the TinyORM library manually if you don't set the TINYORM_BUILD_TREE qmake variable before the inclusion of the TinyOrm.pri file. The INCLUDEPATH is auto-detected every time.

# Link against TinyORM library
# ---
TINY_MAIN_DIR = $$clean_path(<your_path>)

# Configure TinyORM library
include($$TINY_MAIN_DIR/TinyORM/qmake/TinyOrm.pri)

# TinyORM library path
TINYORM_BUILD_TREE = $$quote($$TINY_MAIN_DIR/TinyORM-builds-qmake)
LIBS += $$quote(-L$$TINYORM_BUILD_TREE/build-TinyORM-Desktop_Qt_6_7_2_MSVC2019_64bit-Debug/src$${TINY_BUILD_SUBFOLDER}/)
LIBS += -lTinyOrm

The same is true for the vcpkg include path. If you don't set the TINY_VCPKG_ROOT or have not defined the VCPKG_ROOT environment variable, then you need to set up the INCLUDEPATH for the vcpkg that provides the range-v3 and tabulate header files.

# vcpkg - range-v3 and tabulate
# ---
INCLUDEPATH += $$quote(<your_path>/vcpkg/installed/x64-windows/include/)

You can also use TinyORM's qmake function tiny_add_system_includepath() which handles INCLUDEPATH in a cross-platform way.

# vcpkg - range-v3 and tabulate
# ---
load(private/tiny_system_includepath)
tiny_add_system_includepath(<your_path>/vcpkg/installed/x64-linux/include/)

Do not forget to add TinyOrm0.dll on the path on Windows and on the LD_LIBRARY_PATH on Linux, so your application can find it during execution.

$env:Path = "\TinyORM\TinyORM-builds-qmake\build-debug;" + $env:Path
tip

On Linux -isystem marks the directory as a system directory, it prevents warnings.

On Windows you can use QMAKE_CXXFLAGS_WARN_ON = -external:anglebrackets -external:W0, it applies a warning level 0 to the angel bracket includes; #include <file>.

With the Clang-cl with MSVC you can use -imsvc.

Auto-configuration internals​

The qmake build system does not support auto-configuration of dependencies out of the box but TinyORM from v0.34.0 added its own Auto-configuration feature along with the tiny_dotenv qmake feature. These new features allow us to auto-configure TinyORM project, and with their help, the conf.pri files can be skipped entirely.

While it adds additional complexity to the qmake configuration process, the benefits are significant.

The Auto-configuration feature is designed to find the vcpkg and MySQL installations, and tiny_dotenv to include the .env and .env.(win32|unix|mingw) files in the project's root folder. These new features can be configured using qmake and environment variables, and they also contain some guessing logic if these variables are not defined.

The Auto-configuration feature can be turned off using the disable_autoconf qmake configuration option (eg. CONFIG*=disable_autoconf).

These are qmake and environment variables that affect the Auto-configuration feature:

Variable NameDescription
TINY_VCPKG_ROOTPath to the vcpkg installation folder.
If not defined, then it tries to use the VCPKG_ROOT environment variable.
TINY_VCPKG_TRIPLETThe vcpkg triplet to use (vcpkg/installed/$$TINY_VCPKG_TRIPLET/).
If not defined, then it tries to guess the vcpkg triplet based on the current compiler and OS (based on the QMAKESPEC), and as the last thing, it tries to use the VCPKG_DEFAULT_TRIPLET environment variable.
TINY_MYSQL_ROOTPath to the MySQL installation folder.
If not defined, then it tries to guess the MySQL installation folder (win32 only): $$(ProgramFiles)/MySQL/MySQL Server (9.1|9.0|8.4|8.3|8.2|8.1|8.0|5.7)/

You can set these variables in the .env (recommended) or conf.pri files, in the .qmake.conf file (or wherever you want), or as environment variables.

These variables will be set after auto-configuration is done:

Variable NameDescription
TINY_VCPKG_INCLUDEPath to the vcpkg include folder (vcpkg/installed/<triplet>/include/).
TINY_MYSQL_INCLUDEPath to the MySQL include folder (MySQL Server 9.1/include/).
TINY_MYSQL_LIBPath to the MySQL lib folder (MySQL Server 9.1/lib/).

The TINY_MYSQL_INCLUDE and TINY_MYSQL_LIB are only set on win32 platform except mingw.

Environment files​

The tiny_dotenv feature allows us to define the .env and .env.$$TINY_DOTENV_PLATFORM files in the project's root folder. These files are loaded as early as possible so you can affect the qmake configuration process. On the other hand, the conf.pri files are loaded as late as possible, and they can be used to override the qmake configuration.

The .env file is included first and is included on all platforms.

There is only one requirement for this feature to work correctly, and that is to set the TINY_DOTENV_ROOT qmake variable to the project's root folder. This variable is already set in the .qmake.conf file for the TinyORM project.

Then the following names are taken into account: .env, .env.win32, .env.unix, .env.mingw

.qmake.conf
# To find .env and .env.$$QMAKE_PLATFORM files
TINY_DOTENV_ROOT = $$PWD

The tiny_dotenv feature can be turned off using the disable_dotenv qmake configuration option (eg. CONFIG*=disable_dotenv).

warning

Environment files don't work in the CMake builds.

Partial guessing of the TINYORM_BUILD_TREE​

You don't have to manually define the TINYORM_BUILD_TREE in .env or .qmake.conf files. The TINYORM_BUILD_TREE absolute path can be put together for you (this is happening inside the variables.pri file) and TinyORM build folder name can be guessed for you too.

You must define the following variables before the TinyOrm.pri will be included to make this real (set them in the .qmake.conf):

Variable NameDescription
TINY_MAIN_DIRPath to the PARENT folder of the TinyORM source folder.
TINY_BUILD_TREEPath to the current build tree - TINY_BUILD_TREE = $$shadowed($$PWD).

The TINY_MAIN_DIR is required for another features anyway (so it should already be set) and all that's left is to set the TINY_BUILD_TREE.

.qmake.conf
# Path to the current build tree (used to guess the TinyORM build tree)
TINY_BUILD_TREE = $$shadowed($$PWD)

If you will follow this pattern or logic then you can switch QtCreator Kits and the TINYORM_BUILD_TREE will be auto-generated correctly and will always point to the correct TinyORM build tree.

It works this way, all is happening inside the variables.pri, it takes a build folder name for the current project eg. build-HelloWorld-Desktop_Qt_6_7_2_MSVC2022_64bit-Debug, replaces the HelloWorld with the TinyORM and as we already know the TinyORM build folder location we can simply concatenate these paths like $$TINY_MAIN_DIR/TinyORM-builds-qmake/build-TinyORM-Desktop_Qt_6_7_2_MSVC2022_64bit-Debug.

warning

This will only work if you follow the recommended Folders structure.

Manual configuration internals​

There is not much to say about the Manual configuration feature. It uses conf.pri files (there are four, one for every project or sub-project), and every project has prepared its own conf.pri.example file for faster initial configuration.

These conf.pri.example files are nicely commented on, so you can see what needs to be modified. The conf.pri files are loaded as late as possible, and they can be used to override the qmake configuration.

If the Auto-configuration feature is disabled and there are no conf.pri files, then the TinyORM qmake configuration or build will fail at 100%.

These conf.pri files are intended for configuring qmake's INCLUDEPATH and LIBS, CONFIG or eg. QMAKE_LFLAGS, or any other qmake options or variables.

Ccache support​

The TinyORM supports the ccache out of the box for all supported compilers. For qmake you can enable it using the CONFIG+=ccache and for CMake you can set the CMAKE_CXX_COMPILER_LAUNCHER=ccache.

On Linux it's clear, the ccache is fully supported and works also with the precompiled headers. But was necessary to add some workarounds to the qmake/CMake build systems to make out of the box support on Windows. When you enable the ccache on Windows then the build system replaces the -Zi and -ZI compiler options with the -Z7 (link to the issue) and disables precompiled headers if ccache <4.10.

tip

You can install the ccache using the scoop install ccache command on Windows. See the Dependencies page for how to install ccache on Linux.