https://github.com/secondlife/build-variables
Common variables, such as compiler flags, for building Second Life and its dependencies
https://github.com/secondlife/build-variables
Last synced: 5 months ago
JSON representation
Common variables, such as compiler flags, for building Second Life and its dependencies
- Host: GitHub
- URL: https://github.com/secondlife/build-variables
- Owner: secondlife
- Created: 2022-08-30T18:32:47.000Z (almost 4 years ago)
- Default Branch: master
- Last Pushed: 2025-09-18T20:44:18.000Z (9 months ago)
- Last Synced: 2025-09-18T22:58:23.778Z (9 months ago)
- Homepage:
- Size: 31.3 KB
- Stars: 0
- Watchers: 4
- Forks: 5
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Overview
This repository is intended to centralize string data common to many viewer builds
(such as required compiler switches), both internal to Linden and external, on
TeamCity and on individual dev machines.
# Bash Usage
Intended usage is to clone this repository as a sibling to the source
directory being built, then use the bash "source" or "." commands to read
`../build-variables/convenience` into your build script. This gives you
shell variables such as
LL_BUILD_RELEASE, LL_BUILD_RELWITHDEBINFO, LL_BUILD_DEBUG
which are aliases for the platform-specific variables (e.g.)
LL_BUILD_LINUX_RELEASE, LL_BUILD_LINUX_RELWITHDEBINFO, LL_BUILD_LINUX_DEBUG
et al.
If you pass a build-type argument (`Release`, `RelWithDebInfo`, `Debug`) when
sourcing the [convenience](convenience) script, e.g.:
source ../build-variables/convenience Release
then you get the additional alias `LL_BUILD`, which (in the example above,
assuming you're running on Linux) is the same as `LL_BUILD_LINUX_RELEASE`.
The [`functions`](functions) script (also sourced by [`convenience`](convenience)) provides bash functions
for removing or replacing individual switches from any one of those variables.
See the comments in the script for function usage.
# Other Languages
## Variable Suite
The [convenience](convenience) script sources the [variables](variables) script, which provides the
underlying suite of variables. Variable names are of the form:
LL_BUILD_{platform}_{buildtype}
where:
component | meaning
----------|--------
platform | `WINDOWS`, `DARWIN`, `LINUX`.
buildtype | `RELEASE`, `RELWITHDEBINFO`, `DEBUG`. `BASE` for switches common to all.
These variables are in turn composed of variables that separate out
command-line macro definitions from other kinds of compiler switches:
LL_BUILD_{platform}_{buildtype}_{category}
where:
component | meaning
----------|--------
category | `MACROS`, `SWITCHES`.
These are typically aggregated into the corresponding
`LL_BUILD_{platform}_{buildtype}` variables:
LL_BUILD_LINUX_RELEASE="$LL_BUILD_LINUX_RELEASE_SWITCHES $LL_BUILD_LINUX_RELEASE_MACROS"
CMake, in particular, distinguishes between macro definitions
([add_definitions()](https://cmake.org/cmake/help/v3.1/command/add_definitions.html))
and other compiler switches
([add_compile_options()](https://cmake.org/cmake/help/v3.1/command/add_compile_options.html)),
so it may be useful to populate those CMake commands from the underlying
`_MACROS` and `_SWITCHES` variables.
## Parsing the variables file
The variables file should be kept as simple as possible to parse, so it can be
read from other languages than bash. Refer to the comments in that file itself
for syntax rules.