Redistributable builds

Introduction

If a binary runs on a different machine depends on a lot of factors. The following sections provide some tips to maximize portability. In general Windows binaries are more portable than *nix binaries.

CPU Architecture Optimization

Default compiler flags

/favor:blend: Optimizes for AMD and Intel architectures, see MSDN docs
/arch:sse2 on 32-bit, /arch undefined on 64-bit

Optimization CMake options

OGS_CPU_ARCHITECTURE: possible values AMD64 or INTEL64 (sets /favor:{AMD64 | INTEL64} flag)

Default compiler flags

-march=native: Optimizes for current CPU

CMake options

For redistribution

OGS_CPU_ARCHITECTURE: set to generic for good balance between optimization and portability; set to core2 for maximum portability, more info on GCC docs

For optimization

OGS_CPU_ARCHITECTURE: tot to native for best optimization for your current CPU, possible values are listed here, more info on GCC docs

See Linux-tab!

Package the build

Use the package-target which tries to gather all dependencies and fixes up shared library paths:

make package

This creates a zip- or tar-archive which should be redistributable.

This article was written by Lars Bilke. If you are missing something or you find an error please let us know.
Generated with Hugo 0.147.9 in CI job 638941 | Last revision: October 9, 2025
Commit: [web] Fix a few ms docs links. a3833a6 | Edit this page on